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

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?

I’m about to start doing some rigourous testing of plug-ins using virtual machines and all the main DAW’s.

Do people have advice on this process or have you come across any bugs that you’ve had to fix pre or post release?

Anything to watch out for?

All advice would be greatly appreciated!

EDIT: Bypassing is not Bypassing in exported plug-ins either

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

I am experiencing a few glitches when using HISE as of recent.

Hardcoded FX are set to bypassed but they don't actually bypass. I.e I will bypass a tape FX and the hiss FX will still sound. This doesn't happen in exported plug-ins.

Another strange behaviour is whenever I add new Samplemaps to the project, switching between the older samplemaps works fine, and switching from an old samplemap to one of the new samplemaps works fine, but when switching between the newer samplemaps it seems like the same sample map just jumps up and down in volume. This isn't just using a combobox in the interface, it's also when I use the sampler module to switch samplemaps. Again, it works fine in the exported plug-in.

It's just tricky making the last presets if I've bypassed the chorus, the chorus is still on... It feels like guesswork and quite a pain in the last development phase of this project.

I'm wondering if it has something to do with compiling multi-channel FAUST FX. Thats when it seemed to start happening, but who knows...

Any pointers?

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