INTERACT FORUM
More => Old Versions => JRiver Media Center 25 for Windows => Topic started by: Tsiobbel on April 09, 2019, 02:18:09 am
-
I've installed version 25 and deleted (too early) version 24 from my computer. Cd ripping problem : when a new cd is inserted and I choose 'cd ripping' I get a screen with only "rip" and "track". Where is the artist, title, genre, year, etc. section which I always get when I want to rip a cd ? Thanks
-
It's possible a firewall is preventing MC from doing the Internet lookup.
-
I have checked the Windows defender settings. Same as in 24. I've tried to re-install 25, but that doesn't help. I have already deleted version 24. Can I switch back to 24 and will the license in 25 be recognized for version 24 ?
-
Same here.
I am ripping a whole bunch of CD's. I insert one, it looks it up and I rip it. It spits out the CD, I click away the previous rip dialog and close the riplog. I insert the next, and either one of three things can happen:
1. It loads the previous CD title and tracks
2. It doesn't load anything (no tracks, as if there is no CD)
3. It loads the correct info.
It seems completely random but when 1 or 2 happens most often, I have a very hard time to get MC to recognize the CD. I eject it, close MC, insert the CD and watch Windows Explorer to recognize it, open MC and it just comes back with whatever it detected before closing.
It seems like a caching issue.
I'm having this issue with almost any CD change. Option 3 rarely happens.
For now I installed EAC just to see if it has the same issues. EAC picks the correct CD tracks and downloads the right track info. Even after EAC loaded it, MC refuses to see a CD change.
Let me know if you need anything. I can make a debug log and upload it.
-
Can you double check your firewall?
-
Same here. I reported a problem with CD ripping with build 16.
https://yabb.jriver.com/interact/index.php/topic,120054.msg829868.html#msg829868
-
I had this problem a while ago. I thought it was related to the caching on a specific drive, but I never could track down the details. But, when I moved to a different drive, the problem went away.
-
I've run JRiver 25 on another computer. I tried to rip a 2 CD. First cd went ok. Second cd : only tracks visible (as if there was no cd). I've stopped the program, launched it again and inserted again the cd. In the second try, JRiver recognised the cd this time. Compared to the previous version, it takes much more time before a cd is detected (first get the message there is no cd inserted). On my other machine however (same Windows 10, same firewall), the problem remains (only track numbers visible).
-
Can you double check your firewall?
I have. It's not a firewall issue. Besides, sometimes it does read the CD correctly and fetches the info. Most of the time, it detects the CD as the previous one ripped, or pretends the drive is empty (no tracks shown).
Then, without ejecting or doing anything special, I start EAC and the correct tracks are immedately shown.
MC is really a lot slower and if I had to guess, the current build has a 50 to 75% failure rate detecting CD changes when ripping multiple CD's successively.
-
I'm having the same problem as InflatableMouse, except I don't get the previous rip information, it goes straight to not recognising the CD. Additionally, once MC25 has not recognised the CD, the drive disappears from Windows Explorer. If I rip through EAC, it all works smoothly.
-
I am having the same issue. Will not rip or play. If it does retrieve disc info and I select play it jumps from track to track in seconds and then stops.
-
Please try updating. 25.0.24 is available.
-
Latest update does not solve the current problem : only 'ripping', 'track' and 'status' are visible. Same problem occurs on both of my computers.
-
I installed 25.0.24 and continue to have the same issue.
-
haveing simular prob...open file to rip..spins...no disk....have to restart.....rips maybe 3 more.....then starts over....since new ###...happy feaster...
-
Updated to 25.0.24 and still the same problem for me too. Disk goes in, choose to rip, disk spins up and then nothing. If I select rip again from the action window, it asks me to insert a disc, so checking in Windows Explorer shows the location is unavailable. Sometimes it will take multiple reboots to get it to rip. EAC rips on the first try, every time.
-
Again, latest MC25 update did not solve the cd-ripping problem. E.g. a cd with 18 tracks in MC 25 : no track info and only 11 tracks visible. Same disc but opened with MC 24 : track info and with 18 tracks (correct). Is somebody within MC taking this cd ripping problem seriously ?
-
25.0.27 installed. Seems to be working for me, I've just ripped a number of discs consecutively.
-
Please state your OS version as well as whether it works. Thanks.
-
Also have most of these issues
[New PC with Window 10 Home]
request
It would be great if I could do a search for the album when MC is not able to load the correct album
I have ripped CD box sets and upon ripping the 3rd CD I realize that MC has loaded the info for CD 1 for each disc
(regardless of the number of tracks - that is if CD 2 has more, they don't even get ripped)
-
Also have most of these issues
[New PC with Window 10 Home]
request
It would be great if I could do a search for the album when MC is not able to load the correct album
I have ripped CD box sets and upon ripping the 3rd CD I realize that MC has loaded the info for CD 1 for each disc
(regardless of the number of tracks - that is if CD 2 has more, they don't even get ripped)
Please include the full version of MC.
-
2 computers with same cd ripping problem in MC25 :
Windows 10 home
Version 1803
Build 17134.706
and
Windows 10 Home
Version 1809
Build 17763.437
-
If you click "close" the next rip it will work :Do not push "Rip another disk"
-
@Jim 25.0.27
@arrowc interesting
-
25.0.31 is here:
https://yabb.jriver.com/interact/index.php/topic,120483.0.html
-
Have updated to 25.0.31 and I still can't rip CD's.
Window 10 Home
V. 1803
OS Build 17134.706
-
Updated as well and cd ripping (and cd recognizing) problem persits.
Tried to find logic but unable to find : or cd is not recognized or previously ripped cd text and artwork appears. Once not detected in MC 25, same in MC 24 (on same computer). Only solution I got : ripping in MC 24 on an old Windows 7 computer which works fine.
-
When it doesn't recognize, does hitting the refresh button on the top toolbar get it to fill in? Thanks.
-
Unfortunately I've tried the refresh button but that doesn't make a difference It also takes much more time in MC25 to '"recognize" a cd (mostly by getting first the message that no cd is inserted). So I also get a stability problem of the system.
-
^^ what he said
first CD I wanted to Rip today got ejected automatically. Closed MC. Insert CD. View tracks in Exporer. Open MC and rip away.
Also since updating a couple nights ago - still get last CD ripped info for next CD. Hitting the Close button doesn't work/solve for me.
Rebooting MC has been my best bet
Refresh doesn't always work either...
All efforts are appreciated!!
-
EAC (Exact Audio Copy) works fine. I've tried it after the problems with MC25 for cd ripping. So I still keep on ripping or in MC24 or in EAC. However I would prefer MC as I'm more familiar with this program. It looks like this is the other way around. I don't understand the logic : MC24 does work and MC25 cannot perform (despite the current updates). What can this basic German (but well performing and stable) program do what MC25 is not capable of ? I'm wondering the reduced number of people facing this problem (or they don't rip cd's anymore ?) in MC25.
-
We can't reproduce the problem, so we need help finding out what you have in common with each other. OS, antivirus, country, etc.
-
Please test this build and let us know how it goes:
http://files.jriver.com/mediacenter/channels/v25/latest/MediaCenter250034.exe
http://files.jriver.com/mediacenter/channels/v25/latest/MediaCenter250034-x64.exe
Thanks.
-
Installed latest build and still same issue. I attached a pic of the message I get. Once again I am in U.S.
Window 10 Home
V. 1803
OS Build 17134.706
-
If you're having problems, would you be willing to test the last v24 as well:
https://yabb.jriver.com/interact/index.php/topic,119837.0.html
There just haven't been any intentional CD changes except the change reverted in build 34.
Thanks.
-
I am sorry but V24 is what I have to use to rip with now so not willing to over ride it. Mine is MC 24.0.75
-
MC25 won't override MC24, they're separate installs with seperate settings and can co-exist.
-
I understand that 24 and 25 can coexist. I have them both. The question was if I would be willing to install the latest version of 24. And since my version of 24 is working correctly I am not willing to lose it.
-
I had the same issue, I had done some OS analysis (latest build on windows 10) and initial findings indicated that jriver was not fully authorized to use my CD drive (I was having intermittent failures or the previous CD's info was being displayed). The only way around it was to continually remove the device and re add, that is until I installed the 64 version as suggested in this thread - now works perfectly.
very much appreciated.
-
I had the same issue, I had done some OS analysis (latest build on windows 10) and initial findings indicated that jriver was not fully authorized to use my CD drive
Can you share how you determined this? I suspect that this is the same issue for everyone having the problem, and is probably drive make, model, and driver related. It would be great if there was an easy test other users could do to see if this was their problem.
Don't see why the bitrate of the OS would influence the capabilities of the cd ripping system - but always open to learning!
I think he meant he changed from the 32bit to the 64bit version of MC, rather than of Windows 10. If that was the fix it would probably indicate that heuristics in some security software was the issue. But an answer to the above question may clarify that.
-
Apologies,
I now realize that I should have been more complete with my post - I was just so happy that the new version fixed it.
To be clear I have been using MC since V21 and have taken all MC upgrades with no issues running it on a 64bit win 10 machine.
I upgrade to MC25 as soon as it became available, however I only attempted to rip cd's today - which is when I started experiencing similar issues as those reported in this thread.
after a little bit of googling I came across an article on using the win 10 "component services admin" tool
right click on start , select run and enter in %windir%\system32\dcomcnfg.exe
I then spent a little while (about 15 mins) looking through the "Windows Log" section see attachment "MC 25 component services info" which indicated that errors were being generated with exactly the same timestamp as when I was attempting to rip a cd. The error appeared to suggest the MC 25 was not providing a CLSID see error message in the attachment.
I then went to the forum and re-searched the issue and found the link to ver 25.0.34. once I installed this it cured the issue.
Hope this is of more help
-
Thanks for the clarification.
Those logs are also viewable using just the Event Viewer. I have similar errors reported on my system, and I don't have the problem ripping CDs. The error messages don't reference MC at all, and I don't think the timestamp is enough evidence that MC was the cause. In fact the most recent of those errors I am seeing happened at a little after midnight, which is when my PC is woken to run backup processes. MC isn't running at that time.
I don't think those errors can be blamed on MC. Maybe if I worked out if the CLSID referenced belonged to MC I could be more sure, but that is work!
Nevertheless, at least CD ripping is working for you now, with MC25.0.34, which has the threaded update for CD lists turned off.
-
Update:
I installed the latest release of MC25 which appeared to solve the issues I reported - however all of the issues re-appeared after a re-boot.
Background:
Earlier on in this thread it was requested that a user try MC24 and verify if the issues were being manifested on a stable release, I tried this and they were.
My particular hardware setup I have 2 Sata connections available on my motherboard 0 - HDD and 1 internal Cd Rom. After finally ripping my cd collection (000's) to NAS (network attached storage) I replaced the CD rom with an internal 4tb SSD.
2018 - NAS issue, resulting in a requirement to re-rip CD collection.
I purchased a USB 3.0 portable CD/DVD unit and this is when I experienced issues.
After searching here and online I came across lots of users in the Window 10 forums reporting exactly the same issues, with quite detailed technical solutions (some involving renaming the onboard sata connections) on how to "fix" the issues with windows 10. My machine was fully up to date regarding drivers, OS and Bios.
I thought that it may be the make and model of the usb CD\DVD , so I trailed 3 - all failed with the same issue
Conclusion: It does appear that there maybe a wider issue with windows 10 and USB 3.0
My solution:
I returned all of the portable USB 3.0 cd\DVD units to the suppliers. I purchased an "IDE/Sata to USB 3.0" cable from amazon (£18) and I re-used the internal CD\DVD unit I'd removed previously - The cable turns the unit into an "external" CD/DVD.
Everything works as it should
Hope this helps
-
My ripping problems appeared to have been solved (the internal CD writer would 'disappear' after one rip), but now I have similar problems to other users.
I'm trying to rip a box set of CDs and the previous CD track listing is appearing instead of the latest CD. I've just updated to 25.0.36, loaded CD number 2 in the drive and CD number 1 track listing is displaying.
I open EAC and it recognizes the CD as disc 2
Windows 10 1809
Intel Core i7 6600U @ 2.50GHz
931GB Samsung SSD 860 EVO
DVD Writer: HL-DT-ST DVDRAM GUE0N
-
Interesting topic from woollies66.
I have changed some months ago the internal HDD from my 2 laptops by 2 internal SSD,using the Samsung migration tool. MC 24 and now MC 25 installed on both laptops.
So when I installed MC 25 the cd ripping problem began. With the latest update problems appear less frequently but still have some stability problems. It takes some time before the tracks are detected.
-
We'd like to find a few people who are still having problems and would be able to test private builds. Any volunteers?
I'm sorry for the continuing problems with this.
-
I installed the latest release of MC25 which appeared to solve the issues I reported - however all of the issues re-appeared after a re-boot.
Make sure you're using 25.0.36.
-
My solution:
I returned all of the portable USB 3.0 cd\DVD units to the suppliers. I purchased an "IDE/Sata to USB 3.0" cable from amazon (£18) and I re-used the internal CD\DVD unit I'd removed previously - The cable turns the unit into an "external" CD/DVD.
Everything works as it should.
Hope this helps
I missed this the first time I read it. That suggests that we may have been chasing more than one problem and that a Windows update could have been part of the problem.
-
I'll give it a go.
We'd like to find a few people who are still having problems and would be able to test private builds. Any volunteers?
I'm sorry for the continuing problems with this.
-
Me too
-
I missed this the first time I read it. That suggests that we may have been chasing more than one problem and that a Windows update could have been part of the problem.
It has been documented for a long time that USB connected CD Drives do not allow Windows 10 to take the low-level control required for secure CD ripping. Only IDE/SATA CD Drives will work when ripping which requires more control than just reading a CD. Of course that depends somewhat on the method used for CD ripping, but it seems that MC's method falls into this category.
It is interesting that an IDE/SATA to USB 3.0 cable gets around this issue. I assume that some of the protections Windows 10 implements for the unexpected removal of a USB drive are removed. Which means care needs to be taken in removing the drives. That would only be a significant issue if the CD Drive was writing to a disc of course. Maybe if the drive was marked as Read Only, or non-removable half these problems would disappear.
But generally, using a USB connected Optical Drive for ripping optical discs is a bad idea.
-
I rip with Exact Audio Copy (must be force of habit) … have 1 SATA drive, 2 USB drives … EAC able to use all of them at low level access for accurate ripping … not sure why MC cannot use USB drive (can be actually drive limitation rather than interface problem … for example - not all drive able to retrieve C2 error information or "Accurate Stream" features)
PS … in case you were wondering … those CD/DVD/bluray drive survive my PC upgrade phase (aka I did not throw them away when upgraded hardware) … I have lots of damaged CDs that I haven't rip yet … and some of my drives handle some errors better than others … in some cases 2 drives fail to accurately rip (lots of scratches), while another one able to do it several times (albeit after several attempts … might be just luck)
-
The latest update in MC25 for cd ripping is making things worse. I've tried to rip a cd
Folder rule : album
Filename rule : track artist name
I was not able to rip this disc (after trying 4 times), I thought it was a Synology nas problem. However, I've tried to rip on the same laptop in MC24 and the disc rips perfectly.
I don't know if the cause is linked with my computer. But if MC 25 does not keep on ripping cd's at it should be, and MC 24 does the job without any problem, I have the strong feeling it is MC 25 based. The stability problems which occur with MC 25 make things worse
-
We'd like to find a few people who are still having problems and would be able to test private builds. Any volunteers?
Sorry, haven't checked back here in a while. Sure, I would try if you still need people.
Also, I just tried to play a CD with MC and it plays less than 2 sec of each song, goes thru entire CD in less than 10 sec. I assume this is related.
-
I've still got the same same problem as I reported months ago, although intermittent. CD goes in, drive spins, MC either freezes or takes ages to do nothing. I reboot as my device has disappeared, try again same problem. I reboot, use EAC, no problems.
Any ideas?
-
Firewall? Antivirus?
-
There is an intermediate solution. Let MC play the cd first. MC recognizes the titles and artist. Some seconds is enough. I switch to 'rip disc' and it works fine. If however, I insert a cd and take the rip option I als keep on having the same problem as described many times. It is probably not the most elegant option but it works. With MC 24 I didn't have to do this 'less elegant option' as ripping was executed from the first time correctly. If it would have been a firewall or antivirus problem, the same ripping problem would occur on MC 24 as well, as both versions are installed on the same computer.
-
Firewall? Antivirus?
Firewall and antivirus is standard Windows default. I went through the checks previously. If it is related to either of these, would that account for the drive 'disappearing' i.e. no optical drive shows up in file explorer? The PC has to be rebooted for the CD drive driver to reload.
Thanks Tsiobbel, I will give your workaround a go next time.
-
Tsiobbel,
I've just tried the last CD that wouldn't rip using your suggestion, i.e. play first, stop playback and then rip and that worked. I'll try again once some more new CDs arrive this week.
To MC:
Does this problem have any form of ongoing priority? There was talk of a private build back in May but I haven't heard anything since.
-
MC won't even recognize that discs are in either of my drives. I have never had any luck ripping from both drives at once but one at a time would work. Now I get nothing. Yesterday it was freezing up my whole system when I would try to rip. The CD drive light wasn't even on. I had to restart the computer multiple times.
EAC recognizes both drives fine. I would just use that to rip but it doesn't let me rip to mapped drives.
-
I've still got the same same problem as I reported months ago, although intermittent. CD goes in, drive spins, MC either freezes or takes ages to do nothing. I reboot as my device has disappeared, try again same problem. I reboot, use EAC, no problems.
Any ideas?
Me too - I use Foobar when this happens with MC.
-
Tsiobbel,
I've just tried the last CD that wouldn't rip using your suggestion, i.e. play first, stop playback and then rip and that worked. I'll try again once some more new CDs arrive this week.
This worked again on a new batch of CDs, first time rip after playing the disc.
To MC:
Does this problem have any form of ongoing priority? There was talk of a private build back in May but I haven't heard anything since.
No reply to this?
If you are investigating the problem still, please say so.
If you're not going to investigate any further, please say so.
Thank you
-
But now the problem returns again. This is getting tedious as I have to restart my laptop every time I try and play or rip a CD through MC.
I take it from the lack of response to my query above that it isn't a priority even though the forum is still getting new reports of a problem with CD ripping.
-
My guess above is still my bet.
-
That's not the most helpful of replies. I mentioned that I have the standard Windows defender and anti-virus, it's not some strange esoteric software. The firewall has MC as an allowed app. What else am I supposed to do in terms of anti-virus and firewall?
The problem with ripping was perceived as enough of a problem before that we were asked if we would test custom builds, then it all went quiet, hence my question if this is no longer a priority?
-
I think that means we didn't learn anything. Sorry.
-
I meant it was asked if we would test custom builds, to which I at least replied yes, but then I never heard anything again. Did this go ahead with others and nothing was learned, or did it get forgotten about.
Do I then take it that you are not pursuing this problem, it's difficult to tell from your rather brief replies.