search for: laces

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

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

Hi all, Here are some thoughts on Vorbis framing, which may make it easier to stream Vorbis in real time. The suggested changes also move more audio data closer to the beginning of each page. A note in the Vorbis framing spec suggests a simple 'bandwidth limited' mode whereby important information is placed at the front of each page and the end of each page is discarded. When operating

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

Has anyone been able to get the Lace (ajax chatroom) ported over to Ruby for a Ruby on Rails implemention? (The current version is PHP-based) ... or is there a ROR-chatroom distribution that exists? Thanks! -- Posted via http://www.ruby-forum.com/.

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

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

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

>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

Hi, Guys: Does anybody know is it allowed for the OGG segment including more than one Vorbis frame? Or should I consider about that? I am working on OGG+Vorbis player now, but met some cases that OGG segment includes some garbage bytes after one Vorbis frame, I want to know whether it's safe if I just drop the left bytes after decoding one Vorbis frame? I read the page

So, version .16 has come out and I wouldn't mind upgrading. The thing is, I have to patch my Wine source code for a particular game. I guess I have to remove the Wine version I have now, patch the .16 and compile the source code? If there is another way, please let me know. Though, my main question is if I uninstall Wine, will it take thing installed with it; I mean, does .wine still exist

Hey all, If my understanding is right, there's a serious big in vorbisfile.c, in the routine _fetch_headers(), which will only show up when comment packet spans multiple pages. The code to read the first 3 Vorbis packets ogg_stream_pagein() once, then calls ogg_stream_packetout(). The problem is that ogg_stream_pagein() only adds a single page to the ogg stream state, whereas

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

David Flynn has proposed a new Ogg Dirac mapping. The draft is here: http://davidf.woaf.net/dirac-mapping-ogg.pdf This is a much bigger break from other codecs than my draft (at http://wiki.xiph.org/index.php/OggDirac). We talked a bit about it on IRC today. Below is my summary; hopefully David can correct anything I got wrong or misleading. Comments? There are two main differences

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

> > Looks like a disk sector to me too. However the partition table > is further on. See: > > https://en.wikipedia.org/wiki/Master_boot_record#Sector_layout So that reference says the "classical generic MBR" partition entry # 1 is offset 0x1BE. Which in this image is right in the error strings (?) section. 00000170 13 59 5A 58 72 09 40 75 01 42 03 5E 0B E2 CC C3

Hello, I want to state my question again because I think the question I wrote was vague or not clear. I'd like to know - on which file I need to work, and - on which part of the file I need to modify - to add a path for 3rd party(ACE) header files, - to add a path for my custom header files, - to add a path for 3rd party(ACE) Library, - to define a Macro, and - to specify a 3rd party(ACE)

I had already looked at bug # 27298 (The Witcher 2 Slow Performance on any setting.) as well as http://appdb.winehq.org/objectManager.php?sClass=version&iId=23504&iTestingId=64212 My problem is it not laucher is not even starting which is different from the performance problem. When I tried the 'WINEDEBUG=-all wine application.exe' I still get 'fixme:heap:HeapSetInformation

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>