@Christoph-Hart I tried this using the doc example but I wasn't convinced I could do it, so now you say so 👍 😉

@iamlamprey said in Couple of Rhapsody Questions:

Roger that! Will the new boilerplate break instruments made with the previous version?

Yes, I make no attempt for backwards compatibility (ok that's not quite true, but I don't worry about it if I break it). However it only affects a project if you choose to update the boilerplate, there is no reason you can't stay on the previous version for existing projects. Also if you're just using the Rhapsody template and not the full boilerplate with the additional includes and modules it probably won't cause any issues (or it will be minimal).

@iamlamprey said in Couple of Rhapsody Questions:

the actual instrument isn't using any Loris methods

Then there should be no issues.

@iamlamprey said in Couple of Rhapsody Questions:

Very exciting, as much as I hate protools it's still quite a popular DAW

Yup I have no love for it either, but it seems like there is enough demand.

@Lindon it is zero based so in fact 25 not 24.
This means there are 25/5 param per "real" band

So my guess is that:
Band 0 is Gain
Band 1 is Freq
Band 2 is Q or Enabled
Band 3 is Q or Enabled
Band 4 is Type

They effectively could have been named more appropriately

So without saying this is what you should do since there might be a better solution for your use case, you have the possibility to parse those bands numbers (modulo 5) and retrieve the values

@d-healey they weren't in the folder yet. Once I added them to the folder the problem went away!

@treynterrio I had to go into HISE's source code to change this some time ago. Look up SimpleEnvelope.cpp or AhdsrEnvelope.cpp. There you can change the max values of the parameters. I believe you also have to add a preprocessor for it to work HISE_SCRIPT_SERVER_TIMEOUT=yourMaxTimeHere or else it kinda cuts off. Finally rebuild hise.

⚠ PD: play with HISE's source code at your own peril.

@iamlamprey Alright, this method definitely worked. Though I'm still wondering about getNumSamples(), I tried with audio files as objects and still gave me an error.

Anyhow, the audio.length method accomplishes my initial objective and I learned a few new tricks so, thank you soooo much.

cheers!

@WaterSpoon sidenote: you pretty much always want to be building with the develop branch, since it's quite a few commits ahead of master

@DanH Thanks, Dan - that one's had me for years!

@Mors scriptnode is proably your best bet. there are already templates in there that will set up a multiband network for you, then its up to you to write your saturation dsp and make it available for each band.

Oh I know what the problem is! I just remembered that I ran into this some years ago when bypassing/enabling modulators through scripting - so there's probably another post about this...

Through clumsy scripting I managed to bypass the entire gain chain. This shows up in the xml. Changing the 1 to a 0 solves the issue.

b0dc04f5-7170-4ca7-86d9-d43417f602d6-image.png

And if anyone else is doing something similar (programmatically bypassing modulators) you can check if it's the entry for the entire chain and ignore it:

if (modulator.getType() == "ModulatorChain")

@Lindon Yes! Compiling without IPP has worked!

I know I'm not missing a ton of functionality without it, but would like to know if there is a way to get it working as I was hoping to mess with the convolution reverb.

@bendurso If it works it works. I think the problem you were having before is that containers don't work the same way in FX plugins as they do in instruments so it was messing up the routing.

@meto396 i think one of the properties in the interface designer controls it

@d-healey said in Prevent Slider Value Going Negative:

You can cap it using Math.max()

Knob2.setValue(Math.max(component.get("min"), Knob4.getValue() - Knob3.getValue()));

Ah yes, great idea! Thank you!

@d-healey ohh I think I got it... just need to add the little loadAudioFilesIntoPoolcode...just donned on me after all this time. my oh my, sorry

@aaronventure Hmmmm... Not sure I quite understand 😆

Any example of this in action?

@treynterrio said in Export as AU and VST:

@d-healey just cleaned the build folder but still the same error. I'm using a M1 MacBook Pro

Since you're on M1 processor and probably are using the Sonoma and Xcode v.15...., you need to use this develop build of Hise.
Christopher made a change in the develop branch so this error doesn't occur anymore,

Skärmavbild 2024-03-21 kl. 16.55.01.png

@d-healey I believe only the sample based plugins are based on HISE. It seems like they built a convolution reverb plugin together with another provider. Probably not HISE

@DanH Thanks. The elements are all there. I guess I will have to look very closely to see if I can spot anything out of the ordinary.