R128GAIN: An EBU R128 compliant loudness scanner Options

[pbelkner]

I've just uploaded on sourceforge a first version of r128gain, an EBU R128 (http://tech.ebu.ch/loudness) compliant loudness scanner:

http://sourceforge.net/projects/r128gain/files/

• process single files (tracks):
  
  • In order to just scan and analyze one file (WAV, FLAC or WV):
    
    CODE
    r128gain <file>
  • In order to scan, analyze and tag one file (currently only FLAC, result will be in <directory>):
    
    CODE
    r128gain <file> <directory>
  • In order to scan, analyze one file (WAV, WV) and encode and tag into FLAC (result will be in <directory>):
    
    CODE
    r128gain <file> <directory> flac
• recursively process directories (the content of a directory is considered an album):
  
  • In order to just recursively scan and analyze a directory:
    
    CODE
    r128gain <directory>
  • In order to recursively scan, analyze and tag a directory:
    
    CODE
    r128gain <directory> <directory>
    r128gain <directory>/* <directory>
  • In order to recursively scan, analyze a directory and encode and tag into FLAC:
    
    CODE
    r128gain <directory> <directory> flac
    r128gain <directory>/* <directory> flac

Tagging is currently supported only for FLAC:

• REPLAYGAIN_REFERENCE_LOUDNESS: always -23 LUFS (corresponding to EBU R128)
• REPLAYGAIN_TRACK_GAIN: loudness difference to -23 LUFS in LU measured for this track
• REPLAYGAIN_TRACK_PEAK: true peak measured at 192 kHz for this track
• REPLAYGAIN_ALBUM_GAIN: loudness difference to -23 LUFS in LU measured for the whole album
• REPLAYGAIN_ALBUM_PEAK: true peak measured at 192 kHz for the whole album

These tags should be honored by each Replay Gain compliant media player.

[Zao]

You cannot always dynamically link to a library, and in any way the LGPL is extremely vague when it comes to class templates, function templates and data in import libraries.

[cpchan]

You cannot always dynamically link to a library,

Please give me an example where you really have to link statically.

and in any way the LGPL is extremely vague when it comes to class templates, function templates and data in import libraries.

Don't know, I don't do C++. However, if is easy enough to ask at gnu.org, if you are interested. However, the program we are discussing is pure C

[mudlord]

You cannot always dynamically link to a library,

Please give me an example where you really have to link statically.

To avoid dependancy hell. I am sure FB2K users would appreciate one singular DLL to install rather then the library, SoX, etc, just to tag some files. >_> Sure, with "GNU/Linux" thats not a problem, but with Windows, it sorta is. >_>

Funny how people EXPECT Linux development philosphies to carry over to the Windows world. Well, sorry, we don't have package managers to install all dependancies. Sorry to jerk you around so much.

This post has been edited by mudlord: Jan 7 2011, 07:20

[googlebot]

To avoid dependancy hell. I am sure FB2K users would appreciate one singular DLL to install rather then the library, SoX, etc, just to tag some files. >_> Sure, with "GNU/Linux" thats not a problem, but with Windows, it sorta is. >_>

Funny how people EXPECT Linux development philosphies to carry over to the Windows world. Well, sorry, we don't have package managers to install all dependancies. Sorry to jerk you around so much.

Not even funny but rather irritating how people feel entitled to a demanding tone about something they have neither contributed to nor paid for. No one on this forum has any intention or purpose to fulfill your christmas wish list.

I think you have made your position clear several times. How about you program your own lib or shut up about this now?

This post has been edited by googlebot: Jan 7 2011, 11:28