T2 Sync problems

[valley]

I can't make head or tail of your problem description above so I haven't been able to think of anything useful to tell you. If you could post a problem report that actually explains what you are trying to do, and what happens when you try, someone should be able to help you.

[Breakpete]

I know extremely little about recording from external gear in Tracktion, but I'm wondering what soundcard latency the original poster is working with?

I've also experienced various synching issues with T1/T2 Demo midi and audio data. Yesterday I got the Asio4All drivers to work in T2 thanks to good advice on this forum, and I noticed alot of these issues were gone or not so severe. It seems like T is very dependent on good soundcard drivers and latency. In my experience FL, Orion and Reason handles this better for some reason.

[igglebop]

I had to adjust the latency to 58 ms today to elliminate some popping. I still don't really understand the latency concept, but I guess it'll (inevitably) come with more experience with computer-based recording. I've had no problems with popping or syncing in other multitrack programs. Maybe T2 just takes more tweaking than the others.

[Breakpete]

Might I ask what soundcard you are using? If you are using a laptop, does it have an integrated soundchip like e.g. SoundMax?

Have a look at the Tracktion settings tab and audio devices. Make sure you have selected your 'proper' soundcard drivers, preferably ASIO drivers. I had something like 58ms latency when using DirectSound, and I experienced synch issues too.

Now, with Asio4All, I get 10ms latency with no problems, and can push it down to around 5 if I'm working on something that's not too heavy on the CPU.

[Madness]

MTC = Midi Time Code = used for syncin' external devices. (read: nuttin' to do wit latency)

Good to see some new peeps playin' wit T2.

[Breakpete]

The reason why I mentioned this is that I've had syncing problems between audio and midi clips, and I think they were more or less directly related to the soundcard drivers I were using. With better drivers and a lower latency setting, some of these problems haved dissapeared on my setup.

Now, if igglebop has a latency setting of about 58ms, he's probably not using the best of drivers, which might explain some, but not all, possible synch issues.

[rustyfingers]

Also having sync problems.

Setup:

Akai DPS24 midi out -> M-Audio FW1814 Midi-In

Akai setup- MTC Master/MMC Master/30FPS

PC Setup - 2GHz, 1GB running Traction 2 - slaved to MTC/MMC 30FPS (tried other frame rates also)
Tempo and time sig set to the same for both.
----------------

Sync is off by about 5 to 8 frames. It was really inconsistent about frame differences as sometimes it was 5 and other times it was 7 or 8.

Pressing play on the DPS causes T2 to play.
Pressing stop on the DPS causes T2 to stop.
That was pretty much all that worked. Pressing RW would cause T2 to rewind by 2 seconds. You had to keep pressing RW on the DPS to eventually get T2 to the beginning.
FF did nothing in T2.

If you started the DPS at 2:05(example, T2 would start wherever it left off last time. In other words it wouldn't set it's clock the the reference sent to it by the DPS.

FWIW- The DPS syncs up perfect with my Triton Pro. I was hoping the sync would work on T2 because MIDI editing on the Triton kinda' sucks compared to PC editing. I can dump the MIDI from the Triton but something alwasy seems to get screwed up in the translation when you go Triton -> PC for edit -> back to Triton.

Hope this helps
Dennis

[IIRs]

Also having sync problems.

Setup:

Akai DPS24 midi out -> M-Audio FW1814 Midi-In

Akai setup- MTC Master/MMC Master/30FPS

PC Setup - 2GHz, 1GB running Traction 2 - slaved to MTC/MMC 30FPS (tried other frame rates also)
Tempo and time sig set to the same for both.

Try running Tracktion as the master instead. Tempo and time-sig don't matter for time-code (only for MIDI clock)

That was pretty much all that worked. Pressing RW would cause T2 to rewind by 2 seconds. You had to keep pressing RW on the DPS to eventually get T2 to the beginning.
FF did nothing in T2.

If you started the DPS at 2:05(example, T2 would start wherever it left off last time. In other words it wouldn't set it's clock the the reference sent to it by the DPS.

It sounds like you need to tell Tracktion to chase MIDI time-code (Choose the input in the timecode menu, and click the little padlock thingy by the transport controls)

If you do it the other way round however (I have had better results syncing my VS880 with Tracktion as the master) you will need to tell the DPS to chase timecode, and make sure Tracktion is set to transmit it on the correct output. (settings page IIRC: I'm at work..)

[valley]

MTC = Midi Time Code = used for syncin' external devices. (read: nuttin' to do wit latency)

not entirely true. large processing blocks make it tougher to synchronise stuff, and at very high latencies Tracktion (and a range of other sequencers I have tried) tend to be a little less stable for timing.

The lower the latency the better generally (within reason of course - sub 3ms is usually overkill).

[rustyfingers]

OK everything works !!!

Jog wheel acts kinda funny. Sometimes it works perfect othertimes it doesn't. Using the mapper I was able to map the Userbank faders and pans on the DPS24 to T2 and everything worked great.

Recording Midi from a Triton was perfect, no problems.

Sent audio from the DPS to T2 via Adat. Everything recorded fine and there wasn't any lag while recording. When you played back there was a noticable delay between the audio on the DPS and traction. If you pushed STOP on the DPS and START right after, the delay was gone. If you started in the middle of an audio clip there was no noticable delay. The delay only occured when you started from the beginning of the audio track and is easily cleard up by stopping and starting again without doing a rewind.

It worked so good that I found myself recording MIDI tracks in T2 and started working on a tune. I suddenly realized I was using the DEMO and the notes were cutting out. Bummer, now I have to wait until I can purchase T2.

So far so good though. A few little nit picks but for the most part it worked great. THANKS T2 for saving me from Cubase or Sonar.

Dennis

[Beno]

Hey Guys,
Just checking through some old bug reports. Is anyone still having sync problems with T2? If so please post a bug report again (even if it posted above). Also, before you check please check that the frame rates are indeed matching. this is usually the biggest cause of problems. Many devices do midi a little bit differently and we couldn't test with every device on earth so if you having problems, let me know what's going on we'll do our best to get things sorted.
Thanks,
Ben

[igglebop]

Hi Beno,
I am still having the same problem. I've tried midi through both my Edirol UA-25 and my Edirol UM-1SX, and have the same problem (granted, it's probably the same driver). As others have mentioned, they've had similar problems. Reducing the latency seems to make it better, while turning on the "Auto-return" feature can sometimes make it really bad.

[FoxV]

Cool Ben, thanks. I want to sync T2 with my Roland VS1680, but haven't gotten round to it yet. I will soon!

[Sidhu]

I suddenly realized I was using the DEMO and the notes were cutting out. Bummer, now I have to wait until I can purchase T2.
Dennis

Is that supposed to happen mods ?

Sidhu

[valley]

Is that supposed to happen mods ?

The demo sends all-note off messages every so often, so yes.