Thanks for confirmation!

2526 works great! Thanks so much guys! Love MM!

FYI - I also tried the DLL on 5.0.1.XX (whatever the most recent regular/non beta release is). I got 2 ipods showing up and weird sync crash issues. 2526 fixed all of it. Thanks again.

Please download rather version 2526 instead which already includes the fix and the d_iPod.dll isn't needed anymore.

It's posted here: viewtopic.php?f=6&t=86639&sd=d
and let us know how 2526 works for you.

Thanks!

My music appears on MM v.5 (both in the library and on my device) but even after a sync there appears to be nothing on my iPod. It's been suggested on Apple forums that the database could be corrupt but the only fix I can find require iTunes. My iPod is currently syncing but MM v.5 tells me there's insufficient memory (I'm guessing it's adding my entire library again??)

It's actually really easy:
1) Download and install the debug version of MediaMonkey on top of your existing install (like any update): https://www.mediamonkey.com/beta/MediaM ... _Debug.exe
2) Download and run DebugView: http://technet.microsoft.com/en-us/sysi ... s/bb896647
3) Start MediaMonkey and reproduce the problem you're trying to capture
4) Once done, save log in DebugView and attach saved log to a Support Ticket

re: step 4b. . .
I can't read any of the words on that page!
LOL if i knew how to do step 4b, I'd be a Phd in engineering and i would fix the problem myself.
Anyway, i posted the complete, exact text of the error message. I don't see how attaching a screenshot will give you more information.

Also note that this DLL was for build 5.0.2.2524 (not any older).

If you are still experiencing crash then download 2524 debug , replace the DLL and the debug build will usually auto-generate crash log to submit. Submit it and write the log ID here (see item 4a here: viewtopic.php?f=30&t=86643 )

Please capture this in a debug log (step 4b) and attach the log to a Support Ticket: viewtopic.php?f=30&t=86643

This will allow a developer to analyze why this occurs in your setup.

So I tried syncing one folder, using the new .dll.
It worked fine!

But then when I tried to sync more folders, I got this error:

"APPLICATION ERROR: Application throw an exception Access violation at address 00406E5F in module 'MediaMonkeyEngine.exe'. Read of access 29CEA006. Would you like to restart mediamonkey in safe mode?"

I tried to restart in safe mode, but it made no difference. Not only will it not sync, but the small orange bar at the bottom of the screen? The one which shows the progress of files synced? That bar is frozen. I cannot terminate the process.

So, I still can't sync files.

Is this 'APPLICATION ERROR' message common and easy to fix? Is there some tutorial elsewhere on the forum?
Or is this error also part of the upgrade to 5?

Thanks, Ludek
I will give the new .dll a try.
Thanks for working on the problem.
MM has been my only music player for a decade and I really enjoy it, but it must be a lot of work to program and maintain it, so I'm grateful to all you guys.

Until 2525 is available you can just replace your current d_iPod.dll from 2524 by this one:
https://www.dropbox.com/s/j6eohfyfxgndh ... d.dll?dl=0
and it will does the trick.

This is set to be fixed in Build 2525, the latest available is currently 2524. Build 2525 still needs to be released.

Hello again, I did find the links to the unreleased Mediamonkey 5.0.2.2524 AND the debug.exe file.
I've installed both, and neither one helps. I don't know what else to do. . .

I am having the same problem.

Ipod classic, Windows 10, newest Mediamonkey version (1.2433) , and the newest Itunes version is on the pod.

Today all of a sudden, after my sync ended, I eject the pod and then look down - "no music."

I've been restarting the computer and trying it again and again, but no luck.

Like an idiot, I then plugged in my OTHER ipod classic, and now IT doesn't work either.
And yes, I can put music from Itunes onto the pods, no problem.

I was reading on this thread, that the issue had been fixed, but we have to wait until the next update for the fix to become available? Is that right, or did I miss something? And when do you think the next update will be?

Thanks

Yes, this has been fixed as https://www.ventismedia.com/mantis/view.php?id=18619 for the next build 5.0.2.2525