Midi bug

Has there been anyword on the Midi bug where the first note of a sequence is a messed up if you start a note at the beginning of a sequence? Just wondering, I know a few people have experienced this.

I am having this problem too.

does any one have any suggestions?

its solved with os 4.98

Unfortunately(even with 4.98 installed) I still have the Midi bug that cuts the first notes off only on the sequences first loop....

I got this problem only if the program of the module is selected on the main screen (mpc). Kinda switches the program and forgets the note length of the notes on 1:00:00.

Does it does that everytime with your setup?

rinseout wrote:I got this problem only if the program of the module is selected on the main screen (mpc). Kinda switches the program and forgets the note length of the notes on 1:00:00.

Yeah that might be the issue. I can't say for sure if I've had this problem, (maybe, have to check again) but with a number selected in the PC field the MPC will always send that PC command when PLAY START is pressed, and that could very well cause and external midi module to have problems playing a note that appears on the first midi tick of the sequence.

rinseout wrote:I got this problem only if the program of the module is selected on the main screen (mpc). Kinda switches the program and forgets the note length of the notes on 1:00:00.

Does it does that everytime with your setup?

It is not fixed, still there. This sounds like the same problem and its really **** annoying. I know its been brought up a couple of times, I pretty sure JJ is aware of it. Hope it gets looked into. I dont know about switching the program, it just doesnt seem to play the first note of the sequence if its played at the start. Seems like a pretty big bug to me or for other people that use sound modules alot. It only happens on start up, not after the sequence plays through a second time. Also when you switch to another sequence.

I hate this dang bug. Does this happen in OS 2?

Nebulou5 wrote:

rinseout wrote:I got this problem only if the program of the module is selected on the main screen (mpc). Kinda switches the program and forgets the note length of the notes on 1:00:00.

Does it does that everytime with your setup?

It is not fixed, still there. This sounds like the same problem and its really **** annoying. I know its been brought up a couple of times, I pretty sure JJ is aware of it. Hope it gets looked into. I dont know about switching the program, it just doesnt seem to play the first note of the sequence if its played at the start. Seems like a pretty big bug to me or for other people that use sound modules alot. It only happens on start up, not after the sequence plays through a second time. Also when you switch to another sequence.

I´ll ask again, do you have anything entered in the p.c. field of that tracks? That would make perfect sense as the program gets changed only on start and on switching the seq.

I don't think it matters with PC or not. It seems to happen even without it.

i never noticed or had this bug (although i use 4 midi channels, but no PC in the main screen, only in separate tracks.).

well, definitely looks like it needs to be resent to JJ with more details.

You know what, I took it off PC and it went away. I guess there is some sort of latency or delay enough to where it isnt fast enough to register before the sequence starts. For you Midi experts, is it this normal? Please chime in if you have experience.

Seems to be a problem of midi and/or the receiving unit (esp. if JJ already knows about this problem and its still there). Theres no time "before the sequence starts" the synth/whatever tries to do two things at the same time i guess.

Try either truvc´s "workaround" (actually thats a very good way to use pcs) or use a blank sequence before your beat starts to switch the programs, thats what i do.

So you use empty tracks or sequences for PC? Smart work around. When I meant "time before the sequence starts" I meant the time it takes for the MPC to transmit data to the sound module, for it to play it, and you to hear.

Nebulou5 wrote:You know what, I took it off PC and it went away. I guess there is some sort of latency or delay enough to where it isnt fast enough to register before the sequence starts. For you Midi experts, is it this normal? Please chime in if you have experience.

more ofen than not - the pc command gets there ontime, but the patch takes a few msec's to load/initialise whatever.

and in some more modern synths the dsp's need to get up n running with the voice architecture for each and every patch.

pc's in a sequence can be placed in the right spot in time to get the patch loaded before the first note is played, (so a 'pc' setting like eg: "Seq 5", will use the program change event #5 in a sequence and change only as the event is read in the time its placed at only when the track is not muted.

yet if set to 'pc' setting like "5", will trigger the program change as soon as the sequence is selected even if the tracks muted! even when the sequencer is in stop.....so for me a very dangerous and costly midi scenario, and a few of these say on a few tracks in one sequence will slow a lot of midi traffic down)

i use quite a few prog changes in sequences, and always use the 'pc:seq xx' setting , just so i have ultimate control over when tracks send the pc's