similar to: ogg123 volume?

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

Is there any particular reason why ov_read() packs floats to integer PCM inline, rather than being implemented in terms of ov_read_float() and a separate packing fucntion? There are obviously many advantages doing audio manipulation on the floats before packing, but right now you have to reinvent the packing stage yourself - in a replaygain backend that I'm working on, I ended up copying

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

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

Greetings, I'm having some sort of problem using ov_read_float(). Everything looks good to me, but I'm trashing memory somehow, so clearly I'm screwing something up. What confuses me is why it takes a ***float for the buffer. I call it like so: float **buffer bytes_read = ov_read_float(&vf, &buffer, 0) memcpy (b, *buffer, 0); This compiles fine, but after a few reads,

Hello, ogg123 | ices2 are doing transcoding but ogg123 is staying frozen under certain circumstances here is the stack #0 0x401f25d4 in __pthread_sigsuspend () from /lib/libpthread.so.0 #1 0xbffff94c in ?? () #2 0x401f2398 in __pthread_wait_for_restart_signal () from /lib/libpthread.so.0 #3 0x401eef0b in pthread_cond_wait@GLIBC_2.0 () from /lib/libpthread.so.0 #4 0x0804b0d3 in

Hi all, I have implemented ReplayGain support for Vorbis. If you are not familiar with it, it is basically a method of making sure all your files have equal loudness, remove the need for normalization and prevent clipping during playback. The process is totally lossless, and supporting it requires minimal work. More info about the exact workings can be found on www.replaygain.org (recommended

I'm considering patching my copy of ogg123 to support vorbisgain tags. Is there any interest in folding this sort of patch into the main line ogg123? Has anyone done this already (or to another command line ogg player)? John --- >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

I don''t know if this has been suggested before but.. What about adding support for a bookmark or hyperlinked index? The idea is that a large compilation such as a long speech or an album would be maintained as a single file, but on playback, the player would show numerous ''tracks'' which are really just bookmarks relating to starting position of the specific part or

Hello. I noticed that when reading data with ov_read_float(), you can get values outside [-1..1] when the stream is encoded at lower quality, but with higher quality, the values trim down to inside [-1..1]. Looking at the plot from -q10, the data from ov_read_float seems clipped. I've made some plots of encoding the start of Rammsteins Feuer from the xXx soundtrack (it's a pretty loud

Hi, I think that it would be a good thing to know more about those 2 projects (and also the future patent free format). I think that many people as me know about Lame, but not about Vorbis, and vice-versa. It would be fine that someone (perhaps the maintainer) of every project would introduce to both group of people those projects. 2 things would be interesting (to my mind): - to know about the

Subj!. Kind Regards, Michail. _________________________________ Michail A.Baikov, Linderdaum Team http://www.gamedot.ru http://linderdaum.gamedot.ru <p><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

Dear list, My query follows on from a question I posted a few days ago. I have the following 2 sets of data: wetMeans[1] 9.904762[2] 6.344828[3] 6.346154[4] 6.855769[5] 9.074324[6] 9.953988[7] 13.482966[8] 14.546053[9] 10.841584[10] 9.752033[11] 6.739336[12] 8.955056burnMeans[1] 0.06214286[2] 0.05396552[3] 0.04096154[4] 0.05302885[5] 0.05831081[6] 0.07392638[7] 0.29969940[8] 0.25596217[9]

Hi, in ov_read_float.html there is a small mistake: long ov_read(OggVorbis_File *vf, float ***pcm_channels, int *bitstream); hould read: long ov_read_float(OggVorbis_File *vf, float ***pcm_channels, int samples, int *bitstream); It seems this function has been changed (compared to the RC3). Anything else worked fine for me with the 1.0 release. Olaf <p>--- >8 ---- List archives:

Hello everyone, I'm new to this flac thing (started about a week ago) but I have read a lot about flac and replaygain. As far as I understand it, replaygain is lossless in the sense that I can tell my player to ignore the settings or I can even use foobar2000 to remove the tags entirely, hence getting back to the original audio. If that is the case, why is there a warning in the foobar2000

On 24-04-13 14:34, Erik de Castro Lopo wrote: > That's an error in the awk script, which is embedded in the shell > script. I know GNU awk supports lshift, maybe BSD awk doesn't. I'll > investigate that futher. On my system awk links to mawk 1.3.3 >> I don't know why, but the test continues and says all tests passed while >> that clearly isn't the

Erik ? ? Testing FLAC file with unknown metadata... OK ? ? ./test_metaflac.sh: line 450: syntax error near unexpected token `then' ? ? ./test_metaflac.sh: line 450: `? then' Do both /bin/bash and /bin/dash give exactly the same error message ? Earl ________________________________ From: Erik de Castro Lopo <mle+la at mega-nerd.com> To: flac-dev at xiph.org Cc: Earl Chew

Hello all, I'm glad to announce to you that Vorbis now has full ReplayGain support. If you're not familiar with ReplayGain, take a look at www.replaygain.org. The main features are: a) all songs play back with equal loudness b) removes the need for normalization c) allows for clipping prevention Using it is very simple. Get a compatible decoder (ogg123, XMMS and WinAmp all support it

>b) According to http://wiki.xiph.org/OggOpus#Comment_Header >there should be no REPLAYGAIN_*** tags in Opus files; Opus uses >R128_TRACK_GAIN tag. If some audio player reads Opus tags then it should >be aware of the difference between ReplayGain and R128. But this doesn't >require REPLAYGAIN_REFERENCE_LOUDNESS tag. > > The Opus replaygain spec is fundamentally broken, so

> You don't. Audio CDs don't support ReplayGain tags. The only thing > you may do on Audio CDs is to use Volume Normalize techniques > available on certain programs. Normalization of sound is not a good, > clean thing, though. Surely it would be possible to have something apply the ReplayGain to the WAV after decoding and prior to writing them to CD... but I don't know