Yeah, sorry about that... I haven’t had Bazille for several years, and not on the recent system. I didn’t realize I have all the old presets copied over.
Still, it seem like a strange issue to suss out on a new install.
Yeah, sorry about that... I haven’t had Bazille for several years, and not on the recent system. I didn’t realize I have all the old presets copied over.
Looking forward to CtrlA/B in RePro so hoping that's included whenever the next round of builds come (no rush)! I'd also love to see the Mod Matrix curves from Hive included too if that's a possibility.tasmaniandevil wrote: ↑Mon Jul 01, 2019 2:15 pmBecause there are some issues in current builds of Repro which we need to solve first.
Not so strange at all.
Yep, Ctrl A/B will of course be added to the next Repro update.Funkybot's Evil Twin wrote: ↑Mon Jul 01, 2019 7:16 pm Looking forward to CtrlA/B in RePro so hoping that's included whenever the next round of builds come (no rush)! I'd also love to see the Mod Matrix curves from Hive included too if that's a possibility.
There is no uninstaller, but there are instructions how to remove all files from your computer in this support article: uninstalling u-he plugins
Ah... Nothing like a surprise to keep you going!tasmaniandevil wrote: ↑Tue Jul 02, 2019 8:15 amNot so strange at all.
The latest build of Bazille is the first build that includes the new browser.
And it simply didn't "know" what to do when it encountered the very unusual "// author stripped" line instead of the normal author line it expected.
Quite an edge case, though. Even I didn't know that we had added this line to the old Bazille competition presets, so it was never tested what the new browser's preset scan would do in such a case. But now we know.
Any software with high resolution images will suffer notably. We could downsize the graphics but that would mean blurry looks on scaled up user interfaces. The performance hit is there, not just with our stuff.
VST3 MIDI Learn should work perfectly now. We do now "what the others have always done".
Well, if your host were to send tens of thousands of automation points per second, it sure wouldn't be a myth. CPUs would fry though, as the plug-ins would be very busy updating their states for every single samples. Block processing would become impossible.EvilDragon wrote: ↑Tue Jul 09, 2019 3:07 pm Isn't the point of sample accurate automation allowing specifying exactly what happens within an audio buffer - which for larger buffer sizes can definitely be important (and your internal plugin smoothing might not be sufficient). Correct me if I'm wrong?
We support 14-bitEvilDragon wrote: ↑Tue Jul 09, 2019 3:07 pmMIDI CCs are ok-ish, but their resolution is far from host automation resolution...
© KVR Audio, Inc. 2000-2024
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement