Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion.

Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules.

 

Go Back   Doom9's Forum > Programming and Hacking > Development

Reply
 
Thread Tools Search this Thread Display Modes
Old 2nd August 2019, 02:51   #1621  |  Link
T-Hawk
Registered User
 
Join Date: Jul 2019
Posts: 2
Quote:
Originally Posted by LoRd_MuldeR View Post
It is important to understand that the ReplayGain tag that LAME is creating (by default) is nothing but a meta information. It does not alter the volume of the audio file at all!

ReplayGain normalization happens, if at all, at playback time. So, IMO, there are only two possible situations:
  • If you do want ReplayGain to normalize the volume of you media files, then you need a playback software that supports ReplayGain and your media files need to contain proper ReplayGain meta information.
    The latter is exactly what LAME is doing (by default). In other words, LAME prepares the created MP3 files for ReplayGain processing, but the actual processing happens in your playback software.
  • If you do not want ReplayGain to normalize the volume of you media files, then use a playback software that does not support ReplayGain –or– just disable the ReplayGain feature of your playback software.
    Either way, as long as ReplayGain is disabled (or unsupported) in your playback software, the ReplayGain meta information that may be present in the media file will simply be ignored.

tl;dr If you don't like ReplayGain processing, then disable it in your playback software
I would rather just not have to deal with it. It's not always obvious if a particular player is using ReplayGain and how to disable it. Foobar and Audacity are not adding the "meta information" to the best of my knowledge and both are using the LAME encoder. So I assume it is a LAMEXP default and not a LAME default. Looks like I will just use Foobar from now on and have to go back to the files I've already converted with LAMEXP and remove the track volume info.
T-Hawk is offline   Reply With Quote
Old 2nd August 2019, 05:08   #1622  |  Link
manolito
Registered User
 
manolito's Avatar
 
Join Date: Sep 2003
Location: Berlin, Germany
Posts: 2,632
Quote:
Originally Posted by manolito View Post
But there is a command line switch in Lame.exe which disables calculation of the ReplayGain value, maybe adding "--noreplaygain" to the custom MP3 parameters in LameXP will fix it for you.
Have you tried this workaround?
manolito is offline   Reply With Quote
Old 2nd August 2019, 19:49   #1623  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,047
Quote:
Originally Posted by T-Hawk View Post
So I assume it is a LAMEXP default and not a LAME default. Looks like I will just use Foobar from now on and have to go back to the files I've already converted with LAMEXP and remove the track volume info.
Nope, it really is a LAME default. LameXP does nothing to enable ReplayGain tag generation. Though, LameXP does northing to disable this default behavior of LAME either.

See LAME manpage:
https://linux.die.net/man/1/lame

Quote:
--noreplaygain
Disable ReplayGain analysis.
By default ReplayGain analysis is enabled. This switch disables it.
Manually add switch "--noreplaygain" to custom parameters, if you really wish to suppress ReplayGain tag creation.
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.



Last edited by LoRd_MuldeR; 2nd August 2019 at 19:53.
LoRd_MuldeR is offline   Reply With Quote
Old 11th August 2019, 18:23   #1624  |  Link
LoRd_MuldeR
Software Developer
 
LoRd_MuldeR's Avatar
 
Join Date: Jun 2005
Location: Last House on Slunk Street
Posts: 13,047
LameXP v4.18 Beta-5
https://sourceforge.net/projects/lam...6.exe/download

Quote:
Changes between v4.17 and v4.18 [unreleased]:
* Upgraded build environment to Microsoft Visual Studio 2017.9 (MSVC 14.16)
* Updated LAME encoder to v3.100.1-SVN (2019-07-23), compiled with ICL 19.0 and MSVC 14.16
* Updated Opus encoder/decoder libraries to v1.3.1 (2019-04-14) and Opus-Tools to v0.2+3 (2018-10-16)
* Updated Vorbis encoder to OggEnc v2.88 (2018-11-14), using libvorbis v1.3.6 with aoTuV b6.03 (2018)
* Updated FLAC encoder/decoder to v1.3.2+ Git (2018-09-19), compiled with ICL 19.0 and MSVC 14.16
* Updated Monkey's Audio binary to v4.73 (2019-05-15), compiled with ICL 19.0 and MSVC 14.16
* Updated mpg123 decoder to v1.25.11 (2019-07-18) and added 64-Bit binaries, compiled with GCC 9.1.0
* Updated MediaInfo to v19.07 (2019-07-16), compiled with ICL 19.0 and MSVC 14.16
* Fixed encoding with Nero AAC encoder for input sampling rate less than 8 KHz or greater than 96 KHz
__________________
There was of course no way of knowing whether you were being watched at any given moment.
How often, or on what system, the Thought Police plugged in on any individual wire was guesswork.


LoRd_MuldeR is offline   Reply With Quote
Reply

Tags
aac, aotuv, flac, lame, lamexp, mp3, mp4, ogg, oggenc, opus, vorbis

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +1. The time now is 22:47.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2019, vBulletin Solutions Inc.