Import DVD problems
Submitted by joltman on February 19, 2007 - 6:12am
I've been playing with Import DVD lately, and have been having problems. If I import as ISO or Perfect quality, everything seems to work fine. But if I try Excellent or Good, it doesn't work right. When I do Excellent, it rips the file, and then does 1 of 2 passes of transcoding, but then just stops when the first job is done and doesn't do the second pass, and there is no video file in my videos folder. When I do Good, it appears to finish OK, but there is no video file. The mtd logs seem OK, but I couldn't figure out where the transcode logs are. Any help?
Re: Import DVD problems
I just wanted to let anyone else who's having the problem know that I fixed it. While looking around at something else, I found this post - DVD Rip fails to transcode - and since that mentioned lame problems, I re-installed lame and installed libmp3lame and ripping at Good works now. I haven't tried Excellent yet, but I assume it will work as well.
For what it is worth, I am
For what it is worth, I am having a similar issue in that ISO and Perfect settings work perfectly but Good and Excellent fail almost instantly. When selecting either Good or Excellent the Rip/Transcode interface momentarily flashes the progress bars but then tell me there are no jobs and nothing to do and would I like to hit 0 to rip a new dvd.
This is a default 3.2 backend-only install. I am manually launching mythfrontend to import the dvd. I also noticed that initially the Import DVD interface failed to start because mtd was not running. I'm curious to know why mtd is not configured to run automatically in the default install or if that has something to do with this being a backend-only install.
If you run mythfrontend
If you run mythfrontend manually then the mtd deamon will not start automatically. If the frontend starts on it's own or if you start it from the desktop the mtd gets checked and if it's not running then gets started up. You can see this in the mythfrontend.sh file located in /usr/local/pvr under the startmythdora array. If mtd isn't running after trying to do anything other then a Perfect rip then something is killing it.
"Please ignore the man behind the curtain"
Dennis
"Please ignore the man behind the curtain"
Dennis
Aha! It also might be worth
Aha! It also might be worth mentioning that I attempted to launch mythfrontend via the installed desktop icon but while it appears to try to launch it never actually does. The little M icon bounces around for a bit but mythfrontend never comes up. It seems that the only way it will start is if I call mythfrontend from the command line.
My eventual intention was to run the backend headless in a closet but as I anticipate using the ISO import feature frequently this doesn't seem practical. There is a thread on mythtv-users right now describing the desire to be able to pop a dvd into a frontend and have the disc ripped to the backend but it does not appear that mythdvd has this functionality at present.
My present understanding is that even though i have seperate frontend and backend systems, I should install the backend box w/ the combined frontend-backend option and that I will need to do all my dvd-importing on the backend. Does this sound correct?
Quote:Aha! It also might be
Aha! It also might be worth mentioning that I attempted to launch mythfrontend via the installed desktop icon but while it appears to try to launch it never actually does.
This is a tell tell sign that you didn't disable selinux during install. But if selinux is installed then the frontend shouldn't work at all. You really need to get this fixed.
My present understanding is that even though i have seperate frontend and backend systems, I should install the backend box w/ the combined frontend-backend option and that I will need to do all my dvd-importing on the backend. Does this sound correct?
That is correct.
"Please ignore the man behind the curtain"
Dennis
"Please ignore the man behind the curtain"
Dennis
Re: Quote:Aha! It also might be
This is a tell tell sign that you didn't disable selinux during install. But if selinux is installed then the frontend shouldn't work at all. You really need to get this fixed.
Hmm. The frontend system seems to more or less work fine. I definitely completely disabled both the firewall and selinux during install. I'm going to reinstall the backend machine as a combined frontend-backend system on different hardware shortly so I'll see if the problem persists.
Thanks.
Just an update on this
Just an update on this issue. Initially I had installed my backend as "backend only" and experienced the inability to launch mythfrontend via the installed desktop icon. To get mythfrontend running on the backend machine I had to call mythfrontend directly from the commandline.
I reinstalled my backend box tonight as a combined frontend-backend system and I was then able to launch mythfrontend from the desktop icon without issue. I was also able to begin an import dvd transcode job using the "good" quality setting.
I then reinstalled a third time as backend only, making absolutely sure selinux was disabled during the install(I see startup msgs saying disabling selinux at runtime and removing netfilter hooks) and I was once again unable to launch mythfrontend from the desktop icon but could successfully run it via the commandline.
Why would you want to run
Why would you want to run the frontend on a backend only setup? The shortcut doesn't work when you do that.
"Please ignore the man behind the curtain"
Dennis
"Please ignore the man behind the curtain"
Dennis
I'm glad you asked. I'm
I'm glad you asked. I'm definitely a confused n00b here. The chain of events was as follows:
1. Reinstalled backend system.
2. Existing frontend complains it can't connect to master backend server--I assumed that since the backend had been configured exactly as before the frontend should never realize it had been down...same ip, shared videos in the same dirs, nfs shares the same, etc.
3. Double check IP settings in mythtv-setup on backend box and mythfrontend settings on frontend box. Everything looks good. Still can't connect to the backend.
4. Occurs to me to see if mythfrontend on the backend box can connect to the backend server. Nope. Same error msg.
5. Check mythfrontend settings on the backend box. They are still at the defaults. Once I enter in the ip of the box and the right directories(/video/recordings,/video/videos, etc.) the frontend box and mythfrontend on the backend box can now connect to the backend server.
I'm still confused about why I would need to configure mythfrontend on my backend box for my frontend box to work. My assumption was that if I did a backend-only install I should only need to manipulate mythtv-setup and define the IP there. It's highly likely that I am just misinterpreting what is going on but this is the observed behavior thus far. In any case, that is how I ended up clicking on the shortcut. Might be worth removing the shortcut for backend-only installs.
Anyways, definitely appreciate the responses. I seem to be really adept at unwittingly breaking it during my first week. At the moment I've somehow managed to get the backend to demand a password to start mythbackend upon a reboot.
Quote:I'm still confused
I'm still confused about why I would need to configure mythfrontend on my backend box for my frontend box to work.
There is no reason to configure the frontend to make another frontend work. When you choose backend only, your assuming that this box will only be the server. Then other frontends will connect to it. I have made things so that when you choose backend only it is wide open for any frontend to connect to. All that you need to state on the backend only is to have the IP address entered twice in mythtvsetup under General. Then on any frontend only you have setup, simply edit the mysql.txt located in /home/mythtv/.mythtv and enter the backend IP address where it says database=.
Might be worth removing the shortcut for backend-only installs.
Done on the new version.
"Please ignore the man behind the curtain"
Dennis
"Please ignore the man behind the curtain"
Dennis
Re: Import DVD problems
Perhaps check your setup options. I have mine set to rip into /video/videos and temporary files in /video/temp.
--
Michael Palmer
I don't believe either of
I don't believe either of those are the problem, since I know the rip to directory is set right, and I'm pretty sure the temp folder is set right, and as I said ISO and Perfect work, it's just that Excellent and Good don't. If anyone can at least point me to where in the logs to look for the transcode stuff, I'd appreciate it.
You should have a .mtd log
You should have a .mtd log somewhere in that same directory.
"Please ignore the man behind the curtain"
Dennis
"Please ignore the man behind the curtain"
Dennis
You mean in the temp folder?
You mean in the temp folder? I found the mtd log and it looked OK, that's why I thought transcode had a different log. From what I understand, mtd and transcode are two different programs, correct?