similar to: Decoder speed: Test on slow machine

Hello, I translated OggEnc (RC3) into German language. Nothing fancy. Neither Goethe nor Schiller. Could anyone please make a Win32 build? I don´t have a Win32 compiler. Sourcecode of modified files is available at http://www.metalunleashed.de/oggenc_ger.zip Just replace RC3 files with the modified versions. I hope this is useful for anyone. bye, Maik Merten -- MetalUnleashed:

Hello, anyone with an idea why Peter´s great plugin is not included with the latest full-install of Winamp? I thought it was planned to release Winamp 2.77 with Vorbis support... bye, Maik Merten -- MetalUnleashed: http://www.metalunleashed.de DHTML-Bibliothek: http://www.fortunecity.de/wolkenkratzer/flick/403 ICQ: 45648209 --- >8 ---- List archives:

Hello, congratulations to the Ogg Vorbis team - RC2 sounds good. But... RC2 in 128 kbps mode seems to clip off all frequencys beyond 16 KHz. On the tracks I tested Beta 4 gave response even beyond 18 KHz. Some testings on a randomly chosen track: (other tracks gave similar results) Artist: Judas Priest Album: Jugulator Title: Bullet Train Beta4: 127 kbps, ~ 18 KHz (!) RC2: 132 kbps (!), ~ 16

you can write your own software mixer that can decode MP3 on the PS2 so I can't see why you can't do that with ogg, however, even mp3 is processor intensive and programers are not going to give up that much processor power which will decrease or detract from the rest of the game. However, I'm sure there are some people out there that have been able to work around this. Regardless, ps1

Hello folks Anyone know if this would be enough to decode oggs? AMD Elan SC520 133 MHz If not, what seems to be the lower limit required for decoding oggs? Many thanks, Kerry. <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-request@xiph.org' containing only

I updated my home server with the 6.4 CR packages, and I've experienced 3 or 4 hard lockups since. The server is a fanless VIA C7 "CentaurHauls" system with a 1GHz CPU underclocked to 800MHz and 1GB of RAM. It has a dual-port Intel 82546GB NIC in its single PCI slot. (It also has an on-board Realtek RTL-8110SC/8169SC NIC that is plugged in, but doesn't currently have an IP

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'

Hello, I took the liberty of quickly slamming together http://www.theora.org/benefits/ . This is supposed to answer the "why should you use Theora" question in some detail. This section is not yet included in the navigation bar and I'd like to get confirmation that this information can be considered "canon" before making it "visible" (oh, and of course someone

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