@Christoph-Hart I had a feeling but I did have to ask 😆

@d-healey @ustk Thanks for the insight! I keep getting amazed at how extensive and deep HISE's features are :)

@d-healey ok, thanks

@Christoph-Hart thanks a lot Master Hart! After deleting it the file the building works.

@ulrik @d-healey Major lesson learnt! I had been doing some tests with building a swift app on my iPhone and somehow it was still doing it with HISE! So always double-check if you have any outputs activated
in Xcode>Window > Devices and Simulators.

Although now I did find a major bug on an instrument we are building, so I will do a separate post on that.

Thank you for all the great help!

@Christoph-Hart I just noticed this setting :

Screen Shot 2020-02-07 at 8.44.32 PM.png

Does that mean that we could theoretically set to more mic channels than 2 without breaking HISE? I have a 3 capsule mic that is capable to matrix out to numerous setups such as X/Y or Omni, or even multi-channel ambisonics (it's a Josephson C700S), so I am intrigued as to this possible functionality, please tell me more :)

@d-healey You are a legend! Thanks so much mate! I have to get you properly drunk as a thank you next time I am in your hood! :folded_hands_medium_skin_tone: :folded_hands_medium_skin_tone: :folded_hands_medium_skin_tone: ☺

@Brian said in Lottie animation controlling parameters?:

I am currently experimenting with controlling Lottie animations using sliders, but once I set up the knob to control a parameter I lose the connection with the Lottie animation. I am sure there is a way to have all three of these elements linked but it's beyond my current coding skills.

Here is a test project ( latest Scriptnode build and rLottie DLL needed):
Got it — thanks for explaining what’s happening. From what you describe, it sounds like you’ve successfully set up a slider/knob to control a parameter, but in the process the link to the Lottie animation playback got overridden (likely because only one connection is being made at a time instead of merging them).

What you probably need is a single control signal that both the Lottie animation and your knob/slider can “see.” In Scriptnode (and similar node-based systems), this usually means:

Don’t directly replace the Lottie’s input with the knob.

Instead, use a merge/multiply/mix node (or equivalent) to combine the knob value with the animation’s internal time parameter.

Feed that merged output into the Lottie node, so the animation continues to play but is also scaled/offset by your slider.

Another approach:

Use the knob to control animation progress directly (frame / totalFrames), bypassing “playback.” That way the knob defines where in the animation you are, and you don’t depend on Lottie’s internal clock.

If you want both free playback and manual knob scrubbing, you’ll need logic that chooses between “auto-time” and “knob-time” (for example, a switch or crossfade).

If you share your node setup (or a screenshot), I can suggest the exact node combination to keep all three elements linked.

@d-healey I very much agree on all your points, I am all for sharing and keeping it as open as possible within my personal projects, so maybe I should have explained it better.

It's not fear or paranoia on my part, but rather trying to see if there could be practical options since I do often work with clients in the video game industry that are incredibly stringent on this aspect by default (the last project went for four years + insane data transfer protocols and contracts ).

@Christoph-Hart Thanks for the suggestion on the NDA's - I will definitely go this route :)

@d-healey There's a snake in my flute! 🤣 🤣

Thanks mate. Looks like it's a script he made somewhere. I'll check github...

I had a feeling it was so. I think I might have found a way by installing the original Lottie IOS library as a package dependency (https://github.com/airbnb/lottie-ios)

Screen Shot 2019-11-12 at 6.59.53 AM.png

Not sure if you might have to change something on your rLottie integration for it to work with this version, but either way, I am happy to test a build if you think its a good idea.

@Rognvald

To answer my own question.. :)

To add another Lottie animation in a HISE project, you'll need to first create a new Lottie panel on the UI and then assign a different JSON or B64 string to this new panel using the set animation function. This is done by adding a second animation element and using a distinct variable to hold its data, as HISE's set animation command expects to be assigned a unique animation element.

// Example for assigning the new animation to the panel
const secondAnimationData = "PASTE_YOUR_NEW_B64_STRING_OR_JSON_HERE"; // Replace with your actual data
const myLottiePanel2 = Content.getComponent("MyNewLottiePanel"); // Assuming your new panel is named "MyNewLottiePanel"
myLottiePanel2.set animation(secondAnimationData);

Thank you both for the great suggestions and wisdom! I probably saved a lot of wasted time and effort on this! And on that note, I can't wait to share what is cooking in the background, me and my studio team have been busy sampling away these past few weeks, so there is a backlog of sonic goodness that will hopefully see the light of day in the coming weeks :)

deleted . . . .