@obolig Sadly no :/

I just decided to scrap it and focus on other stuff. If anyone finds a possible solution so animation would work on Standalone, AU on Mac etc please let us know :)

As far as I understand the only shaders that would work would be Metal, so a converter would be an option here. MoltenGL is a bit pricey but allegedly it can convert openGL stuff to Metal quite seamlessly.

@d-healey omg...

this is way easier...apologies for such dumb questions, I guess I complicate too much for pretty straight to the point solutions.

I assume this can be changed even by the user?

@d-healey good question...

too fresh out of the oven when it comes to HISE work I'm afraid, so probably didnt even realize that was the way too go. Will look into using modulators next.
thank you!

Apologies for reviving an old topic;

Whenever I hit a problem or a feature implementation I like to dig through the forum. I want to code a midi CC to a filter's cutoff running through my Sampler.

To my understanding it should be done like this?

I put this in my MIDI scrip editor for Sampler1 (onController section)

function onController()
{
    if(Message.getControllerNumber() == 1) //using modulation wheel
    {
        knbFiltr.setValueNormalized(Message.getControllerValue() / 127.0);
    }
}

on my main Init page for the UserInterface

I've put this

const var knbFiltr = Content.getComponent("knbFiltr");

referencing my cutoff Filter knob.

...reading @d-healey reply I also put in the init of the script processor

const var knbFiltr = Content.addControl()

trying to compile it states function does not exist.
I'm sure I missed something dumb here :) still learning...

@d-healey said in MIDI Routing - Floating Tile Keyboard Retrigering (strategy help):

Message.ignoreEvent(true);

This works perfectly! Thank you @d-healey

@d-healey said in MIDI Routing - Floating Tile Keyboard Retrigering (strategy help):

No idea, is that what you've done?

yeah, I'm using a button connected to the MIDI Processor to trigger a note on event, kickstarting the Audio Loop Player. Should I done it a bit differently? :)

const var processorButton = Content.addButton("processorButton", 0, 0);
const var AudioLoopPlayer1 = Synth.getChildSynth("Audio Loop Player1");
 
reg eventId; 
 
processorButton.setControlCallback(playAtmo);
 
inline function playAtmo(component, value)
{
	if (value)
	{
		eventId = Synth.playNote(64, 100);
	}
	else 
		
		Synth.noteOffByEventId(eventId);
};

hope this is ok?

@d-healey said in MIDI Routing - Floating Tile Keyboard Retrigering (strategy help):

This is done using Message.ignoreEvent(true);

great! will try it with this tomorrow!

@d-healey said in MIDI Routing - Floating Tile Keyboard Retrigering (strategy help):

it's on note on and on note off callback's you ignore the incoming events.

thank you as always @d-healey! I assume this is done by using the following command?

Settings.toggleMidiInput( String midiInputName, bool enableInput)

however, aren't the Audio Loop Players also triggered by MIDI note 64? - which is connected to the button?

Have a rather simple setup,

• sample player for instrument samples "controlled" by floating tile keyboard
• two audio loop players for atmos controlled by two buttons

Whenever I play through the floating tile keyboard it also retriggers the Audio Loop Player. Both of the Audio Loop Players are connected via Buttons on the main interface and I use a MIDI Processor to specifically trigger those two players.

I assume I would need to MIDI map the keyboard just to the sampler but am thinking what would be the best way to do it? Through MIDI Processor? Channel selection?

Any help greatly appreciated!

@fellowfinch

edit:

needed to add this in inteface

Button1.setControlCallback(onControl);

and this in MIDI processor

processorButton.setControlCallback(playAtmo);

works fine now! however, I still get MIDI keyboard (floating tile) that plays the audio loop. What would be the best way to have the keyboard fltile be hooked only to the main sampler?

@d-healey

thank you for your help, however I'm still struggling a bit to understand what would be the best practice here.

Looking at the Scripting practices I think I understand the gist, comments added to showcase my though process

//button atmos
const var Button1 = Content.addButton("Button1", 0, 0);  // call for button to be added to the main script
const var MIDIprocessor = Synth.getMidiProcessor("Midi Processor"); //calling a MIDI processor to be added

Synth.deferCallbacks("true"); // need this to to run in the message thread instead of audio thread?


///call for a function
function onControl(number, value)
{
	MidiProcessor.setAttribute(0,value); //calling our Midi processor
}

after this, jump into my MIDI processor & Script Processor, I have added this

 const var processorButton = Content.addButton("processorButton", 0, 0); // adds a button to the MIDI processor
 const var AudioLoopPlayer1 = Synth.getChildSynth("Audio Loop Player1"); //connects to my Audio Loop Player?
 
 reg eventId; 
 
inline function playAtmo(component, value) //function to play the atmo button
{
	if (value)
	{
		eventId = Synth.playNote(64, 100); 
	}
	else 
		
		Synth.noteOffByEventId(eventId);
};

and then back to my interface with

Content.getComponent("processorButton");

I can see the button in both interface and MIDI processor but cannot get them linked up or to play a note. I'm still trying to wrap my head around how exactly to set up this trigger :) I'm assuming that I need to somehow tell my MIDI processor to trigger the button for the atmo.