It's never been perfect, responding a little late, hanging onto notes and including in the next chord, but this plug in seems to be currently screwed. I haven't used for a while, but today I tried on something and as I had been using EZKeys, I wasn't sure if it was interfering somehow, sending some data. SO I cleared and deleted all the other tracks and it was still mis-behaving. So I closed Sonar and started a project with just one instrument track, and just added the midi plug in. I entered all the chords on the PRV and turned off and disconnected external midi controllers. But the results remain the same, the plug in is un-usable
 
6 bars
G,C,C,D,Am,Am
 
Bar one, G, says C Maj Root (wrong)
https://fbcdn-sphotos-g-a...39ee8dbf580fe731829c26

 
Bar two, C, says C Maj Root (right)
https://fbcdn-sphotos-e-a.akamaihd.net/hphotos-ak-xpa1/v/t1.0-9/10407923_10152455402696034_5440160781703599976_n.jpg?oh=c354a815dbb79aee63514ecd1eaa99b5&oe=5520030A&__gda__=1427917084_907f07ab2816e4c137585f112983b721

 
Bar three, C, says D Maj Root (wrong)
https://fbcdn-sphotos-c-a.akamaihd.net/hphotos-ak-xaf1/v/t1.0-9/1508128_10152455403006034_5940932436700992214_n.jpg?oh=2ac9dc6b9e5483c770021a7477a0e2eb&oe=550FCE95&__gda__=1427297058_681d3c6f6557a9702479f2f72c4607a5

Bar four D, Says A min Root (wrong)
https://scontent-b-sjc.xx.fbcdn.net/hphotos-xfp1/v/t1.0-9/10347631_10152455403961034_4347852638375491197_n.jpg?oh=521e2a9613d0dfc0c83e5228111198fa&oe=551B9D4B

 
Bar five Am, Says A min Root (right)
https://fbcdn-sphotos-f-a.akamaihd.net/hphotos-ak-xpf1/v/t1.0-9/1690395_10152455404191034_5620587159925170280_n.jpg?oh=d22f2c9499ecbb43fd27b656f82a51d2&oe=55164F5B&__gda__=1427565924_48c1fca521a543b627130448bd051f76

 
Bar six Am, Says A min Root (Right)
https://scontent-b-sjc.xx.fbcdn.net/hphotos-xpf1/v/t1.0-9/10501973_10152455404341034_2575708810740128210_n.jpg?oh=843ec86a4e837852ba4a1d27afb70e89&oe=5519B152

 
I increased the analysis window to 20 tics, with the same results, and same with 50 ticks. Also pausing and clearing between bars.
 
Anyone else the same?
 
 

Can one of the forum hosts move this to Problem Reports. Maybe I should have posted there.

We'll leave it here because the Problem Report forum is for confirmed bugs.  We don't know that about your problem at the moment.

Hi Scoot, I have not used this in ages either, but a quick glance and what you are showing seems like it has a look-ahead feature to it. It shows accurately the next bar as if it is intending to have the transport running while using it. In the few times I have used it, the transport was running, and I never noticed it like this (it seems accurate that way because it updates the chord as the transport gets to the MIDI ON events).
 
However, I have no idea how this is scripted, so hopefully a baker can chime in for you.

The chord analyzer works with the data in the buffer defined in Preferences > MIDI > Playback and Recording "Prepare Using nnn Millisecond Buffers." The larger the playback buffer the further in the future the analyzer sees. Reducing the buffer will get better analyzer results but may negatively affects performance.

If it is using a look ahead function as seems to be a pattern, then looking a whole bar ahead in plain wrong, especially with something that is analyzing a chrord, as this will typically be used in a working out a chord sequence, which would be required for looking at the bar you are working in. sometimes it triggered the second bar on hitting play. You set a number of ticks  that a chord should be held for, indicating how responsive it should be. Surely it's more capable than this. You're going to get bars with 2 or more chords in them, sometimes, just for a beat
 
Cheers scook, for noting that the playback buffers may need changing, but I think I shouldn't need to for a Midi plug in that has been with Sonar pre X range. This shouldn't be a system hog. but fast and reactive
 
This is a basic tool, and I its not really usable in it's current state.
 
I don't want our midi tools forgotten and overlooked. At one point it was all about midi, this should be bread and butter stuff.
 
What's the procedure on getting an official in.

The lookahead is a function of the playback buffer, I decreased the buffer and the analyzer worked reasonably well. The official report form is here http://www.cakewalk.com/Support/Contact/Problem-Report

I much prefer that guitar plugin for this stuff. It's a soft synth called AAS Strum Acoustics. The biggest drawback is that when you stop playback, it hides the last chord. I find this tool works much better for calling out changes.

Cheers scook, yeah gwitz, I have the fuss AAS collection, but not really paid much interest in the strum duo, but I mainly want it for keys, so this plug should, and once did do the job. I'll have a check of it at some point, but soo many things to be checking out at the moment. 

midiChordAnalyzer is my go to because...
The font size is larger,
It works well
and it's free
You can find it at KVR... http://www.kvraudio.com/product/midichordanalyzer-by-insert-piz-here