search for: lacing

-----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 found an example where the first lacing value (in this case out of 13) is less than 255 (190 in the example I'm looking at). *)...

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 that the lacing values for audio packets are rather wild. A hex string looks like: 9D 9893 FFFF 08FF FF15 5352 514E 5595 8F92 FFFF 1BFF FF11 FFF8 FF...

...th limited' mode, packets modified in this way could offer slightly better audio quality. This message is based on a message I sent to 'Monty' on 29/7. He didn't offer any comments, so I thought I would run it by this mailing list. Does this suggestion make sense? POSITIONING OF LACING VALUES The format for a Vorbis page is something like: header, lacing values, data. When building this in hardware, it is necessary to buffer all the lacing values, then identify each data segment. It would be easier if each lacing value appeared at the beginning of the relevant segment, avoidi...

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 + 27 bytes header = 65052. But later it states the maximum size of a page is 65307 which is strangely 255*256+27. Now where does that extra segment com...

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

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

...t without the "stop the press" fancier encoding. > I'll take this opportunity to mention my pet idea (don't think I ever mentioned > it on ogg-dev), to start with a byte, then, if larger than 255, add two bytes, > then for packets larger than 255+65536, add 4 bytes. This lacing is worse > than the current one only for packets between 256 and 511 bytes (admittedly > a probably common case, but adding only one byte). Now that you mention > flags, lacing type could be put in flags, so this worsening could be avoided > too. So this would be: len = read_uint8() i...

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

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

...en 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 ogg_stream_packetout(), loops until it finds a non-255 lacing value. So, if the comment packet is larger than one page, all lacing values will be 255, and ogg_stream_packetout will start reading uninitialized memory. The relevant part of _fetch_headers() is here: i=0; while(i<3){ ogg_stream_pagein(&vf->os,og_ptr); while(i<3){...

...ixed 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 ogg pages and their lacing values to exactly determine where the packets start and end. It just wasn't clear to me that the lacing values signal the borders of the packets in such a clean way (this actually isn't very easy to read out from the specs for a person which is new to ogg). I thought padding of the first p...

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

...ire page in memory. > > When networking, it is always a problem when fields like the length and > checksum are stored at the beginning of a packet because the entire packet > must be stored in memory before being sent. ATM (Asynchronous Transmit > Mode) AAL5 solved this problem by placing the length and CRC at the end of > the packet. In ATM, each packet is chopped up into 48 byte cells where a > 5 byte header is prepended. A bit in the 5 byte header indicates that the > cell is the last cell of a PDU and the last 8 bytes contain a trailer, 2 > unused bytes, a 16-bit l...

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

...r chunk. These chunks are called "Ogg Segments". They are only a logical construct and do not have a header for themselves. A group of contiguous segments is wrapped into a variable length page preceeded by a header. A segment table in the page header tells about the "Lacing values" (sizes) of the segments included in the page. A flag in the page header tells whether a page contains a packet continued from a previous page. Note that a lacing value of 255 implies that a second lacing value follows in the packet, and a value of less than 255 marks the...

...r chunk. These chunks are called "Ogg Segments". They are only a logical construct and do not have a header for themselves. A group of contiguous segments is wrapped into a variable length page preceeded by a header. A segment table in the page header tells about the "Lacing values" (sizes) of the segments included in the page. A flag in the page header tells whether a page contains a packet continued from a previous page. Note that a lacing value of 255 implies that a second lacing value follows in the packet, and a value of less than 255 marks the...