Hi, hope someone can help: I use Tracktion to master MIDI clock a Korg ESX and a Yamaha DX200. Never had any problems with MIDI sync.
I do the upgrade yesterday and now the MIDI timing is screwed. The HW still receives start/stop signals correctly but they play with wrong/changing speed, weird pauses every few beats. It's completely whacked!
I still have the installation files for previous version. Is it safe to go back?
T2 update has given me problems with MIDI timing to hardware
-
- KVRer
- Topic Starter
- 14 posts since 30 Jan, 2004
(PS, HW never did receive stop signals correctly as it happens, but at least it did play in sync)
PLEASE HELP! Can I at least go back a version?? Is it safe? I think I still have the installer.
PLEASE HELP! Can I at least go back a version?? Is it safe? I think I still have the installer.
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
you can go back without any problem.
Someone shot the food. Remember: don't shoot food!
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
I found the update to be significantly better than earlier builds, and I think that seems to be true for most people (though it's early days yet).
Can you provide some system specifics so I can report this back to the beta group, please.
Can you provide some system specifics so I can report this back to the beta group, please.
Someone shot the food. Remember: don't shoot food!
-
- KVRer
- Topic Starter
- 14 posts since 30 Jan, 2004
1x Intel Pentium 4 3.00 GHz 800FSB CPU, 512K cache
2x 512 Mbyte DDR400 PC3200 DIMM
1x ATI Radeon 7000 64 Mbyte AGP graphics card
1x 120 Gbyte 7200 rpm Seagate Barracuda 7200.7 HDD (10Gb XPmusic, 10Gb XPgeneral, 100Gb audiodata)
1x Sony DWU10A DVD+/-RW internal combo drive black
1x M-Audio Delta 44 audio interface
1x M-Audio MIDISPORT 1x1
1x M-Audio Oxygen 8 controller keyboard
2x 512 Mbyte DDR400 PC3200 DIMM
1x ATI Radeon 7000 64 Mbyte AGP graphics card
1x 120 Gbyte 7200 rpm Seagate Barracuda 7200.7 HDD (10Gb XPmusic, 10Gb XPgeneral, 100Gb audiodata)
1x Sony DWU10A DVD+/-RW internal combo drive black
1x M-Audio Delta 44 audio interface
1x M-Audio MIDISPORT 1x1
1x M-Audio Oxygen 8 controller keyboard
-
- KVRer
- Topic Starter
- 14 posts since 30 Jan, 2004
Hardware status, running previous Tracktion Version:
Korg ESX-1, Yamaha DX-200, both syncing fine to MIDI.
Elektron Monomachine SPX, not syncing to MIDI, query open with Elektron support.
Running new tracktion version
MIDI sync is gone, all hardware intruments play together upon start signal, but overall timing is totally out and has random pauses. So Tracktion is sending something out, but it's wrong.
Korg ESX-1, Yamaha DX-200, both syncing fine to MIDI.
Elektron Monomachine SPX, not syncing to MIDI, query open with Elektron support.
Running new tracktion version
MIDI sync is gone, all hardware intruments play together upon start signal, but overall timing is totally out and has random pauses. So Tracktion is sending something out, but it's wrong.
-
- KVRist
- 413 posts since 17 Mar, 2005 from Cumbria, England
I made a FR a little while ago about this. This new version of T is very good in many other aspects but midi sync is still not right.
Tracktion should send midiclock in a similar way to midiox.
Pressing start in the transport area at the start of the song should create a START timing signal.
Pressing start elsewhere within the song should create a CONTINUE.
Pressing stop should send a STOP midi siganl and not just stop the timing pulses.
There appears to be a problem in way Tracktion handles the very first few timing pulses. The slave hardware does not sync reliably at first and will thus be a random amount of steps behind Tracktion. This would indicate that perhaps the midi data is not being given priority. Again, see the midiox implementation of this. Its perfect.
Tony
Tracktion should send midiclock in a similar way to midiox.
Pressing start in the transport area at the start of the song should create a START timing signal.
Pressing start elsewhere within the song should create a CONTINUE.
Pressing stop should send a STOP midi siganl and not just stop the timing pulses.
There appears to be a problem in way Tracktion handles the very first few timing pulses. The slave hardware does not sync reliably at first and will thus be a random amount of steps behind Tracktion. This would indicate that perhaps the midi data is not being given priority. Again, see the midiox implementation of this. Its perfect.
Tony
-
- KVRAF
- 10815 posts since 26 Nov, 2004 from UK
have you tryed enaybleing
"use realtime priority mode" in settings>audio devices? *warning this can cause T2 to freeze if you open a few spersific vst's* but its only if you open the gui from the vst, so if you dont edit any vst's while testing you should be fine even if you do have a moody plugin installed
i dont have any thing to try sending midi clock to
Subz
"use realtime priority mode" in settings>audio devices? *warning this can cause T2 to freeze if you open a few spersific vst's* but its only if you open the gui from the vst, so if you dont edit any vst's while testing you should be fine even if you do have a moody plugin installed
i dont have any thing to try sending midi clock to
Subz
-
- KVRian
- 1323 posts since 3 May, 2005 from Victoria, BC
-
- KVRAF
- 1600 posts since 1 Apr, 2003 from Seattle, WA
-
- KVRAF
- 6490 posts since 14 Jun, 2004 from Rochester, NY