Riki Slugic
2016-10-31 20:02:47 UTC
Hello again,
After a few days of enthusiastic remembering about QT and C++ (some
years of java and php made me forget many things), reading, studying,
the criticisms provided (I really appreciate the prompt and precious
reply to posts and questions), the tutorials regarding midi, github
etc. etc. I am daring to submit a small change in the arpeggio files.
As I am digging into midi and the lmms code, slowly (very)
understanding some of the features which led to such an elegant and
functional implementation, I can just admire the work that has been
done!
The arpeggio section caught my imagination, I'm using it a lot and as
it is it already produces marvellous effects: it's potential goes far
beyond simple scale repetition!
I currently use the diff I'm proposing here to set up rhythms in
conjunction with the excellent tempo syncing.
Up to now I only added the possibility to use -1 as a semitone,
substituting it with a boundary constant.
But this is just temporary and here follows the next step:
I've just forked the lmms repo (I am thankful for the clear
explanations) and will try to do the following (won't be easy, I'm not
a pro, know little c and am working only in my spare time):
- the arpeggio data at present work through an array of hardcoded char
semitones.
I'll try to change that into an array of structs (key, volume,
panning, silenced, active), eliminating the boundary program logic,
too.
the data should reside into text files, maybe json formatted, and in
time there should be an editor for it to be easily edited.
I have a question: all I'm doing is by inspecting and trying to
understand the code. Am I so dumb to have missed any lmms specific
coding notes/tutorials/manuals (all I found so far was work in
progress)?
Hoping not to be too naive and dreamy
I'm sending all my best regards and appreciation
R.
After a few days of enthusiastic remembering about QT and C++ (some
years of java and php made me forget many things), reading, studying,
the criticisms provided (I really appreciate the prompt and precious
reply to posts and questions), the tutorials regarding midi, github
etc. etc. I am daring to submit a small change in the arpeggio files.
As I am digging into midi and the lmms code, slowly (very)
understanding some of the features which led to such an elegant and
functional implementation, I can just admire the work that has been
done!
The arpeggio section caught my imagination, I'm using it a lot and as
it is it already produces marvellous effects: it's potential goes far
beyond simple scale repetition!
I currently use the diff I'm proposing here to set up rhythms in
conjunction with the excellent tempo syncing.
Up to now I only added the possibility to use -1 as a semitone,
substituting it with a boundary constant.
But this is just temporary and here follows the next step:
I've just forked the lmms repo (I am thankful for the clear
explanations) and will try to do the following (won't be easy, I'm not
a pro, know little c and am working only in my spare time):
- the arpeggio data at present work through an array of hardcoded char
semitones.
I'll try to change that into an array of structs (key, volume,
panning, silenced, active), eliminating the boundary program logic,
too.
the data should reside into text files, maybe json formatted, and in
time there should be an editor for it to be easily edited.
I have a question: all I'm doing is by inspecting and trying to
understand the code. Am I so dumb to have missed any lmms specific
coding notes/tutorials/manuals (all I found so far was work in
progress)?
Hoping not to be too naive and dreamy
I'm sending all my best regards and appreciation
R.