by Ludek » Fri Apr 23, 2021 4:46 am
OK, I see three logs 19F86866 here, all three are from user sergio79 (two from 2338 and one from 2336). So not sure whether Sergio is you?
Anyhow the issue is a little bit tricky to replicate as it appears only when there is at least 100 "unpaired" tracks.
The initial pairing process between MMA and MM5 happens typicaly when MM5 instance is changed.
So in scenario like this:
- having 150 track in MMA
- clean install of 2236 (or deleted MM5.DB so that it creates fresh empty library)
- wifi-sync to force pairing the tracks
=> first batch of 100 tracks is paired correctly
=> it crashes on the second batch and thus leaving 50 tracks unpaired
- restart MM5 and sync again
=> no crash as the remaining 50 songs has been paired in the first batch
So if you have e.g. 320 unpaired track then MM5 (2336-2338) will crash three times for you, then the Wi-Fi sync will start to work.
OK, I see three logs 19F86866 here, all three are from user sergio79 (two from 2338 and one from 2336). So not sure whether Sergio is you?
Anyhow the issue is a little bit tricky to replicate as it appears only when there is at least 100 "unpaired" tracks.
The initial pairing process between MMA and MM5 happens typicaly when MM5 instance is changed.
So in scenario like this:
- having 150 track in MMA
- clean install of 2236 (or deleted MM5.DB so that it creates fresh empty library)
- wifi-sync to force pairing the tracks
=> first batch of 100 tracks is paired correctly
=> it crashes on the second batch and thus leaving 50 tracks unpaired
- restart MM5 and sync again
=> no crash as the remaining 50 songs has been paired in the first batch
So if you have e.g. 320 unpaired track then MM5 (2336-2338) will crash three times for you, then the Wi-Fi sync will start to work.