MIDI DESIGNER
The only MIDI controller for iPad, iPhone, and Mac


Talk to other MIDI Designer users about MIDI Designer, iOS MIDI and related topics. Or share layouts, pages, and ideas.

Check out our Facebook Group.

Of course, if you want to send us an email, feel free.

Open problem reports

Summary of user requests
Midi notes sound but not all display - MIDI Designer Q&A
0 votes
in Defect (Is this broken?) by mossontherock (270 points)
edited by mossontherock
Hi we'll look into this later today. Thanks!
These are just button groups, right? If they are: SAVING YOUR LAYOUT FIRST to a named file, please try deleting the supercontrol that makes them a button group and seeing what happens, please.
also: first thing to check is the log under Config -> Log. See if MD is receiving those notes in the first place. Second thing might have to do with the velocity that you're sending? Thanks!
The keyboard isn't in a group or supercontrol.  The transpose feature is handled laptop side and not within midi designer itself.  I can't see it being a velocity issue and the test from MD to laptop send all the notes at maximum velocity.

I haven't yet taken time to check the config log, but it is apparent that all notes are been sent and recieved and interestingly enough the issue from the perspective of MD to Laptop shows failure on one vst device (pizmidi keyboard/Sample Tank2) but not another (NI B4II organ).

I've attached the mididesigner file - if anyone want to test or use it, you're free to do so.  It not important to get an answer to this, but if the keyboard feature worked fully it add something to the program.
How are you connecting the two MIDI Designer instances together?
In the example given, my phone is acting as the wireless hub connecting ipad and laptop;
iphone via littlemidi app makes a wireless midi link to laptop
iPad via littlemidi app makes a wirelss midi link to laptop
laptop (running windows XP sp3) linking devices via rtpmidi
The link between the iphone and ipad running MD is made through the laptop software (Reaper) and not directly and depend on the midi out from the laptop via rtpmidi to communicate.
This is a little bit technical, but: what's happening here is that the display is not updating because the note is already off by the time it needs to show it. So it's not stacking up messages (like on then off) but rather showing whatever message is ready to show when it has a chance. Both the on and the off message are being processed -- so if there are subcontrols, they'll do their thing in response -- but in many cases the on message fails to show because the off arrives before the display gets a chance to update.

This is how other software and even hardware (like NI Maschine) does its work: if it cannot update the display, that's ok, but it always puts all processing first.

That said, we could try tightening up the incoming message throttle and see if that helps performance. Are you on the beta team? Would you like to be?
...