Displaying 20 results from an estimated 700 matches similar to: "R128gain & metaflac"
2014 Jun 16
3
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
2014 Jun 15
3
R128gain & metaflac
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?
Best regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xiph.org/pipermail/flac-dev/attachments/20140615/1c1ca9c9/attachment.htm
2014 Jun 16
0
R128gain & metaflac
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
2014 Jun 15
0
R128gain & metaflac
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.
2012 Feb 02
3
Meet the new maintainer
Olav Sunde wrote:
> very good to see activity on flac development again. I am not a developer
> unfortunately, but I'd like to check with you if updating code for
> flac/metaflac to handle high-rez files (24/192 or higher) for writing Replay
> Gain tags is in your 'pile' of things to fix?
I think there are patches to do that in the queue. Perhaps you can check
back in
2014 Nov 23
2
New release
I'd definately recommend binaries for download as suggested by lvqcl and Janne Hyv?rinen. All the fabolous work on the code base is of little use to me if I can not find binaries at the official site.
Olav Sunde
At 12:01 23.11.2014, Janne Hyv?rinen wrote:
>On 23.11.2014 12:44, Erik de Castro Lopo wrote:
>> lvqcl wrote:
>>> 2) Do you plan to release any official binaries
2014 Jun 18
4
R128gain & metaflac
>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
2014 Nov 23
0
New release
There have been some offers to help building for various platforms: http://lists.xiph.org/pipermail/flac-dev/2013-July/004271.html and there was discussion last year to create official ?blessed builds?, compiled by Xiph for security reasons. http://lists.xiph.org/pipermail/flac-dev/2013-July/004274.html
However, this sounds like something that can be sorted out after the release of the source
2013 Jun 27
1
flac-dev Digest, Vol 103, Issue 11
I posted Mac binaries a few weeks ago but nobody did anything with them, or
even acknowledged them.
Here is a DMG with a .pkg installer for Flac 1.3.0
https://dl.dropboxusercontent.com/u/52358991/FLACInstaller1.3.0.dmg
On Wed, Jun 26, 2013 at 3:00 PM, <flac-dev-request at xiph.org> wrote:
> Send flac-dev mailing list submissions to
> flac-dev at xiph.org
>
> To
2012 Feb 06
3
Meet the new maintainer
At 14:16 06.02.2012, you wrote:
>Olav,
>
>A change like this could easily break the format. That would be a bad choice.
That makes sense. Explains why it is not there today.
>On the other hand, an informational 'application' block could be added in a way that does not break the format, and this would even be backwards compatible since 'application' blocks have
2013 Jun 26
2
Sourceforge website redirecting
Olav Sunde wrote:
> under download, most links still point to Sourceforge with 1.2.1 as newest
Where?
On this page:
https://xiph.org/flac/download.html
there are links to OS specific builds of FLAC on sourceforge, but all the
main links are to Xiph.
Are you sure you're looking at the Xiph page and not the old sourceforge
page that may have been cached by your browser?
Erik
--
2017 Nov 27
0
R128Gain question
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
2013 Jun 10
4
FLAC 1.3.0 released
There are several links to Windows compiles in the Hydrogenaudio thread
for FLAC 1.3.0 at
http://www.hydrogenaudio.org/forums/index.php?showtopic=101082 .
On Unices or Linuxes building from git should be straightforward enough,
or you wait until the distributions/package maintainers catch up.
Also, congratulations to the whole development team for reinvigorating FLAC!
Christoph
On
2014 Jun 18
0
R128gain & metaflac
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
2014 Jun 19
0
R128gain & metaflac
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
2014 Jun 18
0
R128gain & 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
2014 Jun 19
2
R128gain & metaflac
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
2014 Jun 18
2
R128gain & metaflac
>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
2013 Jun 26
2
Sourceforge website redirecting
Olav Sunde wrote:
> I just followed the redirect Ralph Giles posted about above. That works
> as expected, but on https://xiph.org/flac/download.html the Windows
> link point to this page: http://sourceforge.net/projects/flac/files/flac-win/
> with only old compiles.
Thats correct. Xiph is responsible for the FLAC source code. Xiph does
not provide binaries for Linux, Windows or Mac.
2013 Jun 10
4
FLAC 1.3.0 released
Dear Free Audio Tool Lovers,
I am very pleased to announce the first official release of FLAC, the Free
Lossless Audio Codec, in over 6 years. FLAC is not dead! It is however a
mature software product that is now being maintained by a team working
under the auscpices of the Xiph.Org Foundation.
The executive summary of changes in this new version:
* Nothing major.
* Source tree is now hosted in