Never give up! Never surrender!
I like solving problems. I learn more doing that than just using the software. Of course, sometimes I know just enough to be very dangerous.
On the forum issues:
Good that you found the Preview buttons.
There is a "handle" in the middle button of the typing window, which looks like two additional horizontal lines. Hover over that with the mouse and you will see that the cursor change to a double-ended vertical arrow. While that shows, click and drag the bottom of the window down to make it bigger.
There is no way to just quote a portion of a reply directly. The "Quote" button (top right corner of a post) always quotes the full text. What I do is keep the original thread open on one browser tab, so that I can read it and still see attached images. Then I have another Reply tab open that I am typing in. In fact, as I have a large high-resolution screen, I often have two windows open side by side, one with the original post and one with the reply window I am typing in.
Then if I want to quote a small portion of a large post, I Ctrl+left-click on the "Quote" button in the original thread, which opens another tab with the full text of the post quoted. Then I edit that quoted text down to what I want, copy it, and paste it into the window where I am typing my reply. I have some other tricks, but I would need to make a video to show those rather than try to explain them.
Try the above ideas though. You will find them much easier than using Word to edit quotes, and a larger reply window makes a world of difference.
=================================================================
Now, on to this issue.
I should have thought that yes, you will need to also correct file paths which have special characters. When I said it was only the file name that has issues with special characters, I meant in comparison to the other tags in the file, such as the [Name], [Artist] and [Album] fields. I was just working with your sample files, so forgot to think about the paths you use.
It looks like your "Base Path" is now "D:\Music\My Music\" on the Windows 7 PC, and that your directory rule should be:
[Album Artist (auto)]\[Album]\
You may have just used [Artist] or [Album Artist] as the first part of that expression in the past, but [Album Artist (auto)] is better and prevents Albums being broken up in MC due to multiple Artists on one or more tracks. But this comes down to the accuracy of the metadata in your Library. I did notice that for the track named "El Huracán"
[Artist] is "Alfredo De Angelis"
[Album Artist] is "El Húracan"
[Album Artist (auto)] is "El Húracan", since it follows [Album Artist] when it exists. I think that is wrong, and the track should be under Artist "Alfredo De Angelis".
If that is so, and your library is set up that way for most music, you might want to use the expression:
[Artist]\[Album]\
Whichever way you go, test with small numbers of files, and check the Preview before committing the change.Again, taking into account the comments above for the directory structure you use for all music, you can use the RM&CF function to move the files to a new directory with a path that works. I can't test this, as I don't have your broken paths. Any path I create works fine.
The files reverting to unplayable a short time after you did the file name change may not be an issue. What I expect happened there is that MC did the file name change, marked the track as playable because it had just updated the file, and then checked it again and noted the issue with the file path, so marked it unplayable again.
Once you fix both the path and file name, with a sample on files, refresh the View and then check that the files remain playable. Also, check using the "Locate > On Disk (external)" function for a few files to confirm that the files are found correctly.
Be careful not to process all the file at once without testing first, as your Library could become a real mess if files are moved to paths they should be in.
Give the above a go, and report back.
PS: The renaming of the files using the expression above should remove the " (1)" suffix from files. It will only be a problem if a duplicate file without the suffix exists. So, this will be fixed in MC. You could run the same process on the Mac, within MC, to fix them there.
PPS: I see you have worked out the Jirón Porteño file issue. I noticed at least one issue of that type in one of your earlier screenshots.
We
are working on the Windows 7 PC currently, and not the Mac. Right? What is happening in Finder doesn't matter, except for comparison of changes you have made to the original files.
PPPS: When this is fixed on the Windows 7 PC, I would Backup and Restore a Library from W7 to W10, and copy the files from W7 to W10. Alternately, you could run the same fixes on W10. From what you have said, W10 is the primary computer, the Mac is the secondary, and the W7 will be retired. Stick to the plan to fix W10 after testing/learning on W7.
PPPPS: It is a bit of a worry if after the rename files in Windows Explorer have a " (1)" suffix, but in MC they do not. However, once all other issues are fixed, only those files should remain unplayable, so we can easily add the " (1)" suffix back in only in MC using the "Update database to point to new location" mode of RM&CF, and then the Explorer and MC should match, and then you could rename them to remove the suffix in MC and on Windows. Simple, huh?
Carry on!