The big bug tier list

[ustk]

@ps Mmmm... That might be why I have a customer experiencing a bug, failing LogicPro validation... (though it works on some systems like mine)

[ps]

@ustk if you draw in an animation in ableton live for a plugin parameter it doesn't instantly jump to not automating because it thinks you interfered?

[Dan Korneff]

@ps I'm getting some reports from beta testers that automation is bunked in Cubase. Gonna take a closer look this weekend.

[ps]

@Dan-Korneff @ustk I can confirm that after reverting to the last commit before the new plugin parameter system was introduced makes the automations from the DAW work as expected again. I'm cherrypicking other later commits now to narrow it down.

[ustk]

@ps interesting, which commit is it?

[ps]

@ustk 02ac163c295b4ac053c6172b1567d9e0148d6e09
It would be very unlikely that DAW automation of plugin parameters (recorded) is not broken for any plugin compiled with a commit later than that. Once the parameter is changed by the DAW it reports back from the plugin again leading to the same behaviour as if you would have moved the slider - in ableton live this leads to "interference" mode which makes automations from the DAW simply not working.

[Lurch]

Clicking a draggablefilterpanel controlling a ParametricEQ within a panel that is disabled will hard crash HISE, and Cubase + Logic once the plugin is compiled. This is a real bummer as my latest plugin uses panels to display a series of effects which users can enable and disable, disabling the panel makes it visibly obvious the effect is off, but if a user was to click the panel they'd hard crash their DAW.

[d.healey]

@LozPetts said in The big bug tier list:

Clicking a draggablefilterpanel controlling a ParametricEQ within a panel that is disabled will hard crash HISE,

I'm pretty sure this bug has been around for a while. Place another panel over the EQ when it's disabled ;)

[HISEnberg]

@Dan-Korneff @ps Just got a report back that the automation system isn't working in Ableton properly. Thanks for sharing your insights.

[Dan Korneff]

Automation bug added here:

Previous automation data overwritten on playback when Read/Write automation enabled · Issue #749 · christophhart/HISE

Description: When Read/Write automation is enabled on the plugin, any previously recorded automation data is overwritten during playback. Haven't confirmed the commit that breaks yet. Steps to Reproduce: Load your host (e.g. Logic, Cubas...

GitHub (github.com)

[Christoph Hart]

@Dan-Korneff I added a comment with a manual fix, please check whether this solves it (it works with my minimal test plugin here but I could use some help in verifying the fix for real world projects as this is a rather sensitive problem).

[Dan Korneff]

@Christoph-Hart excellent. I'll give it a try now.

[HISEnberg]

Not sure if I should post this here or on the Github but I did a pretty deep test on MacOS and everything is working quite smoothly for the automation fix. I tested all types (AU/VST/VST3/AAX) on ProTools, Ableton, Logic, & Bitwig and I haven't had any issues, strange CPU spikes or crashes. Mind you I only tested my janky EchoPlex-FX plugin so will still need to test both an instrument plugin and on Windows.

macOS M2
Sequoia 15.1.1

My hats off to you for the fix @Christoph-Hart !

Edit* I should have shown the automation lane but the sliders are being modulated by automations, not by my mouse!

[Chazrox]

@HISEnberg this looks awesome!!!

[HISEnberg]

@Chazrox haha thanks it was just a small project for a class, now it’s just for running tests!