similar to: some more granulepos questions

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://westfish.xiph.org/pipermail/vorbis-dev/attachments/20040618/e7bee431/attachment.pgp

Hi While implementing OSS Ogg/Vorbis encoding and streaming using RTP/RTCP for both unicast and multicast, I have come across a few issues I need to clear out regarding the numbering of ogg_packets and their granulepos value. Below are the result for two different scenarios. <p>In the first scenario, ogg_packets are generated using a) vorbis_analysis_headerout() b) while

Hello I have experienced some problems with vcut (media-sound/vorbis-tools-1.0-r1 package from Gentoo/Linux). I have a long live record I have encoded in OGG (maybe it would have been easier to cut the WAV file and encode the parts, but still). The file was encoded with oggenc from the same package as vcut. I have therefore tried to use vcut to split the long OGG file in several smaller files.

Hello again. If you recall, I am the guy working on enabling Audacity to losslessly rearrange Ogg Vorbis files for my senior thesis. I have more or less completed the required modifications to Audacity to support this. You can read more about the work this entailed by reading my journal: http://www.reverberate.org/computers/thesis/journal Now my attention moves to the Ogg Vorbis code

Hi, I have a question regarding vcut. In the man page, it says: DESCRIPTION vcut reads an Ogg Vorbis audio file and splits it at the given cutpoint, which is a sample number. <p>What I want to do, is to cut an Ogg Vorbis file at a given time. Say, I have an Ogg Vorbis file, which is 1 hour long, and I want to cut it into two half hour parts. With a fixed bitrate

Hi there, First of all, sorry for my English I'm not a native english speaker. I need to develop and application witch does 3 tasks with oggs files : 1/ chain 2 ogg files 2/ extract a part from an ogg file 3/ add silence between two chained oggs files. Basically, - For the 1st task, I think that the best way to chain ogg files is to use the "cat" (on linux) or "copy

While testing the new vcut, some of the early results had badly framed headers. I actually didn't notice it at first, because I was testing with oggz-validate, but ogginfo does identify the problem: "WARNING: Vorbis stream X does not have headers correctly framed. Terminal header page contains additional packets or has non-zero granulepos" Conrad (or someone else) may want to

Hi, I'm hacking on and off on oggmerge (from ogg-tools). I've added support for Theora, Speex, and Kate, as well as a few other fixes and changes. Now, I've got an issue relating to the ordering of pages as done by oggmerge, and the way oggz-validate tests for presentation time ordering. oggmerge, when deciding what timestamp to assign to a page, uses the previous page's

Hi all, I noticed the following Subversion commit today: r6719 | xiphmont | 2004-05-18 16:04:53 +1000 (Tue, 18 May 2004) | 11 lines Updated doc to reflect current proposal... Not as much a proposal at this point actually; this is the way I'm now implementing it. Although we're still in the 'RFC'/'look for horrible lossage' stage, this is close to being

Hi all, something which came up recently in relation to the design of Kate's granulepos was whether or not the granulepos of successive Ogg pages is allowed to be the same, ie. whether or not granulepos must be strictly increasing. As this question is more generally about Ogg granulepos, how about we answer it first and then get back to the discussion of Kate's granulepos ... Here is

2008/11/26 David Flynn <davidf+nntp at woaf.net>: >>>> http://trac.annodex.net/changeset/3801 >>> >>> I'll test this shortly. > > Ok, i've tested muxing some audio and video together and that works fine. > woo. great, thanks :-) So the last remaining tool to check is oggz-chop. I at first assumed it would not work with Dirac's granulepos,

I've got a question about the granulepos in speex packets. >From the speex manual (http://www.speex.org/manual2/node7.html#SECTION00073000000000000000): >The third and subsequent packets each contain one or more (number found in header) Speex frames. These are identified with packetno starting from 2 and the granulepos is the number of the last sample encoded in that packet. In

Jean-Marc, What exactly does the speex code do to calculate the granulepos? With vorbis it's the 'count of decodable samples including this packet'. So if you had a packet that allowed you to decode 1024 samples since the beginning of playback, the granulepos is 1024, not for example 1023 which would be the *index* of the last sample assuming C-style array indicies starting at

2008/11/14 David Flynn <davidf+nntp at woaf.net>: > On 2008-11-13, Conrad Parker <conrad at metadecks.org> wrote: >> I'm wondering if the Dirac granulepos parsing in liboggz and display >> in the oggz tools is currently correct, as I'd like to do a release of >> these soon. > > I believe it is -- although if correct support in the rest of the >

Hi, I'm wondering if the Dirac granulepos parsing in liboggz and display in the oggz tools is currently correct, as I'd like to do a release of these soon. A couple of days ago David Schleef mentioned there were some problems. David, is that currently true (ie. since David Flynn's recent updates to support Dirac), and if so could you please explain what the problems are, or point me

On 6/18/09, Conrad Parker <conrad at metadecks.org> wrote: > This sounds like it needs a new tool specifically for fixing broken > Ogg files. I see two solutions: 1) the new vcut which I reckon will fix the problem since it has to split and rebuild the audio in a new Ogg 2) an Hex editor, even if just to check what's wrong in the metadata section -Ivo

On 2008-11-13, Conrad Parker <conrad at metadecks.org> wrote: > I'm wondering if the Dirac granulepos parsing in liboggz and display > in the oggz tools is currently correct, as I'd like to do a release of > these soon. I believe it is -- although if correct support in the rest of the liboggz tools is required, a little more work may need to happen. > Here's some

On Thu, Nov 13, 2008 at 06:06:10PM +0900, Conrad Parker wrote: > A couple of days ago David Schleef mentioned there were some problems. > David, is that currently true (ie. since David Flynn's recent updates > to support Dirac), and if so could you please explain what the > problems are, or point me to a bugtracker where they are reported. eg. I mostly meant what you apparently

2008/11/21 David Flynn <davidf+nntp at woaf.net>: > On 2008-11-21, Conrad Parker <conrad at metadecks.org> wrote: >> 2008/11/15 David Flynn <davidf+nntp at woaf.net>: >>> On 2008-11-14, Conrad Parker <conrad at metadecks.org> wrote: >>>> It seems oggz chop, merge and sort will need some attention to deal >>>> with the Dirac

Hello, I'm just totally confused. In my theora streams encoded using ffmpeg2theora (but also when using my own encoder) I have packets with a granulepos of -1 so I can't identify the packet during a seeking operation correctly. I can also see those strange value when I just print the packet granulepos before sending it to the Theora decoder. I know why there are PAGES with granularpos of