similar to: Ogg Vorbis Framing

I'm trying to write a program that reads an ogg stream and check all the CRC values along the way. But I have big trouble with computing the checksum, or at least I never got checksums that match the one that is in the ogg file. I do set the CRC field in the header to 0 before calculating it. I start with 0 and have no xor at the end. I feed page header with all lacing values and the page

On Wed, Aug 13, 2008 at 3:05 AM, ogg.k.ogg.k at googlemail.com wrote: > And that's the canonical way AFAIK. Comparing times computed from > the granpos you get from pages you get from a bsearch requires good > knowledge of the codec, whereas comparing granpos can seek within > any codec. No. it's in general impossible to calculate the granulepos that corresponds to a

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>

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 Aaron, thanks for your thoughts on improving the Ogg encapsulation format. As Monty was the person who developed the specification, I am forwarding your suggestions to him. Maybe some of these changes can be adopted into a future version of the Ogg encapsulation format. Best Regards, Silvia. Aaron Williams wrote: > Hi Silvia, > > After reading the RFC on the ogg streaming

2009/6/26 Adam Rosi-Kessel <adam at rosi-kessel.org>: > Can I fix the checksum with a hex editor? I just realized that the hogg tools will fix the CRC issues (by design accident: hogg ignores the CRC on reading but sets it correctly on writing). "hogg rip" rewrites the pages (fixing the CRC), and "hogg reconstruct" also rewrites the I've uploaded the outputs of

On Tue, Aug 12, 2008 at 5:46 AM, ogg.k.ogg.k wrote: > This could be something to add to Skeleton. Kate (and probably CMML) > needs the one-packet-per-page thing also, and any discontinuous codec > probably needs it as well (well, not *need*, but no good buffering without > it). It's trivial for a muxer to do, and it's transparent to a demuxer. That's a good idea. Any

Hi, I'm reading the logical bitstream framing doc, and I have a question about lacing values, which encode the length of a packet (I think). For example, the values 255, 255, 243 encode a length of 753. I'm wondering whether a format more like this was considered length bytes encoding 0-254 1 value in one byte 255-65534 3 one 255 + value in two bytes

-----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

Someone could tell me the question about the question about lacing values values of segments. I mean i know what happens about segmentation but reading ogg specs i didn't understand this lines: "We simply add the lacing values for the total size; the last lacing value for a packet is always the value that is less than 255. Note that this encoding both avoids imposing a maximum packet

I noticed that, when decoding an ogg vorbis file that was encoded with the xiph library, that the comment header and setup header are encoded on one page. Okay, the vorbis documentation says you can do this, no problem. My question is, the lacing values seem to indicate where the packet boundaries for the two of these are, is this required, or is this just a hint? Further, I'm seeing

Hello, I recently added discontinuous stream support to libogg1. The patch is attached. I also wrote Writ codec for libogg1 (based on original code by Arc), and sample Writ encoder (SubRip to Writ converter) and decoder. Is anybody interested? WBR, Roman. -------------- next part -------------- Index: include/ogg/ogg.h =================================================================== ---

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

>Searching for 'vorbis' to find the packet boundary is wrong however. >The lacing values in the Ogg page header tells you exactly where the >division is. OK, so given the fact that a page can also contain multiple packets this means that the lacing values of one page could be like the following example: 255 255 189 (something less than 255, indicating that a new packet starts

I saw the talk Seeking is hard: Ogg design internals by Ralph Giles at linux.conf.au MEL8OURNE2008. Some suggestions: In the page checksum section of http://xiph.org/ogg/doc/framing.html please add a link to the wikipedia page, since there are links to faster variants of table driven CRC calculation there - though it is not a thing of beauty. http://en.wikipedia.org/wiki/Cyclic_redundancy_check

Hi, I'm having lots of difficulties with BCM5719, which is the default network card of HP Proliant DL 360 G8 servers. I can get a few ping replies before I get a couple of these: bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting Then everything hangs. Can not log in using ssh.

Ralph, thanks for your help. >>Since the length of the precedent identification header is fixed, this even is a fixed offset >>into the logical ogg stream. >This will work for all the vorbis-only files I've seen (because no one >pads the first packet). You should really implement a proper ogg parser, >but by all means get a hack working first. I will of course use the

Asic-technologies.com We make ASIC Bitcoin Mining Gear using the ASIC chips Sourced from Taiwan. 3.1 -3.3 GHash/sec 4 Board (has 32 chips) - 15 BTC 9.3-9.9 GHash/sec 12 Board (has 96 chips) - 30 BTC Each module board uses about 39 Watts of power. Mining board's supplied (No case) power supply , On-board heat sink , USB connectors. Ready assembled (suggest that you insert board's into a