@d-healey Thanks David, the loading times are not a major problem just would be nice to show spinner so users can't click again. As far as the crash on offload adding this to expansion.js seems to solve the problem Screenshot 2024-04-08 115541.png

thanks again.

@Lindon thanks! i will now go that route. Standalone it works perfectly fine, so that's what I will do from now on!

@d-healey You a God 🥇
Thank you so much Lifesaver

@d-healey I'll aim to get a snippet, but maybe this is enough.

Here's the code:

// ------------- Mic Target Combos const var mictarget_Options = [ "Kick Drum", "Snare Drum", "Tom", "Hi-Hat", "Ride", "Bell Cymbal", "Splash Cymbal", "China Cymbal", "Crash Crash Cymbal", "Cymbal Stack", "___", "~~Custom~~" ]; const var list_mictarget_Options = mictarget_Options.join("\n"); combo_GLOBAL_CreateSession_Viewport_MicTarget_1.set("items", list_mictarget_Options);

And here's what happens:

Untitled.gif

@Christoph-Hart Thank you,

@Lindon yeh my attack & release samples are in their own samplers with their own processing, i'm avoiding synthGroups because i need individual midiProcessors

mind you, i haven't tried this technique for anything except picked guitars/bass, it SHOULD translate to percussion (glocks, marimbas, things like djembes etc) and maybe piano, but im not sure how well it would go for brass/strings without adding a more complex multi-dimensional setup 🤷♂

@Christoph-Hart I am delighted to report that the method you provided here works like a charm! Thank you so much!

For anyone using it, just remember to set the condition that if

Engine.getOS() == "OSX"

use the method above and place those variables as 'var' inside the condition.

@d-healey alt text

@tomekslesicki Just took a look at this. Are you using a frame container with the full 12 channels?

I commented out the code that forwards the calls for channel counts > 2 because it blows up the code generation size, but I can add a macro that you can use to increase the number of available channels for frameprocessing.

@Casmat slowly remove each scriptnode from the compile process until you find the culprit.

@clevername27 said in XML Component Tree / ScriptNode Apparent Corruption / Modulators Connections Failure / Filter Display Update Failure:

h. According to the screen display in the Table view, data was now getting through.

But the modulated effect (a filter) did not display any updates in the filter-view. And everything had a message I haven't seen before: "Not Assigned".

Yeah I can confirm this is what was happening - seems the latest build might have a problem with the Global Modulators -> filter freq.

@d-healey Thank you for asking; it's inconsistent. I'll make a screen capture video next time it happens.

@ulrik Yes, same here. To clarify, I'm able to compile the network and the knobs work without issue. But several kinds of crashes start to happen. Thanks for confirming.