T1 and sysex

[cecil]

Hi

i'm trying to control my juno parameters with sysex, in Tracktion1. I also have a edirol PCR-30 controller keyboard in which i can assign sysex faders. Works perfect...but if i record these movements in TRacktion, the sysex is there, but i cannot hear them when i play it back. Even when i set them manually with it sysex editor, they're not played back. In this thread gwydi states that

'it handles *some* sysex, but it imposes a maximum length on sysex strings that is well below what some synths use, and is therefore useless to many of us. '

so i gues my sysex-strings (e.g. F0 41 36 00 23 20 01 11 00 F7) are too long!? My question is: does anybody know more, have the same problems, or even workarounds about this, and what is the maximum amount of bytes?

[falseotter]

I've been having some sysex problems myself lately. I looked at some exported MIDI files with a hex editor and learned a few things.

First of all, Tracktion automatically adds the F0 and F7 to your sysex string, so you don't need to enter them. It probably doesn't hurt, but it will slice four bytes off your string...

More importantly, Tracktion always adds my sysex strings three times as far into the song as I want it to. In other words, if I insert a sysex event at 1|1|480, it will play it at 1|2|480 (3x480=1440), and if I insert it at 1|2|000 (3x960=2880), it will play at 1|4|000; but if I insert it at 1|1|000, it plays at the correct time (3x0=0).

Anyone else know experience this bug? Jules, if your listening, I think the problem is with how you're computing the bits in the delta-time bytes before the sysex events. If I promise to upgrade, would you fix this?