Hi Rory,
I am basically done with my Plugin. I finished it in Cabbage 2.6.11 because I already noticed this problem when I updated to the official 2.8.0 release.
So far everything else seems good, but the graphics of my parametric EQ doesn’t show up anymore. It’s build with a bunch of GenTables stacked upon each other. I tried it again with 2.8.65 (2.8.74 didn’t open after installation). I realised by accident that the updated graphic is shown when I close the window and open it again. I tried updating at i and k rate. The video shows what happens.
Here’s the script for that (a tiny bit large though EQ Curve13.csd (15.2 KB)
Is there anything that has changed recently, that you suspect could causing this?
Thank you so much for sitting with this!
Interesting that it makes a difference over
cabbageSet “table”, “tableNumber(1010)”
So then I changed the code for the individual bands to
cabbageSet SIdent, “tableNumber”,iB + 1000
and that works.
I don’t have to hide anything for it though. I would like to know what you have to hide to make it work as I’m planing to distribute. This .csd is a fully working stand alone version for the GUI of the parametric EQ part of my plugin, nothing missing there.
Yeah I would probably use an image for the lines rather than a widgetArray, I think it would be more efficient, and lead to less code, which I think is generally a good thing
That was already in 2.6. but you clearly advanced with it. I can drag an EQ band now while a soundfiler is scrolling through playback of a sample and everything is super smooth.
That’s incredible!!! And I’m getting really excited about my plugin this way. I wonder if it also loads faster now…
WHAT!!! HELL YEAH!!!
Loading time is basically eliminated. Wow!
I have a lot of filmstrips. One of them is quite large and is only for a nice look. I had to juggle a lot with resolution and “frame rate” to make the loading time acceptable. It just pops up now.
I can rethink some stuff there.
Oh yeah, that dramatically improved too! I worked with @Kzz on that one. He was sending more some incredibly complex instruments to test with. In the end I think we reduced the load time by more than a 2/3rds.