DSP Robotics Support

Im using Leifs keyboard. Everything is working but when i change presets The sound is repeating. And wont stop what can be The problem?

When using leifs keyboard half piano disapair after some time ?

yeah ive seen the dissapearing keys happen before as well, couldnt remember which one it was that did it.

I dont usualy put keyboards into my synths, since i really think that they are just visual bells and whistles and are of no use to players and they just suck up graphical resources, ie you dont need to look at your peddles on a bike to know you are peddling.and most serious music makers i have conversed with find them a bit silly, kinda like fake wooden sides and screws ha ha. but hey, each to thier own!

i did at one time make a split keyboard for a drawbar synth i did a while ago though and i am sure i somehow fixed the vanishing keys on it! I think its on this forum, posted last year!

regards

When i use one of the pianos it says error inside module. And whole synth is error

When using leifs keyboard half piano disapair after some time ?

Confirmed. There is a problem there. messed up with it a little and found out a strange behavior that occurs:

1) the keyboard module sends "changed" trigger twice to the midi event on note release

2) combinig the midi routine with the graphical part in the same module causes crashes as they are Interdependent and the midi part get slowen down by the graphical part when an external midi massage comes in(green's speed issue again..) and also causes very high cpu usage

tried this method:

1)duplicated the keyboard module and created two keyboard modules with exactly same size.

2)Separated the midi stuff from the graphical stuff by making one keyboard for midi sends and one

keyboard for recieving graphical data only.

3)took out the whole graphical elements from the first keyboard and the whole midi elements from the second.

4)made a small module inside the "graphical" keyboard which captures the "changed" trigger that come from
the midi split primitive and sends "zero" or "one" to the graphical keyboard (using a counter and own made midi note filter)

5)made the first keybard (which responds to mouse and actually sends midi to the synth) completely transparent.

6)conected the first keboard to the synth's midi routine

7)made one module from both keyboards and put the first transparent keyboard before the graphical one so any time
you click the gui notes, the transparent keyboard sends the note that you see on the screen,thanks to the graphical keyboard.

the results:

midi that goes out from the first transparent keyboard (when mouse is clicked), operates the synth's midi routine and the second "graphical" keyboard as well by filtering the relevant note that has been played and sending a "changed" trigger massage to it. also, the graphical keyboard gets any midi massage from any midi device.

this method works great without any crashes or issues with any midi device, besides of the keyboard it self...
as the keyboard it self sends "changed" trigger twice when note is released, and its "maddening" the counter which
receives the "changed" triggers. i dont know why its acting like it. still looking for a solution. maybe because of the
mouse draging event?
anyway, if i find a way to fix that issue, i will upload the fixed module to the "user examples" sections.

Thnx Kortezzz

yeah i see it! also when passing midi through it from my midi controler keys im getting 2 note on messages and no note offs when hooking it up to troggs midi inspector! keypress - note on, key release - note on there is other weird stuff going on in there too

yeah i see it! also when passing midi through it from my midi controler keys im getting 2 note on messages and no note offs when hooking it up to troggs midi inspector! keypress - note on, key release - note on there is other weird stuff going on in there too

Of cours. As i said, that is because you havn't separated the midi part from the graphical part, and you just conected your primary midi in to the keyboard's midi in. If you use the "separting mathod" as i did, your midi controller will work perfectlly, but not the keyboard it self, as the problem is inside it's midi circuit
all we have to do now is to find out why the keyboard's midi circuit sends 2 triggers on note release when playing whith mouse, and we will get the best keyboard module + midi in ever created in both SM and FS!
maybe the experts here will find somthing.
Trog, are you there?

Trog is always pro

kortezzzz wrote:
Of cours. As i said, that is because you havn't separated the midi part from the graphical part, and you just conected your primary midi in to the keyboard's midi in. If you use the "separting mathod" as i did, your midi controller will work perfectlly, but not the keyboard it self, as the problem is inside it's midi circuit
all we have to do now is to find out why the keyboard's midi circuit sends 2 triggers on note release when playing whith mouse, and we will get the best keyboard module + midi in ever created in both SM and FS!
maybe the experts here will find somthing.
Trog, are you there?

well no! it wasnt anything to do with FS the errors i was seeing! it was my computer! all fixed now!

Did you fix the piano? do you have a working module mate? then pls post it!