[mythtv-users] Automatic mythtranscode

Isaac Richards ijr at case.edu
Mon Jan 17 10:56:30 EST 2005


On Monday 17 January 2005 01:41 am, Brad Templeton wrote:
> On Sun, Jan 16, 2005 at 09:09:53PM -0800, Chris Petersen wrote:
> > This is why I wrote nuvexport.  MythTV can't play anything other than
> > nuv files or mpeg2 files (which annoyingly also must have the incorrect
> > .nuv suffix on their name), so even if you transcoded them with

It plays most other types of files just fine, though for things to show up in 
the recorded programs interface they must follow the internal naming 
convention.

> I am curious about the history of this.  Was Nupplevideo the best choice
> at the time the system was developed?  I have often wondered why Myth
> uses the nupple player rather than taking something like mplayer and
> adding Myth features to it (Myth OSD, keyboard interface, commercial skip
> and editing modes.   Aside from the fact that mplayer seems a very actively
> developed project with support for huge numbers of different video formats
> (including nuv and ty) it would also mean a single player for DVDs, videos
> and TV recordings with a single UI.

You've never looked at the mplayer source, have you?

> No, I'm not demanding the work to recode it this way now, just curious
> about the design reasoning.   Was nupple the only good mjpeg grabber at
> the time?

It's not mjpeg - rtjpeg has much lower cpu usage when decoding.  I started 
with it because it's speedy, and the nuppel encoder/decoder framework was 
small and halfway decently written, so it was easy for me to rewrite it into 
something useable.  That would have been impossible with mplayer or xine.

Isaac


More information about the mythtv-users mailing list