@ericchesek Good thinking, it does appear to be that midi cc message(s).

After extensive testing, I think it may be a bug or at the very least a less than ideal behavior.

I downloaded some of the various Hise instruments that are linked on the main page of the Hise site as well as even bought a couple commercial releases that were made with hise.

It appears that if in the MIX tab <> Auto Select Automation Parameters <> is on, the behavior in the video posted above happens.

If you have that mode unchecked, it does not happen.

@d-healey thanks!

@d-healey That's the thing I think I may have to build something from scratch since I'm actually thinking of using a legato that uses the samples position and transfer that position into the samples that are being glided to.

@d-healey I forgot to say earlier but this worked like a charm. Thankyou for your help as it would have taken me forever to figure that out (if ever)

@d-healey That's what I thought was going on.

Ya, it's for a quick demo, which is why I did it in this instance.

It'll be cleaned up later, haha.

That's what I was looking for!

Looks like the main developer of Windows Vista was doing the last nodeBB update...

Oh great thanks so much!

Noah

@Christoph-Hart I didn’t realize at the moment haha, sorry for the confusion! :flushed_face: :grinning_face_with_sweat:

@Lindon @d-healey I figured it out...posting the solution for other idiots like myself that would make this rookie mistake...So when I downloaded 3.6.0 as a clean install(coming from 2.something)...I saw this tick box under settings for "Use Global app data folder for MacOS" I ticked that box...thinking it was necessary while resetting my project settings...I cleared the checkbox and recompiled...all is working now...Always new things to learn and figure out in the world of HISE... Screenshot 2023-08-30 at 11.34.34 AM.png

The main reason I haven't really used Git is because my Unity and Unreal projects are always like 50 gb or 100gb or more and I could never upload that amount of data to Git.

That's what .gitignore is for - just exclude the folders with big assets and you're fine. In HISE you need to add the Binaries, Samples and PooledResources folder to the ignore file too.

@d-healey Thanks David and Orange!

Following up on this, how can we detect the name of the track a plug-in is on?

@Sphere perhaps you will get polyAT -- lets wait and see...

@d-healey said in Dynamic FX Chain:

This has down sides as you'll need to re-add sub modulators manually.

So the way I did it for these - tho I've changed - I had separate panels for each of these six "slots" (so 6 slots x Num of Effects - so a lot of panels and controls) - The advantage here is when you set up an effect in a slot - then swap out the effect then swap it back in again it will "remember" the settings you had.

These days I dont do this - I have a single set of controls that are mapped dynamically to the params of the loaded effect (I now have 10-15 effects, and it seems more every week, so the previous method was getting out of control and hard to maintain) . This means when you load in an effect it sets itself up as its default state - which I think is a fair compromise. But, yes, David is right you will need to somehow "remember" the modulators you have assigned or (as I do) say "Hey you changed the effect - so you will have to re-do the modulator assignments".....

@ulrik ahh thanks! The code was exactly what I was looking for! Thanks!

@orange yeah there are many places that need to be fixed manually, but I think I got the majority of stuff right now, but let me know if you spot anything else.