similar to: Lacing Values

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

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

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

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

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

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

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

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

> > E_ Under FreeDOS, SYSLINUX.COM doesn't seem to install ldlinux.* > > (specially when used with "--directory"), and there are no ([error]) > > messages; not even when executed with no parameters, or with > > "--help", or with "--version". The messages disappeared _after_ > > 5.00-pre7. > > Right, as Peter pointed out on

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

In usr/src/uts/common/xen/io/xnbu.c, function xnbu_cksum_from_peer() http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/xen/io/xnbu.c#110 we have this: if ((flags & NETTXF_csum_blank) != 0) { /* * The checksum is blank. We must fill it in here. */ mp = xnb_process_cksum_flags(xnbp, mp, 0);

Hey guys, I've finished my work on reading vorbis files (straight reading at either PCM sample lengths, or time lengths). However, I've run across a question. When you call vorbis_synthesis_read, I assume that increments the internal ptrs so you don't get the same data twice. The question is, what happens if you call vorbis_synthesis and vorbis_synthesis_blockin? Does the next call

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

When using -fPIE/PIC with function tracing, the compiler generates a call through the GOT (call *__fentry__ at GOTPCREL). This instruction takes 6 bytes instead of 5 on the usual relative call. With this change, function tracing supports 6 bytes on traceable function and can still replace relative calls on the ftrace assembly functions. Position Independent Executable (PIE) support will allow to

Hi, I have mentioned before that we have added some sdt dtrace probes in SAX, our APL interpreter. Encouraged by Angelo and Jignesh, I have created a small document (5 pages) describing our experience with it, together with some problems we have encountered and some scripts we use for pretty-printing dtrace outputs. The said document can be found at

Hello All, When going through the Ogg format, I have a basic question. As per the RFC the Ogg format encapsulates the logical stream. Now consider the scenario where a raw mono stream is being encoded with Opus Codec. The stream is 48KHz and the length of the stream being encoded is worth 20ms of data. This makes it 960 half words (considering 16 bit format). Now if the final output is say 100

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

Setup: Server: Mac OS X Server which serves dhcp and tftp requests client: Acer with PXE boot agent 4.0.19 file to transfer: -rw-r--r-- 1 root wheel 10988 Apr 12 13:50 pxelinux.0 The default tftpd daemon doesn't support the tsize option (I think, look at the packet trace at the end, it reports the file isn't found, but I think this is because of tsize ... but I could be