similar to: PostFish question

Hello folks, Although Jack graciously permitted me to keep tinkering on the Postfish alongside OggFile work ;-) allowing it to sit there in a partially tinkered state continued to be a distraction. So yesterday and today I cleaned up the source repository and put together a prerelease. With this prerelease, I'm putting the project out of mind until I put out a beta of OggFile. Actually,

Hello folks, Although Jack graciously permitted me to keep tinkering on the Postfish alongside OggFile work ;-) allowing it to sit there in a partially tinkered state continued to be a distraction. So yesterday and today I cleaned up the source repository and put together a prerelease. With this prerelease, I'm putting the project out of mind until I put out a beta of OggFile. Actually,

Hi everybody: Here is a new Ogg Traffic, with release announcements for Vorbis 1.0.1, Speex 1.0.3, and Icecast 2 Beta 1. The HTML version is at http://www.vorbis.com/ot/20031119.html. Enjoy! -Carsten <p>Ogg Traffic for Wednesday, November 19, 2003 Author: Carsten "Purple" Haese Contact: [1]carsten@xiph.org Date: November 19, 2003 Table of Contents 1

My replaygain player side backend code is up at savannah: https://savannah.nongnu.org/projects/vgplay/ Pull it from CVS for the time being, as the file area isn't up and working just yet. It applies album and track gain values as scale factors to float pcm and includes an arbitary value preamp, a couple of limiting strategies. There's also helper function to pull the replaygain

Hey When playing an http ogg stream served by icecast, ogg123 (vorbis-tools-1.0.1) seems to detect replaygain metadata because it displays it in a nice way, but does ogg123 actually alter the playback volume according to the replaygain variables? I can notice no effect. I did some googling on this but didn't find much help. I discovered a vgplay patch for vorbis-tools 1.0.1 but after

I've written an updated xmms vorbis plugin, which is currently available from the vgplay cvs as a file tree and patch: http://savannah.nongnu.org/cvs/?group=vgplay (Once some file area problems are sorted, I'll put the patch there for easier access). It's a patch or Input/vorbis tree for xmms 1.2.8 and includes the following features: - Replaygain is now implemented using

On Mon, Sep 26, 2005 at 05:30:11PM +0200, Michael Smith wrote: > > Assuming this is correct, the next question that arises is "Is Vorbis > > when used this way truly gapless?" > > Yes, it is. ... and I can confirm this. No gaps were perceivable decoding in ogg123. However, an interesting effect can be had if all the parts have the same serial number. You get a bump

Hi, While testing ReplayGain (so it could be related to a bug), I noticed the following gain comments for a file: RG_PEAK=1.71580 RG_RADIO=-7.91 dB RG_AUDIOPHILE=-6.72 dB I've never seen such a large peak. Not that I've looked much, nor have I analyzed the file further. I just thought I should mention it. :) The file is the track Board Burner by Mixmaster Mike, available at:

I've just uploaded the second patched version of the xmms vorbis plugin to savannah, which primarily includes the logical streams as playlist items feature that I've been working on. The good stuff: There are now three modes for handling local (or more to the point, seekable) physical streams that contain multiple streams: 1. Load into the play list as a single file. This is the old

On Tue, Sep 06, 2005 at 09:56:06PM -0500, Jay Krivanek wrote: > Yea, don't get me wrong, ogg is definitely an awesome format but aacplus v2 > is currently the leader in high fidelity quality at low bitrates. 24kbps > aacplus even kicks ass in my view. Is that 24kbps AACPLUS a full 44.1kHz stereo signal with frequencies preserved up to at least 15kHz? (Just curious, not

I've been experimenting with the ideas of Replay Gain[1] and find that ogg123 doesn't have a way of specifying the scaling applied to replayed samples (like -f in mpg123). Looking at libvorbisfile, I see no function exactly matching this possibly desirable behaviour. ov_read() scales by either 128 (byte output) or 32768 (word output), but there's nothing in between. ov_read_float()

On Mon, Sep 26, 2005 at 12:41:00PM +0200, Michael Smith wrote: > On 9/23/05, Paul Martin <pm@nowster.zetnet.co.uk> wrote: > > Mike... did you look into this? I posted a waveform from a file > > generated by ogg123 dumping to a wav (so that audio driver problems were > > eliminated). > > > > It looks to me like ices2 is restarting the vorbis encoder in a >

Mike... did you look into this? I posted a waveform from a file generated by ogg123 dumping to a wav (so that audio driver problems were eliminated). It looks to me like ices2 is restarting the vorbis encoder in a non-gapless way when it stops and starts the encoding (to change the stream id and update the metadata). Because I'm doing crossfades from one track to another, this shows up.

I'm using ices2's metadata facility to update the name of a track in a vorbis stream: <input> <module>alsa</module> <param name="rate">44100</param> <param name="channels">2</param> <param name="device">hw:1,0</param> <param name="metadata">1</param>

I'm having some difficulty getting into Ogg. Being my first time encoding to Ogg, I am left doubtful of the quality in reproduction. Hopefully, it is merely something that I am doing. My original intentions were to go through my CD collection and rip everything out at 224kps VBR. I began with an album I was relatively familiar with. I used FreeRip 2.53 initially, but found that I had

On 8/16/05, Paul Martin <pm@nowster.zetnet.co.uk> wrote: > > Caught it yesterday, as I was already running level 4: This line: [2005-08-15 04:10:58] EROR stream/ices_instance_stream Send error: No error (Success) is the one that catches my attention. Unfortunately, ices's error logging is somewhat sub-standard. Can you cross reference this against your icecast error.log to see

Hi, I'm new here. I would like to write 2 simple utilities to maniputale OGG files: 1) oggjoin --output-file=result.ogg file1.ogg file2.ogg ... Merge file1, file2, ... into result.ogg file 2) oggpause --output-file=result.ogg --duration=0.5 Generate result.ogg with silence for 0.5 seconds oggpause --output-file=result.ogg --input-file=source.ogg Generate result.ogg with silence equal

Alright folks, here's the solution. 1) Keep extensions to 3 letters for audio & video. Except for special situations where the user might be doing a codec specific name. Since the official extensions are 3 letters, those can always be used on any 8.3 device. 2) introduce a new extension .OGV for ogg container video. With a strong preference for Xiph only codecs. (If you want 3rd

Hi, I need to adjust the output volume from ogg123 the same way that mpg123 has the "-f n change scalefactor [32768]" option. I need to do this within ogg123, instead of alternatives that involve pipes, such as piping the output to sox. I do not believe that this is currently possible in ogg123, and I'm looking for some suggestions as to how it can be accomplished by modifying

Hi, I need to adjust the output volume from ogg123 the same way that mpg123 has the "-f n change scalefactor [32768]" option. I need to do this within ogg123, instead of alternatives that involve pipes, such as piping the output to sox. I do not believe that this is currently possible in ogg123, and I'm looking for some suggestions as to how it can be accomplished by modifying