[mythtv] MythArchive bugs and "fixes"

Martin van Es mrvanes at gmail.com
Thu Oct 23 07:35:54 UTC 2008

On Thu, Oct 23, 2008 at 00:07, Paul Harrison <mythtv at dsl.pipex.com> wrote:
> Martin van Es wrote:
>> 1. mythreplex fails because the audio stream was not correctly
>> detected by mythburn.py. After some debugging it turns out that
>> mytharchivehelper writes lower-case types in the streaminfo.xml, but
>> mythburner.py strictly looks for AC3 and MP2 (capitals). As a result,
>> no valid audio stream is found and the demux fails. Changing all
>> capital references to lowercase ones in mythburner.py fixed this
>> problem.
> Are you sure about that?

Well... I'm sure about the fact that mythreplex didn't die in a
"floating point exception" anymore after the changes. What I saw from
debugging output is that it found a valid audio stream, and the
commandline changed from "-v 224 -a 192" to only "-v 224". I have no
idea if this is wanted behaviour, but like I said: mythreplex didn't
choke anymore, at least not violently. I DID choke silently like I

> The first thing mythburn.py does in
> selectstreams() when reading  the  codec from the info  file is:-
>  format = string.upper(node.attributes["codec"].value)

I did try to follow the route of audio1 and audio2 but missed this
statement. I only saw the conditions and the fact that the info file
contained lowercase codec id's.

> in other words it converts the codec to uppercase and it is that that is
> stored in the audio1 and audio2 tuples that are passed to all the other
> functions where it's needed.

Ok, so then my changes are nonsensical and the floating point
exception of mythreplex is due to something else I guess. My apologies
for crying wolf.

> Personally I've never had any problem with  mythreplex but  I know it
> can break the audio sync for a few people.

I tried to manually run mythreplex on my pvr-500 recording but I
couldn't get it to start properly. I didn't quite understand the logic
behind the video and audio stream selection, but a little reading in
the mythburner code should help I guess.

> This is the first I've heard it  looping endlessly though.

I don't really know if it's looping. I only know it doesn't end in a
timely manner and writes LOTS of the 'appending 1 frame' messages to
stderr (and thus to mythburner.log).

>  The script also supports using projectx
> as an alternative to using mythtranscode/mythreplex. Did you try that?

No, I didn't find it in the debian repository and a quick search
learned it's a java-based tool  (that's what I found) and I didn't
feel like bloating my system.

> m2psd looks interesting but unfortunately it's not a real replacement
> for mythreplex though,

I realise that, since it's a quick 'n dirty solution for pvr-150 based
recordings. In that sense perfect for me.

> doesn't support TS streams for one thing and it
> doesn't look like you can select which audio stream you get.

I just thought maybe mythreplex could be "enhanced" with some logic in
m2psd for the case the stream is really only a simple video+audio one?
Maybe an extra alternative in the mytharchive settings for pvr-150 (et
al) users?

if but was of any use, it would be a logic operator

More information about the mythtv-dev mailing list