Mytharchive setup

Maybe your apt-get or yum has not been set up to correct repositories to get these packages. So you might have to update your sources. Xvfb can be installed from atrpms while dvdauthor is not on the usual fedora and atrpms repositories, but it can be installed with the command:. On Fedora Core 3 mjpegtools can be installed from atrpms.

Some versions of transcode on atrpms versions around transcode If you use one of those versions, you will get green squares instead but the menu will work. There are some details on this problem here: [1]. Note: This is his home dsl connection and that it has been compiled on Fedora Core 4.

Pressing the number keys will jump to that thumb image. The most common reason for this is python is missing some required modules.

The script requires imaging PIL and mysqldb both of which are not part of a standard python install so have to be installed separately. This is also a symptom of an incorrect temporary files setting. Note that the user running mythfrontend needs write access in this directory, regardless of the user running mythbackend. Once you have addressed the above dependencies and permissions, you may need to clear out your temp DVD directory to get the log viewer to start over, making files with the correct support.

Finally, the problem might be that your frontend hasn't permission to write to one of the two directories that you've configured in MythArchive's setup. The easiest way to figure out what's wrong in a case like this is to start mythfrontend with it's stdout and stderr pointed to a useful logfile, if you don't already do this.

Also remember that mytharchive has it's own log file located under the work directory you set on page 1 of the mytharchive settings. It's possible the user you're running the front end as as opposed to the mythtv user doesn't have write permissions on the MythArchive temporary directory. Either make that directory tree writable by the user running the front end, or change the MythArchive temp directory to one that user can write to,.

This can happen if something should prevent the script from completing like a crash, a reboot or if you kill the script before it finishes. When this happens the script leaves behind a lock file which prevents the script from restarting. In order to fix this you need to locate the lock file called 'mythburn.

The user MythArchive is being run as does not have access rights to write to the dvd. For example, with Gentoo it would be necessary to execute:. This is caused by the media monitor mounting and locking the DVD. The fix until a better way can be found is to tell the media monitor not to monitor the drive you use to burn DVD's. You simply add it to the list of devices to ignore on the fourth page of general settings.

Just unchecking the option to monitor devices doesn't seem to work. If the source of recordings is a hardware encoding tuner card MPEG-2 files and the card allows the capture resolution to be set PVR-x50 for example , a lot of re-encoding time can be eliminated by setting the capture resolution to a DVD compliant resolution.

The internal player is known to have this problem. I have to get lirc and ivtv working again - before I get mythbackend working. I have a stock install of mythbuntu 7. One buffer is full when the other is empty! Aborting Thanks for any input, Tim. I have solved it for myself by pre-cutting the videos using projectx. Search for my name and projectX and you are sure to find a few hits on this. I have had a few files that projectx fails on but mythtranscode and mythreplex have no problems with so YMMV.

I am still using 0. Happy Saturday Night! I'm trying to use mytharchive to create a DVD copy of an episode of a show so my wife can play it in her Classroom. I'm running into trouble, however, because I have my system setup with a dedicated backend which stores all the recordings locally , and several remote frontends.

It seems that mytharchive needa a 'local' copy of the file to process it, but that's not possible with my setup I thought of temporarily installing mythfrontend on the backend server, but I don't have a dvd burner on that machine, so I'm stuck there too.

I looked it up in the wiki, and it reccommends the following: "MythArchive reports that files are not available locally MythTV usually streams video if you have a separate frontend and backend. MythArchive cannot use streamed video: it needs to be able to access the file locally. I have no problem with NFS, and I have mapped the "recordings" folder to a local folder on my frontend machine but I'm not sure how to create a "frontend storage group" specifically.

I konw how to create a storage group for the backend, but not for the frontend. So how can I trick mytharchive into thinking my recordings folder is on the local machine? I suppose I could create a storage group for the backend that would make the backend connect via NFS to the share on my frontend which is actually an NFS share from a physical drive on the Backend but that seems like it could create a black hole or something worse and seems incredibly hoaky besides. Has anyone else out there managed to use mytharchve to make a DVD from a recording file that is stored on a remote backend?

Is there any non-stupid way of doing it that doesn't involve major hacking? Any advice would be greatly appreciated. Thanks, Josh Yes, it can be done.

I do it all the time, you will need to make the location of the recordings a writable NFS share then mount it with the frontend in the same directory structure.

So when you goto for example. Because it is. MythArchive is a plug-in which allows one to burn recorded programs to DVD. When I tried this, after wending my way through the menus and launching the burn, it hung at the log viewer, with no messages displayed.

The solution, as documented here , was to install the MySQL-python and python-imaging packages:. After that, I was able to get log output when trying to burn, but I kept running up against dependencies. Each time I got an error it was because some tool was not installed, so I had to find out which Fedora package contains that tool and install that package.

Here is the result:. Also, while there is a checkbox when setting up a recording which implies that you can overwrite a DVD-RW disk while recording, that has not worked for me.

If I don't blank out the disk first I get an error in the growisofs step. But it's not. I have to blank the disk manually before recording, using. Jump to: navigation , search. Navigation menu Personal tools Log in.