InSaNe Midi prob-''Atack the head,and the body will die.."

So............I cannot for the everliving soul of me get my virus b module to trigger the first note in a seq. after changing seqs back and forth,or even in the ''main screen'' single seq mode....I went through this before with a korg ms-2000 mk I,and ended up selling it,and getting the mk II model just to have this same ''Midi hiccup'' happen AGAIN! Strangely,not all of my synth modules have this issue,Mopho and Blofeld switch/trigger like a dream...ARRRRGH! Do I have to place some prog. change or early trigger in step write or something...sucks...Every seq.. has anyone else had this kind of prob? Theres a Snow TI down in our studio,and if it triggers correct....Im gonna sell this B on down the river...If you have any clue,Please shed some light brothers.... the B's been good,but...shit.

Does this have anything to do with an MPC or were you just venting your studio woes?

uh...yeah..hence the mpc midi questions... prog. change and/or trigger step insert etc...didnt you read this post?

i'm having a bit of a hard time following what is happening...your virus is like 'missing' the first note of the seq?

it could be that it is changing patches, and the synth is hiccuping as it tries to 'load' the patch. even if it's not actually 'changing' patches, if that program change is being triggered, it could cause the synth to go silent for a sec.

you DO NOT want a program change at the beginning of the sequence if it is looping - a lot of synths (most synths) will go silent as they try to load the new patch and that sounds like what is happening.

be sure to check all tracks.

can you disable receive program change via midi on the virus? that would be a good way to test if that is what is happening.

edit: durp

oscillation communications wrote:didnt you read this post?

I did.

What time position is this first note in your MPC sequence?

Im guessing its beat one, bar one?

If so it's a common issue with MPC's and some synths.

exactly...the very first note...I've tried doubling the note @ the beginning etc...(and so far as to consider sampling my first note with that module..(seems WAY too impracticle.) Turning the prog. change off on the virus b sounds like a good way to trouble shoot,but if it only triggers correct in that way,it ALMOST makes the virus useless to use with the 1000...I went down and hooked up our other 1000 with the Virus snow TI,and noticed the note triggers fine,unless there is a prog. change,and then It still triggers the first note on time,but that first note is from the prog. BEFORE the change...(a lil better,and at least theres prob a work around via seq. structures..(?) hhmmmm..

and yeah,its every first note trigger at the beginning of every seq.regardless of prog.change or using the same sound of any other seq...to bad theres not a tight list of which modules have this issue with which mpc.....we know of 2 synths now...the virus b and ms-2000....super frustrating...

AND if you zero back the seq. and hit play instead of play start,it triggers fine,but when those seq's change,its the same mistriggered sh*t..

oscillation communications wrote:to bad theres not a tight list of which modules have this issue with which mpc.....we know of 2 synths now...the virus b and ms-2000....super frustrating...

you must have missed the part of my post where i said MOST SYNTHS.

only a handful of synths can handle a program change and not have any hiccups. this list of synths, however, is MUCH smaller than the list of synths that exhibit the problem you are describing.

however, and don't take this as offensive, but it's on you to step your programming up and quit blaming the synths. as i said, this has been a known issues with, dare i say 90% of synths, ever since program changes were possible. but you are coming across like, after 30 years of midi, you are the first one to experience this. i realise you are frustrated, but this problem can be dealt with with a little knowledge.

the solution is to NOT insert a program into the sequence if your synth can't handle it. if this is a problem, then you need to buy a new synth (the esq-1 for example does NOT exhibit this behavior).

your best option?
have you tried using the 'PGM' field in your mpc main screen? you can use that to call up a program on the external synth ONCE, and not need to insert a program change into the sequence, which would trigger everytime the sequence loops around. it is basically there to solve this very problem.

so again, go through your tracks (all of them), and remove any program changes.
if you want to initialise to a particular program, use the PGM field on the correct track.
if you need to change programs WITHIN a sequence, either get used to the glitch, or find a new synth that does not behave like most synths do.

does that make sense? here to help.

Hey thanks to everyone who has helped to try and solve this..well...its not a programing issue if the first note does not trigger regardless of the patch right? And Im not blaming a synth for any of my mistakes/lack of prog savy...Im just trying to investigate if this comes down to the individual models im trying to work with...Ive midied upwards of 45-50 synths in many ways over 20 years,and yes,Ive only encountered this maybe 3 times..(guess ive been lucky Even the prophet 600 I used to use (the worlds first midi synth) was tight as a drum.) Its just a drag to possibly have to sell such a great sounding module for such a seemingly simple function issue,and turn around and start the hunt again for a suitable replacement...poor me right? Im not tripping,just trying to connect with ANYONE who has used these two and gone through simular..

turning off pc does fix this...I guess the ''work around'' is to have less prog. changes within the course of a few seq's etc...thanks.

oscillation communications wrote:turning off pc does fix this...I guess the ''work around'' is to have less prog. changes within the course of a few seq's etc...thanks.

you don't actually need to disable program change completely, just program it right. don't put it in the sequence, use the PGM field.

did you try that?

if you really absolutely have to put the prog change into the sequence, put it in early and allow a brief 'catch-up' note after the prog change to let the synth be ready.