@Dan-Korneff Thank you Dan - clever.

@d-healey I appreciate it, man. Unfortunately, this creates keys of different widths - the 0.7 width is hardcoded into HISE (and I believe comes from JUCE). Thank, though.

@d-healey ok this sounds to difficult for me :D

Index 1 & Index 0, that solved. Thank you, it's amazing how simple it was and how much time I've wasted. Thank you for getting me to the next step.

{ "ProcessorId": "Waveform Generator1", "Index": 1, "FollowWorkspace": false }

@Mighty23 said in Help with displaying knob value in a label:

We can mark it as "Solved"

Click this button and select Ask a question. Then click it again and select solved.

6c38e55d-e93d-496e-bdf9-5cc05e67218d-image.png

I've made some progress:

I've selected "Enable Midi Out" in the Project Settings, and found in the documentation that

Message.sendToMidiOut()

needs to be called on the message itself:

This will forward the message to the MIDI out of the plugin.

I understand that Message methods may only be called within a MIDI callback.
I'm not sure where this might be, or how to access a Message when I'm currently only working with MessageHolder.

My assumption is, that somehow calling Message.sendToMidiOut() on each Message in the MessageHolder list will produce MIDI output in the exported MIDI FX plugin, and hopefully also while scripting in the IDE during the development process.

I have an overall understanding of the subtle differences between MIDI FX plugins and VST3, VST2, etc., and how they are expected to perform in the different hosts/OSs, based on various reports I've read both here and in the JUCE forums.

My goal for now is to get some kind of MIDI output working, using any of these paths forward.

@ATWAW said in Sustain Pedal Question:

What function would I use to turn on a sustain pedal via a button on the interface,

If you're only using the sustain pedal for standard sustain pedal sustaining, then you just need to send a CC64 message.

In the button's callback you could use.

Synth.sendController(64, component.getValue() == 0 ? 1 : 80);

@d-healey I see. I'll try to adapt your way to my project. Thank you.

@d-healey worked like a charm... Thank you!

@d-healey Yes - THANK YOU!

@Lindon 🙏 Cheers to you mate

@d-healey Thank you so much Fine Sir :folded_hands:

@Christoph-Hart Right, the issue is with creating the directories in the Application Support folder. Permissions thing?

Because Packages can't install to users' folder. Hopefully the MPC won't have that issue. Or the one where it can't create directories in global appdata

@d-healey said in Finding the Processor Type of a (Module Tree) Processor?:

@clevername27 could you distinguish them by variable name?

or use two array one of fx one of all audio processors and use indexOf....

@d-healey Ahhhhh such a simple solution, thank you!

@Lindon said in User Specified Sample Folder per Sampler?:

FileSystem.browseForDirectory(var startFolder, var callback)

Yes, thank you. I have added this to the SampleLoadSave.js of the CustomSampleImport project. On Right Click, it opens the directory browser twice. I can select a folder but it does not load the samples in the folder or randomize the folder.

SampleDropper.setMouseCallback(function(event) { // Clear the sample on double click if(event.doubleClick) { Sampler1.clearSampleMap(); return; } this.data.hover = event.hover; // Show a directory browser on right click if(event.rightClick) { FileSystem.browseForDirectory(FileSystem.Samples, loadSample); return; this.repaint(); } });

Here is how I am randomizing some components in case I need something here. I know there is a way to reduce the script, I just don't know it.

const sampleMapsRAN = Sampler.getSampleMapList(); inline function onShuffleSamplebtn1Control(component, value) { if (value) { local index = Math.randInt(0, sampleMapsRAN.length); local sampleMap = sampleMapsRAN[index]; Sampler1.loadSampleMap(sampleMap); SampleViewer1.setValue(index); SampleName1.setValue(list[index]); } }; Content.getComponent("ShuffleSamplebtn1").setControlCallback(onShuffleSamplebtn1Control);

Thanks again.

@iamlamprey Okay there's already a method for it:

const bc = Engine.createBroadcaster({"component" : "myCoolFloatingTile", "event" : "All Callbacks"}); bc.attachToEqEvents("bc", ["BandAdded", "BandRemoved", "BandSelected"], {"id" : bc}); bc.addListener("", "update something", function(component, value) { Console.print("you just changed an EQ property!"); });