@DabDab said in Lottie Animation JSON not Loading, HISE Crashes:

What I did was, I rendered all frames( all effects) as image sequences and then imported it back to AE. Then I made lottie files.

Lottie files are vector based. I am not sure the image to lottie will work in Hise.

With After Effects, it works here but all of the layers are paths (shapes), not images.

Out of curiosity, what's your workflow in HISE, do you just use a single editor tab all the time?

This:

a new tab opens when you click on a search entry

in combination with the special search commands (eg f Midi then select the file in the drop down) or Goto Definition - which is broken again at the moment :)

@d-healey Ahh yes that did it. Thank you for your help ! :)

@lalalandsynth Awesome!

@Christoph-Hart RAW wav has the artifacts.

@d-healey That appears to work.

@Christoph-Hart Use Hardened Runtime solved the issue. I don't remember if it was enabled before...

@ustk said in Single-Level Items in Hierarchical Menus Panel?:

@clevername27 Do you have a snippet?

Thank you for your question - this is just the example @Christoph-Hart gave. It's OK, I'll work around it. Thank you, tho.

Yep those two issues are solved! The table issue is still there though, I'm still trying to make a minimal example.

@toxonic The problem is that when the parameter order switches after a compilation - I need to keep the connections alive so that modulation or slider connections will retain their target but that's why this function is for.

@Christoph-Hart I see, well I can change the event.drag to event.dragX || event .dragY, I don't have so many many projects to change.

So the event.dragX & Y doesn't go back to false after a short time?

@Lindon

Ok found.
I need to delete scriptFx (replace by hardcodedmasterFX) that not use anymore.

I notice "solved"

update IPP solved my problem

@Dan-Korneff This is what the audio sounds like for our default INIT patch with no effects or modulation. https://www.dropbox.com/s/k6c0gg0fn3m96bd/Synth pad%2C CUBE 1 Primary Output%2C Rec (5).wav?dl=0

Oh I think it's because the bias knob was at 0%, turning it to 50% the gain is unaffected.

@Lindon Thank you - it's already taken care of.
Both errors disappeared with the new build.