You should have "--r128-2011" in front of any other option. This kind of option loads a complete profile including all default settings, i.e. this kind of option effectively overwrites any other setting in front of it.

You should have "--r128-2011" in front of any other option. This kind of option loads a complete profile including all default settings, i.e. this kind of option effectively overwrites any other setting in front of it.

THX. I reckon that's a workaround for now!?!?

That's IMO a very "dangerous" behaviour you're describing. People can have settings overwritten without noticing it. Dependencies of options should be covered by the program.Even if put into the "help" area, the risk of not getting as result what was intented is pretty high.

That's exactly the same what the next version will do in the presence of "--quiet".

First of all. Good to see that I was not wrong.

Routing to >/dev/null is of course the easy way. Though I'd say it's better to avoid the printfs .

Scripting issue - once more:

Could it be that my earlier reported script problem is also located in the shell environment area. I'm running all kind of shell scripts since years and never had a problem with loops. You're also running a recursive loop inside your program. Maybe those loops interfere somehow. This problem is really bugging me.

I'm running all kind of shell scripts since years and never had a problem with loops. You're also running a recursive loop inside your program. Maybe those loops interfere somehow.

I'm not certain what the intention of your script is. I suspect that you try to descent down a directory tree. "r128gain" is doing exactly that.

1. I'm running quite some other actions on my files.2. I can move files around, I can change permissions3. I can run tailor made loops with certain search masks asf. asf

I used to use metaflac for applying rg-tags btw. That worked without problems by handing over *flac.

In my opinion/experience CLI programs don't need to implement smart recursive functions or similar. Like sox,flac,ecasound,metafac you name it. You hand over a set of filesan that's it. Much less hazzle for the programer.

I used to use metaflac for applying rg-tags btw. That worked without problems by handing over *flac.

That's the same with "r128gain": if you provide a list of FLACs it will process exactly these FLACs. You may use wildcards as well, i.e. "*.flac".

As far as I can see, your script does something else. Try the following:

CODE

find /tmp -iname '*.flac' -printf '%h\n' | sort -u

It gives you a list of directories including all sub-directories. "r128gain" will traverse recursively each directory. Your script will having run "r128gain" multiple times on the same sub-directories potentially colliding with itself.

You simply don't need the loop.

QUOTE (soundchekk @ Oct 30 2012, 15:55)

In my opinion/experience CLI programs don't need to implement smart recursive functions or similar. Like sox,flac,ecasound,metafac you name it. You hand over a set of filesan that's it. Much less hazzle for the programer.

That's your opinion. I prefer to have just a program without the need for writing additional scripts.

EDIT: If you change "$I" to something like "$I/*.flac" it may work, provided the shell expands the wildcard.

i followed this discussion trying to catch the most important points.i am not into programming, though - being left with a more or less "basic" question concerning the output of r128gain.exe:basically, the GUI works quite fine, giving me results after having specified input file.(my OS = Win7 64) But:1.the resulting analysis (in my case: -25.3 LUFS |-10.0 TPFS | range 13.8 LU ) - i would like the analysis be shown not only in the commandline but in a separate (explorer)window. is decent for being batch processed.2.i would like to be able to find the appropriate syntax for the CLI also: i did not get the point, which option should be specified for the output of the results ?(r128gain.exe --r128-2011 --true peak PfadWavOrdner\*.wav -->Results of analysis?3.the resulting analysis showed a wrong prefix in my case:FFmpeg successfully loadedanalyzing... [1/1] "test.686.wav": -25.3 LUFS <2.3LU>but it should read minus 2.3 LU (referring to -23LUFS=0LU), right?

Hope you guys do not get nervous about plain simple probs,nice work, this r128gain...Greez Nico

1.the resulting analysis (in my case: -25.3 LUFS |-10.0 TPFS | range 13.8 LU ) - i would like the analysis be shown not only in the commandline but in a separate (explorer)window. is decent for being batch processed.2.i would like to be able to find the appropriate syntax for the CLI also: i did not get the point, which option should be specified for the output of the results ?(r128gain.exe --r128-2011 --true peak PfadWavOrdner\*.wav -->Results of analysis?

I'm not sure what you mean. If you like to have the EBU R128 analysis from the command line you may type something like

CODE

r128gain file1.wav file2.wav file3.wav

or

CODE

r128gain infolder\*.wav

If you want to have the results saved in some file it looks like

CODE

r128gain file1.wav file2.wav file3.wav > analysis.txt

or

CODE

r128gain infolder\*.wav > analysis.txt

If you want to have the results written as REPLAYGAIN tags the corresponding commands look like