2

[michaelfjacob]

Thanks for all the time you invested.  Certainly appreciated.  Hopefully you’re right.  A correction to metadata should be really easy to fix.

[michaelfjacob]

Absolutely. I think the disconnect is the midi is not yet on the timeline. The steps to reproduce this are easy.

1. Open EZ Keys.  The default key is C.

2. Drag the midi from the Ballads pack as shown in the first screen shot into the timeline and I end up with a chord progression that is clearly in the key of G.  The first 4 bars being G D Em C.  Bars 5-8 also match this pattern, but I am only writing the first 4 bars for the sake of brevity.

3. Remove the midi file from the timeline.

4. Change the key to G.

5. Drag the exact same midi file into the timeline.  The first 4 bars are now D A Bm G.  Clearly the key of D.

Why did it give me a chord progression in G when the selected key is C?  Similarly, using the exact same source midi, why did if give me a chord progression clearly in D, when the key was set to G?  This is definitely a bug.

[michaelfjacob]

I’m sorry, but I must respectfully disagree.  If you look at the chord progression, it is clearly in G.  G add9 is the 1 chord, D add 9 is the 5 chord, Em7 is the 6 chord, C is the 4 chord, therefore D7 is the dominant 5 chord. All of those are diatonically correct for G major, so how is the D7 a borrowed chord?  If the software would have selected to proper key based on the chords in the progression, it would have selected G, not C. Therefore I would not have needed to change the key that triggered the incorrect chord transposition.  The D7 would be borrowed in C, but C is the wrong key and should never have been selected by the software in the first place.

[michaelfjacob]

Sure, key signatures make sure the notes are correct.  I would not have reported this bug if I got the correct chords for G major even though my piece was really in E minor.  If you take a look at my original screen shots, I changed the key from C to G because that is what would work for my chord progression.  EZ Keys made chord substitutions for the key change that included A add9 / C#.  I’m sorry, but there is no C# in G major.  Since the notes are the same, this also applies to E minor (Aeolian).  This is what the bug report is all about and unfortunately, it still exists after all this time.  Very disappointing considering how much time has passed and how much money I have invested in the EZ tools.  Perhaps a simple solution would be allowing us to change keys without automatically transposing the chord progression.

[michaelfjacob]

Apologies for the multiple edits.  I thought I found it, but I really didn’t.  After pulling in an audio track and playing with both the velocity and sustain automation tools, I thought it was having the desired effect, but I forgot to take the audio file out of the mix and that is where the effect was coming from.  I still haven’t been able to achieve this effect on a pure midi note within EZ Bass. It appears so far the only thing I found that works is using the audio volume automation in my DAW.

• The post has been modified 2 times, last modified 4 years, 5 months ago by michaelfjacob.

[michaelfjacob]

Since I originally posted this question I decided all I really needed was the guitar work in guitar pro, but there is something that might work for you. EZ Drummer has an option in settings to enable midi out, but it isn’t available in stand alone mode.  I think this is what is meant by needing a host, so if you run EZ drummer in a DAW you should be able to enable the midi out option and send that data to guitar pro.  I never actually tried it, but it sounds like it could work.

[Author]

Replies