No products in the cart.
If you take a look at the attached screen shots, I loaded a midi file from the Ballads collection. Based on the chord progression, it is clear that this is the key of G major, but the software identifies it as C major. As seen in the second screen shot, I switched the key signature to G major it changes the chords to a progression that is actually D major. Can anyone explain to me whats going on there? Thank you!!
Hi,
please start with updating to the latest version.
John Rammelt - Toontrack
Technical Advisor
We have a small bug in the software that makes ezkeys recognise the wrong key of “80s POP 66 BPM” (and possibly some other songs from the Ballads pack). Until we release a fix for this you can:
– Set the Key of EZkeys to G major (in the display, left of Signature and Tempo).
– Go into the menu, select “Browser/Use Original Key Signature”
– Drag the MIDI files from “80s POP 66 BPM” to the track and the key should be correct.
When you are done, go back to the menu and deselect “Browser/Use Original Key Signature”. If not, the MIDI you drag down to the song track won’t be transposed to the key of the song.
We are sorry for the inconvenience and we are working to fix the bug!
Henrik Ekblom - User Experience Designer
Toontrack
I have this problem with the Jazz selections is this a known problem that is being addressed?
Holy Cow, this is still not fixed after all these months! Come on guys, you are driving me crazy. (By the way, the new Manager looks to be working nicely). So now lets get the key signature working.
Dear ToonTrack Support,
I have just purchased the MIDI Packs (Song Writing & Roots Music), the issue is still existed. Please help to fix.
Thank you very much.
Cheers,
Minh
Sigh.. this is still a problem. Seems no matter what midi is dragged in it stays in C Major , if you then switch it it just goes to the major key no matter what you choose. For instance
set the song to C Major, drag in a midi, then set the key to Em and the chord just change to the chord in G major… YES I get it…the chords are actually the same but the tonal center is NOT. If I am in Em then my tonal center is Em and not the G major.
This stays the same no matter what the key you change it to. This is BEYOND frustrating. As this is the very functionality you buy Ez keys or Bass for.
Unfortunately as much as I really love Ez its is becoming less and less useful as I go along.
The circle of fifths is used for tonal centers. Key signatures are for transposition to the correct scale. Using a relative minor to denote a key signature is more of a convenience. Scalar wise, the progression in G would still be considered correct regardless of whether you said it was in G or Em. Moving it within the circle of fifths, however, will change its tonal qualities.
jord
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.
If you look in the shot containing the C major signature, you will notice that there is a D7 chord. This is known as a borrowed chord. Changing the key signature to G major changed the borrowed chord to A7. A9 is an embellishment. So far, that is pretty much correct behavior. The other part with the C# is based on the F# in the other progression. That also looks correct. Transposing the key signatures it’s not going to remove the accidentals intentionally placed in a progression. That in itself would be a bug.
jord
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.
I think we agree that the very fact that your key signature is C makes D7 a borrowed chord, regardless of the progression on the timeline. There is no F# in C. It is outside of the key signature.
if your midi is already on the timeline, then changing the key will also change those borrowed chords. That itself is not a bug.
as far as dragging and dropping midi onto the timeline, I haven’t been able to re-create this type of issue of the wrong chords in a progression. That is even with the “keep midi“ option checked and unchecked. Perhaps list some steps to re-create this. The only way I can remotely come close to this is by using my own progression and replace browser midi with “ keep midi” option unchecked.
jord
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.
Okay, that sounds like a bug with that particular Midi pack. Unfortunately for me, Ballads is one I don’t have so I can’t recreate it faithfully. All of the other packs that I have are working for me in that respect (Horror is in question, but that one is freaky unto itself – I might make a ringtone with it to let me know when my in-laws call). I wouldn’t be surprised if it was metadata related.
jord
1
Thanked by: michaelfjacobThanks for all the time you invested. Certainly appreciated. Hopefully you’re right. A correction to metadata should be really easy to fix.
No products in the cart.