After discussing this briefly with @bob (Thanks!), his advice was to put it in the Windows section (so that it gets the most attention), as it affects all versions/OS.
During evaluation of MC27 on a MacBook of a family member (for camera photos and videos only, to get rid of whatever Apple calls its own implementation), I saw several issues during import, and I could reproduce them under Windows and Linux (Debian).
For some files, mostly videos, MC27 will do strange stuff...
- It'll use parts of the filename to fill the date field (which isn't empty for the actual file...). This, I had to correct manually, and was a lot of work (going back top each file, check the date, and correct the library).
- It'll just truncate the filename for the name field. This forced me to use "Name: FileName(,0)" on import (it worked, as far as I can tell).
- It'll use parts of the filename to come up with some fictional Season/Episode naming for the file and assign media sub type "TV Show". In the screenshot, I had already corrected this, so that the file shows up in the view I used to show another issue... This is also mitigated by using "Name: FileName(,0)" on import.
- It'll also ignore the date meta data of the actual file (same screenshot). This also requires manual work see first bullet point).
- It'll therefore also ignore the "Album: Left([Date],10)" I apply on import to get the home video files grouped as the images are by default (would be cool, if these would be treated the same way as the images are, so they are automatically grouped). You'll note that the Album field is empty
All files are on a server, and accessed via SMB/CIFS (read only). The imports are done with a blank, completely unmodified library (so, everything's "off the shelf").
Also, there are the other issues I'm seeing with the Views themselves having some issues (also unmodified, "off the shelf")...
https://yabb.jriver.com/interact/index.php/topic,129640.0.htmlThanks in advance for looking into this!
