stay local to each of the processors that imports the module.

I'm not fully understanding your terminology here. What do you mean by processor and what do you mean by module?

@DanH said in Debugging... How?:

@d-healey So how do I build my HISE project from within Xcode...?

HISE should generate an xcode file in the binaries folder when you export.

@tabulius Unless you're building a project that requires FFT routines then you don't need it.

@ulrik reimported my initial snippet and now it's fine...

@ulrik Didn't have to - downloaded „New Layout“ last Saturday - compiled without error - runs.

it gets weirder and weirder :-)

Ok. It works but not with tempos slower that 1/1 bummer 😕😭.
I been testing it out on 8/1 tempo

@allyesw said in UI display issues on Big Sur:

Would compiling HISE myself avoid this

Maybe. But you should definitely build it yourself anyway because the prebuilt version is ancient.

Build from either the master or develop branches.

@UrsBollhalder said in Breakpoint?! Help please...:

Or develop still good?!

Stick with develop for now, the new_layout will be merged into develop soon-ish.

@Jerems134 I have no opinion on it but I recall someone else was working on integrating a HISE app with an ELK Audio device.

@ulrik Thank you Sir... now it is working ... :)

Sure does look a lot like spam to me

@Mwins Here in my system it happens even if i use only one midi overlay...i think something is going on with the source code of midi overlay.

@iamlamprey yep, that was what I was exactly what thinking. Any methods to get not so linear filter response curves for emulating imperfections?

@DanH Haha, This Happens To Me Quite Often :) 😆
So I Stored This On My Mind
It's A Meter >>> Enable That Friend = 1 😆

UPDATE with

juce::ValueTree UserPresetHelpers::createModuleStateTree(ModulatorSynthChain* chain) { ValueTree modules("Modules"); if (auto sp = JavascriptMidiProcessor::getFirstInterfaceScriptProcessor(chain->getMainController())) { for (auto id : sp->getListOfModuleIds()) { auto p = ProcessorHelpers::getFirstProcessorWithName(chain, id); if (p != nullptr) { auto mTree = p->exportAsValueTree(); mTree.removeChild(mTree.getChildWithName("EditorStates"), nullptr); mTree.removeChild(mTree.getChildWithName("EditorStates"), nullptr); modules.addChild(mTree, -1, nullptr); } } }

It does work! But I need to click twice to recall the CurveEq values if coming from Empty Slot or other FX. If I'm already on a CureveEq then it loads on first attempt ->

glitch.gif

@Christoph-Hart