Tracktion 2 sending random All Notes Off (midiox data)

[hexman]

OK. Tracktion 2 is definitely sending out random ALL NOTES OFF. This is from MidiOx connected to Traction midi out. I **disconnected** my SY77 midi in, made a midi loop in tracktion. Note: I actually entered the note **IN** tracktion midi edit, NOT recorded from my synth.

I play, and this is what I get. The All notes off occur at the end of the loop marker- ok no problem I guess. The problem is below where it spits out the CC in the middle of the loop. This makes it sound like the note gets hit again. This sometimes takes awhile. This is actuall the end of 3-4 minutes.

I have not tried listening to a VST to see if it will do because then I cant capture the midi data (I have to listen).

originally posted here:
http://www.kvraudio.com/forum/viewtopic.php?t=87087

Help???? BTW- yes my T2 is registered

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00164C47 1 -- 90 3F 60 1 Eb 4 Note On
00165409 1 -- 90 3B 60 1 B 3 Note On
0016541A 1 -- 80 3F 00 1 Eb 4 Note Off
00165BDC 1 -- 80 3B 00 1 B 3 Note Off
00165BDC 1 -- 90 3F 60 1 Eb 4 Note On
001663AA 1 -- 80 3F 00 1 Eb 4 Note Off
001663AA 1 -- 90 3A 60 1 Bb 3 Note On
00166B7B 1 -- 80 3A 00 1 Bb 3 Note Off
00166B7B 1 -- 90 3F 60 1 Eb 4 Note On
00167348 1 -- 80 3F 00 1 Eb 4 Note Off
00167348 1 -- 90 3A 60 1 Bb 3 Note On
00167B08 1 -- 80 3A 00 1 Bb 3 Note Off
00167B08 1 -- B0 7B 00 1 --- CC: All Notes Off

00167B1B 1 -- 90 3F 60 1 Eb 4 Note On
001682DD 1 -- 90 3B 60 1 B 3 Note On
001682E8 1 -- 80 3F 00 1 Eb 4 Note Off
00168AA8 1 -- 80 3B 00 1 B 3 Note Off
00168AAA 1 -- 90 3F 60 1 Eb 4 Note On
0016927A 1 -- 80 3F 00 1 Eb 4 Note Off
0016927C 1 -- 90 3A 60 1 Bb 3 Note On
00169A47 1 -- 80 3A 00 1 Bb 3 Note Off
00169A4F 1 -- 90 3F 60 1 Eb 4 Note On
0016A21C 1 -- 80 3F 00 1 Eb 4 Note Off
0016A21C 1 -- 90 3A 60 1 Bb 3 Note On
0016A9DD 1 -- 80 3A 00 1 Bb 3 Note Off
0016A9DD 1 -- B0 7B 00 1 --- CC: All Notes Off

0016A9ED 1 -- 90 3F 60 1 Eb 4 Note On <<-- ok
0016B1AE 1 -- 90 3B 60 1 B 3 Note On <<-- ok
0016B1B9 1 -- 80 3F 00 1 Eb 4 Note Off <<-- ok
0016B97B 1 -- 80 3B 00 1 B 3 Note Off <<-- ok
0016B97B 1 -- 90 3F 60 1 Eb 4 Note On <<-- ok
0016BD2A 1 -- 80 3F 00 1 Eb 4 Note Off <<-- ok
0016BD2A 1 -- B0 7B 00 1 --- CC: All Notes Off <<----ERROR
0016BD2E 1 -- 90 3A 60 1 Bb 3 Note On
0016BD32 1 -- 80 3A 00 1 Bb 3 Note Off
0016BD32 1 -- B0 7B 00 1 --- CC: All Notes Off <<----ERROR
0016BD32 1 -- 90 3F 60 1 Eb 4 Note On
0016C14F 1 -- 80 3F 00 1 Eb 4 Note Off
0016C14F 1 -- 90 3A 60 1 Bb 3 Note On
0016C91C 1 -- 80 3A 00 1 Bb 3 Note Off
0016C91E 1 -- 90 3F 60 1 Eb 4 Note On
0016D0ED 1 -- 80 3F 00 1 Eb 4 Note Off
0016D0ED 1 -- 90 3A 60 1 Bb 3 Note On
0016D8AB 1 -- 80 3A 00 1 Bb 3 Note Off
0016D8AC 1 -- B0 7B 00 1 --- CC: All Notes Off

0016D8B9 1 -- 90 3F 60 1 Eb 4 Note On
0016E07C 1 -- 90 3B 60 1 B 3 Note On
0016E08E 1 -- 80 3F 00 1 Eb 4 Note Off
0016E29D 1 -- 80 3B 00 1 B 3 Note Off
0016E29D 1 -- B0 7B 00 1 --- CC: All Notes Off

[hexman]

Sorry for the data dumps, but its even stranger...

This is "easier" to see.
The notes are one bar long, C-D-E-F-G-A-B.
I entered the notes in Tracktion and then loop (push play).
The data is MidiYoked to MidiOx.
The "error" took about 3 minutes to occur.

Look "bad loop" order when it errors: its C-D-E(CC off)-A(CC off)-E-F-G-A-B.
Like its looking ahead or gets out of timing sync or??
Compare with the "good" loop C-D-E-F-G-A-B.

Wierd or what ?



"Bad" Loop
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
000606DA 1 -- 90 3C 20 1 C 4 Note On
00060EAB 1 -- 80 3C 00 1 C 4 Note Off
00060EAB 1 -- 90 3E 20 1 D 4 Note On
00061677 1 -- 80 3E 00 1 D 4 Note Off
00061677 1 -- 90 40 20 1 E 4 Note On
00061BA5 1 -- 80 40 00 1 E 4 Note Off
00061BA5 1 -- B0 7B 00 1 --- CC: All Notes Off
00061BA9 1 -- 90 45 20 1 A 4 Note On
00061BAE 1 -- 80 45 00 1 A 4 Note Off
00061BAE 1 -- B0 7B 00 1 --- CC: All Notes Off
00061BAE 1 -- 90 40 20 1 E 4 Note On
00061E4C 1 -- 80 40 00 1 E 4 Note Off
00061E4C 1 -- 90 41 20 1 F 4 Note On
00062619 1 -- 80 41 00 1 F 4 Note Off
00062619 1 -- 90 43 20 1 G 4 Note On
00062DED 1 -- 80 43 00 1 G 4 Note Off
00062DED 1 -- 90 45 20 1 A 4 Note On
000635B8 1 -- 80 45 00 1 A 4 Note Off
000635B8 1 -- 90 47 20 1 B 4 Note On
00063D79 1 -- 80 47 00 1 B 4 Note Off
00063D79 1 -- B0 7B 00 1 --- CC: All Notes Off


"Good" Loop
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00063D8B 1 -- 90 3C 20 1 C 4 Note On
00064558 1 -- 80 3C 00 1 C 4 Note Off
00064558 1 -- 90 3E 20 1 D 4 Note On
00064D2B 1 -- 80 3E 00 1 D 4 Note Off
00064D2C 1 -- 90 40 20 1 E 4 Note On
000654F7 1 -- 80 40 00 1 E 4 Note Off
000654F7 1 -- 90 41 20 1 F 4 Note On
00065CCA 1 -- 80 41 00 1 F 4 Note Off
00065CCB 1 -- 90 43 20 1 G 4 Note On
00066497 1 -- 80 43 00 1 G 4 Note Off
00066497 1 -- 90 45 20 1 A 4 Note On
00066C69 1 -- 80 45 00 1 A 4 Note Off
00066C69 1 -- 90 47 20 1 B 4 Note On
00067424 1 -- 80 47 00 1 B 4 Note Off
00067424 1 -- B0 7B 00 1 --- CC: All Notes Off

[valley]

good stuff!

[DHR53]

No, bad stuff...

[mandolarian]

Yeah, but it's good that the bad is well documented and repeatable....but I don't care thanks to Wusik mania no midi ever leaves my desktop. I am working on a 20+ minute piece just now with Wuiskal synths and have not experienced the random note off behaviour. Thankfully.

[rich_h]

Nearly exactly what I was getting.

If it's important to Jules (driver issues possibly) my MIDI i/o is part of the Emu 0404 card.

[hexman]

SInce Im routing with MidiYoke to my MidiOx, I would think actual Midi hardware and driver are not in the loop? (and hence not a factor) Am I thinking wrong?

[rich_h]

No, you're probably right. I just thought I'd mention it in case there was some sort of interaction that I couldn't think of! Working in software myself, I'm very aware than totally unexpected things can bugger you up sometimes!

[valley]

Is this happening only in loop mode, or if you copy paste the same clip over a few minutes and watch it, does the same thing happen then?

Probably irrelevant, but what is your ASIO buffer latency currently?

What MIDI hardware are you using in addition to MIDI Yoke, and is MTC or MIDI clock being sent to any MIDI outs whilst you were testing?

[Beno]

Hey Hexman, got your email from tech support too. One question, has anyof this been duplicated with midi to a VSTi inside of tracktion? I see you notice it happening when it leaves tracktion (either by a midi interface or a loop back driver) and I just want to see if anyone has had it happen with midi that doesn't leave tracktion. I read through the previous threads and didn't see anyone mention this but I wanted to double check.
Thanks,
Ben

[hexman]

PostPosted: Thu May 12, 2005 10:28 am
Is this happening only in loop mode, or if you copy paste the same clip over a few minutes and watch it, does the same thing happen then?

Pretty sure thats what I was doing when I first noticed it (ie not looping, just playing along with a track I had recorded then cut-n-pasted.) Will check tonight for sure.

Probably irrelevant, but what is your ASIO buffer latency currently?

M-Audio Delta-410 11ms

What MIDI hardware are you using in addition to MIDI Yoke, and is MTC or MIDI clock being sent to any MIDI outs whilst you were testing?

Onboard motherboard midi out. Havent tried the SBLive MidiOut. Yeah, I know but it has been flawless in my other apps (Sonar). Also, I belive by routing to midiyoke I effectively bypass the midiout on the other devices. No MTC or MidiClock.

[hexman]

Hey Hexman, got your email from tech support too. One question, has anyof this been duplicated with midi to a VSTi inside of tracktion? I see you notice it happening when it leaves tracktion (either by a midi interface or a loop back driver) and I just want to see if anyone has had it happen with midi that doesn't leave tracktion. I read through the previous threads and didn't see anyone mention this but I wanted to double check.
Thanks,
Ben

I did try a long (4-5 min) of the exact same loop (the C-D-E-F-G-A-B) with a VSTi (mda Piano) and it did NOT do it.

I have noticed that sometimes it takes quite awhile to show up so this may not be conclusive (but sitting there for 5 min listening to scales is cruel).

[hexman]

Beno
Please note it doesnt seem to be just a CC All Notes Off.

Its playing "E", then a CC Off goes out in the middle of the note. Then it jumps (out of time order) to "A", then CC Off goes out and it goes back to the "E"


TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
000606DA 1 -- 90 3C 20 1 C 4 Note On
00060EAB 1 -- 80 3C 00 1 C 4 Note Off
00060EAB 1 -- 90 3E 20 1 D 4 Note On
00061677 1 -- 80 3E 00 1 D 4 Note Off
00061677 1 -- 90 40 20 1 E 4 Note On
00061BA5 1 -- 80 40 00 1 E 4 Note Off
00061BA5 1 -- B0 7B 00 1 --- CC: All Notes Off
00061BA9 1 -- 90 45 20 1 A 4 Note On
00061BAE 1 -- 80 45 00 1 A 4 Note Off
00061BAE 1 -- B0 7B 00 1 --- CC: All Notes Off
00061BAE 1 -- 90 40 20 1 E 4 Note On
00061E4C 1 -- 80 40 00 1 E 4 Note Off
00061E4C 1 -- 90 41 20 1 F 4 Note On
00062619 1 -- 80 41 00 1 F 4 Note Off
00062619 1 -- 90 43 20 1 G 4 Note On
00062DED 1 -- 80 43 00 1 G 4 Note Off
00062DED 1 -- 90 45 20 1 A 4 Note On
000635B8 1 -- 80 45 00 1 A 4 Note Off
000635B8 1 -- 90 47 20 1 B 4 Note On
00063D79 1 -- 80 47 00 1 B 4 Note Off
00063D79 1 -- B0 7B 00 1 --- CC: All Notes Off

[rich_h]

I've not had it on any internal VSTi, and it occurs on external MIDI both with looping on and off.

[Stuttaton]

I have this problem with Tracktion 1. I really expected that it had been fixed in T2. Actually, I was going to upgrade, just to get rid of it.

/Jorgen