Hi,
Thanks for your suggestion. :) Yes, it is a good idea: it
would be far more interesting to train notes for a specific
melody rather than a random sequence.
There are two points, though, which make it a bit
complicated to make it really usable. They are both
connected to the fact, that for now KLearnNotes2 shows only
one note at a time. :/
Sorry for the length of this reply - you can skip to the
conclusions in the end. ;)
-------- unimportant explanation --------
First of all: midi files can be quite complicated. There can
be full (harmonic) chords. The only way we could implement
it now would be to make them a melodic arpeggio (whenever
there is a chord, train each note one-by-one, separately) or
check the file and use it for tests only if it is simple
enough.
Even more important point is about how one reads music. It's
a bit like reading text: you don't read it letter-by-letter:
whole connections of letters come naturally. Similarly in
music: when you know the scale key (say, C Major) and known
previous note - you expect next one in a natural way. Also,
even if you don't know about keys, you read that "next note
is two semitones higher than the previous one", rather than
"the next note is G, oh, it is at the third fret" (although
the latter is important too). In other words: training the
recognition of a chord is a bit different than recognition
of each of the chords notes separately.
Anyway: yes, we can implement soon reading a simple midi
file and training it note-by-note. This would mean, that you
could train then a simple (one-voice, or one-line, no
chords) melody. For a more complicated file you would then
train all needed notes, but would probably need a printed
score (e.g. use rosegarden) too, to make any sense of it
(i.e. which of the notes should be played together and which
in a sequence).
In future, when KLearnNotes2 will be able to show multiple
notes, two kinds of tests may appear:
1. you SEE the full chord and have to play/name all the
notes of it, one by one (and they get highlighted one by
one, until the full chord was played)
2. you see full sequence of notes - all grayed except from
the middle one, which is a question; then the score would
scroll left, and next note would become a question.
Only then reading a midi file will be really beneficial.
----- end of unimportant explanation ----
I hope it makes sense? Unfortunately it seems like quite a
lot of work within KLearnNotes2, quite independent of
reading a midi file itself. Yes, it's worth it, but I really
don't know when to expect it. Sorry. :(
For now, yes, we'll try to implement the simple version of
reading a midi file in a reasonable future. :)
Anyway, thanks again for your suggestion.
Regards
~Marek
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=879528
Hi,
Thanks for your suggestion. :) Yes, it is a good idea: it
would be far more interesting to train notes for a specific
melody rather than a random sequence.
There are two points, though, which make it a bit
complicated to make it really usable. They are both
connected to the fact, that for now KLearnNotes2 shows only
one note at a time. :/
Sorry for the length of this reply - you can skip to the
conclusions in the end. ;)
-------- unimportant explanation --------
First of all: midi files can be quite complicated. There can
be full (harmonic) chords. The only way we could implement
it now would be to make them a melodic arpeggio (whenever
there is a chord, train each note one-by-one, separately) or
check the file and use it for tests only if it is simple
enough.
Even more important point is about how one reads music. It's
a bit like reading text: you don't read it letter-by-letter:
whole connections of letters come naturally. Similarly in
music: when you know the scale key (say, C Major) and known
previous note - you expect next one in a natural way. Also,
even if you don't know about keys, you read that "next note
is two semitones higher than the previous one", rather than
"the next note is G, oh, it is at the third fret" (although
the latter is important too). In other words: training the
recognition of a chord is a bit different than recognition
of each of the chords notes separately.
Anyway: yes, we can implement soon reading a simple midi
file and training it note-by-note. This would mean, that you
could train then a simple (one-voice, or one-line, no
chords) melody. For a more complicated file you would then
train all needed notes, but would probably need a printed
score (e.g. use rosegarden) too, to make any sense of it
(i.e. which of the notes should be played together and which
in a sequence).
In future, when KLearnNotes2 will be able to show multiple
notes, two kinds of tests may appear:
1. you SEE the full chord and have to play/name all the
notes of it, one by one (and they get highlighted one by
one, until the full chord was played)
2. you see full sequence of notes - all grayed except from
the middle one, which is a question; then the score would
scroll left, and next note would become a question.
Only then reading a midi file will be really beneficial.
----- end of unimportant explanation ----
I hope it makes sense? Unfortunately it seems like quite a
lot of work within KLearnNotes2, quite independent of
reading a midi file itself. Yes, it's worth it, but I really
don't know when to expect it. Sorry. :(
For now, yes, we'll try to implement the simple version of
reading a midi file in a reasonable future. :)
Anyway, thanks again for your suggestion.
Regards
~Marek