Ok we are getting somewhere…Neutron works fine in Cubase and Ableton. Ozone eq doesnt work in Cubase but works in Ableton…
I would simply use that but its not linear phase…critical for what Im doing
We’re stuck in the land of assumptions here. On one hand you could argue that there is an issue with Cubase since this particular operation works in DAW A, B and C. On the other hand, you could also argue that there is an issue with iZotope plugins since the operation in Cubase works for plugins X, Y and Z.
I tested with Neutron 3 Elements v3.10 on Cubase 12.0.70.
I’m using MIDI Remote.
Via a custom script.
In my screen recording above, no. But i could and the result would be the same.
First of all, for accuracy, there isn’t really anything such as “relative 14-bit” MIDI messages.
But regarding endless rotary encoders sending relative values; when Cubase 12 came out I started a long thread explaining how a scaling factor was missing in the mapping assistant. In a nutshell, the mapping assistant handles 3 flavors of relative MIDI CC messages and does so correctly. The issue is that mapped VST parameter is always scaled to a 7-bit resolution. That scaling should be user definable.
The only way around this limitation is to craft your own MIDI Remote script using the MIDI Remote API.
Sorry, don’t have it. I purchased an iZotope bundle on sale a few years ago but I ended up not really using any of them. I already have tools that much perform the same tasks that I’m more accustomed to. (The bundle came with some Exponential Audio plugins that I use on occasion, so it wasn’t a total waste.)
thanks @mlib
Ozone EQ was/is actually free I think…not why I bought it but they floated it as free. The reason why I particularly use it is because after sorting the myth from fact with all the rubbish out there…it has great phase linear filters, it is super cpu efficient and just as clean as anything on the market (that I could see), so…I push on
Yep, I was just basing my thoughts on what happens when I code to someones API, as time moves on, sometimes peeps obey the framework but from a perspective that is not considered in the original conception
Well it really doesnt need it with relative controllers but after couple of chats with Steve from Bome…seems its in the spec…ultimately I dont care how we get there; relative with precision is really the key for remote anyway.
I was on that thread and totally agree…in reality, I was just after a super res for issues like this…
Its actually the reason why Im not upgrading again until some of these key half baked issues are sorted…all the hype of remote turned out to just be frustration without coding which im not doing anymore…this is music right.
Its deeper as the automation is also at fault because of a precision issue anyway. Even the 14bit has issues with quickly getting to extents etc in Cubase (that I could see) so I coded ctrl ad shift for fast jump and finer tune with the unmod state being in the middle…Id be interested to see how you rigged your set up
Ive given up on trying to sort this…sent a bunch of stuff to ozone but unlikely they are interested based on other interactions I have had with them.
In the end I have just made filters in the required pos and turn them on and off…but pretty clunky.
Cheers
1 Like