similar to: R128gain & metaflac

I mention metaflac because there are a few shell scripts that use it to write RG tags in a flac music library on Linux. With support for Ebu R128 gain in metaflac (the calculation according to specification, not an external program) it would be easy to use, just change the cmd line for metaflac in the script. Now that metaflac supports sample rates higher than 48kHz this would be a good thing in

>The use of R128 also raises the question about "REPLAYGAIN_REFERENCE_LOUDNESS" >tag. Currently flac/metaflac writes "REPLAYGAIN_REFERENCE_LOUDNESS=89.0 dB" >but doesn't use it when decoding (it seems that nothing uses this tag). >R128 defines reference level differently, so this tag makes little sense for >it. IMHO it's better not to write this tag when

>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

As far as I know, R128 as ReplayGain isn't really considered final yet (see http://wiki.hydrogenaud.io/index.php?title=ReplayGain_2.0_specification for example), so it would probably be a bit early to update this in the FLAC source. op 16-06-14 10:15, Olav Sunde schreef: > I mention metaflac because there are a few shell scripts that > use it to write RG tags in a flac music

Olav Sunde wrote: > has anyone looked at adding R128gain code to metaflac so we can select > to use this calculation for RP tags rather than replay gain? Why metaflac only? flac is also able to calculate RG values. And, as far as I can see R128GAIN (http://r128gain.sourceforge.net/) is a standalone app, not a library. So probably it would be difficult to reuse its code in flac/metaflac.

Ian Nartowicz wrote: > I use it :) To optionally allow adjustment of tracks containing different > types of gain tag to a similar overall loudness. Admittedly this isn't > common. Files using the original replaygain algorithm with a reference > loudness of 83dB are now very rare, but R128 tags are starting to show up > (eg. in Opus) and these play at a significantly

On Wed, 18 Jun 2014 16:39:12 -0700 "Timothy B. Terriberry" <tterribe at xiph.org> wrote: >Ian Nartowicz wrote: >> The Opus replaygain spec is fundamentally broken, so let's ignore that for >> now. It is discussed ad nauseam elsewhere, but isn't going to change any >> time soon. > >I haven't seen anyone make any concrete proposals for how it

Copy additional filter values from Foobar2000 as found in <http://code.google.com/p/sirens2/source/browse/trunk/libwavpack-4.32.psp/wvgain.c?r=32> to allow metaflac to perform gain analysis on high sample rate audio. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/flac-dev/attachments/20120107/018c821b/attachment-0001.htm

Hi has anyone looked at adding R128gain code to metaflac so we can select to use this calculation for RP tags rather than replay gain? If this message turns up twice I apologize. I may have used the wrong subject tag Regards Olav Sunde -------------- next part -------------- An HTML attachment was scrubbed... URL:

Ian Nartowicz wrote: > The Opus replaygain spec is fundamentally broken, so let's ignore that for > now. It is discussed ad nauseam elsewhere, but isn't going to change any time > soon. I haven't seen anyone make any concrete proposals for how it should change. Maybe I missed something. AFAIK, the only objection to it is that there is no way to distinguish between whether

Ian Nartowicz wrote: > It is certainly the biggest issue. Sure it should be simple to address, but > nobody seems willing to do so. The only response I've had so far is that the > output gain should *always* be applied, yet it *might* be an album gain. It > can't be both and there is no way to tell which. Sorry, but that makes it Well, make a proposal on the IETF list that

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

Hi Erik, I've noticed a couple small things missing in the metaflac man pages. Namely, the new sample rates provided by Earl Chew as well as the PICTURE block being a valid block type. Attached is a patch for metaflac.sgml and metaflac.1 that details the new sample rates metaflac's replaygain supports. Also, there is now the PICTURE block added as a valid block type. Thanks!

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

Josh Coalson <xflac@yahoo.com> wrote: > --- Scott F <graue@oceanbase.org> wrote: > > > If I use flac to encode with the --replay-gain > > option, I get a warning about the --no-padding > > option... > > > > "NOTE: --replay-gain may leave a small PADDING block even with > > --no-padding" > > > > ...even though I'm

The test is rather simple, and only compares the computed output values for a 1kHz signal at the known filter table sampling frequencies with previously obained golden values. As such, the test only verifies that the performance of the replay gain analyser has not changed. A better test would be to compare the computed value with an independently obtain theorectical value. This is possible by

Just a quick question to make sure my understanding is correct on something. R128Gain is part of the opus standard and the information is part of the stream itself, correct? So if I use mkvmerge to take an opus stream from an ogg opus source and stick it into a Matroska audio, I don't have to worry about replaygain or r128gain tags because the opus stream itself will have the gain

have linux install on my laptop, and decide to clean up my music collection, found allot of my music that has replaygain tags, and allot don't. How would I fix the ones that don't have any replaygain tags, ? have flac and flac123 ogg ogg123 vorbistools and vorbisgain..etc, all installed, can play music fine, but when I hit a song, that doesn't have replaygain tags, need to turn down

I know Erik is busy with maintenance and wants to get a release out soon. In the meantime, is it appropriate to tag HEAD as 1.2.1_git and include this in the CLI tools (flac, metaflac, etc)? This would make it easier to allow programs in development to test against git flac and older flac versions. For example, sample rates above 48kHz (for ReplayGain) is available in git flac but not 1.2.1.

Hello, I'm currently doing a little music player using libflac and libao. What I've currently done works as it should, but I have a problem where only one metadata block is detected, even if there are more (it doesn't have the last attribute set to true). This is using flac 1.3.2 on Gentoo amd64. The main code file is attached, it mainly follows the examples given with the libflac