MediaMonkey forum

#1: crash while ripping a cd to flac ... it ripped OK when I changed Read Type from Jitter Corrected to Standard Read .. I have no evidence that this change was related ... the time that crashed it seems that the MusicBrainz lookup delivered no results ... results were available when i (successfully) retried

#2: The dbox containing the Rip Log, listed success notifications and described them as "problems"

#3 Why is MM5 shipping with a very old Flac library from September 2007 ... the latest is from August 2019. ... There have been performance improvements.

#4 The Folder targets in the SendTo menu just lists only local disks ... it doesn't list the NAS share where all my music is located.

#5. I had this crash when navigating.

4. https://www.ventismedia.com/mantis/view.php?id=17258

https://www.ventismedia.com/mantis/view.php?id=17279

https://www.ventismedia.com/mantis/view.php?id=17278

1. https://www.ventismedia.com/mantis/view.php?id=17267 Tried I am unable to replicate.

2. When there is a problem on CD RIP whole rip Result is shown so that you can Compare the result If track 1 (like in your picture) is bad it can be due the Dirty/Scratched CD or that CD drive head do not read start of track. I would rip that track only with Secure RIP possible several times, making sure that there is no CD tracks in Now playing.

3. added as https://www.ventismedia.com/mantis/view.php?id=17269

5. added as https://www.ventismedia.com/mantis/view.php?id=17268

Hi Barry,
166D0000 is here, but 775292E7 did not come, have you submitted it?

Could you please send me this file: C:\Users\<USERNAME>\AppData\Roaming\EurekaLab s.a.s\EurekaLog\Bug Reports\MediaMonkeyEngine.exe\MediaMonkeyEngine.el

2) Shows Ripping Results as dialog title when all files return verified with confidence

Ludek wrote: ↑Mon Dec 21, 2020 8:34 am Could you please send me this file: C:\Users\<USERNAME>\AppData\Roaming\EurekaLab s.a.s\EurekaLog\Bug Reports\MediaMonkeyEngine.exe\MediaMonkeyEngine.el

Both Bug Reports folders are empty at C:\Users\<USERNAME>\AppData\Roaming\EurekaLab s.a.s\EurekaLog\

Did not see your msg until after I had installed the latest version of MM5, so maybe that cleared old logs?

Peke wrote: ↑Mon Dec 21, 2020 6:52 am Take another look at my illustration

• the heading is "There was a problem ripping or verifying the following tracks"

• it then lists every track on the album, with a retry checkbox against every track

[Update] Whoops .. I meant to quote from whatever was in here ... but I ended up overwriting it

Yes, the dialog lists all files ripped. That's expected. The amount of people matching is related to the amount of people that send in their Accurate Rip info which many programs don't do.

Lowlander wrote: ↑Mon Dec 21, 2020 10:40 pm Yes, the dialog lists all files ripped. That's expected.

Expected by you maybe.

Lowlander wrote: ↑Mon Dec 21, 2020 10:40 pm The amount of people matching is related to the amount of people that send in their Accurate Rip info which many programs don't do.

I do know that .. because I am not new to ripping.

This isn't a Support Call. Is just beta feedback.
The design of that dbox is substandard for reasons explained; information unclear ... heading inapproprioate ... misleading check boxes.

Is Ok to leave as-is, as long as you don't mind wasting the time of whomever it is that is the poor sod manning the Support Forums.

Hi,
@Barry4679 have you managed to locate/replicate crash log id 775292E7 as requested by @Ludek at viewtopic.php?p=475900#p475900 and documented at https://www.ventismedia.com/mantis/view.php?id=17268 ?

Peke wrote: ↑Sun Dec 27, 2020 10:16 am @Barry4679 have you managed to locate/replicate crash log id 775292E7 as requested by @Ludek at viewtopic.php?p=475900#p475900 and documented at https://www.ventismedia.com/mantis/view.php?id=17268 ?

Hi Peke,
I don't know. If I was able to locate it I would have sent it directly to him. An .el file is an ephemeral thing; it gets replaced by the next crash, and doesn't get archived.

I sent him three .el file crashes yesterday ... They were all crashes when navigating ... I have no way of knowing whether they were the same issue as something that happened more than a week ago.

BTW you should focus upon whatever the issue is that makes your submission server be so flaky ... that way we would have to do nothing other than just report and describe the incident ... the three files from yesterday were required because your submission server was down again

Barry4679 wrote: ↑Sun Dec 27, 2020 8:47 pm An .el file is an ephemeral thing; it gets replaced by the next crash, and doesn't get archived.

It should append not overwrite. Have to check but it was like that in MM4.

Peke wrote: ↑Tue Dec 29, 2020 10:28 pmIt should append not overwrite. Have to check but it was like that in MM4.

Oh, I did not know that. Thanks.

There are more problems with the MM5 Rip Log.

• when I 1st looked at the report it appeared that at least you were listing any problems at the top of the report ... but no, if I scroll down there are more problems listed off-screen ... there needs to be a summary which lists any|all problems prominently ... this comment applies to other reports like the sync to Internet report

• why list the tracks in random sequence? ... you list the tracks in the following sequence; 2, 4, 1, 6, 11 ...

• there is no option to print the report ... that would be my 2nd choice ... my 1st choice would be that you persist the log into the album's folder