I see your point, but you also have proved mine.
Maybe fixed is the wrong word. Right and wrong don't exist. They are nothing more than human constructs, ideas. But they are useful terms to describe a correct path to your destination.
Your description of humans being too slow is indeed the whole purpose of peak hold, so we can physically see if the peak has gone over the 0db threshold and therefore clipped the signal.
As clipping is always an unwanted artifact of audio production, and that recording from noisy sources, such as mics, require you to set recording volumes high as possible, you need a peak hold so you can get as close to 0db without clipping.
So my description of Rm being 'wrong' is in fact correct from my perspective as my goal is to maximise the signal whilst avoiding clipping. But as Rm was designed purely with 'entertainment' value in mind then, yes, I understand I am also wrong for expecting it to be something it isn't.
That said, I am a perfectionist, and believe that if you're going to do something, do it right. Right in this instance is as I described above, which is from a professional audio engineers perspective. No audio engineer would be able to work from that kind of peak hold set up, it's literally not possible and is actually pointless from that perspective. So 'fixed' is the correct term from that perspective. Is it not? If the CPU monitoring wasn't right, it would be 'fixed', why? Because it has a definitive purpose. There is no room for error. But as the VU Peak meter has no defined way of working, it is open to interpretation. But the interpretation for something like this should be from the standpoint of a pro audio engineer. That is, of course, only my opinion, but shouldn't it be how it works to ensure correct and proper usage for everyone?
I'm not trying to be argumentative, or arrogant, or attack you or anyone here, sorry if it appears so. My aim is to explain that there is a perfectly valid reason why peak hold exists, and why there should be a peak hold setting in the plugin.![:)]( "Smiler")
![:thumbup:]( "Thumbs Up")
Maybe fixed is the wrong word. Right and wrong don't exist. They are nothing more than human constructs, ideas. But they are useful terms to describe a correct path to your destination.
Your description of humans being too slow is indeed the whole purpose of peak hold, so we can physically see if the peak has gone over the 0db threshold and therefore clipped the signal.
As clipping is always an unwanted artifact of audio production, and that recording from noisy sources, such as mics, require you to set recording volumes high as possible, you need a peak hold so you can get as close to 0db without clipping.
So my description of Rm being 'wrong' is in fact correct from my perspective as my goal is to maximise the signal whilst avoiding clipping. But as Rm was designed purely with 'entertainment' value in mind then, yes, I understand I am also wrong for expecting it to be something it isn't.
That said, I am a perfectionist, and believe that if you're going to do something, do it right. Right in this instance is as I described above, which is from a professional audio engineers perspective. No audio engineer would be able to work from that kind of peak hold set up, it's literally not possible and is actually pointless from that perspective. So 'fixed' is the correct term from that perspective. Is it not? If the CPU monitoring wasn't right, it would be 'fixed', why? Because it has a definitive purpose. There is no room for error. But as the VU Peak meter has no defined way of working, it is open to interpretation. But the interpretation for something like this should be from the standpoint of a pro audio engineer. That is, of course, only my opinion, but shouldn't it be how it works to ensure correct and proper usage for everyone?
I'm not trying to be argumentative, or arrogant, or attack you or anyone here, sorry if it appears so. My aim is to explain that there is a perfectly valid reason why peak hold exists, and why there should be a peak hold setting in the plugin.
Statistics: Posted by sl23 — Today, 7:26 am