that the MIDI player is only intended for short passages, mainly loops.

No, it can have any arbitrary length.

this sequence can apparently only be one bar long,

That's not correct. You can set any length by giving the MidiPlayer a time signature object with NumBars=XXX (or NumQuarters=XXX).

I think the main problem with the MIDI Player is that it's highly under documented up to a point where it gets ridiculous - and if I'm being honest, every time I'm using the MIDI Player, I end up looking in the source code how it works and a programmer with a little bit more self-awareness would have taken this as hint to improve the docs...

It appears that both a Transport Hanlder and a MIDI Player would be required for this approach, but there seem to be overlapping methods here leading to some ambiguity.

Of course they have some overlapping methods, but that's because the Transport Handler will act as external synchronization source for multiple MIDI Players. These are the cases where you want to hook up one or more MIDI players to the transport handler:

multiple MIDI players that should play in sync synchronisation to an external clock like the DAW timeline.

However If you start the MIDI players from a note callback (I'm doing this in PercX) you can synchronize them without the need of the transport handler.

@clevername27 Solved.

@d-healey thanks will do!

@ForeverLive said in Auto Show Hide Values On Label [ Solved ]:

@Lindon thank you! Do you think it's even possible to use label instead of a panel? And just make label react to keyboard with some scripting? Or it's require supercomplex rewriting hacker C++ direct JUCE code mega recompilation process? Sorry for humor.

why would you when you can use a panel?

@Christoph-Hart Ayaya (in my Mario voice). I just got into LAF and already have my hair falling out. I haven't even glanced at scriptnode yet.

Squirrel Pattern Baldness, here I come (shitty Spongebob reference)

Another method that I used before the apparition of child panels (and I think is still valid for that kind of operation) is one unique panel with an object that hold the data, and a paint routine that paints them
This is particularly useful when you wan't to draw specific shapes, like a pie chart style

@Dan-Korneff that was it, thank you lots

@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.