During early versions of T2 I had very unstable timing, but later builds resolved it. Seems like things are still fluffy for some people, I'm just looking for anything to narrow down why and where.
Another Midi-sync issue
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
nope.
During early versions of T2 I had very unstable timing, but later builds resolved it. Seems like things are still fluffy for some people, I'm just looking for anything to narrow down why and where.
During early versions of T2 I had very unstable timing, but later builds resolved it. Seems like things are still fluffy for some people, I'm just looking for anything to narrow down why and where.
Someone shot the food. Remember: don't shoot food!
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
when I get some free time later this week, I'm going to try detweaking my 2k install and see ig I can't cause things to go wonky
Someone shot the food. Remember: don't shoot food!
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
husker: do you have many other USB devices running? Maybe try unplugging all but the 4x4 and see if the timing gets any better..?
-
- KVRist
- 412 posts since 17 Mar, 2005 from Cumbria, England
[Lurker mode: off]
I have T2 (registered version) with a USB Midisport 4x4 interface running on a 3GHz PC. midi timing is currently all over the place compared to Sonar and VSTis within T2. You can garantee that timing will suffer during a screen redraw.
This also appears to happen with rewired Reason too if using Tracktion as the main sequencer. If driving Reason's own sequencer and merely taking audio streams back into Tracktion, then timing appears to be rock solid.
I am this close to buying Live...
Tony
I have T2 (registered version) with a USB Midisport 4x4 interface running on a 3GHz PC. midi timing is currently all over the place compared to Sonar and VSTis within T2. You can garantee that timing will suffer during a screen redraw.
This also appears to happen with rewired Reason too if using Tracktion as the main sequencer. If driving Reason's own sequencer and merely taking audio streams back into Tracktion, then timing appears to be rock solid.
I am this close to buying Live...
Tony
-
- KVRAF
- 3617 posts since 26 Sep, 2003 from Bradford - The Armpit of Britain
hmmm - i never experienced any problems with reason & Tracktion, then again i was only playing around with my bro's copy of reason at the time (i own's it myself now - & I is pleased) so i didn't do anything to complex in it.
It seemed stable for me with Tracktion sequencing stuff.
It seemed stable for me with Tracktion sequencing stuff.
-
- KVRist
- 412 posts since 17 Mar, 2005 from Cumbria, England
I just tried to replicate the problems I had with Reason controlled by Tracktion. I couldn't replicate the problem at all. So it may have been just a system funny. I need to investigate more on this one. It may be down to the number of active tracks. Today's test only had three re-wired channels, whilst I noticed the problem before I had a very complex set-up stored. Alas I didn't keep this when I had a bit of a tidy up.
However, what I did find today was all sorts of other things wrong with ordinary midi. Timing is definitely poor and CPU overhead seems to be one thing that affects it. Certainly screen re-draws are the worst offender. But I now have things happening that didn't happen in T1 I don't think.
I have notes being cut-off and some notes are ignored. This seems to happen if the receiving synth is monophonic and a new note overlaps with an older one. The note-off from the previous note seems to cancel the other note. But this does not always happen, but if a note is truncated it will always be truncated. Moving its position within the clip may bring it back. Its odd alright.
Other timing issues are that the midi-CV convertor is detecting legato notes even when the individual notes are distinct.
Another was recording a series of short notes into a clip. Then moving that clip to another place in the track. Recording another set of notes in its now empty place... but the note off's from the previous recording appeared to be still in place, thus truncating the new notes.
I am sad to say I'm getting rather cheesed off with it really.
However, what I did find today was all sorts of other things wrong with ordinary midi. Timing is definitely poor and CPU overhead seems to be one thing that affects it. Certainly screen re-draws are the worst offender. But I now have things happening that didn't happen in T1 I don't think.
I have notes being cut-off and some notes are ignored. This seems to happen if the receiving synth is monophonic and a new note overlaps with an older one. The note-off from the previous note seems to cancel the other note. But this does not always happen, but if a note is truncated it will always be truncated. Moving its position within the clip may bring it back. Its odd alright.
Other timing issues are that the midi-CV convertor is detecting legato notes even when the individual notes are distinct.
Another was recording a series of short notes into a clip. Then moving that clip to another place in the track. Recording another set of notes in its now empty place... but the note off's from the previous recording appeared to be still in place, thus truncating the new notes.
I am sad to say I'm getting rather cheesed off with it really.
-
- KVRAF
- 6740 posts since 25 Mar, 2002 from sheffield, england
What synth is this happening with? Hardware or software? Could you post an archive that demonstrates the problem?Synthbuilder wrote:I have notes being cut-off and some notes are ignored. This seems to happen if the receiving synth is monophonic and a new note overlaps with an older one. The note-off from the previous note seems to cancel the other note. But this does not always happen, but if a note is truncated it will always be truncated. Moving its position within the clip may bring it back. Its odd alright.
Other timing issues are that the midi-CV convertor is detecting legato notes even when the individual notes are distinct.
-
- KVRist
- 412 posts since 17 Mar, 2005 from Cumbria, England
I have found the problem with the truncation of notes. It took me a while... but I now fully understand why some notes get cut off and other's remain. This also goes to explain some of the wierd timing issues I have been having.
CC#123 All notes off.
My controller keyboard, a D50, sends all notes off whenever the last key is released. Tracktion records all notes off as a separate event! This is the first time I have come across this one.
So when you edit the notes, the all notes off controller remains in the clip at the same place the D50 put them there. Even if you quantise, move notes, or edit lengths.
Fortunately, one can delete CC#123 data easily enough with the delete controller button.
Now if tracktion could ignore CC#123 while recording that would be great.
But I still have midi timing errors though.
P4 3GHz Carillon AC-1 with USB midisport 4x4, Radeon 64MB graphics card.
I can run Sonar fine.
CC#123 All notes off.
My controller keyboard, a D50, sends all notes off whenever the last key is released. Tracktion records all notes off as a separate event! This is the first time I have come across this one.
So when you edit the notes, the all notes off controller remains in the clip at the same place the D50 put them there. Even if you quantise, move notes, or edit lengths.
Fortunately, one can delete CC#123 data easily enough with the delete controller button.
Now if tracktion could ignore CC#123 while recording that would be great.
But I still have midi timing errors though.
P4 3GHz Carillon AC-1 with USB midisport 4x4, Radeon 64MB graphics card.
I can run Sonar fine.
-
- KVRist
- 60 posts since 4 May, 2003 from wellington.newzealand
Just a mouse...if I unplug that i sure won't have any timing problem, I won't be able to do a goddam thingplatinumears wrote:husker: do you have many other USB devices running? Maybe try unplugging all but the 4x4 and see if the timing gets any better..?
If i only send midi-clock out 1 port, then my midi timing is OK. I only really use midi-out for driving the clock in the Electribes and arpeg in the A6, not note sequencing, so not sure if there is another note timing problem there also?
I will try another USB port to see if it makes any difference. Midi yoke is quite happy to send midi-clock out all 4 ports without any nastiness though...
-
- KVRist
- 60 posts since 4 May, 2003 from wellington.newzealand
You could try routing via Midi-ox and mid-yoke and filter the CC#123 in there. And if you are outputing to more than 1 port on the 4x4, then outputing to midi-yoke in Traction and then routing to the 4x4 might help your timing problems too. Not ideal, but migth be a viable workaround until they sort T2 out.Synthbuilder wrote:
Now if tracktion could ignore CC#123 while recording that would be great.
Interested to hear if this helps...