chord parser errors

[cstivers]

Prior to Encore 5.0.2 (Windows) I used chord parsing to help me fly through creation of rhythm parts. This new version is giving me fits in that it parses incorrectly over half the time. For example:
keyboard: A-C-E
Parser: A+7(#9)

keyboard: C-E-G
parser: Fmaj9

keyboard: D-F-A
parser: Gm6/Bb

Does anyone else have this problem? Is there a fix?

/chris/

[polarbreeze]

Chris, for me chord parsing on 5.0.2 still works the same way it did on previous versions, ie with the inputs you describe I get Am, C and Dm respectively. I'm not sure what to suggest - did anything change on your system? Did you try going back to the previous version as a test?

[cstivers]

Yes, previous version still works well. Something I notice about 5.0.2 is that it's not quite as good at recognizing midi input, i.e. I have to enter data more slowly. Again, this is is not the case in my earlier version.

[polarbreeze]

Yes, previous version still works well. Something I notice about 5.0.2 is that it's not quite as good at recognizing midi input, i.e. I have to enter data more slowly. Again, this is is not the case in my earlier version.

Do you get exactly the same results every time (ie the chord parser interpretations you posted earlier) or does it vary?

[polarbreeze]

Chris, what is your MIDI setup? What make/model of keyboard; what make/model of MIDI adapter?

[cstivers]

I'm using an Alesis keyboard running through a USB-connected Midisport 2x2 (M-Audio).

[Denkster]

USB ports are notoriously sloppy with timing.
Especially when your computer is busy and receives input from other sources, timing of USB input is unreliable, it gets the leftovers.
Switch off as much programs as you can, especially networking (MSN, chat programs, e-mail, browser, torrent client, programs checking for updates).

Eveline