Potentially nasty bug in current HEAD when printing the name of the file being played (the "Playing: filename.ogg" bit), any % symbols in the name appear to be printf parsed causing either junk to be printed or a crash or both. I noticed this when trying out http streaming as the url has %20's in it for spaces in the file name. Oh, and it still says it's rc2... -- ______________________________________________________________________________ | Brian Havard | "He is not the messiah! | | brianh@kheldar.apana.org.au | He's a very naughty boy!" - Life of Brian | ------------------------------------------------------------------------------ --- >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' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Brian Havard wrote:> > Potentially nasty bug in current HEAD when printing the name of the file > being played (the "Playing: filename.ogg" bit), any % symbols in the name > appear to be printf parsed causing either junk to be printed or a crash or > both.Thanks for the report. Fixed. Stan: please check if the vstatus... family of functions needs a fix as well.> > I noticed this when trying out http streaming as the url has %20's in it > for spaces in the file name. > > Oh, and it still says it's rc2...Well, it still isn't rc3... Segher --- >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' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Hello everyone,
When using the aRts output device while playing multiple files,
ogg123 stalls when you use Ctrl-C to prematurely skip to the next
song. You then have to kill it.
Steps:
* Have aRts running (e.g. use KDE 2)
* Run
$ ogg123 -d arts file1.ogg file2.ogg
* Type Ctrl-C
Software versions:
* Slackware 8.0 kept up-to-date with slackware-current
* KDE 2.2.2 compiled by Slackware Team
* artsd 0.6.1
* latest official Ogg Vorbis release (i.e. RC3)
compiled by myself (without warnings or errors)
If you need more information, feel free to ask.
--
adrien.beau@free.fr - http://adrien.beau.free.fr/
--- >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'
containing only the word 'unsubscribe' in the body. No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.
Hi: My friend found this vorbis rc3 bug. He runs an automated ogg stream which he listens to for long periods on end. Apparently, after around 2 hours, ogg123 will start playing short snatches of white <?> noise during the audio. It's different every time it happens, but it will get into a pattern of a few short bursts over a couple of seconds and stay in that pattern until you kill the player (i.e. it doesn't get worse). It is also unrelated to the audio of the ogg stream (i.e. it doesn't get louder or softer with the music). He thinks that it begins at the start of a song, but couldn't sware to that. He is running ogg123 from the Debian unstable branch. I think he also has a CVS version at home that does the same thing, though his home system has gone belly up at the moment so I can't confirm this. He witnessed this behaviour on two different boxes. He is using the OSS output plugin but is actually running alsa0.9. The stream he listens to can be found at http://bumpy.braille.uwo.ca:9000/egoplay.ogg (the material is pretty much all 128kbps RC2). I'll put this in the bug tracker in the next day or two. Geoff. <p><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' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.