Thanks misterflibble! I'll give it a try this evening (or next) and report back on the results.

Just to be sure... I downgrade mysql-common to version 4.0.whatever (in my case it was version 4.0.22-2) and allow whatever dependent packages that were upgraded/installed by the earlier mysql-common 5.0 upgrade to be removed. Theoretically this downgrade will remove the libmysqlclient15off package and python2.3-mysqldb 1.2.1-p2-1, but if it doesn't I will have to remove them. I will then have to install python2.3-mysqldb version 1.2.1c2-1.

misterflibble

Hopefully your problem with the DVD menus and NTSC should now be fixed. If you could update to the latest svn version of mytharchive and try again. The only question mark is whether the font sizes needed to be scaled or not. Let me know if the text now looks too small.

Yesterday I was able to build and install SVN versions of mythtv, mythplugins, and myththemes following the wiki instructions. However, when I try to build MythArchive I get the following error which is also shown on the wiki page without a solution:

I have manually updated both libiec61883 and libraw1394 to the latest versions from the Linux 1394 website, but I still get this error.

I found the same problem on the mythtv mailing list, and the only proposed solution was to add --disable-firewire to the ./config statement. However, this has no effect.

Any more ideas on how to get around this problem?

Ok, now I see that they meant to disable firewire in the mythtv build, not mytharchive, but there's got to be a better way that keeps firewire support in tact. In the meantime I'm re-building mythtv with firewire disabled since I don't use it.

Whew! Thanks to misterflibble, mysql is working properly again.

Paul H. - I upgraded to the most recent svn of mytharchive and tried running it again. I finally figured out where the temp directories and files you referred to in an earlier post are actually located. The config, logs and work directories were created as was the mydata.xml file, and the permissions are set to mythtv, which seems correct. However, I'm still having the same problem when I try to archive recorded programs, which is that nothing seems to happen when I click on "Finish".

I only have one log file in the logs directory - mythburn.log. Its complete contents are given below:

Looks like you still need imaging (PIL) module for python (aka python-imaging). I think this one installed without any foolishness.

Thanks, DoomedTX. I assume you mean python2.3-imaging rather than python-imaging?

I installed python-imaging which I think also installed python2.3-imaging and at least one other package. Nothing that killed the system though.

Now that I've managed to install Mytharchive without firewire, hopefully paulh can address the next problem:

When I select the programs to archive, I move down and check the "Use Cutlist" box. However, when I get to the archive files menu it says "no cutlist available" and the cutlists don't seem to be used. I'm going ahead with the burn just to see if it cuts anyway, but I'm not hopeful.

Well, looks like I was getting ahead of myself; the DVD project didn't even finish. After an hour of encoding the first of 4 videos (which is excessively long compared to mythburn) the process suddenly stopped. The last line in mythburn.log, which kept getting updated, was that it was working on frame #83589 which is the same frame # it was on for about 15 minutes.

After this failed attempt I suddenly had no programs in the database and got a blank page when I tried to view mythweb. A reboot seems to have fixed both of those problems. I guess I'll be leaving mytharchive alone for awhile unless there's something specific paulh wants me to try for troubleshooting.

I've installed python-imaging (which also installed python2.3-imaging), so at least now mytharchive starts to do something.

However, it dies very soon after starting and complains that it can't find mythreplex.



I have found mythreplex located somewhere deep in the svn checkout folders I downloaded, but I guess the install routines didn't actually install it. I also found it in /usr/lib/debug/usr/bin.

Paulh: Success with mythcenter NTSC and 3+ recordings!
I gotta admit though, I can just barely read the description text on a 28'' hdtv at 720p. I think it'd be unreadable for anything less.

No help on the mythreplex, sorry. I'm guessing that should have installed with mytharchive but I'm not sure.

Here's another problem I have others may want to think about before trying to install MythArchive (too late for us cmaines):

The mythweb in the svn version seems to use a different directory structure than the Knoppmyth R5B7 did. That means that mythburn and mythstream are no longer available. I don't care too much about mythstream but just spent 2 hours trying to install mythburn since mytharchive isn't working for me. I was able to get the correct header.php patched but when I click on the MythBurn DVD link I get the dreaded "Unknown Module" error. Tried lots of things including the full path to mythburn's welcome.php page, but I keep getting the error.

I sure hope mytharchive's development moves along quickly now that I have no DVD burning capability. In the meantime I'll be forced to transfer the individual MPG files over the network to another computer and burn them from there. Looks like it's really time to get a wire in to the MythTV box; wireless will be unacceptably slow!

Doomedtx: Have you tried installing mythburn-ui to access mythburn from inside of mythfrontend? It seems to work with the svn versions I've tried it with. I gave up getting the web interface to work too.

I haven't, but I certainly will. In the meantime, I woke up this morning realizing why mytharchive utterly failed the first time. On the Linux box where I'm writing this message, my /tmp directory is a separate partition with gigs of free space. My MythTV box is a different story, with /tmp being part of the 1-gig-left / partition. I'm going to map /tmp to my unused /cache partition left over from the upgrade and try another mytharchive run. I'm still predicting that the commercial cutting won't work, but hopefully it won't bring down my system.