@Matt_SF OMG!!!!!!! Yes!!! Thank you!!! (And thank you, David, as always.)

@clevername27 Good work (y)

@d-healey Thanks - brill. I'll post it here for everyone.

@d-healey Brill, thanks!

@ustk Not at all, mate. You and what you wrote are awesome; I appreciate the opportunity to learn from someone as knowledgable about HISE as you. I value any critiques you can offer from going through my code - thank you! I'll follow up on any suggestions/corrections you make.

@ustk and @d-healey, thank you - I can't believe I didn't think of that. Thank you!

@d-healey You rock. Thanks!

@clevername27 so I think you are on the right path with option2.

First you need some method(script) to record MIDI events arriving, and more specifically their time (as ppq?). So some "record" button that sets the script in ready mode, and on first event defines this as "start time", then everything is an offset from there until the user stops recording.

At this point you would have a long list of events, so playback should be pretty simple - especially if you are using ppq instead of milliseconds - so the playback can be tempo aligned with the DAW tempo

@ustk Thank you!

@Christoph-Hart Thank you for your question. Just the kinds of things that lower-level access allows. I realize the struct is deprecated and may go away at some point.

Polling parameters (e.g., bpm and time signature) when needed, instead of keeping track of them with callbacks — it's a cool feature when you need to know when something has changed, but otherwise can be a little clumsy?

This may be my own issue, but the callbacks aren't being called at init. (They obviously work in your code example.)

Writing your own callbacks — for example, I want to show the user the seconds and samples of the DAW's playhead with high granularity—like the display in the MIDI keyboard. Another is example is doing calculations on the playhead in real-time.

The specific things in CurrentPositionInfo that simply aren't available in the Transport API, such as whether the DAW is recording or not.

@ulrik Thanks so much. Truly appreciate.

@Lindon Thanks, Lindon! That's the way I ended up doing it now after watching David's video Playing with Knobs.

@d-healey Wooow that works!!!
Thank u so much!!!

I think having one sampler per letter is not the most efficient way to do this.

Yes, that was just for testing😁

@paper_lung Yes this was just a simple demonstration so button on = preset 1, button off = preset 2.

You can use whatever system you like for the UI, knobs, buttons, panels, menus.

@d-healey oh great, thanks!

Brilliant as always, @d-healey.

@ulrik https://forum.hise.audio/topic/373/delete-object-item?_=1675813186372

@Soundavid Thank you that worked!

@oskarsh Oh I'm with you now, yes the are not part of HISE script.