More > JRiver Media Center 19 for Windows
NEW: Improved audio analysis and volume leveling (R128)
6233638:
--- Quote from: Vocalpoint on November 12, 2013, 09:48:59 am ---Since I had 60000 tracks to analyze over this weekend - I spent a bit of time watch MC do it's thing and noticed a peculiar "lag" in the first thread of a 4 thread analysis cycle. While the first track (Thread) seems to start with the others - it then starts to slowly grind along 5%, 9%, 11% sometimes stopping and waiting for awhile etc etc while the other 3 active rip right through from 0% to 100%....then when the next group of four are targeted - another thread seems to always lagging behind the other three.
--- End quote ---
This happens all the time - I suspect it's when MC is limited by disk/network speeds.
I have often requested that MC tries to assign a drive to each CPU core rather than working down the list of files sequentially to try and move the limiting factor back to your CPU rather than disk/network access.
I'd also like to see MC be "smarter" about how many files it's analyzing when limited by disk I/O.
Vocalpoint:
--- Quote from: 6233638 on November 12, 2013, 11:11:30 am ---This happens all the time - I suspect it's when MC is limited by disk/network speeds.
--- End quote ---
But I still see this behavior on local files...certainly not limited by disk I/O...that first thread always stands around like it has no idea what it should be doing :) Over the network - yes - could be anything - but that said - the other three threads - network or local - still burn through with lighting speed...
Something is going on with that first thread...maybe it's normal or by design?
VP
Hendrik:
I've not seen this, i typically use 3 threads and they all run just fine at about the same speed. More threads caused disc IO issues when analyzing video files, so i settled on 3 (it slowed down all analysis tasks, not just one, though)
Vocalpoint:
--- Quote from: Hendrik on November 13, 2013, 01:18:41 am --- I've not seen this, i typically use 3 threads and they all run just fine at about the same speed. More threads caused disc IO issues when analyzing video files, so i settled on 3 (it slowed down all analysis tasks, not just one, though)
--- End quote ---
I will crank it back to 3 today and see what happens.
VP
jamesecox50:
--- Quote from: InflatableMouse on November 10, 2013, 03:14:23 am ---Funny.
Of course, and I appreciate that. I didn't mean to imply the opposite. My previous post didn't quite come out the way I intended. I was tired, I rushed it and wanted to go to bed. And the toothpaste joke was just a silly joke, nothing more. I'm actually trying to understand this.
I've read this before and I just read it again with the wiki page on crest factor. I'm honestly trying to understand :P. I went back to the RR DR site and found a link to this which was also a site referenced above.
From that EBU – TECH 3342 pdf I found:
So there's that. Crest factor is not dynamic range. I get that. Then what is dynamic range (which is actually what I meant to ask all along)?
I found this:
Is that an accurate description of dynamic range then?
--- End quote ---
There may be no official standard but we know good DR when we hear it! The Loudness war movement is real and correlates well with my taste, R128 seems worthless. Thanks for incorporating DR, I was just starting to think the upgrade was farce, you squeaked her out though.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version