search for: buffer_shutdown

Displaying 4 results from an estimated 4 matches for "buffer_shutdown".

2001 Jan 09
1
PATCH: Segfault fix for ogg123
...f it has even been allocated. Ken probably didn't notice because he was using a buffer (which is optional). :) A patch for ogg123.c is attached. (Probably takes the record for the smallest patch submitted.) --- Stan Seibert <HR NOSHADE> <UL> <LI>TEXT/PLAIN attachment: buffer_shutdown.patch </UL> -------------- next part -------------- A non-text attachment was scrubbed... Name: buffer_shutdown.patch Type: application/octet-stream Size: 476 bytes Desc: not available Url : http://lists.xiph.org/pipermail/vorbis-dev/attachments/20010109/69a954c6/buffer_shutdown-0001.obj
2001 Mar 03
1
(Yet another) ogg123 buffer patch
Here's yet another ogg123 patch that: 1) Adds a command-line parameter "--prebuffer n" or "-p n" that decodes "n" chunks into the buffer before even forking off the writer thread. 2) Moves the buffer_shutdown call in ogg123.c to its proper place. 3) Doesn't use signals ;) This way, the default behavior is to start playing immediately, while allowing the user to buffer as much as he/she wants. It may be worth it to make the writer thread stop and rebuffer when it empties, but that may require a rew...
2001 Jan 14
3
Wave Header Question
...them for that purpose. However, since I have to pick something to put in those blanks, I want something that will be useful in the most cases. [The long term solution is to create a raw device that just dumps the data so you can massage it into whatever format you like.] Oh yeah, Ken, commit the buffer_shutdown patch in CVS so wav writing works again, please!! --- Stan Seibert --- >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 'unsu...
2001 Feb 21
0
Buffer problems
There seem to be a couple of problems with the buffering code just checked in: 1. buffer_shutdown(NULL) is called when the bitrate changes and you're not using a buffer. 2. The buffer is not used for anything but the first file. 3. The buffer isn't explicitly closed when playback is finished, sometimes leaving an ogg123 process sitting sucking up 100% CPU time. Here's a patch tha...