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!

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

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

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