INTERACT FORUM
More => Old Versions => JRiver Media Center 18 for Windows => Topic started by: Juniorjbl on December 14, 2012, 09:53:48 pm
-
Is there something I am doing wrong? Trying to rip a disk but it says there are 0 files on the disk and if you press play it says "nothing to play".
Go to "computer" and double click the Bluray Drive icon and it plays (in MC) at what looks like 1/2 speed with no sound. AnyDVD HD see's disk and will rip it to HDD.
MC version is 18.0.90.
-
You need AnyDVD HD or equivalent to read the disc.
-
I did say AnyDVD does see the disk and will rip it to an iso. version 7.1.2.0
BTW it is a new release BD
-
It also has the title of the movie in MC but says there is nothing to play.
-
I am having the same problem with MC version 18.0.90 & .94. MC plays the Blu Ray fine but will not rip.
Any DVD HD will rip to hard disk with no problem. Never had this problem previously. Tried with MC 18 on win 7 computer and on win 8 computer, both with no tracks to rip. Will not rip disks ripped previously.
Am I missing something simple?
-
I installed .94 today as well. Same outcome.
-
Bump.
-
It's been reported by several users. It may be our bug.
-
Upgraded to .94 last night and I am having the same problem: Media Center sees my DVD drive and titles but when I try to rip it says "no files are available on the CD drive" .......
-
MC 18.0.94 won't rip a BD if you choose to start rip from auto play window with "ask every time" selected.
Also won't rip if you select rip button with BD drive selected in tree.
Works fine if rip is selected in action window.
Tried with two different machines- same result.
A most excellent program, thanks.
-
It has also affected my install of V17 running side by side
Sorry to those who knew about this possible bug, I did not read this.
-
Works fine if rip is selected in action window.
Tried with two different machines- same result.
A most excellent program, thanks.
You're welcome. Thanks for posting the work-around.
-
Issues on my system too. I get the MC "do you want to rip/play/do nothing" box and select rip and back comes no disc in drive.
FastKayak / Larry
-
MC 18.0.94 won't rip a BD if you choose to start rip from auto play window with "ask every time" selected.
Also won't rip if you select rip button with BD drive selected in tree.
Works fine if rip is selected in action window.
Tried with two different machines- same result.
A most excellent program, thanks.
Yes I really like the program too!
I am not able to rip from any shortcut in the program at all. Both v17 and 18 but same machine.
-
Hey guys, could you send a log file my way following one of these errors?
Thanks!
johnt at jriver dot com
-
I will in the next hour or so.
-
We can duplicate it now.
-
Thanks for the update Jim.
I got stuck at work and have not been able to get home to get the logs. Should I still get them?
-
I don't think we need them now, the next build should fix the problem.
Thanks.
-
Thanks for the update John!
-
Well I tried .97 and still I do not get files to rip. Can someone please tell me what I am doing wrong?
I have attached a pic showing that "My Computer" see's the files but MC see's nothing.
-
Does anything happen if you click the "Rip Disc" button in the header, or right-click the drive in the tree and select "Rip Disc"?
Please send a log file to johnt at jriver dot com.
Thanks.
-
Did you try a reboot?
-
I tried to right click on the disk in MC explorer, I tried to use the action menu. Tried to double click in the main area to refresh the content.
But as before AnyDVD HD see's and will rip to .iso but MC says 0 files.
I did reboot twice.
It seems as though it is some files or settings that get changed to both installs (v17 and V18) because 17 used to work flawlessly.
-
What (if anything) does it do if you click the "Rip Disc" button to the right of the "Get Movie & TV Info" button up near the top of the view?
-
It brings up the "rip disk" item in the bottom left corner above "action window" and says "Insert a disk and click here"
-
Thanks for the log file. It's showing this error (many times):
CCDManager::Open: error opening drive H:, error 266, text=Unknown problem while loading the specified device driver.
I don't remember ever seeing this one before. Is this an external drive, like USB, eSata, or Firewire?
-
Do you have an audio CD handy that you could place in that drive and check if you see the contents and it's rippable? This information might help me track down the source of the problem. We might be taking some unnecessary steps when we're examining video discs which could cause problems on some drives.
-
The drive is an internal LG WH12LS39 on the SATA 3g bus on an intel X79/C600 chipset board (ASUS P9X79 Deluxe).
I am having the same experiance with the audio cd as well. (I dont normaly use MC for audio just video. Dedicated HTPC)
Do you need more logs?
-
John I sent you some more info.
-
I'm also having this issue. I'm sticking on build .078 for now. I look forward to a fix/workaround. If there is anything I can do to help, let me know. BTW, I also have an ASUS board, Z68 chipset though.
-
I'm also having this issue. I'm sticking on build .078 for now. I look forward to a fix/workaround. If there is anything I can do to help, let me know. BTW, I also have an ASUS board, Z68 chipset though.
So you are getting the "Insert a disc and click here.." message in the action window? And if you click on the message nothing happens? If that's the case, please send a log to johnt at jriver dot com so I can compare it to the other ones I've gotten to look for commonality. Thanks!
-
Yes, exactly. I'll get one over to you. Thanks!
-
I sent a log over the holidays. Let me know if you didn't receive it.
-
I sent a log over the holidays. Let me know if you didn't receive it.
JRiver is closed this week.
-
Glad to hear that! I hope everyone enjoys spending well earned time with friends and family.
It seems that build 103 has resolved this issue. Thanks.
-
Thanks for the update on this issue. I believe there may be two separate issues causing this problem and one is fixed in the latest builds but the other one may still be there. On Monday we'll revisit this issue.
-
Thanks for the update John. :)