The big bug tier list

[aaronventure]

@DanH said in The big bug tier list:

but I have to re-set my midi controller in the Hise settings every time I open Hise!

this happens on crashes too, but I've been using this for a long time now and completely forgot that this is still actually an issue

https://forum.hise.audio//post/80689

defo not a long term solution but might help your sanity until it gets fixed. the fact that I can hardcode it like that with a few lines of code and it remains consistent through everything means it should not be that hard of a fix so we never ever have to go back and change it

There we go, I made an issue for this

Too many requests · GitHub

(github.com)

[DanH]

@aaronventure applied the workaround - keyboard works (great) but error message still appears upon loading Hise.

[aaronventure]

@DanH yep, happens here occasionally as well

[d.healey]

Timestretch causing pops and white noise · Issue #718 · christophhart/HISE

I'm finding that enabling time stretching on a sampler is causing artefacts during playback, even with the ratio unchanged. Forum thread: https://forum.hise.audio/topic/11966/bug-timestretch-causing-pops-and-white-noise

GitHub (github.com)

[clevername27]

ScriptNode Clone Nodes don't compile under some circumstances. Verified with other developers.

[aaronventure]

Code-only UI declaration is broken because of this. This bug seems to have been around for at least 2.5 years!

[Engine] setZLevel() doesn't execute on init · Issue #731 · christophhart/HISE

const button = Content.addButton("btn", 0, 0); const panel = Content.addPanel("pnl", 0, 0); button.setZLevel("Front"); It has to be called with a delay so that it executes after init, because calling in during init does nothing. Also, ca...

GitHub (github.com)

[d.healey]

@aaronventure said in The big bug tier list:

Code-only UI declaration is broken because of this.

Declare your components in the order you want them to be at init.

[aaronventure]

@d-healey ah that's true, but that will forces a way of grouping components by place instead of functionality and messes with certain aspects of modularity. Also, you have to delete the entire component list every time you want to make a change, which means that you have to do the UI entirely in code (else you lose any property changes you put in by hand.

Kontakt had Z_LAYER since 2017.

[Christoph Hart]

@aaronventure don't want to derail this topic from its intentional purpose, but you can easily rebuild the component tree by clicking on the refresh button in the interface designer, this way you don't have to

do the UI entirely in code

[Goodflow]

This bug's been present for a while, but will likely become more noticeable as the new pitch_shift node is implemented.

DLL Compilation Errors With Nodes Using Time_Stretcher · Issue #733 · christophhart/HISE

Steps to Reproduce: Add a stretch_player or pitch_shift node to a scriptnode network. Attempt to compile The usual process yields the error: Undefined symbols for architecture (your_target_architecture) Compiling in Xcode provides a litt...

GitHub (github.com)

[Consint]

@Christoph-Hart Two tick marks in a combobox popup. This has already been mentioned here somewhere. A screenshot and a snippet are in the GitHub issue.

Two tick marks in combobox popup · Issue #739 · christophhart/HISE

In a combobox with custom popup there are always two tick marks. One for the main item with the most submenus and one for the actually selected menu item. Snippet: HiseSnippet 778.3ocsUkzaZCDEdFBNp3tnDodnmp3RkRphpv.g.zCkxVKpkDTIMp2hFFONd...

GitHub (github.com)

[VirtualVirgin]

Viewport viewPostionX and viewPositionY Value Errors · Issue #742 · christophhart/HISE

Steps to reproduce: Load the snippet- HiseSnippet 1123.3ocsVs0TabCEVK3kIrsoSSZ+An5mLTCr1EJgllo.FSqmxEOXJSX5zgHqU1VCqk1YWYHdxjeA8w9d+M1G56omydwdM1PR7jtOsma57oi9z4nlgZtHJRGRrbNeXffX841sFpL8p0iIUjFGPrJaegTbafNzPuA9ooNRZjZ0Ko6GpYdbVjQDRiTxf....

GitHub (github.com)

[clevername27]

Clones in ScriptNode don't work. I've posted three threads of examples which multiple devs have confirmed.

[ps]

PluginParameters are not working anymore.
I assume since the new system there is a major bug that the plugin parameter is creating a loop reporting back the value which breaks automations in Ableton Live (i assume also major problem for other DAWS). As not everyone maybe tries if automations are still working when pushing an update I thought it's important to mention as it fully breaks automations.
Recreate: one slider - pluginParameter == true - compile and try to automate - live will instantly behave as if there was an interference.

[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.