1247 problems with ripping some tracks

[see-beyond-me]

ok, there are most likely only a few that see this problem, but apparently it's there and rather difficult to reproduce if one doesn't have it. I do see it and as I said, I do see it on two completely different systems (hw and os). And I also don't see any problem on those 2 systems when ripping with some other software.
One question to those that see this problem:
what is the target location you are ripping to ? Is it a locally attached drive or a networked drive, provided for example on a NAS like in my case ? Maybe that could make a difference, just being curious. As soon as I've time, I'll try to do a few rips to two different local drives, one SATA attached, the other USB attached.

rgds
/MD

[Ludek]

So far I couldn't reproduce it too.
Nevertheless I have added some debug messages so that I could see what is going on.

So could you please generate debug log by using this MediaMonkey.exe ?
http://www.yousendit.com/download/MnFpL ... MWxMWEE9PQ

[see-beyond-me]

can't install this debug image, immediately after launching installer, I get a message that the file 'sqlite3.dll' cannot be found.

rgds
/MD

[robojock]

I think you have to copy that .exe that you downloaded to your mediamonkey folder and write over the one thats in that folder... maybe just rename the other one to mediamonkey.exe.bak or something like that.

or once you have finished doing the tests you can just reinstall mediamonkey

[see-beyond-me]

oh, silly me, of course this is only the main executable and not the install package...

now have done the following:
-replaced .exe with the debug one
-started up MM, ripped one CD
-debug .exe happily did not rip track2
-when exiting it first showed some special window but only for a fraction of a second, then it disappeared and a crash window popped up with a message that windows needed to terminate mm audio whatever and then a small window with some kind of runtime error message.
- I try to do reproduce this again, then taking some screenshots, where could I send them to, PM attach maybe?
- or is there someting else I need to do when running this debug .exe version?

note that I won't be able to test further things before this evening (METDST) earliest.

thanks
/MD

[Brouwerik]

Here's what I did.

-Downloaded the file and copied it over the old .exe
-Run MM and dbgview
-Started ripping a CD
-Saved logfile to a .txt

Is this what you meant? If so where can I upload or send the file to?

Greetz,
Brouwerik

[Ludek]

Here's what I did.

-Downloaded the file and copied it over the old .exe
-Run MM and dbgview
-Started ripping a CD
-Saved logfile to a .txt

Is this what you meant? If so where can I upload or send the file to?

Greetz,
Brouwerik

Yes, that is exactly what I meant.
Share the debug log file via a free service like www.yousendit.com or rapidshare and attach here the link to the file.
Or send it to my email ls at mediamonkey.com

[Brouwerik]

Here it is
http://rs40.rapidshare.com/files/235144 ... _Debug.LOG

[Ludek]

Thank you.
I am actually confused about the log.
Tracks have been correctly assigned to the 3 threads as can be seen from the log:
00000846 43.12335968 [2424] Encoding: Track 0 (G:\Quarantaine\Uriah Heep - Look At Yourself - 01 - Look at yourself.mp3) assigned to thread 3136
00000847 43.12353134 [2424] Encoding: Track 1 (G:\Quarantaine\Uriah Heep - Look At Yourself - 02 - I wanna be free.mp3) assigned to thread 3804
00000848 43.12369537 [2424] Encoding: Track 2 (G:\Quarantaine\Uriah Heep - Look At Yourself - 03 - July morning.mp3) assigned to thread 5148

but actually tracks 1,2,6,7 have been ripped as can be seen from the log:
00000978 43.19463348 [2424] Going to encode file: E:\Track02.cda -> G:\Quarantaine\Uriah Heep - Look At Yourself - 02 - I wanna be free.mp3
00000980 43.20385361 [2424] Going to encode file: E:\Track01.cda -> G:\Quarantaine\Uriah Heep - Look At Yourself - 01 - Look at yourself.mp3
00001764 86.30360413 [2424] Going to encode file: E:\Track06.cda -> G:\Quarantaine\Uriah Heep - Look At Yourself - 06 - What should be done.mp3
00002551 110.73141479 [2424] Going to encode file: E:\Track07.cda -> G:\Quarantaine\Uriah Heep - Look At Yourself - 07 - Love machine.mp3

That is very strange, did you terminate the ripping process?

Could you please re-generate the log by using this MediaMonkey.exe?
https://www.yousendit.com/download/MnFq ... MnQzZUE9PQ
thank you.

[Brouwerik]

No I didn't terminate anything. Just pressed Shift+Ctrl+R. Pressed OK and waited till CD was spitted out.

Here's the new log as you requested:
http://rapidshare.com/files/235190900/B ... 2.LOG.html

[blade-bunny]

I also have the same problem actually. The last days I've ripped over 10 cds, and every single one of them has missed 2-3 tracks after first ripping. Mostly it's track #3 and #4 for me, but it has occured to others also.

I also have a Quad Core btw, and I've set Ripping to "All".

[Ludek]

Although I cannot reproduce and the log looks really strange I see something interesting that would make sense.
Entered the issue to our bug tracking system in order to investigate further:
http://www.ventismedia.com/mantis/view.php?id=5633

[robojock]

Ludek,

Should I create a log file for you too since i dont get that error and maybe you can compare? Maybe its os related with the quad cores? Im currently running windows 7 RC 1 so i dont know if that will have an effect?

[Ludek]

Brouwerik,
give a try with this MediaMonkey.exe:
https://www.yousendit.com/download/MnFp ... cWNLSkE9PQ

And let me know whether it is fixed.
Thx.

[see-beyond-me]

Brouwerik,
give a try with this MediaMonkey.exe:
https://www.yousendit.com/download/MnFp ... cWNLSkE9PQ

And let me know whether it is fixed.
Thx.

needed some moments to get familiar with dbgview and such stuff. Now run a rip with previous dbg image and the one (presumabley containing a fix) referred to in the previous post. Sent 2 dbgview logs and some screenshots to your mail address.
Looks like the fix did change something indeed, at least the rip went through on the first attempt. Will do some further rips to check the latest image.

/MD