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!

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

@Chazrox Having the same issue. Finding it super hard to build the installer for the audio resources.

Have you tried moving the audio resource in the pooled resources to the app data folder?

@d-healey Do the resource and the post install script need to be code signed? And both pkg?

@d-healey cool! Thanks heaps!

@d-healey Yeah XD

Question: if the audio resources are over the 50mb and you don’t embed audio files - I’m assuming you need to change the pkg installer so that it installs the resources to the app data folder?

Or does the hr1 also install them?

@d-healey Okay, it’s working now - creating the app data folder and link file… And that’s without the global app data checkbox enabled…

@d-healey yeah I have tried it.

I could try recompile without and test on another computer and recompile with on another computer… being careful cleaning the build folder maybe?

@d-healey I checked and nothing was created for the project.

I had the global app data checkbox checked (and tried unchecked)

@d-healey [Here's the video] (https://youtu.be/UikC9U2iAA4)

• Have tried deleting the samples/installing from scratch
• Have tried force overwriting
• Have tried choosing the samples too

After successfully installing the hr1, I close and open a new instance of the plug in and the window appears again.

I've checked the version number and bundle identifier.

Even choosing the uncompressed audio files doesn't get rid of the window.

Any thoughts?

@Christoph-Hart Awesome,
Primarily interested in the accessibility side, but a little confused about delivering future expansions and whether or not I need to send expansions to NI for approval... - or if it's just the initial functionality/integration...