I often use Raw MIDI / System Exclusive outgoing messages that concatenate as many as 16 separate messages. MT handles this nicely, except that the Log Window truncates the outgoing messages. So what I often see is something like this:
In this case there were 9 messages, but only the first 6 are shown in their entirety. The seventh, eighth, and first two parts of the ninth (channel and note number) are represented by the three dots. Finally comes the Velocity of the ninth message (01).
This isn't terribly serious because I can look at the code that generates the output and figure out what the whole string.
It would be nice, though, if the entire output could be explicitly stated.
If I’m really struggling with a section of the code which does this kind of output, I sometimes take the trouble to break the ”offending” translator into two or more parts so that I can see, more easily, what is going wrong. But it’s just a work-around.
Hmm, I sent a long single SysEx ( 255 bytes and I didn’t see any truncation) using Send SX. It just broke the incoming message up in to several lines but everything in the log file was there. What version of MT Pro are you using?
It’s the outgoing messages from MT which exhibit the problem. Try sending, say, 10 consecutive note on messages within the same translator. I think you’ll see the truncation then.
The important stuff works, in that the message is sent, but the log window truncates, so one cannot check the entire message to see what was actually sent.
OMG!!! Why didn’t I think of that. It would have saved me hours of scouring through my code to see what I was actually sending – vs what I thought I would be sending ;-).
Well, just a bit of time lost. Thanks for the insight.