qrobur2 wrote:I still have this problem - that is, the autosync crashing at various points during the on-the-fly conversion and synchronisation of 36K+ tracks to my iPod classic. It did this at anything between a few hundred tracks and several thousand tracks. However, it never got anywhere near the full 36K and MM is next to useless for maintaining this iPod because after numerous autosyncs I seem to be left with database corruptions.
I was able to sync the iPod with all 36K tracks using foobar2000 - but it took 8 days! However, it's curious that the latter program can do what MM can't.
I have two questions:
- Can I "fool" MM into accepting the tracks put on the device by foobar2000 as its own work? If I try to autosync now MM wants to either wipe them off or append the 36K tracks again.
- What is used to do the autosyncing and can it be updated or replaced?
qrobur2 wrote:Thanks for the reply, nohitter151.
So, the list of what is synchronised to a device is not maintained in a table to which data could be appended by means of an SQL query? Pity.
Regarding the second question, I'm wondering if the problem is a corrupt component in the conversion or transfer process that could be replaced. If foobar2000 (which I pointed at the Lame encoder for the 'on-the-fly' conversion) can successfully transfer, albeit very slowly, 36K files in principle so should MM because it doesn't appear to be a problem with the iPod in question. The implication is that there's a defect in the MM system somewhere and it would be worth replacing any physical items (dll files? encoders?) to see if that cures the problem.
Users browsing this forum: No registered users and 9 guests