Yeah and the world really has gone full retard when people get cancelled for trying to defuse a situation with dark humour. Human beings are more complicated than the cartoons painted by the Rockefeller-sponsored pretend left.
It’s hilarious that I wouldn’t have got banned if I didn’t try to defuse anything and protect the person who got me banned.
Yeah and that leads to them taking permanent control of every contribution somebody has made, which - without prior agreement - is legally theft. There’s sharing by consent and sharing by force, which isn’t sharing.
This is still on the back burner btw, I refactored it back then but just the final touches to go. The drawing will be more CPU friendly now as well, which will be nice for the graphics thread. Not done anything with the actual maths/logic.
Here you go, I refactored it a bit/lot, gave it a nicer font and made the labels disappear when it’s small. It should still be improved though. I still want to change more stuff so I need to post it now.
( I could have been more organised with the git commits too, sorry 'bout that! )
It might still be a bug if you always need to make the mcp bigger. The CPU is low because it’s doing the calculations in the gfx thread, the CPU there should be lower now too because I’ve removed a couple of loops and the grid/labels are now drawn off screen and only redrawn when the window size changes now. The rest of the time the off screen buffer is just blitted.
The CPU readout will only show what the audio thread is doing so you could have software rendered Doom in a JSFX and it would show 0,01% if there was next to nothing happening in the audio thread.
Yeah, that sounds like a bug… I’ll have a look to see what’s happening.
I want to get 2 plugins down to 1, and expand their text
I use the Tukan Peak Needle 2 js plugin embeddeded in the MPC on all tracks
I set it up to show peak levels on the VU meter,
and the max peak displays in the bottom left.
Problem #1,
Embedded, the max peak is too small for me to read at an operating distance
It’s smaller than the Reaper meter peak text
Ideally it would be 3x larger than that or more, whatever fits and I don’t have to lean in close
Problem #2,
I run the Cockos Loudness meter after that,
setup to show just the LUFS integrated level in large text
The Tukan peak needle can also display LUFS,
so ideally it would display the LUFS INT level on the bottom right in large text,
while also showing max peak level on the bottom left,
and the momentary peaks on the needle.