I've just been having a look at the MIDI data stream being sent to an external port. For the vast majority of the time the All Notes Off and Reset Controllers events do not occur, other than at the start of a loop.
I'd also been experiencing problems that when the display was being updated the timing of the MIDI output when screwy. I've recently adjusted bus latency timings so I thought I'd see if that had changed anything by scrolling the display when playing external MIDI. It hadn't cured it, but I still had MIDI Ox open, and it appears that when Tracktion's display is being updated, MIDI output stops *entirely* and when it resumes our old friends All Notes Off and Reset Controllers are sent. Note that it is *only* Tracktion's display that has this effect, no other program affects the MIDI timing.
Given the obvious interaction between MIDI and the display here, could this also be related to the problems "dee ess pee" has been having?
I hope this information is of some use.
That MIDI bug that Hexman and I have been having, new info
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
It does sound a little like UI updates are causing some machines to temporarily become *very* busy, doesn't it.rich_h wrote: Given the obvious interaction between MIDI and the display here, could this also be related to the problems "dee ess pee" has been having?
I suspect that the period is too short to be caught by the reolsution of a CPU usage meter?
Question: is MIDI stable if you hide Tracktion's display[1]?
[1] anyone trying this, be sure that the "stop all playback when minimized" option from the "options" menu is disbaled.
Someone shot the food. Remember: don't shoot food!
-
- KVRian
- Topic Starter
- 779 posts since 3 Apr, 2003 from UK
Interesting - I did get a situation this afternoon where Tracktion hanged whereby the CPU meter was red-lined and Tracktion just locked (the rest of the PC was still responsive.)valley wrote:It does sound a little like UI updates are causing some machines to temporarily become *very* busy, doesn't it.
I suspect that the period is too short to be caught by the reolsution of a CPU usage meter?
It seems to be stable all the while there is no or very little display update going on.valley wrote:Question: is MIDI stable if you hide Tracktion's display[1]?
-
- KVRist
- 161 posts since 30 May, 2004
rich_h
Nice work!
I can duplicate that. 
I put midiox in the background running. (I slightly minimize Tracktion so I can see the midiox readout)
Play a midi clip (it does NOT have to be looped) and resize the tracktion window (lower right corner). Usually when I release the mouse button I get the CC off message to show up!
Interestingly it doesnt error **while** I resize and pretty agressively move the mouse. Its when I let up on the mouse button that the error appears.
Ive also seen this if I mess with the inputs. When I release them it shows up.
Hopefully this is a clue
Nice work!
I can duplicate that. I put midiox in the background running. (I slightly minimize Tracktion so I can see the midiox readout)
Play a midi clip (it does NOT have to be looped) and resize the tracktion window (lower right corner). Usually when I release the mouse button I get the CC off message to show up!
Interestingly it doesnt error **while** I resize and pretty agressively move the mouse. Its when I let up on the mouse button that the error appears.
Ive also seen this if I mess with the inputs. When I release them it shows up.
Hopefully this is a clue
-
- KVRian
- Topic Starter
- 779 posts since 3 Apr, 2003 from UK
A thought occurred to me earlier. We had a similar type of problem at work a while back - certain threads weren't behaving as expected, either they would take over the PC until done or they would run with very low priority. It turned out that the variable setting the thread priority hadn't been initialised so was setting the thread to a random priority. Just thought it might be something for Jules to look at, no wish to teach anyone to suck eggs 
-
- KVRer
- 8 posts since 22 Jan, 2005 from Seattle|Washington|USA
I believe I have encountered a related midi bug.
I use an old Roland D-50 as my controller and connect it's Midi Out to an E-mu0404 card. In recording a badly played passage last night I found two "All Notes Off" cont. controller events. These events where cutting of notes during playback (obviously). The VST instrument was the Free Alpha synth packaged with T2. The events happened over a period of about 15 bars at 70 BPM.
I have had similar cut off notes with SampleTank as the VST as well.
Any ideas out there how to fix this?
Thanks.
Tracktion 2.0.1.2
Win XPSP2
E-mu0404
I use an old Roland D-50 as my controller and connect it's Midi Out to an E-mu0404 card. In recording a badly played passage last night I found two "All Notes Off" cont. controller events. These events where cutting of notes during playback (obviously). The VST instrument was the Free Alpha synth packaged with T2. The events happened over a period of about 15 bars at 70 BPM.
I have had similar cut off notes with SampleTank as the VST as well.
Any ideas out there how to fix this?
Thanks.
Tracktion 2.0.1.2
Win XPSP2
E-mu0404
-
- KVRAF
- 3441 posts since 15 Mar, 2003
I get those "all note off, all controllers off" points in my midi tracks from time to time. I don't use any external controllers. I use my computer keyboard with Trollo to live input midi.
On playback the sound will cut off and if I look at the midi there will be both a single point of all notes off and a single point of all controllers off.
I am using T1.
On playback the sound will cut off and if I look at the midi there will be both a single point of all notes off and a single point of all controllers off.
I am using T1.
-
- KVRian
- Topic Starter
- 779 posts since 3 Apr, 2003 from UK
I have also encountered spurious controller data in MIDI input streams. Since enabling Real Time Priority mode I haven't experienced this (or at least I haven't noticed)
Obviously RTP mode isn't the ideal solution for everyone as it breaks some plug-ins.
Obviously RTP mode isn't the ideal solution for everyone as it breaks some plug-ins.
-
- KVRist
- 413 posts since 17 Mar, 2005 from Cumbria, England
[quote="JohnEh"] I use an old Roland D-50 as my controller...
Don't forget that the D50 sends all notes off everytime you take your hands off the keyboard. Its Roland's literal understanding of the 'all notes off' command in the midi spec.
Unfortunately, T2 records these events as a separate cc to the note offs sent by the same controller. So if you move the notes around a bit in the edit screen the 'allnotesoff' will remain in place. This causes all sorts of playing errors.
So you either have to filter out 'all notes off' or remove them the moment you have recorded them in the midi editor. Neither way is very nice.
Don't forget that the D50 sends all notes off everytime you take your hands off the keyboard. Its Roland's literal understanding of the 'all notes off' command in the midi spec.
Unfortunately, T2 records these events as a separate cc to the note offs sent by the same controller. So if you move the notes around a bit in the edit screen the 'allnotesoff' will remain in place. This causes all sorts of playing errors.
So you either have to filter out 'all notes off' or remove them the moment you have recorded them in the midi editor. Neither way is very nice.
-
- KVRist
- 413 posts since 17 Mar, 2005 from Cumbria, England
Try this one:
http://www.niallmoody.com/ndcplugs/ndcmidi.htm
Use the cc range filter. Set it up so that takes out all CC information for the all notes off command. I think its CC#123.
Works a treat for me.
http://www.niallmoody.com/ndcplugs/ndcmidi.htm
Use the cc range filter. Set it up so that takes out all CC information for the all notes off command. I think its CC#123.
Works a treat for me.