Bazille 1.1.1 RC revision 10667

[Yorrrrrr]

Interface is laggy on Live 11 Beta, MacOS Big Sur, VST2 version.

[mholloway]

Interface is laggy on Live 11 Beta, MacOS Big Sur, VST2 version.

Same here with Mac OSX Catalina.

Like a lot of plugins ever since Catalina, if you switch the OSX 'color mode' to sRGB, the graphic performance of the UI improves substantially.

[pdxindy]

Is there some way to disable the auto increment on presets?

I just checked and it's called "Auto Versioning" in the options.

Edit: In the Tokyo Ghost skin, it seems to be called "Generational Save".

Thanks!

[tslays]

...........................

[Urs]

Yeah, we have pretty much identified the main culprits for slow drawing on MacOS since Mojave. It's mostly related to a new thingy where Apple converts bitmaps to colour profiles on the CPU (as opposed to GPU), which neither Windows nor pre-Mojave MacOS do. It's particularly evil with so called High Gamut displays which have more than 32 bits per pixel and cause MacOS to exhaust the CPU. In addition, MacOS X also apparently *resizes* bitmaps on the CPU which it never did since the GPU could do it in no time. The outcome for us is quite hilarious, as we're now forced to pre-grade and pre-resize all UI-bitmaps for all monitors attached to your computer...

Another issue is that normally a UI only needs to draw the areas of change. Since Mojave (maybe earlier) however, the OS collects all these areas, then lets our plug-ins update a whole big rectangle made up out of those areas merged together. As a result, all plug-ins with a keyboard control and an info-display on top for instance pretty much draw 90% of the UI the whole time. Our measurements show that on average, MacOS draws ten times more pixels than necessary on each UI update since Mojave.

A major refactoring of our UI stuff is on its way, but it takes quite some time. And it eats on backward compatibilty. This Bazille release will come as is, and it will be the last 32-bit release on MacOS (ah, it's already 64 bit only on Mac, but it's the last Intel-only release). There will be another Bazille update early next year when we publish native support for Apple Silicon, and we expect to resolve the issues on Mojave. But don't expect wonders, finding our how to workaround these undocumented changes is a tedious process.

Another problem is that the workaround we found for Mojave/Catalina's excessive need to draw too many pixels does not work at all on Big Sur, again without any documentation by Apple as to why that is. So we're going to spend a few weeks trying to figure out what Apple did this time.

*sigh*

[billcarroll]

Interface is laggy on Live 11 Beta, MacOS Big Sur, VST2 version.

Same here with Mac OSX Catalina.

Like a lot of plugins ever since Catalina, if you switch the OSX 'color mode' to sRGB, the graphic performance of the UI improves substantially.

How are you switching to a sRGB Color Space in macOS Catalina and Big Sur, or are you talking about switching color profiles?

[tasmaniandevil]

How are you switching to a sRGB Color Space in macOS Catalina and Big Sur, or are you talking about switching color profiles?

System Preferences > Displays > Colour: uncheck the "show profiles for this display only" option, then scroll down and choose the sRGB IEC61966-2.1 profile.

[elnn]

Yeah, we have pretty much identified the main culprits for slow drawing on MacOS since Mojave. It's mostly related to a new thingy where Apple converts bitmaps to colour profiles on the CPU (as opposed to GPU), which neither Windows nor pre-Mojave MacOS do. It's particularly evil with so called High Gamut displays which have more than 32 bits per pixel and cause MacOS to exhaust the CPU. In addition, MacOS X also apparently *resizes* bitmaps on the CPU which it never did since the GPU could do it in no time. The outcome for us is quite hilarious, as we're now forced to pre-grade and pre-resize all UI-bitmaps for all monitors attached to your computer...

And they don't inform developers when they make such changes?
They're so intent on making things "simple" that they leave out such basic and simple requirements, it's sometimes mind-boggling. Such a huge revenue, such little consideration. (And I have a feeling they wouldn't change it because it would be a silent acknowledgement that they were wrong… and as it is not something that's accessible to the public, they can't spread the news of how large and new their decision is…). I'm sometimes ashamed that I love their OS.

[billcarroll]

How are you switching to a sRGB Color Space in macOS Catalina and Big Sur, or are you talking about switching color profiles?

System Preferences > Displays > Colour: uncheck the "show profiles for this display only" option, then scroll down and choose the sRGB IEC61966-2.1 profile.

Ahhh, gotcha. Thanks. You're saying switching color profiles gave you increased graphics performance?

[Urs]

Yeah, we have pretty much identified the main culprits for slow drawing on MacOS since Mojave. It's mostly related to a new thingy where Apple converts bitmaps to colour profiles on the CPU (as opposed to GPU), which neither Windows nor pre-Mojave MacOS do. It's particularly evil with so called High Gamut displays which have more than 32 bits per pixel and cause MacOS to exhaust the CPU. In addition, MacOS X also apparently *resizes* bitmaps on the CPU which it never did since the GPU could do it in no time. The outcome for us is quite hilarious, as we're now forced to pre-grade and pre-resize all UI-bitmaps for all monitors attached to your computer...

And they don't inform developers when they make such changes?
They're so intent on making things "simple" that they leave out such basic and simple requirements, it's sometimes mind-boggling. Such a huge revenue, such little consideration. (And I have a feeling they wouldn't change it because it would be a silent acknowledgement that they were wrong… and as it is not something that's accessible to the public, they can't spread the news of how large and new their decision is…). I'm sometimes ashamed that I love their OS.

They *might* have notes or something, but we can't spend a week or two every year to read about every little aspect they "improve". When something seems odd, we consult the developer documentation. The documentation of the services we use ("Quartz", "CoreGraphics") looks nearly identical to what it looked like ten years ago. But still, some things have started behaving differently, and it's a bit of a guessing game as to what to make out of that.

[pdxindy]

Having fun with Bazille...

https://dandelionaudio.com/sound/B-Seq-2.mp3

[Shabdahbriah]

^^^

[Blogbert]

Having fun with Bazille...

https://dandelionaudio.com/sound/B-Seq-2.mp3

That sounds like that synth that isn't working properly... which is what I often aim for with my Bazille patches.

I am also happy with Bazille pretty much as it is, though I do enjoy daydreaming about possible features, which I have done in another thread. In my opinion, it would be good if you could overdrive the filters without losing the efficacy of BP and HP filtration - currently, if you overdrive a filter, only the LP outputs actually filter the sound consistently. That's the only issue where I think there is room for improvement... I'd be interested in how the developers or other users feel about this characteristic of Bazille's filters. Anyway, it's still the #1 synth in my opinion.

Here's a thing I've been working on (everything is Bazille except simple kick and snare pattern):
https://voca.ro/15pk5vsxxrh7