ronpietrantoni wrote:into Windows Task Manager and setting the affinity for the MTD process to just one processor seems to have eliminated my MIDI issues!
That is very interesting! Amazing!
Would you please enlighten me some more:
I'm not gonna lie to you, Marge: it was mostly dumb luck! The Yahoo thread (http://tech.groups.yahoo.com/group/gvox-users/
) said something about changing the Process priority in Task Manager to High. Pursuing that led me to see what the rest of the drop-down menu had to offer; next below Set Priority is Set Affinity. Once I figured out what it was referring to, I thought, "Nah, that can't be it - someone else would have figured it out by now." <bg>
Are you saying:
- there is a difference in MIDI-handling, between MusicTime Deluxe (MTD) and MasterTracksPro (MTP),
- they apparently approach the (dual-core) processors for MIDI in different way or method
- the way MusicTime Deluxe (MTD) does approach (dual-core) processors via Windows7 drivers is not good.
If I understood you correctly, yours are very important observations!
1. This is what I've been trying to tell John Miller. <smile> He suggested that the trouble was my M-Audio MIDISport 2x2 not having a W7 compliant driver. So I purchased a Cakewalk UM-3G - no change in MTD; MTP still worked.
2. It occurred to me that it might have been that MTP somehow installed with single-core affinity, but I just fired up my copy and checked: It has both my CPUs checked. I read somewhere (possibly another section of this forum; or maybe Matt e-mailed me about it) that 6.8.4 had a resolution issue - if I run the PPQ higher than 96 there are all sorts of nasty timing discrepancies. However, since I've created a starting template with that resolution, I've been able to use MTP just fine in a W7 environment: meter changes, accelerandos, ritards, the works (well, for the pop/rock/Gospel stuff I produce). Funny thing is, it was working before
I got the beta of the M-Audio W7 driver!
3. In the sense that I could only get 3-4 notes on a page with step-entering before MTD would stop receiving MIDI intel until I shut down and restarted the program? Yeah, I think 'not good' qualifies. And it's not just W7. Earlier in this thread, I think it was, someone else mentioned hitting one note and getting a splattered chord - that was happening to me on an XPsp3 box which just so happened to also be a dual-core processor. Changed the affinity there and bam! the problem stopped. So setting the affinity fixed MIDI problems both on a 32-bit XP box and a 64-bit W7.
I think this goes back to the origin of this thread: the chord parsing problem and the 'glob of notes' problem are, in fact, the same symptom. You play something on a MIDI keyboard and MTD/Encore in a multi-core environment mistranslates it somehow.