• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Solved Issue with re-metering on a VST plugin on SP8 yet working on S7

parityflux

Member
I use Bute Loudness Analyzer 2 by Signum Audio. I have used it since S5 and it was working fine all the way through S7. It is my preferred metering solution because it keeps a running history of my levels and I can go back and address certain areas that might be peaking over my true peak. It gives me the same metrics as ADAPTR Streamline, Orban, Youlean Loudness Meter and iZotope Insight (thought Insight tends to do its math a little differently). Anyway I like it and I want to keep using it.

Properly operating, when I stop and start the DAW, the meter knows where in the song I am and re-meters starting wherever my song pointer is. Here's screenshot from S7. Whenever I restart my killer 2-bar song, the meter goes right back to beginning and overwrites its analysis:

bute1.png


In SP8, the metering does not reset its position and instead it continues on in the horizontal direction. I have no idea if the metering is right at this point and it defeats a lot of the purpose of having the graph in the first place:
bute2.png


Also, it has a warning in SP8 that "Remetering is not supported for VST3 in Unknown". I haven't devised a test yet that can check my actual numbers. The only way I guarantee it is by clearing the meters and restarting from the beginning. I liked not starting from the beginning when making tweaks as it was extremely close number wise and I could make a bunch of spot edits before running a full pass.

I am wondering if I should take this to Fender Support or to Signum? Or has anyone else using Bute, or another metering solution with history has come across this. Behavior changed from S7 to SP8, but maybe there was an SP8 change that was more standards compliant and broke this part of the VST. This is a VST3 (and I confirmed the same with the VST2 version just for a sanity check).

-John
 
My guess here is that the plugin is the source of the problem, I don’t use this plugin but other plugins that use the position of the DAW (like Metric A/B) and they all work fine here with FSP8. NERDY WORKAROUND: route your main output audio to a version of Studio One 7 where you pin the metering plugin onto the screen. You could use any stereo virtual audio routing plugin or driver for that.
 
Back
Top