[mythtv] mythtranscode request

Chris Petersen lists at forevermore.net
Wed Jul 14 16:28:05 EDT 2004

> There was a reason I didn't do that originally (I think it had to do
> with using stdout for other purposes).  In any case, it would be a
> trivial change.  I'll look into it when I get a chance.

Could always send to stderr like ffmpeg, mpeg2enc, etc.  And can turn it 
on/off with a --show-progress flag, etc.

> I need to know precisely wha ouwant though.  Would it be good enough
> if every hudred frames it wrote out 100/10000 frames to stdout, or
> (10/120 minutes)?   I don;t really want to use ncurses to make a
> human-readable variant, so if this is ok, it's what I'll do.

Yeah, that'd be perfect (both would be preferable, esp since vbr can 
sometimes make for inaccurate minute estimates), as long as I can get an 
accurate percentage (frames) with a human-meaningful number 
(minutes/seconds) ->

     Processed:  1000/10000 frames (2:15 minutes)

Wasn't talking ncurses at all, just something I can capture with 
nuvexport and parse.  Heck, you could use \r instead of \n if you feared 
it printing too much info to the screen and messing up scrollback buffers.

And to save printing, you could print out only every 5 seconds' worth 
(or whatever) of data (realtime or video-time) -- it would be more than 
enough for my needs.

> It has never been planned that mythtranscode handle anything other
> than mpeg2/nuv.  Isaac didn't want to deal with any other formats at
> the time, and that was fine by me.

well, then I guess I'm headed in the right direction with nuvexport.


More information about the mythtv-dev mailing list