similar to: Libvorbis suggestion & floating point exception

> vorbis_encode_init( &vorbisInfo, 2, 44100, 96, 96, 96); > > which by all reasons should generate a 96 kb/s stream, as all > max_bitrate, nominal_bitrate and min_bitrate are set to 96. Strangely > enough, the generated stream's bitrate (according to XMMS and WinAmp) > varies between 49 and 59. Currently min and max are ignored by the library, since bounded bitrates

Hi, I'm experimenting with IceCast2, using DarkIce to generate the stream. I have found some peculiarities with the vorbis bitrates. In DarkIce, I call vorbis_encode_init() with about the following values: vorbis_encode_init( &vorbisInfo, 2, 44100, 96, 96, 96); which by all reasons should generate a 96 kb/s stream, as all max_bitrate, nominal_bitrate and min_bitrate are set to 96.

Hi, Maybe this is documented somewhere, if so, please send me a link to the documentation. My question is: how to set up different (VBR, CBR, ABR) modes when calling the Ogg Vorbis API? Currently I do: CBR: ret = vorbis_encode_setup_managed( &vorbisInfo, getInChannel(), getOutSampleRate(),

Hi devs, I am developing winLAME, a frontend for LAME, and it also supports Ogg Vorbis decoding and encoding. I've got a question about the new API function vorbis_encode_init_vbr(). Do I have to call vorbis_encode_init() before to set the bitrate(s)? And what is a good default value for the "base_quality" parameter? I read on the mailing list that ABR use in Ogg Vorbis is not so

Hi, a newbie query about a potential bug in VorbisLib (I tried using bugzilla with no success): My problem is that I encountered a divide by zero exception that I tracked down to bark_noise_hybridmp() in PSY.C. I don't pretend to know what bark_noise_hybridmp() does but there are a few instances of the following in that routine: D = tN * tXX - tX * tX; R = (A + x * B) / D; When I

Colleagues, I am using R 2.5.1 on an Intel Mac (OS 10) to create PDF outputs using pdf(); same problem exists in Linux (RedHat 9) While adding text to the document with text() and mtext(), I encounter the following problem: In order to align the text, I have embedded tabs ("\t") in some of the text. Each time I do so, I get the following error messages: Warning: font metrics

I am no longer able to access CVS: Logging in to :pserver:anoncvs@xiph.org:2401/usr/local/cvsroot cvs [login aborted]: recv() from server xiph.org: Connection reset by peer I had no problems a few days ago. -- -:-:- David K. Gasaway -:-:- XNS : =David K Gasaway -:-:- Email: dave@gasaway.org -:-:- Web : dave.gasaway.org <p><p>--- >8 ---- List archives:

Has anyone compiled the ogg and vorbis libraries with borlands c compiler (bcc32)? If so, are there any makefiles or similar available which can make it easier for me to do the same? /Erik <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org'

vcomment.c contains this line: fprintf(stderr, "Vorbiscomment " VERSION "\n"); I can't figure how / where VERSION is defined. <p> -- -:-:- David K. Gasaway -:-:- XNS : =David K Gasaway -:-:- Email: dave@gasaway.org -:-:- Web : dave.gasaway.org <p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage:

Daniel Aleksandersen wrote: > On Monday 17. September 2007 07:47:19 David K. Gasaway wrote: >> Even today, I use my own "metadata format" -- essentially a superset of >> vorbis comments. There is one file per release, even with a multi-disc >> release. As a final part of the ripping process, I apply this metadata >> to the FLAC or Vorbis files. > > Why

On 16 Sep 2007 at 22:10, Ralph Giles wrote: > These applications are complementary. Many music players do have their > own database, and it makes sense to keep metadata there, if only as a > cache. It is also to have metadata in the file itself, so that when it > is moved, copied, posted for download by others, or just indexed by > another music player instance it is easily

On 10 Sep 2007 at 18:42, Ian Malone wrote: > Classical music is a rich source of examples; works are > most often associated with a composer but you may still > care who the performers or conductors were. A piece may > be split across several movements which may be even further > broken down into tracks on the source. This things are easily solved with vorbis comments ...

On 15 Sep 2007 at 16:53, Silvia Pfeiffer wrote: > Skeleton, CMML and Vorbiscomment are not sufficient for some people - > in particular when there is a more complex piece of metadata to be > communicted, e.g. from an archive that stores a lot more information > than just name-value pairs. In my opinion, for this purpose it would be more appropriate to store the data separate from

On 14 Sep 2007 at 15:52, Ian Malone wrote: > Vorbis comments could do better than they currently do > but no-one seems compelled to implement any of the exotic > tag proposals that have hung around for years. Exotic tag proposals?! Do you mean the ones linked from the wiki? As far can tell, the only roadblock to "implementation" (by which, I assume you mean support from

On 9 Sep 2007 at 23:11, Daniel Aleksandersen wrote: > To me, Vorbis comments are insufficient. Ask anyone playing in an ensamble > if they would like recognition. Ask the record label holding the rights to > a song. Ask the music geek that wants his music collection sorted by > something other than artist, album, or release year. They would all prefer > this to Vorbis comments.

Hello everybody, today I had some time to test Peter´s decoding plugin on a very slow machine. My setup: - Pentium "classic" @ 50 MHz (underclocked!) - Mainboard with Mercury Chipset (I think) - CD-ROM and HDD in PIO-Mode (CPU intensive) - MAD16 Soundcard (ISA slot, CPU intensive) - Win95B, Winamp 2.76, Decoder Plugin 1.16 (RC 2) The hardware setup is something like the

Hello folks, This is a periodic mailing of the FAQ[1] for the various xiph.org mailing lists. Hopefully, this FAQ will preemptively answer questions some posters have. [1] In this case FAQ == Frequently Answered Questions. We answer 'em before you ask 'em. They're not rules, they're just the way it works. 1) Do not send subscribe/unsubscribe messages to the list; they'll

Hello folks, This is a periodic mailing of the FAQ[1] for the various xiph.org mailing lists. Hopefully, this FAQ will preemptively answer questions some posters have. [1] In this case FAQ == Frequently Answered Questions. We answer 'em before you ask 'em. They're not rules, they're just the way it works. 1) Do not send subscribe/unsubscribe messages to the list; they'll

Hello folks, This is a periodic mailing of the FAQ[1] for the various xiph.org mailing lists. Hopefully, this FAQ will preemptively answer questions some posters have. [1] In this case FAQ == Frequently Answered Questions. We answer 'em before you ask 'em. They're not rules, they're just the way it works. 1) Do not send subscribe/unsubscribe messages to the list; they'll

Hello folks, This is a periodic mailing of the FAQ[1] for the various xiph.org mailing lists. Hopefully, this FAQ will preemptively answer questions some posters have. [1] In this case FAQ == Frequently Answered Questions. We answer 'em before you ask 'em. They're not rules, they're just the way it works. 1) Do not send subscribe/unsubscribe messages to the list; they'll