Can you do another quick test? If you create an arpeggio in the midi roll in Tracktion, and send that to an external midi device, does the timing go wacky on that too? Or is it just when you use Ext in the latest version of Tracktion?
Cheers
external midi way off
-
- KVRAF
- 2417 posts since 17 Jun, 2003
"my gosh it's a friggin hardware"
-
- KVRist
- Topic Starter
- 76 posts since 31 Jan, 2003 from Outer Bongolia
Ok. Thanks for asking me this. Thanks also for reminding me to do some more research into a problem before I post bug reports.
Because as I've now discovered, it's really an extremely specific problem. It only happens when I actually play live from a midi input into eXT within Tracktion, and send the midi output of that on to an external synth. Only in this case. It does not happen with midi clips within Tracktion being sent to external synth, it does not happen with playing live into eXT arp within T and on to a VSTi (in T or eXT), not even midi clips within T sent to arp in eXT and then on to a midi output. And the same setup with eXT standalone, as I've said, does not cause this error.
The patch on the external synth was set to respond to external midi only (ie. not local), and the midi notes was sent from this synth as well, but using another controller or another external synth as sound source still reproduces the error, so the fault is not with the synth itself.
I'm terribly confused.
Because as I've now discovered, it's really an extremely specific problem. It only happens when I actually play live from a midi input into eXT within Tracktion, and send the midi output of that on to an external synth. Only in this case. It does not happen with midi clips within Tracktion being sent to external synth, it does not happen with playing live into eXT arp within T and on to a VSTi (in T or eXT), not even midi clips within T sent to arp in eXT and then on to a midi output. And the same setup with eXT standalone, as I've said, does not cause this error.
The patch on the external synth was set to respond to external midi only (ie. not local), and the midi notes was sent from this synth as well, but using another controller or another external synth as sound source still reproduces the error, so the fault is not with the synth itself.
I'm terribly confused.
-
- KVRAF
- 10815 posts since 26 Nov, 2004 from UK
did you check the bpm in eXT?kobresia wrote:Right. I've never had bad timing issues before v2.0.2.8, now external midi is all over the place. Tried using energyXT as an arpeggiator yesterday, I've done this hundreds of times, and simple 1/16 notes are WAY off.Mackie wrote:Fixed issue with MIDI data not working well with external MIDI hardware. This fixes complaints of doubled notes, dropped notes, or bad timing when sending MIDI to external MIDI hardware.
Midi interface is a Midisport 2x2. No problems with energyXT standalone.
Tracktion is now suddenly unusable for me, as I do rely to some extent on external hardware.
So where can I download old versions?
are thay the same?
Subz
-
- KVRist
- Topic Starter
- 76 posts since 31 Jan, 2003 from Outer Bongolia
You just might be on to something here Subz.
They are the same, but it only happens when Tracktion is not playing. In other words no host sync messages are being sent to eXT (or something like that). But still, it does work with VSTi when it is not playing, that's still strange.
Ok, so even if there's a bug, the only problem is I can't use Tracktion purely as an effect rack. That's not a big issue for me.
Thanks everyone.
They are the same, but it only happens when Tracktion is not playing. In other words no host sync messages are being sent to eXT (or something like that). But still, it does work with VSTi when it is not playing, that's still strange.
Ok, so even if there's a bug, the only problem is I can't use Tracktion purely as an effect rack. That's not a big issue for me.
Thanks everyone.