oops.. almost forgot to answer this question..
it skips the first note if recorded before or on bar 2,
with or without automatic track creation
and to add to that… it seems to skip the first note in automatic track creation when the note falls on the beginning of a bar
in case you read my post when I was still messing with it..
..it seems to skip the first note in automatic track creation when the note falls on the beginning of a bar
I’ll set aside time to examine this, when I’ve completed the things I’m working on currently. I may have further questions to you later on.
I’ll stay tuned 8)
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?
@Zynewave wrote:
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?
it records fine if the notes are short but it messes up when I use long notes (around 1 bar long, etc).. this happens everywhere, also when I put the punch-in on bar 1
latency is 440
Hi , Frits , i have the same problem , but if i do as you say (creating the event manually with the pencil), its ok.
Hi , Frits , i have the same problem , but if i do as you say (creating the event manually with the pencil), its ok.
In my case , if i draw the event before recording with the pencil , its ok , otherwise i have the same problem , the first note is missing 🙂
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.
it records fine when I press the note after the punch in mark
but not with long notes right(ish) on the first beat
the way I record I usually let the track play and pick in at the needed point so this recording bug usually doesn’t bother me.. but it’s good to mention anyway, it will save you from more whining from users