![Smile :)](./images/smilies/icon_smile.gif)
So no, this won't happen for Surge.
Getting a better foundation in place w/ JUCE rather than getting distracted by putting out too many fires before then makes total sense to me. I mention the remaining related issue knowing it might be easier to address later, and again suggest a workaround to help address questions in the meantime.baconpaul wrote: ↑Thu Feb 04, 2021 2:43 pm Yeah it was easy enough (https://github.com/surge-synthesizer/su ... 3807/files there's the diff)
Would have been impossible before 1.7. There's a massive diff required behind that that which makes typein values work in the UI. Luckily we wrote that last summer! Now just refactoring to re-use that code through the VST3 api here.
should be in a nightly in an hour or two. And should work in any VST3 host that supports that VST3 API point. But I only tested bitwig mac.
There are three primary things motivating our port to juce. The first is just raw software quality vs our current platform. The second is missing a particular widget which isn’t important right now in vstgui. The third is I couldn’t bear the idea of writing a proper patch browser in vstgui when juce was just - you know - sitting there.Held wrote: ↑Fri Feb 05, 2021 12:01 am Is it possible to change the font size of the patch browser? It's so big that I have to scroll about two pages to get to the bottom. The scroll speed with the mouse wheel is also really slow.
I would also prefer to have the user patches at the top since I use those most often. Is there currently a way to change this?
(I'm on Manjaro Linux with REAPER v6.18 if that matters)
Thanks for all the great work you're doing with Surge!
So just so I understandbboxdw wrote: ↑Thu Feb 04, 2021 9:56 pmGetting a better foundation in place w/ JUCE rather than getting distracted by putting out too many fires before then makes total sense to me. I mention the remaining related issue knowing it might be easier to address later, and again suggest a workaround to help address questions in the meantime.baconpaul wrote: ↑Thu Feb 04, 2021 2:43 pm Yeah it was easy enough (https://github.com/surge-synthesizer/su ... 3807/files there's the diff)
Would have been impossible before 1.7. There's a massive diff required behind that that which makes typein values work in the UI. Luckily we wrote that last summer! Now just refactoring to re-use that code through the VST3 api here.
should be in a nightly in an hour or two. And should work in any VST3 host that supports that VST3 API point. But I only tested bitwig mac.
The Bitwig knob and Surge slider values differ in value when turning the Bitwig parameter knob. They seem to systematically differ by one point of resolution (from the perspective of the Bitwig knob). This is with no Bitwig or Surge LFO modulating the parameter.
In other words, if turning the Bitwig knob for A Filter 2 Cutoff jumps from values of 680.54 to 706.57 Hz, setting that parameter at 680.54 in Bitwig will set it at 706.57 in Surge. When increasing the value with the Bitwig knob, the Surge value is one step higher, and when decreasing the value with the Bitwig knob, the Surge value is one step lower. I've observed this with the filter cutoff, filter envelope, and LFO rate parameters (latter when not synced to tempo--works perfectly when synced to tempo).
In addition to the latest nightly, I went back and checked it with the 1.8.1 release version. Same thing there, so not an issue intro'd w/ the latest changes.
Recommended user workaround: When you make the adjustment within the Surge GUI, the Surge slider and Bitwig values match up exactly. So do it there in the meantime if you need a particular value to be exact, or if you're working with a parameter where one point of resolution is a significant difference.
Thanks for seeking clarification. I'm pretty sure we're on the same page. If you need more info, or further explanation, let me know.
I'll give one more example, just to make sure we're on the same page with the term "resolution minimum."
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement