@David-Healey ahhh! Okay - I’ll probably implement a lock button so the user can opt in/out of the save in preset UI jumping

And a seperate button to close the panel so it doesn’t jump.

Oh… and THEN I’ll need to implement your random value script before release

HISE feels like whack-a-mole sometimes!

@David-Healey the panel flashes sometimes

@David-Healey hmm.. Still glitchy for me.

Are you using the latest commit?

@David-Healey How did you get it work on Mac and windows?

Maybe I should wait and see if there’s a new commit soon or try a different commit. Still glitchy to and it’s the last thing I need to fix before releasing the plug in :/

@dannytaurus

Just saw this in the oscillators lib.

EXCEPTION TO THE LGPL LICENSE : As a special exception, you may create a
larger FAUST program which directly or indirectly imports this library
file and still distribute the compiled code generated by the FAUST
compiler, or a modified version of this compiled code, under your own
copyright and license. This EXCEPTION TO THE LGPL LICENSE explicitly
grants you the right to freely choose the license for the resulting
compiled code. In particular the resulting compiled code has no obligation
to be LGPL or GPL. For example you are free to choose a commercial or
closed source license or any other license if you decide so.

@dannytaurus

Dang it!

Thank you for the clarification.

Hi everyone,

I'm developing commercial audio plugins using HISE with Faust integration. My Faust code uses standard library functions like:

• (oscillators.lib - LGPL)
• (filters.lib - LGPL)
• (noises.lib - LGPL)
• (delays.lib - LGPL)
• (reverbs.lib - MIT)
• (signals.lib - MIT)

I understand that when HISE compiles Faust code, the generated C++ is statically linked into the plugin binary. I want to ensure I'm LGPL-compliant for commercial distribution.

My questions:

1. Does HISE's Faust integration handle LGPL compliance appropriately for commercial use?
2. Do I need to provide object files or take additional steps beyond attribution in my EULA?
3. How do other commercial HISE developers using Faust handle this?

I've already included proper attribution to the Faust Standard Libraries in my EULA. Just want to make sure I'm covering all the bases before releasing commercially.

Thanks for any guidance!

@David-Healey Just so the setting saves in the DAW project. I.e the user has the chord button on for a project - reopens the project and that setting is still on

@David-Healey yes that would be good

I suppose the values have to jump from what’s saved in the preset to the previous value?

@David-Healey Snippet ```
code_text

const uph = Engine.createUserPresetHandler();

const var Knob1 = Content.getComponent("Knob1");

reg knobValue;

uph.setPreCallback(function(presetData)
{
	 if (!uph.isInternalPresetLoad())
	 	knobValue = Knob1.getValue();
});

uph.setPostCallback(function(presetFile)
{
	 if (!uph.isInternalPresetLoad())
	 	Knob1.setValue(knobValue);
});

@David-Healey Restoring values in a daw session without the save in preset flag

@David-Healey Would there be any way to make it so that the values don't update visually every time you change a preset?

In my case the button opens a panel and it’s quite abrupt seeing it open and close every preset change. Could this be to do with where the code is placed?

It’s a trade off between the option to say, browse presets without turning off the arp every time or the unaesthetic UI value jump.

@David-Healey No errors found. I will try recompile them

@David-Healey Yeah I recompiled them on windows

@David-Healey Hardcoded Master FX... Faust and a .h Limiter which I was having issues with as it had Pregain (dB) which would cause errors

My project builds fine on a Mac, but when I try build on Windows i get an error saying 'XML Parsing Issue - expected "=" after atribute "1" and then Project XML invalid.'

I have tested a basic project and that builds fine on Windows.

I have checked the XML with XML validators and no errors were found...

It's not creating the AutoGenerated.jucer file...

Any ideas?

When I duplicate a track (in logic) buttons are changed to their default state (0).

Is there a method/setting that saves the state when duplicating tracks?

(I think this sometimes happens when re-opening a saved DAW project too)

@dannytaurus

Thanks for the info!

I’ll probably try make one audio demo for the website in each DAW/OS combination… And then spam the automation etc A heap of work but I’d rather sort out the bugs now.

And then hopefully make some cash to pay some reliable user testers in the future!

There’s a whole reddit thread on ROMPLUR being sketchy and scamming people…..

@dannytaurus @David-Healey

Yeah! I’ve had a few user testers. A couple of meetings afterward were super useful and have resulted in UX changes.

I think the documentation and especially video walkthroughs of the installation process will be essential.

A lot of testers I’ve sent it to haven’t registered their serials (as it’s not really all that official yet/maybe they’re just super busy)

Do you still think it’s worth testing on the different Mac OS and DAWs?