Tiny patch for vu meter testing about as

[aebrouse]

with or without bidoo still get issue. oh and I did try to set processor priority on my system for rack to highest possible. no change.

[AScustomWorks]

Tested this patch too, it worked fine so... I can't reproduce the error. I even complicated things a little bit:

Now, Andrew says audio processing and graphic processing run on separate threads but I'm suspecting that somehow the graphic side is taking a toll on your particular computer/processor/graphic card combo, and well, you computer is not precisely new ;)

I'll keep looking into this but as I can't reproduce the glitches my recommendation for now is to try to not use the VU meters all over the place.

I know they give a nice visual feedback, but mostly VU meters are just eye candy when used like you are doing, on the lfo signal path for example as it probably won't be saturated at any point, and that's the main goal of a VU meter, to check for saturated levels.

So if you need a visual input to see what's going on, maybe ML volt meter module is best in your case?

I may add my own version of a volt meter to AS modules later on ;)

[aebrouse]

Thanks, Freddy.. yeah I liked the eye candy but can work without it .. has me curious if the Nsynthi meters would give me issue.. oh well not a MAJOR issue glad we could make certain of THAT 😊

…

________________________________ From: Freddy <[email protected]> Sent: Tuesday, April 3, 2018 2:58 PM To: AScustomWorks/AS Cc: aebrouse; Author Subject: Re: [AScustomWorks/AS] Tiny patch for vu meter testing (#16) Tested this patch too, it worked fine so... I can't reproduce the error. I even complicated things a little bit: [vus]<https://user-images.githubusercontent.com/34798768/38259984-0d8c280a-372c-11e8-9645-5da4849e0bba.jpg> Now, Andrew says audio processing and graphic processing run on separate threads but I'm suspecting that somehow the graphic side is taking a toll on your particular computer/processor/graphic card combo, and well, you computer is not precisely new ;) I'll keep looking into this but as I can't reproduce the glitches my recommendation for now is to try to not use the VU meters all over the place. I know they give a nice visual feedback, but mostly VU meters are just eye candy when used like you are doing, on the lfo signal path for example as it probably won't be saturated at any point, and that's the main goal of a VU meter, to check for saturated levels. So if you need a visual input to see what's going on, maybe ML volt meter module is best in your case? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#16 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AkNbgH7CwzOo1H3tvB_qCx-Ctvt9uPQKks5tk8Y8gaJpZM4TDKJ5>.

[AScustomWorks]

Oh, good idea about testing with Nysthi meters, he probably made his own implementation (I'm using vcv rack own method).

Now you got me thinking, maybe adding a bypass switch to the meters could be useful, so you can set them off without having to rewire everything.

[aebrouse]

I have yet to bother with the Nsynti VU modules just yet. I have been trying to learn all the new sequencers that we have been veritably FLOODED with 😊. If I had my way, EVERYTHING would have bypass switches 😊 Ha Ha! Though an eight channel vu meter to match the HP footprint of your WONDERFUL mixer would be nifty item for a future update 😊 ( yeah my ocd screams about the mono and stereo VU's not lining up out evenly in HP to the mixer)

…

________________________________ From: Freddy <[email protected]> Sent: Wednesday, April 4, 2018 10:35 AM To: AScustomWorks/AS Cc: aebrouse; Author Subject: Re: [AScustomWorks/AS] Tiny patch for vu meter testing (#16) Oh, good idea about testing with Nysthi meters, he probably made his own implementation (I'm using vcv rack own method). Now you got me thinking, maybe adding a bypass switch to the meters could be useful, so you can set them off without having to rewire everything. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#16 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AkNbgJvZBDAXsuq7M_YpF4OFa4ZApyIEks5tlNo_gaJpZM4TDKJ5>.

[patman023]

Sorry to flog a dead horse, but is there a way to set a frame limit on the VU Meters? I can barely keep a single one of them in my current patch with the sizeable amount of crap going on, but I need at least one for record monitoring, and one for live monitoring, to avoid clipping.

Is it possible to only sample the incoming value at say, 20 or 40 Hz? Anything beyond that is extraneous data for adjusting levels with IMO.

[AScustomWorks]

I'll take a look to see if it can be restricted to lower frame refresh ;)