Ok, I found a way to reproduce this bug.
When Podium records notes on a blank track, it creates a sequence event and snaps the sequence event start to the previous bar line. But it creates the sequence when receiving the first note off message, so that it knows how long the sequence needs to be to hold the note. If you press and hold the first key, and let the play cursor move across the next bar, and then press and release a second note, then the sequence will be created based on the second note, and not the first note that is currently being held. When the first note finally is released, it will have a start time earlier than the sequence event, and thus will be discarded. I’ll change this, so that the created sequence considers the start time of any notes currently being held. Sorry for the long explanation.
However I could not make the first note skip recording if I enabled punch in and set the punch in position prior to the point where I press the first note. Could you check if you manage to record the first note when using punch in?
Oh, and thanks for your help with hunting down this bug.
Hi Francois,
I recently discovered a silly bug, that is causing the input channel filter to be unselectable for MIDI input mappings. It was a bug that sneaked into version 1.21, where I made MIDI input available for plugins as well. It will be fixed in 1.28, which I hope to release this weekend.
Are you using punch in/out when recording MIDI? If not, could you try activating punch in and set the punch in position to bar 1, and let me know if this changes things.
Try showing the ‘latency’ row in the mixer. What is the latency value (samples) shown for the track with your MIDI input?
perhaps that some functions will be implemented for the summer ?
I certainly hope so. Particularly the collapsed track meta event is high on my list.
Hi Jean-Marc,
The good news is that I agree with your feature requests. The not so good news, is that it will probably take months before all the items on your list are implemented. Development of larger features is currently on hold, until I have completed revising the Podium guide. I expect to still spend a couple of months working on the guide, while releasing minor software updates. Unfortunately I am slower at writing the user manual than I am at writing the code. It’s hard work for me, and not as fun as coding 😥
But it has to be done. A complete guide/manual is the only thing missing before I feel I rightfully can claim that I have a full-blown product. There is no point for me to keep adding features, if the features are not documented anywhere. Otherwise no one will ever know what the potential of Podium is.
Frits