Rip CD doesn't open

[chobson]

Hi, been using MB for many years, have ripped my entire CD collection and working on adding LPs. So MB works perfectly to play, including playing a CD I load into my external CD drive. However I can't get the Rip CD menu to open - either in the menu for my external drive that shows up under "Computer" in the far left column or by clicking on "Rip  CD" under the Tools menu in the toolbar. I use two screens, and in the past I've had issues where I don't see the Rip CD menu coming up minimized on the other screen, but that doesn't seem to be the case here. I can't get the Rip CD menu to come up at all. Have closed and reopened MB, restarted Windows, have the latest version... Thoughts? thx!

[phred]

What version of MB are you using? (Help > About) INCLUDE THE LETTER (if any) AFTER THE NUMBER
How was MB installed? (Store, Installer, Portable)

[chobson]

3.5.8447 Store

[phred]

Thanks.

There's not much that can be done with the Store version in terms of updates and bug fixes until a  new version is released. What I would suggest for troubleshooting is to download the latest Portable version from the first forum topic. It can co-exist with your Store version. Place the Portable in a folder outside of Windows control, such as C:\MusicBee. See if that takes care of your issue. If it doesn't, apply the latest 3.6 patch over the 3.5 Portable and see if that resolves it. Get the latest 3.6 patch from my signature below.

Once it's resolved, use the Store version for reference to finish configuring the Portable. Once you're all set, uninstall the Store version and never look back.

If all that fails, I'm out of suggestions.

[chobson]

OK will do. Appreciate it!

[sveakul]

Can anyone who rips CDs regularly help with this??  No shade to Steven, but it has been assumed for years that since an initial problem came up years back that MB can only rip CDs correctly with the literally 10-years old 2.46 version of basscd.dll, still included in all MusicBee full distros  Now that the 2.48 version of same has been released this week, can someone pop that in instead of 2.46 and actually give it a try??  Then we can put that to sleep one way or the other.  THANK YOU!  Here is the link to the new, full release version:

https://www.un4seen.com/download.php?basscd24

[phred]

Now that the 2.48 version of same has been released this week, can someone pop that in instead of 2.46 and actually give it a try??

Yesterday Steven posted that basscd 2.4.8 does not work. It was in reply to something you posted regarding 2.4.8
https://getmusicbee.com/forum/index.php?topic=41509.msg226569#msg226569

[chobson]

Well downloaded the portable version and that fixed it! Sweet! Thanks again - I rarely show up on this forum but when I do it is always helpful. Very much appreciated. I didn't add any patches, not needed. Last question (for now) - can I now just delete the store version?

[phred]

Glad to hear you got the issue resolved.

Since I've never used any MS Store application, I can't tell you how to delete MB. I suggest you let Google be your friend.

[Mayibongwe]

Last question (for now) - can I now just delete the store version?

If you don't plan on carrying over any existing settings to the portable setup, then sure, you can go ahead and uninstall the Store version.

[chobson]

Great, will do. Thx again.

[sveakul]

Now that the 2.48 version of same has been released this week, can someone pop that in instead of 2.46 and actually give it a try??

Yesterday Steven posted that basscd 2.4.8 does not work. It was in reply to something you posted regarding 2.4.8
https://getmusicbee.com/forum/index.php?topic=41509.msg226569#msg226569

I realize that, but he did NOT post "I tested 2.4.8 and it does not work."  This is my point--after actually testing one of the versions newer than the 10-year-old one and finding it doesn't work (I don't know which one that was), it's easy to assume/say "newer versions do not work" every time one appears and not going any farther.  I was just hoping that someone could settle that assumption with THIS new version by reporting results from an actual test.  Again--any takers??

[phred]

I ripped a CD a few months ago using MB's original basscd dated 2014-06-11 version 2.4.6.0 and had no issues. If it ain't broke, don't fix it. I see no need (for me) to update. Perhaps if I still had hundreds of CDs to rip, then maybe.

[sveakul]

I took the above challenge on myself, much as I consider ripping CDs a PITA at this point in my life.

Folks, BASSCD.DLL VERSION 2.4.8 WORKS for ripping CDs using MusicBee.

Test (MB 3.6.8999 P, basscd.dll version 2.4.8 (16 August 2024), Windows 11 x64):

1.  Got the Rodzon HL-DT-ST DVDRAM GT90N out of the desk drawer and plugged it into a USB3-A port on my PC.

2.  Inserted a CD, then opened MusicBee and dropped Tools->Rip CD.  MB recognized the presence but I had to close and re-open the dialog for the track list to populate (cool!).  Whether that's normal or not I don't know because I've never ripped a CD with MusicBee before.

3.  Chose a track, left the settings in their "as-is" condition (no error checking etc), and hit Rip.

4.  The selected track ripped successfully with no error messages and resulted in a playing, tagged file in the folder I had chosen.

There's a moral here somewhere.

[hiccup]

I took the above challenge on myself, much as I consider ripping CDs a PITA at this point in my life.
Folks, BASSCD.DLL VERSION 2.4.8 WORKS for ripping CDs using MusicBee.

I hardly ever rip CDs these days, and when I do I use something other than MusicBee.
But I also took the challenge.
I used the setting 'secure rip with error recovery'.

With 2.4.6.0 things seem to have gone OK.

With 2.4.8.0 I am now looking at this:


So, sveakul, will you be the one providing support for users using 2.4.8.0?  ;-)

edit:
I am wondering what the ripping process was looking for on my C drive.
The portable MB install that I used is on a very different drive.