[mythtv-users] FW: New Source Forge Project MythStreamTV

[Joshua Ebel]

You're completely right about changing the way the MythStreamTV
documentation refers to the files that Myth has recorded. This is totally my
fault by assuming that the .nuv files were in fact Nuppel video files. I am
updating the documentation now.

The other option would be for some poor soul to integrate the Nuppel video
format into the Videolan client. This would allow things to remain the same
for the operation of Myth on everyone's system while allowing MythStreamTV
as a new feature for all. Not just those with the correct hardware.

As for a shift in the container the Myth would/could by default store in.
I'm sure it would be hard to get many others to change how things are unless
there was a great advantage by switching. I'm not a codec wizard or
anything... Just a logical observation I suppose. Personally I agree with
you and would prefer a standard mpeg 1/2 container. That suits my needs
better. But someone with different needs (ie: a less powerful CPU or less
hard disk space etc.) could disagree with that.

Thank you for your comments and information. 

-Joshua Ebel
joshebel at gmail.com

-----Original Message-----
From: mythtv-users-bounces at mythtv.org
[mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Joseph A. Caputo
Sent: Tuesday, January 18, 2005 1:33 PM
To: Discussion about mythtv
Subject: Re: [mythtv-users] FW: New Source Forge Project MythStreamTV

On Tuesday 18 January 2005 14:16, Joshua Ebel wrote:
> You've assumed correctly. Unfortunately there is no support in
> Videolan Client for the MPEG-4/RTjpeg Nuppel video files.

To avoid confusion, you might want to stop referring to the files 
produced by PVR-x50, ATSC or DVB cards as "NuppelVideo".  They are not 
NuppelVideo, they are standard MPEG-2.  The ".nuv" extension is just a 
convenience to simplify the way Myth handles files internally.  It 
should be made clear that this solution will *only* work if:

- you record your programs with a hardware MPEG encoder card (PVR-x50, 
M-179, etc)
OR
- you receive programming in MPEG-2 a la DVB/ATSC/HD

AND
- you do not automatically transcode recordings


Actually, I'm starting to wonder if, with the increasing popularity of 
hardware encoders and digital broadcasting, if it wouldn't make sense 
to enable the internal transcoder to output a standard MPEG container.  
That way only files that were originally software-encoded would need to 
be in Myth's Nuppel container; everything else could either remain 
MPEG-2 or be transcoded to MPEG-4 in an MPEG container.  I imagine this 
might get a little dicey regarding audio sync if there were cut 
points... actually, it would probably be possible to transcode to 
NuppelVideo if (a) the source is already Nuppel, or (b) there are cut 
points, otherwise, transcode to a standard MPEG container.

...come to think of it, you could probably do this now by turning off 
auto-transcoding and instead running a custom JobQueue job that runs 
transcode or mencoder to transcode down from MPEG-2... hmmm, I might 
give that a try... no cutpoints, but you'd get the benefit of 
transcoding to a smaller codec while preserving the ability to stream.

Sorry, I realize this is not necessarily your concern in relation to 
mythstreamtv, but I thought it an idea worth "putting out there", as it 
may be of interest to some folks following this thread.


-JAC
_______________________________________________
mythtv-users mailing list
mythtv-users at mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users