similar to: AW: .NET tagging library for ogg Vorbis and ogg FLAC

On Fri, Apr 20, 2007 at 03:10:09PM +0000, Mathias Kunter wrote: > 1) Is it valid to insert an "empty" page into the stream which simply contains the binary value 0 for the page_segments counter, and which therefore contains no segment table nor any packet data? I'd like to do this to produce a gapless page sequence number so that I don't have to re-number all following pages,

>> 1) Is it valid to insert an "empty" page into the stream which simply contains the binary value 0 for the page_segments counter, and which therefore contains no segment table nor any packet data? I'd like to do this to produce a gapless page sequence number so that I don't have to re-number all following pages, so that I don't have to re-compute the checksums of all

Hello all, my name is Mathias, I'd like to ask about some details of the OGG format because I'm quite new to it. I'd like to write a native .NET library for reading and writing Vorbis comments. It's going to be open-sourced as soon as it's finished. So here it goes: 1) When packing (Vorbis) packets to OGG pages, does a new packet always begin on a fresh OGG page? Within the

Hello, I've mainly finished the native ogg Vorbis tagging .NET library. It already works well for reading and writing the vorbis comments for the files I tested. The library only rewrites the entire file if it has to, and adds 2 K padding in this case so that further changes of the comments won't make it nescessary to rewrite the whole file again. I found out foobar2000 also does it this

Hi, I think we can start by defining an official field name at www.xiph.org/vorbis/doc/v-comment.html which is used as a file system link to an existing image file. I suggest the field name to be "PICTURE". What is ogg MNG? Is it a container format for PNG files which should be embedded in OGG files? If I understand correctly, the picture would be placed in a different logical stream

Amit Ashara wrote: > 1. Since the stream I am working with is a mono channel, what should be > the advised page_segments to use. I am using an embedded system so > keeping the flash and SRAM usage are vital for the development. The number of channels has no impact on this at all. > 2. In the OpusTag the is the libopus a mandatory field? Yes.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I thought I would separate this out into a separate mail since it's not comment specific stuff -- There seem to be a couple of inconcistanies in the Ogg spec as regards to lacing values: *) "The raw packet is logicaly divided into [n] 255 byte segments and a last fractional segment of < 255 bytes." However, in the wild, I've

Hello to the people reading this list! I am developing tagging support for ogg vorbis in Nero products and we are currently thinking of supporting cover art in ogg files. What is the current state of proposal for cover art in ogg files? Is this http://wiki.xiph.org/index.php/VorbisComment#Cover_art still the latest information? Regards, Goran -------------- next part -------------- An HTML

Hi,all I don't quite understand why vorbis I spec dictates that "Ogg stream must be unmultiplexed". Ogg can include both audio and video, that means one Ogg stream can both have vorbis and theora multiplexed. How vorbis I spec say could not allowed? Thanks! Best Regards, Emily Gao Tel:86-21-38764688 ext:6392(WWID 0760) VIA-VEPD-APP-CODEC -------------- next part

Everyone, Pleased to announce the release of libogg version 1.1.1. This is a bugfix release on last year's 1.1 release. Source archives are available from our new download site: http://downloads.xiph.org/releases/ogg/libogg-1.1.1.tar.gz http://downloads.xiph.org/releases/ogg/libogg-1.1.1.zip Maintained from the /releases subtree on svn.xiph.org. This release is tagged in the

Everyone, Pleased to announce the release of libogg version 1.1.1. This is a bugfix release on last year's 1.1 release. Source archives are available from our new download site: http://downloads.xiph.org/releases/ogg/libogg-1.1.1.tar.gz http://downloads.xiph.org/releases/ogg/libogg-1.1.1.zip Maintained from the /releases subtree on svn.xiph.org. This release is tagged in the

Beside that, multiplexed logical streams suffer from pretty bad software / hardware support, isn't it? It's better to display album art as text if the player doesn't recognize the base64 album art, than being unable to even play the file. ----- Urspr?ngliche Mail ---- Von: Kyungjun Lee <kjoonlee at gmail.com> An: xiphmont at xiph.org CC: vorbis-dev at xiph.org Gesendet:

Howdy, yeah, I've finally collected all your feedback on my I-D on the Ogg encapsulation format, many thanks to all of you! Below, I've listed the changes that I have made to the previous version and the attachment contains the complete new I-D. If there are any more change requests, please send me wording proposals as it's easier to include. :) Monty, in case you are doing any

Howdy, yeah, I've finally collected all your feedback on my I-D on the Ogg encapsulation format, many thanks to all of you! Below, I've listed the changes that I have made to the previous version and the attachment contains the complete new I-D. If there are any more change requests, please send me wording proposals as it's easier to include. :) Monty, in case you are doing any

Hi, I'm currently trying to implement the Ogg specification in pure Java from scratch. (I know, something like that does exist, but that's a rewrite from C, at least that's my impression). I'm a bit confused with the number of lacing values/segments in a page, and the maximum length a page can have. The specification says, that there can be 255 segments in a page, 255 bytes each

Hi, There is something I don't understand about the page_segment and segment_table values in the documentation. As I understand it, the segment table consist of as many bytes as specified in page_segment, PLUS one trailing byte with a value between 0 and 254. I've looked at some files that has a Comment tag so large, that it is spread over two pages. Here, the first Page Header (not the

Hi all, I noticed the following Subversion commit today: r6719 | xiphmont | 2004-05-18 16:04:53 +1000 (Tue, 18 May 2004) | 11 lines Updated doc to reflect current proposal... Not as much a proposal at this point actually; this is the way I'm now implementing it. Although we're still in the 'RFC'/'look for horrible lossage' stage, this is close to being

Hi all, just letting you know that I am about to submit the final version of the Ogg 1.0 file format Internet-Draft to the IETF. It is due by today (March 3, Monday - Internet Draft final submission cut-off at 09:00 ET) for the next IETF meeting and I expect they will promote it to RFC status at the meeting. Please send any last-minute changes to me. Cheers, Silvia. <p><p>

Hi all, just letting you know that I am about to submit the final version of the Ogg 1.0 file format Internet-Draft to the IETF. It is due by today (March 3, Monday - Internet Draft final submission cut-off at 09:00 ET) for the next IETF meeting and I expect they will promote it to RFC status at the meeting. Please send any last-minute changes to me. Cheers, Silvia. <p><p>

Hello, I have in the past few days played a bit with libogg. My goal is to learn enough of it to try wrapping current tarkin codecs into an ogg file, with vorbis sound eventually. I did work on a small program which allows you to easyly (de)multiplex Ogg files in a way which seems to conform to the docs. You can do things like: oggmux in1.ogg in2.ogg in3.ogg - mux3.ogg oggmux mux3.ogg -