Need MusicBee's BASS_CD_StreamCreate(Ex) parameters

[sveakul]

I've asked this elsewhere but maybe I was using the wrong forum as I can't seem to get an answer.

I need the parameter described in the subject so that I may supply it to Ian Luck of Un4seen, who asked for it specifically so he could troubleshoot MusicBee's problem ripping CDs with versions of basscd.dll newer than 2.4.6.

If this can't be supplied for some reason, please just let me know and I'll drop the whole issue.  Thanks.

[Steven]

I have been in contact with Ian and some changes he made in v2.4.7 require some changes to be made in MB. At this point I am deciding whether it is worth time investing in making changes to CD ripping given we already have something that works fine.

[sveakul]

I have been in contact with Ian and some changes he made in v2.4.7 require some changes to be made in MB. At this point I am deciding whether it is worth time investing in making changes to CD ripping given we already have something that works fine.

Thank you Steven for your reply, and for talking to Ian.

Of course it's totally your call as to whether the time involved in making the change is worth it, given that 2.4.6 still works.  I would just throw in that making a change now could help future-proof the secure rip feature for new releases and updates to MusicBee for the forseeable future.

MusicBee's rip feature stands out from other popular music players like Foobar, which cannot rip individual tracks only a whole CD, and AIMP, which does not yet even have a secure rip option.  MB keeps up to date with its other BASS libraries because even small corrections/improvements can lead to increased usability and better performance, and it is appreciated.  Thanks for your consideration.

[Steven]

i am going to leave it on v2.4.6 as i cant get the C2 error checking option working. If you dont need to use the secure ripping feature then updating to 2.4.8 is ok

[sveakul]

OK Steven, thanks a lot for getting back to me.  It's a shame about not being able to get the new versions to work with "secure rip with error recovery", but I appreciate that you gave it another try!

For those would like to use the new 2.4.8 basscd.dll for rips, a workaround for not having the secure rip feature is to do Quick Rips, but with validate using AccurateRip and always show results checked.  In addition to being faster than a secure rip, getting a match back from AccurateRip is almost a guarantee of a perfect rip.  The only case where that method is not viable is if you were the only person who had ever submitted that CD's results to AccurateRip.

And if like me you wondered what secure rip/accurate rip actually did, secure rip reads every sector on the CD at least twice, and if the results do not match reads them an additional amount of times until it gets a high confidence result, after which it goes on to the next sector.  It will attempt to repair sector results it cannot officially "pass" after the rip completes.

 AccurateRip OTOH send a CRC checksum of the rip results to a server where they are checked against others who ripped the same CD.  Matching CRCs almost always ensure you got a perfect rip.

Using basscd.dll 2.4.8 on MusicBee with AccurateRip only, showing 36 other people got the exact same rip as I did of track #03:

[hiccup]

For those would like to use the new 2.4.8 basscd.dll for rips,…

Why is this 2.4.6 vs 2.4.8 basscd stuff so important to you?
What (reported) issue is it that this newer version solves, or what is it doing so much better than the version that MusicBee is currently using?

[sveakul]

It's not any more important to me than other parts of my music hobby.  I'm just "into the details."  I like using the latest versions of things--MusicBee itself, video applications, plugins of all kinds, etc.--because I believe developers release updated versions of their work for a reason.  Normally the reason is to tweak performance, add an additional feature, or eliminate a bug;  whether I noticed any of those in my prior use or not, "I want the tweaked-up one!"  Enough improvements you don't notice usually add up to those you can.

"Also, it's very interesting."

[sveakul]

Someone else recently brought this up at un4seen, see link.   I wonder why Ian made the change to asynchronous reads (the source of the problem) in the first place?

https://www.un4seen.com/forum/?topic=20533.0