similar to: bitstream problem: resyncing...

On Saturday, 04 May 2002 at 17:52, Wade Carroll wrote: > This one really has me stumped. > I'm running 866MHz, 256MB RAM, 80GB Disk (7200RPM) on Linux-mandrake 8.2 > icecast 1.3.12 & ices 0.2.3 & lame 3.91 > all mp3s encoded with lame 3.91 or higher and --r3mix (VBR) ices behaves unpredictably in the face of VBR mp3s. It's on the TODO list, but I've never had the

Hi folks! Having trouble with re-encoding to 160Kbps. I have: Linux-Mandrake 8.2 Icecast 1.3.12 IceS 0.2.2 source Lame 3.92 Hardware is: Celeron 533 w/256MB RAM, 40GB Disk All seems to work at first but after a few songs it craps out and give me an ERROR WITH BITSTREAM (or something real close...sorry). ALL of my MP3s are encoded using the --r3mix flag (VBR) with LAME 3.91 or 3.89. All

We are trying to debug a connection between Asterisk and a legacy PBX (Mitel SX200). We turned on the Zaptel debugging and we get the following message quite frequently: Oct 12 07:14:09 localhost kernel: T1: Lost our place, resyncing ( 28 ) Oct 12 07:14:09 localhost last message repeated 3 times -- Oct 12 07:14:11 localhost kernel: T1: Lost our place, resyncing ( 28 ) Oct 12 07:14:11 localhost

I'm interested to know of any player, which can properly resync after receiving a theora+vorbis stream that has been cut somewhere in the middle... ie it doesn't start at granule 0. The problem being... when streams are cut in this way, the start time, and the times of the first few packets in each stream are unknown. When working at a packet level... the first few packets will arrive

This release bundles up the last twelve years worth of build system improvements, including making the configure script more efficient. Alan Coopersmith (9): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Update README for gitlab migration Update configure.ac bug URL for gitlab migration gitlab CI: add a basic build test Build xz tarballs

This release bundles up the last twelve years worth of build system improvements, including making the configure script more efficient and using the -n flag to gzip to improve build reproducibility. Alan Coopersmith (10): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Update README for gitlab migration Update configure.ac bug URL for gitlab migration

Hello, I´m just curious: How far is Theora from a bitstream freeze? From TheoraTodo: "Derf has come up with a number of suggestions for improving the flexibility of the bitstream based on his experimental encoder work. These will be implemented, if not entirely supported by the reference decoder, before alpha 3 is released." Are those changes supposed to be the last adjustments?

Hi, Is it expected that an Ogg logical bitstream might logically serve as the physical bitstream from which other logical bitstreams might be demuxed? I am not sure that I really see the point of doing this, but it would certainly be possible within the current spec. The trouble is that there are any number of ways to do the low-level muxing of several streams into one logical stream, with

I'm having trouble getting libvorbis to cut the beginning of a bitstream when I instruct it to do so with granulepos. I have constructed a file which I believe should have its beginning truncated. I have attached it to this mail. Here is a picture of what the bitstream looks like, as output by a python program that uses pyogg/pyvorbis to read the stream and print a representation:

I submitted four new packages for the NetBSD pkgsrc collection: libao, libogg, libvorbis and vorbis-tools for 1.0beta4. The following is some of the patches needed for libao and vorbis-tools. Official Developers: When you receive patches or development suggestions can you please acknowledge them? (For example: "Noted.", "Thanks, but already done.", "Not necessary,

Jack, thanks for the heads up. Could you possibly tell me what this error means: Warning: Encountered error while transfering /serve/ftp/mp3s/various_artists/Various_Artists-BLLLEEEEAAAUUURRRRGGHHH!-The_Record_7''/06-Nuclear_Roach-Pessimism-Fcs.mp3. [Libshout reported send error: Libshout socket error.] Libshout communication problem, trying to reconnect to server Failed reconnecting to

Since the mailing list archives are a bit difficult to go through at the moment, I'll go ahead and simply ask. If I fire up ices-0.4 with reencode enabled, at pretty much the end of every song I get an error: bitstream problem: resyncing... Occasionally it will also throw in a: mpg123: Can't rewind stream by NNN bits! And eventually after a dozen songs or so I'll get a rash

as per yesterday's discussion at #theora -- It has been suggested that we devise a method such that we will be able to add certain features to the bitstream (interlace, exotic color subsampling, clip length flag for download, etc), in such a way as to not obsolete streams encoded previously. Rillian's suggestion, which is pretty much standard practice, is to add a bitstream revision

Hello all, I've been working a little inside the Theora decoder when I found that it seems that many videos had the very same huffman tables encoded into their bitstreams (at least the ones that I could take my time to dissecate). I found that the tables are listed as TH_VP31_HUFF_CODES in the file huffenc.c. I tried to investigate a little bit more to see who was setting the bitstream

Dear experts, I am trying to understand the structure of the Speex .spx file, so I can packetize each frame in one packet for example, and in the receiving end, I can decode a file that has all the received frames (some of them may lost). I tried to figure out what is the delimiter used to separate the frames but I could not so far. I also tried to deleted some data from the .spx file or change

Hello, could somenone please describe me the vorbis specific physical bitstream structure, as I haven't found any documentation about it. Thank you ******************* Pierre-Henri Quelen phq@laposte.net "Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68 13 50 (0,34€/mn)" --- >8 ---- List archives:

Jonny Daenen a ?crit : > Narrowband (8 kHz), wideband (16 kHz), and ultra-wideband (32 kHz) > compression in the same bitstream > > What is the meaning of this? can i find more information about this > somewhere? > > And what is packel loss concealment, an you enable this somewhere? What are you expecting exactly here? That I explain what's a Hertz and what's a

question for the crowd: In writing the bitstream spec, I need to decide how to name various fields. I can go with names equivalent or very similar to the existing C code, or I can go with a similar set of labels that are more intuitive. Many of the C variables are named in cryptic or confusing ways. Presently, I'm changing the names to be more descriptive whenever it seems to make sense,

I have an ancient device, several actually, called an Audiotron that I use Samba for to access media files. Now, I realize these are old and finicky devices. For ease of management, I keep my media files separated into 4.5GB directories (easy to burn to DVD) and then I have a script that goes into each of those directories and creates one big directory full of symlinks pointing into each

Narrowband (8 kHz), wideband (16 kHz), and ultra-wideband (32 kHz) compression in the same bitstream What is the meaning of this? can i find more information about this somewhere? And what is packel loss concealment, an you enable this somewhere? thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: