Topic: Basscd.dll changes affecting rips

[sveakul]

The latest MusicBee player has no problems creating secure CD rips using version 2.4.6 of basscd.dll;  however, updating basscd.dll to version 2.4.7.1 or 2.4.8 creates constant errors when ripping the same tracks from the same CD in the realm of 90-94 % (this is not using the "AccurateRip" feature, just secure rip with error recovery).

Have there been any major changes since 2.46 that might explain this sudden incompatiblity with a major bass-based player in terms of obtaining secure rips?

[Ian @ un4seen]

To narrow it down some more, please check BASSCD 2.4.7 too. You can get that here:

   www.un4seen.com/stuff/basscd247.zip

[sveakul]

To narrow it down some more, please check BASSCD 2.4.7 too. You can get that here:

   www.un4seen.com/stuff/basscd247.zip

Thanks for the extra test DLL.  Unfortunately, it fails also to produce a secure rip, so the fail that affects MusicBee must have began with changes made to basscd versions after 2.46.

I understand we could just keep using 2.46, but since it's now over 10 years old I'm sure we're missing positive improvements made as well.

[Ian @ un4seen]

OK, here's an update for you to try, which undoes a change that there was between 2.4.6 and 2.4.7:

   www.un4seen.com/stuff/basscd.zip

Let me know whether it helps. Please also confirm what BASS_CD_StreamCreate(Ex) parameters are being used, if you know.

[sveakul]

OK, here's an update for you to try, which undoes a change that there was between 2.4.6 and 2.4.7:

   www.un4seen.com/stuff/basscd.zip

Let me know whether it helps. Please also confirm what BASS_CD_StreamCreate(Ex) parameters are being used, if you know.

Hi Ian--unfortunately I still get "verify failed - 93.x% in error" messages for tracks that verify successfully with 2.4.6.

I'm sorry I don't have the knowledge to confirm the parameter you quoted, but I will ask the MusicBee developer what they are.  In the meantime, do you have another test version I can try?

[Ian @ un4seen]

There were other changes too, but I'm not sure which would be causing your issue. If you can get the parameters, what will hopefully tell where to look.

Have you confirmed that the ripped data from BASSCD 2.4.6 is correct, ie. it isn't just that 2.4.7+ is reporting an error that 2.4.6 ignored?

[sveakul]

There were other changes too, but I'm not sure which would be causing your issue. If you can get the parameters, what will hopefully tell where to look.

Have you confirmed that the ripped data from BASSCD 2.4.6 is correct, ie. it isn't just that 2.4.7+ is reporting an error that 2.4.6 ignored?

I'm currently still waiting on the MusicBee developer Steven to get back to me.  Normally very up to date on bass library updates, basscd.dll stopped being included past 2.4.6 with the player with the comment that "newer versions do not work correctly with MusicBee."  When 2.4.8 came out I tested it myself, and while it produces a rip that seems to play correctly with secure rip turned off, choosing secure produces error rates of +90% every time that stall when the "Trying to repair.." feature kicks in.  Going back to 2.4.6 results in secure rips every time.

I have no way to check myself if the real issue is 2.4.6 ignoring errors, or the likelihood of newer versions ALWAYS reporting errors.  Or if MusicBee itself is the culprit, but with thousands of users worldwide that would surprise me.

I'll "bump" the parameters issue and hope to hear from him over the weekend.