Hi, I've never seen 'The operation has completed successfuly' error, sounds strange and also it doesn't look like native MM error.
Are you still able to reproduce it on the two files that fail to scan?
If yes, could you send us the files for analyze or at least generate debug log (item 4b here http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341 ) ?
No scripts added on to 1681 - for the debug trace, I literally installed it only to get the debug - in the portable mode (would that affect the scan?). And every time, it stops on those 2 files.
Then, during the install/1st start wizard interview, I selected the root of my music library (ie, it would scan all ~30,000 tracks), continuously, and then clicked through to 'Finish', and it started the scan - so it was in a very pristine state.
And I get the same result as you if I copy just the 2 files elsewhere, and scan *that* directory as part of the install: no error.
I just tried starting MM 1681 (ie not part of an install), and on the startup scan, I got the same 2 errors - not sure if it's the same songs or not, as the number is different (13599 vs 13465, 18709 vs 18568 - although is it going to always scan 30K files in the exact same order?), but MM isn't showing the song names it's scanning in the bottom of the window.
So I agree, this is weird....
Just guessing out loud - maybe the logging is at a slightly different place? IOW, what if the filename I'm seeing at the bottom of MM during the scan was the *last* song it successfully scanned, and it's during the reading of the *next* song that it fails, but doesn't make it to the "log current filename to the status bar" instruction? (meaning I identified and sent the wrong 2 files - but now have no way to figure out what song was being scanned next...)
Hmmmm....now it just froze while I was trying to find those 2 offending files - I'll try to recreate that and send later...
Environment:
MMW: ~25,000 tracks, MM.DB on 16Gbps PCIe SSD (Samsung 950 Pro) - up-to-date, not Beta
MMA: ~12,000 tracks sync'd to phone - up-to-date, not Beta
PC: Windows 10/64, Skylake quad+HT @4.2GHz, 64GB RAM, 14TB RAID6
Phone: Galaxy S10 (128GB) + 400GB mSD card (Samsung EVO+)
Sync: all tracks rated >=3 sync'd to phone
.........all playlists only use tracks rated >=3
.........thus sync'ing is 99.99% playlist update - no tracks are sync'd, other than new purchases
Playlists: ~59 synced
..........most are auto-playlists
..........use attributes Rating, Last Played, Date recorded, Genre, Genre "contains", Path "contains"
..........many are nested, i.e. "Top AutoPlaylist" includes "Level 2 AutoPL #1" + "Level 2 AutoPL #2" etc.
FYI this continues to happen on every startup of MM 4.1.0.1681 during the startup scan - I get two of these errors.
The only way to debug it further would be:
1) if the name of the file would appear in the error dialog box that pops up
2) display the names of the files being scanned at startup - both the LAST song scanned, and the one that is ABOUT to be scanned/scanning (and make it clear)
3) log the scan to a file, so that I can view it when the error dialogs pop up
Thanks
Environment:
MMW: ~25,000 tracks, MM.DB on 16Gbps PCIe SSD (Samsung 950 Pro) - up-to-date, not Beta
MMA: ~12,000 tracks sync'd to phone - up-to-date, not Beta
PC: Windows 10/64, Skylake quad+HT @4.2GHz, 64GB RAM, 14TB RAID6
Phone: Galaxy S10 (128GB) + 400GB mSD card (Samsung EVO+)
Sync: all tracks rated >=3 sync'd to phone
.........all playlists only use tracks rated >=3
.........thus sync'ing is 99.99% playlist update - no tracks are sync'd, other than new purchases
Playlists: ~59 synced
..........most are auto-playlists
..........use attributes Rating, Last Played, Date recorded, Genre, Genre "contains", Path "contains"
..........many are nested, i.e. "Top AutoPlaylist" includes "Level 2 AutoPL #1" + "Level 2 AutoPL #2" etc.
Yes, it is strange that it fails to scan those two files only when you scan all 30K tracks, it probably fails earlier on another file.
In the original scan log I saw these two files as failed to scan:
R:\Music\Amazon\Comedy\Spoken\AnsweringMachineMessages\talksam1.wav - error while reading file info
R:\Music\Amazon-0Process\0_Process\0-TryRecode\King's Singers - Oh Danny Boy.mp4 - error while reading file info
Analyze results:
talksam1.wav = It is not wav file but HTML file contain streaming file not found error. It is onlt 755 Bytes long You should redownload, delete or rename to "talksam1.html"
King's Singers - Oh Danny Boy.mp4 = is not MP4 file but actually MP3 file so you shold rename it to "King's Singers - Oh Danny Boy.mp3"
