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

Has anyone made user presets for Komplete Kontrol?

I'm getting a crash when changing presets with this error.
If I let the notes ring out a bit the preset changes without a crash but I hear a loud click and if i change presets while holding a note it crashes completely.

Changing presets within the plug-in works fine.

Crashed Thread:        32  com.apple.audio.IOThread.client

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000088
Exception Codes:       0x0000000000000001, 0x0000000000000088

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [59133]

VM Region Info: 0x88 is not in any region.  Bytes before following region: 4303552376
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START

Thread 32 Crashed:: com.apple.audio.IOThread.client
0   Reel-Synth                    	       0x155d90ec0 hise::ModulatorSynthGroupVoice::resetVoice() + 768
1   Reel-Synth                    	       0x155d6b358 hise::ModulatorSynth::renderVoice(int, int) + 320
2   Reel-Synth                    	       0x155d656fc hise::ModulatorSynth::renderNextBlockWithModulators(juce::AudioBuffer<float>&, hise::HiseEventBuffer const&) + 1444
3   R-Synth                    	       0x155d9b874 hise::ModulatorSynthChain::renderNextBlockWithModulators(juce::AudioBuffer<float>&, hise::HiseEventBuffer const&) + 272
4   R-Synth                    	       0x155c698e4 hise::MainController::processBlockCommon(juce::AudioBuffer<float>&, juce::MidiBuffer&) + 11800
5   R-Synth                    	       0x155cf5794 hise::DelayedRenderer::processWrapped(juce::AudioBuffer<float>&, juce::MidiBuffer&) + 1416
6   R-Synth                    	       0x155fe5194 hise::FrontendProcessor::processBlock(juce::AudioBuffer<float>&, juce::MidiBuffer&) + 280
7   R-Synth                    	       0x155c164ac juce::JuceVST3Component::process(Steinberg::Vst::ProcessData&) + 6972```

Could be references to components that no longer exist. I.e you have a reference to Button1 but deleted button 1.

Check in script view to see if any components are undefined

@Chazrox Yeah, my audio files are about 6mb and 25mb for images… So I’m not quite sure why they’re not embedding in the plug-in.

Could be related

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