search for: lace

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

...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 in 'bandwidth 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...

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

...latency on the sending end. It also > reduces the amount of memory required as well. > > In your page format, you store the segment count and a segment table and a > CRC in the front of each page. Having experience with ATM networking and > some hardware, it is actually better to place any checksums or CRCs at the > end of a packet. > > Another improvement can be made to the segments. > > Instead of a segment count and a segment table in the beginning, just > encode the length of each segment at the front of every segment. Segments > can be anywhere from 1...

....B.^.âÌà 00000180 03 18 01 27 0D 0A 49 6E 76 61 6C 69 64 20 73 79 ...'..Invalid sy 00000190 73 74 65 6D 20 64 69 73 6B FF 0D 0A 44 69 73 6B stem diskÿ..Disk 000001A0 20 49 2F 4F 20 65 72 72 6F 72 FF 0D 0A 52 65 70 I/O errorÿ..Rep 000001B0 6C 61 63 65 20 74 68 65 20 64 69 73 6B 2C 20 61 lace the disk, a 000001C0 6E 64 20 74 68 65 6E 20 70 72 65 73 73 20 61 6E nd then press an 000001D0 79 20 6B 65 79 0D 0A 00 49 4F 20 20 20 20 20 20 y key...IO 000001E0 53 59 53 4D 53 44 4F 53 20 20 20 53 59 53 80 01 SYSMSDOS SYS€. 000001F0 00 57 49 4E 42 4F 4F 54 20 53 59 53 00 00 55 AA .WINBO...

...ang build system. What I need to add into current build system are -I$ACE_ROOT ..............(adding a path for ACE header files) -I../LogManager .............(adding a path for my custom header files) -L$ACE_ROOT/lib .........(adding a path for ACE Library) -DACE_NTRACE=0 .......(define a Macro) -lACE ..............................(specifying an ACE library) What I know is Makefile.am if it is GNU autotools. But I can't find this file from current LLVM/Clang source code. And also I wonder if any people should use any kind of logging or tracing method to debug and trace LLVM/Clang. (This is...

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

...fts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list...

...fts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http:// www.ietf.org/ietf/1id-abstracts.txt. The list...