similar to: ReplayGain Calculation

Hi, I think I might have kind of, sort of found a bug in opusenc. But do correct me if I am worng. :) When converting an FLAC file that contains RG tags written by bs1770gain the resulting opus file has a way, way too high RG value. I am talking >90dB(!). Here is the metaflac output of the flac file: % metaflac --block-number=2 --list bs.1770/test.flac METADATA block #2 type: 4

and that some small indy Classical labels still use it. Since applying deemph appears to be lossy, it seems to me it would be desirable to keep bit perfect data in lossless formats like flac and use metadata to indicate it has CD emphasis, in which case there probably should be a switch on the opusenc encoder to apply deemph on transcode from flac. That way one doesn't have decode to wav and

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

This new ReplayGain feature is cool, but made all my .mp3 and .mod files sound so loud, so I wrote a Winamp DSP plugin that: - If a file is playing that is not known, a ReplayGain value will be calculated while playing. - If a file is known, the ReplayGain value is applied. What that means is that my .mp3 files now sound as loud as my .oggs. I hacked this thing together very quick, so

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

Hi all, New to list and Opus Codec. I've been using it on a beagleboneblack with 'arecord'. One of the things I've noticed while encoding is that Opus reports a float with an 'x' along with "realtime". Where can I look up where this calculation is derived? It got me looking and I've noticed that when I record something from a known source (in testing)

On 2014-02-12 12:11 PM, Ralph Giles wrote: > On 2014-02-11 8:27 PM, Ben wrote: > >> New to list and Opus Codec. > > Welcome1 > >> One of the things I've noticed while encoding is that Opus reports a float with an 'x' along with "realtime". > > This is intended to measure the cpu performance of the encoder. The > float is the number of

On 2014-02-11 8:27 PM, Ben wrote: > New to list and Opus Codec. Welcome1 > One of the things I've noticed while encoding is that Opus reports a float with an 'x' along with "realtime". This is intended to measure the cpu performance of the encoder. The float is the number of seconds of audio data processed divided by the number of real-time seconds since encoding

When a locale is in effect that does not use the point as the decimal mark (e.g., sv_SE or de_DE, which use a comma) and a ReplayGain tag is read for --apply-replaygain-which-is-not-lossless, the gain value was misinterpreted (e.g., "-2.29" truncated to "-2"). This is fixed by resetting the locale to "C" temporarily, based on Josh Coalson's fix of the dual case

In this topic on Hydrogen Audio(http://www.hydrogenaud.io/forums/index.php?showtopic=105586) someone asked a question about the sample rates that FLAC supports for ReplayGain. The outcome was that the current documentation of MetaFLAC is outdated since Commit http://git.xiph.org/?p=flac.git;a=commit;h=0554a4aee6966bc5b251364753ef85de72dfab19 because as of 1.3.0 FLAC supports Replaygain with many

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

Declaring variables in the middle of a block isn't supported by older (pre-C99?) compilers, and gcc 2.95 is one of them. --- a/src/plugin_common/replaygain.c +++ b/src/plugin_common/replaygain.c @@ -28,10 +28,11 @@ void FLAC_plugin__replaygain_get_from_fi double *track_peak, FLAC__bool *track_peak_set,

Hi Is it possible to cross-compile opus-tools with mingw and Ubuntu? So far I have done this:- # prepare $ mkdir $HOME/source $ mkdir $HOME/builds $ export PATH="$PATH:$HOME/mingw-w64-i686/bin" $ PKG_CONFIG_PATH="$HOME/builds/lib/pkgconfig" # Install ogg $ cd $HOME/source $ svn co http://svn.xiph.org/trunk/ogg $ cd ogg $ ./autogen.sh && ./configure

On 31 December 2016 at 21:04, Mark Harris <mark.hsj at gmail.com> wrote: > Ian Malone wrote: >>>> Another thought, could vorbiscomment do with having Opus comment support >>>> added? >>> >>> >>> Or make an opuscomment for opus-tools. I'm not sure which is the better >>> approach, though the latter certainly seems like it

Hi, I am interested in this part of the answer: "Make sure both are also linked to the same libopus (opusenc could be using the system libopus 1.0.x while opus_demo is from git)" I dowloaded a tarball distrib of libopus (1.1-beta),build and installed it,and afterwards did the same with opus-tools (0.1.7),using the former installed libopus library (also using libogg 1.3.1). When I execute

Hi! I have a few questions about the log files icecast produces, plus I have a little issue with replaygain but lets start with the icecast log stuff: If a client (listener) connects to icecast at, say, 12:00, the connection time is stored in the access log about 15-30 minutes later (or on disconnection). Is it possible to get icecast to log client connections immediately with the correct

I suspect the main difference is due to time alignment of the samples and the exact trimming at the beginning and at the end of the encoded files. I also note that there's a missing "--" in front of "bitrate" and only one "-" instead of two for cvbr in your opusenc command line. Make sure both are also linked to the same libopus (opusenc could be using the system

I've recently encoded some older CDs to flac that ended up with a positive album ReplayGain value. (+2.0dB) Problem is they sound noticeably quieter then other albums when played through winamp. (Album mode and ReplayGain are on) When played through foobar2000 they are louder as I would expect. I did a few tests. When the Preamp is down to -24 all playback is very quiet. When I put it up

Hi! I haven't looked into the code yet, but the patch uses different coding conventions like "if(" and "if ("; like wise "){" and ") {". My personal taste is to have spaces after keywords, but that's just me. I'd prefer a consistent coding style. Regards, Ulrich >>> Michael Graczyk <mgraczyk at google.com> schrieb am 26.04.2016

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