INTERACT FORUM
More => Old Versions => JRiver Media Center 31 for Windows => Topic started by: Jason-V on August 26, 2023, 09:22:18 pm
-
Hi,
Been using JRiver for years and this issue has been consistent.
Version 29.0.91 64bit, though it has been happening for years.
When ripping a collection of CD's within the same session,
I insert the next CD to be ripped and JRiver doesn't always realise
that I have inserted another CD, even when I click on another tab in
left tree pane and back to the drive (the CD starts spinning up and JRiver does nothing).
I have to close JRiver and re-open, I click on the drive then it comes up with the CD.
Obviously not a huge issue though if it can be fixed would be nice.
Thanks.
-
What is the drive? Internal? USB? Manufacturer?
-
Thanks
-
What is the drive? Internal? USB? Manufacturer?
External USB connected 4K Drive - Pioneer
This is the drive below
Pioneer bdr-xs07tuhd
Thanks
-
Hi,
Been using JRiver for years and this issue has been consistent.
Version 29.0.91 64bit, though it has been happening for years.
When ripping a collection of CD's within the same session,
I insert the next CD to be ripped and JRiver doesn't always realise
that I have inserted another CD, even when I click on another tab in
left tree pane and back to the drive (the CD starts spinning up and JRiver does nothing).
I have to close JRiver and re-open, I click on the drive then it comes up with the CD.
Obviously not a huge issue though if it can be fixed would be nice.
Thanks.
I haven't had this issue for a while and not in MC 31, but I have seen it again repeatedly recur in MC 31.0.50 (64-bit). When a new CD is inserted for ripping, MC displays the information for the previous ripped CD. The only solution I've found is to completely shut down MC and restart the program. Very annoying.
-
I haven't had this issue for a while and not in MC 31, but I have seen it again repeatedly recur in MC 31.0.50 (64-bit). When a new CD is inserted for ripping, MC displays the information for the previous ripped CD. The only solution I've found is to completely shut down MC and restart the program. Very annoying.
See this other thread:
https://yabb.jriver.com/interact/index.php?topic=134729.0
-
Here's still another recent CD thread with some ideas to consider:
https://yabb.jriver.com/interact/index.php/topic,137501.msg954344.html#msg954344 (https://yabb.jriver.com/interact/index.php/topic,137501.msg954344.html#msg954344)
-
Could be I have just been lucky, but in 16+ years using MC and and ripping 2000+ CDs, I have never once encountered this issue - or issues of any kind when ripping CDs.
markf2748 post points to one of his posts in another thread where he indicates the problem was resolved once autoplay was changed to "take no action" (at least in the short window he has evaluated it so far) - and that is the setting I have used for as long as I can remember. Could the fix really be as simple as that? just changing autoplay to "take no action"?