Tracktion2 bugs?

[Mauvehead]

I ran into a problem that Mackie hasn't figured out just yet. When I try to have Tracktion2 as a master and I try to slave either my Korg Karma or else my Roland MC-505 using MIDI Clock, both machines will initially start rolling in sync but then when I hit "stop" on Tracktion2 the Karma or Groovebox's final note hangs on until I unplug the MIDI cable and hit "stop" on their controls. Also, neither the Karma or Groovebox follow the Tracktion2's transport controls. I've slaved these two units for a few years now using my Roland VS-1680 as a master and have never had this problem. The Mackie techs are baffled and are looking into this over the weekend. I was on the phone for roughly 2 hours yesterday talking with two different techs (nice chaps they were). They said this issue doesn't make sense and they are now looking for plausible reasons. Anyone else tried this scenario and run into any problems? I'm using either an M-Audio Uno or a Presonus Firepod for MIDI I/O. Same results in both cases.
Also, on a side note, what is Tracktion2's MIDI ppq resolution? I didn't see this spec in the manuals anywhere. Thanks!

[ModuLR]

can't help with the midi issue , but T is 960 ppq me thinks..

[Mauvehead]

Thanks! One problem solved......one to go.

[Madness]

Why not make your MC505 or your Karma the MASTER in that setup...

This way...the Transport Controls on your Master could control Tracktion. I do it this way with my MPC its a much preffered method for me.

[Mauvehead]

Thanks for the reply. Actually I only intend on using the Karma and Groovebox on a limited basis. IMHO the Groovebox would utterly suck as a master since it is entirely loop-based. As per the Karma, it would be one big hassle to have to set it up for every song (tempo maps, etc). I'm wanting to remain as mobile as possible. Consequently, the less hardware the better. Besides, the Mackie engineers told me that this shouldn't be a problem and that they need to get to the bottom of it. Hopefully the issue will get resolved quickly. Thanks again!

[husker]

Same problem here with a Korg EA-1...hit stop in Tracktion and the last note gets stuck in the EA-1, which is pretty weird considering the note sequencing is done by the EA-1 (T just provides midi-clock and start/stop. Also sometimes get the issue with the transport not stopping the EA-1.

Another of the midi problems in T2 that I haven't had time to get to the bottom of. Being busy making music in Live, which has very well behaved midi.

Are you running multiple ports on a Midisport? My problems are much worse if I run more than 1 single midi out.

[Madness]

IMHO the Groovebox would utterly suck as a master since it is entirely loop-based. As per the Karma, it would be one big hassle to have to set it up for every song (tempo maps, etc). I'm wanting to remain as mobile as possible. !

I think you should try it with the MC505, being loop bassed won't 'cause major problems at all I suppose it depends how you use it. I have played with one in a simular setup and the ability to JAM out with loops and cut them in and out whilst Multi-Tracking the results is pretty neato.

The real beauty of the 505 is the potential to map the controllers to various parameters in Tracktion. It makes a nifty little control surface, plus it makes sound. Also, being hardware it is inherrently tighter and more stable than Tracktion. I find the MIDI in Traction flaky at best.

That said, if they fix it...that will be SWEET!! 'cause you will have the best of both.

[Mauvehead]

Same problem here with a Korg EA-1...hit stop in Tracktion and the last note gets stuck in the EA-1, which is pretty weird considering the note sequencing is done by the EA-1 (T just provides midi-clock and start/stop. Also sometimes get the issue with the transport not stopping the EA-1.

Another of the midi problems in T2 that I haven't had time to get to the bottom of. Being busy making music in Live, which has very well behaved midi.

Are you running multiple ports on a Midisport? My problems are much worse if I run more than 1 single midi out.

Good thinking..... The "more than one single MIDI out" may be the suspect. I'll try to see if I can narrow down T2's output down to just one channel and see if that helps. I wonder if it is sending more info than the Karma or Groovebox can sort through. I used to run into a similar problem when using the Karma's sequencer to capture performances on my V-drums when the drums were in "brush mode". Seems that the brush mode was kicking out a ton of more data than normal mode and it would bottleneck in the Karma and mess up the timing of the sequencer and the Karma would do all sorts of goofy things. Wonder if this new problem is similar in nature......

[Mauvehead]

Word came back today from one of Mackie's techs:

"I tested Tracktion with a Micro Q, Alesis ION, Kurzweil k2000 and a Arrick modular. I was able to reproduce the stuck note issue on the K2000. It only happened when I had Tracktion trigger the K2000's sequencer. When I stopped Tracktion, I experienced a stuck note with the K2000, exactly as you had experienced. I talked with another tech here and he had the same experience with a Roland Groove box. This sounds like an issue with Tracktion and I will foward on your experience and our findings to the developers. This sounds like something they will need to look at. If it is indeed a Tracktion issue, they will find a solution (future update). Let me know if you have any other questions. Take care."

Can anyone else test this to see if they have this issue?

[MT]

Can't argue with that kind of support. Very cool.

[Mauvehead]

Yep.....that sort of support is fantastic. And from what I gathered from talking with the tech, he did a lot of these checks on his own time over the weekend in his own studio. That speaks louder than words. I'm very confident that this issue will get resolved as soon as they are able. Makes a person feel good about shelling out the $$ for their product.