@d-healey @Lindon @TNTHM

Guys thank you so much, OF COURSE, i did compile it as instrument first, and then , when compiling it as FX i forgot to enable vst3 support. Now its running , and i can take a deeper dive into this ! Thank you thank you thank you

@d-healey yeah thats what I started out looking for and couldn't find....feature request...

@Straticah Did it work?

@johnmike Start by establishing a naming convention for your sample maps. For example all the drum ones could start with drums_, all the guitar would have guitars_, etc.

Then in your script you get all the sample maps in an array. Then you loop over the array and any that start with drums_ you put into a dedicated drums sample map array, any that start with guitar_ you put into a guitar sample maps array, etc.

Then you can use those arrays to populate your combo boxes or viewports or whatever UI elements you want to use.

@d-healey

-- thanks Dave, that works fine...

SOLVED!
I've used a SimpleGain and modulated the Delay Parameter using an LFO.

@d-healey Exactly hahah. Thank you for the information. Will watch the video :)

@d-healey said in git ignore question.....:

@Lindon Strange, that should cover all folders called Binaries. Did you add the gitignore after you'd already commited those files?

You could also try */Binaries

adding in

*/Binaries made git decide everything IN Binaries should be included.....so bad bad git.

I added this :
/DspNetworks/Binaries

to get the preferred outcome....

@Lindon ..actually no - its not working really... removing.. removing...

@tsempire I'll give the solution to those who need it.

Copy this code:

// Get a reference to the MIDI processor as MIDI player
const MIDIplayer = Synth.getMidiProcessor("MIDI Player1").asMidiPlayer();

// Get a reference to the transport buttons
const grpTranportBtn = [Content.getComponent("btnPlay"),
Content.getComponent("btnStop")];
for(b in grpTranportBtn)
{
// Make sure the buttons are not saved with the presets
b.set("saveInPreset", false);

// Assign the control callback to the transport buttons b.setControlCallback(onTransportBtnControl);

}

// Also set the STOP button to be momentary
grpTranportBtn[1].set("isMomentary", true);

inline function onTransportBtnControl(component, value)
{
// get which button triggered the callback
local index = grpTranportBtn.indexOf(component);

// If it's the PLAY button if(index == 0) { // if the PLAY button is pressed if(value) { // start playing MIDIplayer.play(0); } else { // keep the button's value to 1 if it's still playing grpTranportBtn[0].setValue(1); } } // if it's the STOP button else { // only react if the mouse is clicked (not released) if(!value) return; // stop playing MIDIplayer.stop(0); // set the PLAY button's value to 0 grpTranportBtn[0].setValue(0); }

};

// on compilation, reset the playhead position to the beginning
// comment it out if not needed
MIDIplayer.setPlaybackPosition(0.0);

Create 2 buttons with the ID

btnPlay

btnStop

I've tried using the arp thinking I could save some development time however it does not seem fit for this use case. I will implement a custom midi player using tables and note on off events.

@Lindon yeah, this has been very annoying lately to me too. I would open a large project and if I try to navigate to one of the included external scripts, it would throw this killer.
If I reopen the project, then recompile the code again before doing anything, then switch to the external script, it would be fine.

It happens in weird places.

Glad you determined the most likely cause!

@DanH I thought that, at least the fixed band number can be set inside the FloatingTile.

It seems it is not possible without source code modification

@alfaholic I’ve found that it’s a good practice to wait until you’ve added in all your samplemaps before creating the presets…helps keep things in order…secondly I’ve found that you can go into the project folder where the samplemap xml files are and rename them as needed to keep your structure in tact…it’s saved me a few times when I put the cart before the horse