Now when you turn that knob both programs tempo will change in time with one another and be set to the same tempo. Midi sync is terrible - i suggest to all of our members on the forums just to manually set the BPM and if they need to do tempo changes to assign one knob to both programs tempo.Ĭhange the tempo range in Ableton to the same tempo range as the same tempo on as Traktor (40bpm to 300bpm). My conclusion is: using a hardware MIDI clock generator delivers better results, and the TP-Live synchronisation as it is now is maybe not really an option yet, or it is only then an option if you can live with the constant tempo changes in live. using a 3D as MIDI clock sender, TP stays again close to 119.xx, but the intersting thing was that in this case the Live BPM stayed quite stable between 119.7 and 120.2 a 3rd tool as midi clock generator and both TP and Live as receiver, TP stays close to 119.xx and the fluctuations in Live were similiar to test case 1 TP as sender (120 BPM) and live as receiver, the BPM value in live fluctuates between 118.44 and 121.93 I did several test the last days to see how good this works using different scenarios: live as tick signals receiver must be able to translate the ticks perfectly back to BPM there must be no delay or latency on the side of the connection, and traktor needs to be able to send the ticks excatly in these intervals, and the tick interval is 19.53125 milliseconds the midi clock receiver must translate the number of received tick signals back to BPMįor 1 tick signals needs to be sent each minute, i.e. The midi clock sender sends 24 tick signal each quarter note (=beat). The document is nice, but it doesn't tell the whole story
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |