@Lindon No and yes lol, the main objective is to crop the view to cover the start/end point selection and I thought that would be the simplest way if possible, because what else is it gonna display. But this looks like a good start, just gotta figure out how to calculate the zoom level and position based on that and update it automatically on changing start/end points with the AudioWaveform.

@Soundavid Thanks for pointing me to the right part of the docs I appreciate it. Always get sidetracked in there 😁

@d-healey Genius!

@Christoph-Hart said in Callback on drop?:

@blezzbeats You can attach a broadcaster to the audio file player that's connected to the audio waveform and then you're notified when you drop a sample (or if you use the file browser to load something new).

oh really cool...

@Lindon omg of course, thank you!

@blezzbeats glsl shaders. The keyboard was also a raytracing shader that I‘ve rendered to 2000 filmstrips with a custom logic. Wouldn‘t do it again though :)

@d-healey Will do! :)

Nvm found it in the SampleLoadSave.js script :)

Huge thanks to David for stepping to the rescue the other day, I'm still with the master build but managed to export my first VST.

For whoever it may help the solution was either:

Cleaning Build directory before export and exporting as 64bit VST
Screenshot 2021-09-21 105944.png David's mere presence

@blezzbeats Kind of self explanatory, it ignores incoming events (MIDI notes). :p

18c8d302-bfe5-4c91-b4b0-0fc17cb3ef4a-image.png