jvdieks

well, the problem is fixt! thanks a lot..

hah... you're fast :) i'll check it tomorrow..

yeah, cubase provides this, but because i'm using a lot of editors that need to send sys-x through cubase i had to turn it off. and you can't turn the filter on/off for 1 output and input, only for all of them (which would also have fixt this). so, well i fixt the problem by turning off the midi input... but still, i've got 6 other synths and non of them cause this loop.. they get they're own echo back and don't respond to that. thanks for your time.. -J

Hi, i just build a sammi and found a problem with the firmware: I've got it connected to a standard channel in cubase with "all midi inputs" selected. Because i'm using a lot of editors for my synths i've got the option to filter out the sys-x from the through turned off. Now when i start the sammi with it's midi track selected it sends out some message, cubase sends it back and the sammi responds again. So now there's a loop and the sammi won't respond or boot up before i select another midi track. also, when i use the java editor and turn a knob there, the sammi sends a message back, which cubase sends back again and the sammi responds on itself again. So there's a loop again. With my novation interface this loop actually crashes the midi driver.. with my motu it doesn't, but the sammi won't respond anymore because of this loop. the only way to solve this is to take the input of the sammi out of the all midi inputs list. this is the only synth i've got that makes this loop, no other synth loops anything back on it's output... but for me the solution of taking out the sammi's input is workable, but i do think it's a bug? btw, it's only sys-x that loops, it doesn't loop note info. So there's no physical connection between the in and the out. -J