[FFmpeg-devel] [PATCH] Only output necessary NAL units in H.264 extradata in SDP

Michael Niedermayer michaelni
Mon Apr 20 15:10:25 CEST 2009

On Mon, Apr 20, 2009 at 08:26:45AM +0200, Luca Abeni wrote:
> Hi Michael,
> On Sun, 2009-04-19 at 22:06 +0200, Michael Niedermayer wrote:
> [...]
> > > Maybe we should start a new thread collecting requirements and design
> > > ideas for this new streaming protocol (or to see how many developers
> > > are interested in working on it).
> > 
> > anyone interrested in this should maybe look at the thread with subject
> > [NUT-devel] nut-np (nut based network protocol)
> > its from 2006 but still its a cute 3 page replacement for all RT*P specs
> Thanks for the pointer! I am going to search the nut-devel archives and
> to read this thread.
> Just a question before starting to read: so the idea is to have a format
> (NUT, or similar) encapsulating audio and video, and to stream it over
> some kind of network protocol? Or this proposal would allow to stream
> ESs (as RTP does)?

the idea pretty much was to send nut packets, because there is significant
overlap between a container format for files and a network protocol
handling the same data. (timestamps, metadata, error recovery, seperating
packets, seperating streams, ...)
The differences pretty much are AFAICS down to
* telling the server to seek somewhere
* acknowledge & retransmitt if the underlaying protocol does not gurantee
  delivery (UDP)
* numbering the packets so one can refer to them in the protcol
* telling the server to (not) send some stream (like audio of some language)
* choping large nut packets up if the underlaying protocol has size limits
* sending error messages if something goes wrong

> Ok, I am going to read searching for an answer :)
> > comments welcome of course, here as well as on nut-devel
> I hope replying on ffmpeg-devel will be ok (I'd like to avoid
> subscribing yet another mailing list...)

of course
i was hoping when i started that thread that people would read&review
and make suggestions for improvments. For example it surely is too
vague about a few things like which port to connect to.

Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Frequently ignored awnser#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20090420/0344f18f/attachment.pgp>

More information about the ffmpeg-devel mailing list