Zebra 2.9 released

[PALU]

I already have.. diva, hive, repro and ace.. does it make sense to get zebra as my next synth or should I rather look at Bazille?

The genre of music I want to create is pop, synthwave and cinematic music

For cinematic music - I think Zebra is better then the rest and there are millions of presets. Bazille sounds a little to sterile and not very "cinematic" to me, but it's completely subjective.

[Ploki]

Hm, me too. which computer?
I'm running Mini on ultrafine 4K, 10.14.6.
Can you do a video capture see if its the same here or am i just less sensitive about that?

Hm, no, can you please prove by screen capture that scrolling is running smoothly with your Mac? Since I have multiple Macs, and it is the same on all, so I do not need a proof that my statement is true. Since you are questioning it, please prove it.

I wasn't dismissing your point or trying to play it down, I was genuinely curious what behaviour you're observing to compare it on my own system since I have a similar one.

Anyway, I will upload a clip of mine as soon as it renders

[Hanz Meyzer]

Ok thx. Can you also record in 60fps and show the detail editor of the OSC editor? And scrolling of the modular elements.

[Ploki]

Ok thx. Can you also record in 60fps and show the detail editor of the OSC editor? And scrolling of the modular elements.

https://www.dropbox.com/s/fdt6j9xc3pa3h ... i.mov?dl=0

this is how it looks here.
I understand what you would mean by not smooth, but I also don't notice a difference compared to 2.8

[Hanz Meyzer]

I now re-checked v2.8, and 2.8 clearly draws a bunch faster than 2.9 here. Very visible in the zoomed/full OSC editor. I think the GUI speed in 2.9 so far is not ok, it should be at least as fast as 2.8, which wasn't smooth 30 or 60 fps anyway.

[Urs]

I now re-checked v2.8, and 2.8 clearly draws a bunch faster than 2.9 here. Very visible in the zoomed/full OSC editor. I think the GUI speed in 2.9 so far is not ok, it should be at least as fast as 2.8, which wasn't smooth 30 or 60 fps anyway.

As I said, rolling back to where we were before this is a no go on Mojave and later. It will not happen.

A rewrite for Metal is a no go as well, we will not be able to make this in time for Catalina support.

We will evaluate dropping thew zoomed editors as they obviously don't always get hardware acceleration, depending on colour sync profile and operating system. Maybe an additional skin which does not contain overly large editors is way to go for people who experience these issues with their systems.

[Ploki]

I now re-checked v2.8, and 2.8 clearly draws a bunch faster than 2.9 here. Very visible in the zoomed/full OSC editor. I think the GUI speed in 2.9 so far is not ok, it should be at least as fast as 2.8, which wasn't smooth 30 or 60 fps anyway.

oh you meant the "full screen" editor OSC?
I just checked, wont even post a video - indeed works like crap, draw rate is like 5fps.

[Hanz Meyzer]

Hm, but most plugins with 4k support and 120% scaling, not having any special OpenGL/Metal support, just Cocoa or so, e.g. Synthmaster One, also are displayed very smoothly here, no lag, high framerate. So I would assume there is something wrong in your approach, or something unusual is lagging it. Also I wouldn't think your current approach will work any faster then in 10.14 or 10.15, since those are slower in CPU benchmarks vs. 10.13.

If you decide to improve it, I will be happy to help you with testing, if required.

Please have a look onto the videos I PMed to Victor.

[Urs]

Please check that your colour profile is set to sRGB IEC61966-2.1

[Hanz Meyzer]

Yep, it is.

Bildschirmfoto 2019-11-24 um 23.08.39.PNG

[Urs]

Then I simply don't know how to help you.

[Dewdman42]

Try the generic "Apple RGB" profile.

[Dewdman42]

I had an issue with DP10 and one other plugin on my MacPro. couldn't figure it out until someone suggested I used the generic Apple RGB profile. I was using a custom calibration profile that I made using the OSX color calibration feature. Well basically if you are using any kind of custom color profile, an extra color conversion takes place on every pixel, and obviously the more pixels you have, the more CPU it takes to do it. Some programs suffer from it and some others do not. I talked with a well known developer that told me how he worked around it to avoid excessive color conversion from happening, but ultimately when I switched back to the generic "Apple RGB" profile, the problem went away entirely with all programs I am using, including DP10, a couple plugins and even Facebook on Safari was suffering from this problem until I changed my color profile to the generic one, which somehow avoids doing extra color conversions in some programs.

As it turns out, my display had an sRGB profile in the monitor that I wasn't using either and when I switched to that, combined with "Apple RGB" everything looks way better too.

And by the way I am using 3008x1692hiDPI on a 4k monitor. Problem solved with "Apple RGB"

[Hanz Meyzer]

Guys, on the same system (on which the SRGB profile is the speedy/24 bit one, btw. I was the one once posted that SRGB profile info in here to the developer section, since I watched it on admiral bumblebee yt channel) Zebra 2.9 is quite a bit laggier than Zebra 2.8. So it is obviously caused by Zebra 2.9. Also no other plugin is having such a slow GUI. If Urs doesn't want this to be fixed, ok, then it is like that. Also 2.9's GUI is slower on all my Macs, not only one. The systems are 10.13.4 and 10.13.6, which I will continue to use, until all software is safe for system update (which could take another year or so). I am also pretty sure that all are affected, you only might have a more recent core i5/i7 generation than I have, which is 20% faster on single core, so you didn't realized it as much.

[Urs]

The obvious problem is that it is not transparent to anyone whether or not drawing is hardware accellerated or not, and what conditions need to be met under which system. We can only blindly try something else and hope for the best. Maybe, if it works for us, it might work for you. But maybe it will break something else on someone else’s system.

The most promising approach is to abandon anything older than, say, 10.12. That’d shut out roughly a quarter of our customers on macOS. Not sure if I’d rather live with a bit of jaggy movement, or if dropping the large editors would be the smallest issue here.