Segher wrote:>> Another obvious solution is to make a substream that's nothing but >> vorbis comment header packets, and update that way. > > Why put it in a separate substream? We could just change the spec to > allow new headers halfway into the "normal" stream (the spec doesn't > specifically disallow it at the moment, even).Hmm. Maybe that works. I'd been thinking this wouldn't work with rtp, but looks like that's not really a problem. Does mean seeking by metadata is way slow. Monty, Jack, what do you think about this? -ralph --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> Hmm. Maybe that works. I'd been thinking this wouldn't work with rtp, > but looks like that's not really a problem. Does mean seeking by > metadata is way slow.For streaming that wouldn't be a problem, and for fx. saved streams you could just add some functionality to vcut to be able to autosplit oggs at new headers. -- Gerry --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Possibly Parallel Threads
- The metadata problem
- ogg stream-id options
- [: Re: [fwd] CVS: ogg123 rocks! vcut no so much so... (from: wayfarer42@postmaster.co.uk)]
- Fixing ogg vorbis corruption caused by bad metadata
- [fwd] CVS: ogg123 rocks! vcut no so much so... (from: wayfarer42@postmaster.co.uk)