@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.

I have read somewhere that you need to get permission and/or pay for the use of brands in your promotional materials.

Does anyone have advice for this?

Would mentioning specific types of equipment be risky? I.e - Juno 106, ReVox A77.

Would saying the virtual instrument was inspired by pieces of equipment like an MPC (without mentioning AKAI) or saying Stratocaster style guitar also be risky?

If you haven't gotten permission or paid the brands, would it be advised to hide/put a piece of tape over the brand name on a piece of equipment, in visual advertisements? I.e tape over the ReVox logo if you had a video of the machine in your promotional material.

I want to be transparent with the quality of equipment used, but also want to avoid any trouble from big brands.

Would love some advice if anyone has encountered this when releasing plug-ins.

Ngā mihi,
Sam

@d-healey

After opening in Xcode and reading through some of the errors it looked like it was to do with samples.

Deleted the samples and the Standalone App opened.

Time to watch the rest of your Hackspace tutorials!

Thanks!

@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!

@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!

@Oli-Ullmann Great suggestion! Works well with NKS presets too!

@cassettedeath Scratch that

Incase anyone encounters the same issue I did, I used

var  myPresetList = Engine.getUserPresetList();
const var RandomPreset = Content.getComponent("RandomPreset");

inline function onRandomPresetControl(component, value)
{
    if(value)
    {
        // Get the current list of presets from disk
        local presets = Engine.getUserPresetList();
        
        if(presets.length > 0)
        {
            // Pick a random index
            local index = Math.floor(Math.random() * presets.length);
            
            // Load it by name with the .preset extension
            Engine.loadUserPreset(presets[index] + ".preset");
        }
        else
        {
            Console.print("No user presets available.");
        }
    }
}

RandomPreset.setControlCallback(onRandomPresetControl);

@ustk I tested it on OS 15.(Something) - The JUCE forum post mentioned Ventura... I'm still running 12.7 incase you wanted to send a new build to test without the Zoom Handler/resize

@Chazrox "Plug-in is gonna suck for the following users;"

I’m fairly new to Hise, but when I studied music technology I was introduced to Juce and did my honours research on how music technology can be more accessible for blind individuals - the main reason for that interest being I’m going blind myself.

Native Instruments are leading the way in terms of accessibility and software instruments. I believe this sits around Native Kontrol Standard.

It’s very important to me that my instruments are screen-reader accessible. The Zoom handler script is awesome and will be great for users with low-vision.

I believe Juce has some accessibility tools, but I haven’t looked too far into this and how that might implement this into my Hise projects.

Is there any plans to implement screen-reader accessibility development tools in Hise? Alternative text would be an amazing addition, but accessibility is often hard to retrofit.

Thanks @Christoph-Hart ! :)

@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);
});