More > JRiver Media Center 19 for Windows

NEW: Improved audio analysis and volume leveling (R128)

<< < (47/50) > >>

6233638:

--- Quote from: theoctavist on February 22, 2014, 12:11:49 am ---i still have no idea how to ID which files in my library are giving jriver audio analysis problems.

if there is a way to filter them, or some app for that purpose, that would be fantastic. would prefer to do it with jriver tho
--- End quote ---
If you manually run analysis, it will either error out, or stop progressing on bad files.

retro:
I'm trying this feature for the first time, and so far I have analyzed about 20000 of my ca 90000 files.
I have added the relevant columns like "volume level (replay gain)" etc. to see whats happening during the process. Its very interesting.

But, so far it has only analyzed my normal flac's and ape's with new values, none of my 24/48, 24/96, 24/192 or my sacd iso's have been analyzed or show any values in the new columns..?!? Why is that..?!?

Am I missing something..?!?


Edit.
A few of my 24/48 and 24/96 does get analyzed. But the majority wont...?!?

Edit no 2  8).
Manual analyze works! That makes me happy..!! I see now that analyzing sacd iso's takes a long time, at least on my Core2 server. So maybe this issue was a non-issue. Sorry.. ;D

Rafal Lukawiecki:

--- Quote from: 6233638 on August 19, 2013, 02:31:54 pm ---This expression will let you see how much headroom your tracks require. (it could probably be cleaned up - but it works)

--- Code: ---Delimit(if(isempty([Peak Level (R128)]),,formatnumber(math(removecharacters(left([Peak Level (R128)],5),/ /+,0)+RemoveCharacters([Volume Level (R128)],/ LU,0)+1),1)),/ dB,)
--- End code ---

--- End quote ---

Sorry for resuscitating an older thread, but I have a question regarding this expression and Volume Levelling in general. I have analysed audio in my library, and if I understand this expression it adds Peak Level R128 to Volume Level R128 plus 1. I have a track on Grofe Grand Canyon Suite album, track "Crickets and Distant Thunder". It shows:

Volume Level R128: 12.9 LU
Dynamic Range R128: 26 LU
Peak Level R128: -5.1 dBTP, -5.1 Left, -14.6 Right
Dynamic Range: 12
Headroom (from above expression): 8.8 dB

If I understand it correctly, this means it should clip heavily if it is volume levelled at the analysed setting of 12.9. My question is why Mac MC 20.0.40 (oops, should I start a thread in the new forum, Mac or Win?) calculate this value at a level that would lead to such high amount of clipping? Also, why is the Dynamic Range number consistently different from the Dynamic Range R128? 

mwillems:

--- Quote from: Rafal Lukawiecki on November 24, 2014, 12:13:59 pm ---Sorry for resuscitating an older thread, but I have a question regarding this expression and Volume Levelling in general. I have analysed audio in my library, and if I understand this expression it adds Peak Level R128 to Volume Level R128 plus 1. I have a track on Grofe Grand Canyon Suite album, track "Crickets and Distant Thunder". It shows:

Volume Level R128: 12.9 LU
Dynamic Range R128: 26 LU
Peak Level R128: -5.1 dBTP, -5.1 Left, -14.6 Right
Dynamic Range: 12
Headroom (from above expression): 8.8 dB

If I understand it correctly, this means it should clip heavily if it is volume levelled at the analysed setting of 12.9. My question is why Mac MC 20.0.40 (oops, should I start a thread in the new forum, Mac or Win?) calculate this value at a level that would lead to such high amount of clipping? Also, why is the Dynamic Range number consistently different from the Dynamic Range R128?  

--- End quote ---

You have it backwards; the 12.9 number is the number of dB by which the track is attenuated for volume leveling, not boosted.  Volume leveling only works by attenuation, it never rarely adds boost [EDITED: because I was incorrect).

The two dynamic ranges are different because they measure very different things. I explained the difference between the two in detail here: http://yabb.jriver.com/interact/index.php?topic=84489.msg577389#msg577389

Rafal Lukawiecki:

--- Quote from: mwillems on November 24, 2014, 12:27:17 pm ---You have it backwards; the 12.9 number is the number of dB by which the track is attenuated for volume levelling, not boosted.  Volume levelling only works by attenuation, it never adds boost.

--- End quote ---

If I understand you correctly, this might then be a bug, as in this case the Volume Level R128 is, actually, a positive figure of 12.9, not a negative number, like for majority of my tracks. I understood that negative meant attenuation but positive values meant volume boosting. I have 332 tracks for which Volume Level is a positive number. Why would this happen?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version