WARNING!
Maybe this is a known issue?
Some may consider this a funny story but it's not funny for me.
Vestige has worked immediately for every VST that I have tried (yes it wont record them in LMMS for me but that is a non issue). I can load as many as I like at once and use them all at the same time with no issues, or so I thought. Only one problem, as incredible as it sounds unbeknown to me the keys were mapped to the wrong pitch! different to every other DAW, different to a properly tuned Piano.
I have been learning to play my midi keyboard by ear since buying it in November, using LMMS and Vestige VSTs.
I didn't occur to me to test the key pitch against a properly tuned piano or other DAW, who would think that everything would work as expected only for the key pitch to be out?!!!
Now I am going to have to unlearn everything I have played. reteach the part of my brain that tells my fingers to naturally fall on the wrong keys. So much for the fluent solos I can now perform, in LMMS only!!!
I wish LMMS had not worked at all for me now. I have learned to play the keyboards with all the wrong finger positions!
I am using an M Audio keystation 49 (recognised by LMMS software), the keys are mapped correctly in other DAW programs.
It seems incredible to me that no warning is issued on the download page. Surely this has been noticed before?
Have I missed something? I know you can change the pitch (and save settings) for each VST but LMMS does not remember this change (it remembers the pitch figures but goes back to the wrong mappings with new figures!)
I recommend anyone test their VST keyboard key mappings against other DAW programs or known good Piano and if you do not remember pitch for that long check against a known good source such as this video for grade one piano on youtube:
http://www.youtube.com/watch?v=g09JZIZ_SPg
If they can straighten this out and get LMMS to record the VSTs then this could be brilliant but currently I am left feeling like a bit of a wally.
For anyone casually flicking through this, this is nothing to do with the settings for transposing octaves.
Maybe this is a known issue?
Some may consider this a funny story but it's not funny for me.
Vestige has worked immediately for every VST that I have tried (yes it wont record them in LMMS for me but that is a non issue). I can load as many as I like at once and use them all at the same time with no issues, or so I thought. Only one problem, as incredible as it sounds unbeknown to me the keys were mapped to the wrong pitch! different to every other DAW, different to a properly tuned Piano.
I have been learning to play my midi keyboard by ear since buying it in November, using LMMS and Vestige VSTs.
I didn't occur to me to test the key pitch against a properly tuned piano or other DAW, who would think that everything would work as expected only for the key pitch to be out?!!!
Now I am going to have to unlearn everything I have played. reteach the part of my brain that tells my fingers to naturally fall on the wrong keys. So much for the fluent solos I can now perform, in LMMS only!!!
I wish LMMS had not worked at all for me now. I have learned to play the keyboards with all the wrong finger positions!
I am using an M Audio keystation 49 (recognised by LMMS software), the keys are mapped correctly in other DAW programs.
It seems incredible to me that no warning is issued on the download page. Surely this has been noticed before?
Have I missed something? I know you can change the pitch (and save settings) for each VST but LMMS does not remember this change (it remembers the pitch figures but goes back to the wrong mappings with new figures!)
I recommend anyone test their VST keyboard key mappings against other DAW programs or known good Piano and if you do not remember pitch for that long check against a known good source such as this video for grade one piano on youtube:
http://www.youtube.com/watch?v=g09JZIZ_SPg
If they can straighten this out and get LMMS to record the VSTs then this could be brilliant but currently I am left feeling like a bit of a wally.
For anyone casually flicking through this, this is nothing to do with the settings for transposing octaves.