Hi,
Being one of them who doesn't have a MIDI keyboard, I am using my QWERTY keyboard to play MIDI notes. But the problem here is, every time I make any changes to the plug-in, I have to select the virtual MIDI input and then click on a key on the keyboard on the screen by mouse and then I will be able to play on my QWERTY keyboard (I know I can lock the virtual MIDI input screen, but I won't be able to use the other settings until I unlock it), and also, I can't go above or below the octave range.
Like in Bitwig Studio is, please provide an option of Caps Lock On which turns complete QWERTY keyboard into MIDI keyboard, so that I can not only play without clicking on the virtual keyboard and so on, but also I can shift octaves above or below (being Z & X an octave below & above). All the keyboard shortcuts like "/", "D" etc. would work while Caps Lock Off.
This function would be very useful to those who doesn't have a MIDI keyboard. Also there would be no need of creating a virtual MIDI input in settings if this feature gets implemented.
Feature Request: Caps Lock On to turn QWERTY keyboard into MIDI keyboard, like in Bitwig Studio
-
- KVRAF
- 2206 posts since 16 Apr, 2004 from between my ears
Yes, please! This would make my laptop so much more useable for ideas when i am without my controller.
-
- KVRian
- 772 posts since 1 Oct, 2019
This would be useful.
I don't record any instruments live, I construct my music.
Song Contest: Possibilities for new themes
Song Contest: Possibilities for new themes
-
- KVRian
- 767 posts since 25 Jul, 2010 from Northern Ireland
+1 from me, I find this intuitive in Bitwig 
-
- KVRist
- 367 posts since 26 Feb, 2017 from Lituania,Vilnius
+1 from me and as i have a midi controller bat is required input updates,
if i edit vsti again you need to edit the midi input to make the sound,
plus if collective i choose preset - when I reopen the project I don't see what the choice was
and again from the beginning - it is suffering.
if i edit vsti again you need to edit the midi input to make the sound,
plus if collective i choose preset - when I reopen the project I don't see what the choice was
and again from the beginning - it is suffering.
Orion, Bitwig, Tracktion, Mixbus 
Win 10, intel i7, ram 20 steinberg UR22mkII
Win 10, intel i7, ram 20 steinberg UR22mkII
-
- KVRAF
- 1790 posts since 30 Dec, 2012
Would you expect a new MIDI input device such as "Keyboard Input" to receive the MIDI?
Then you would assign this to tracks rather than a standard MIDI input?
Then you would assign this to tracks rather than a standard MIDI input?
-
- KVRist
- Topic Starter
- 55 posts since 26 Jan, 2020
Ya this could be fine. Even if I'm on a plugin, keyboard should focus on MIDI. If I want to work with keyboard shortcuts, I'd simply switch Caps Lock Off.dRowAudio wrote: Mon Mar 30, 2020 9:42 am Would you expect a new MIDI input device such as "Keyboard Input" to receive the MIDI?
Then you would assign this to tracks rather than a standard MIDI input?
Thanks!
-
Peter Widdicombe Peter Widdicombe https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=336849
- KVRian
- 1208 posts since 29 Aug, 2014
One other function I'd really like to see is the ability to move outside the one-octave range, when trying things out away from a full MIDI keyboard. One QUICK suggestion (??) I'd like to see is an "auto-octave" selection. When hitting a note on the virtual keyboard displayed, could the octave for Querty be set to the octave that key was pressed in? I know it's possible to stick a MIDI-modifier in front of the .VST, but it would be much more logical/user friendly to have the one-octave selection at least remain in the octave that was last used - particularly has you have to use that displayed keyboard to trigger the first note anyway ?
Waveform 13; Win10 desktop/8 Gig; Win11 Laptop; MPK261; VFX+disfunctional ESQ-1
-
- KVRist
- 401 posts since 10 Dec, 2002
1. Yes, the idea with Caps Lock is simply great.
2. Also the octave switch sounds perfect. (Arrow keys maybe, when Caps Lock is on?)
I'll add two more
3. Two octaves at the same time (we have 4 rows on the keyboard typically, so it can control 2 octaves).
4. Support for non-english keyboards (mine goes QWERTZ). Waveform doesn't recognize the key number (or position), but strictly THE letter.
It might sound silly to use a computer keyboard, but Waveform is simply made for "composing on the road" And I mean it, it's a perfect tool for sketching music wherever you are.
2. Also the octave switch sounds perfect. (Arrow keys maybe, when Caps Lock is on?)
I'll add two more
3. Two octaves at the same time (we have 4 rows on the keyboard typically, so it can control 2 octaves).
4. Support for non-english keyboards (mine goes QWERTZ). Waveform doesn't recognize the key number (or position), but strictly THE letter.
It might sound silly to use a computer keyboard, but Waveform is simply made for "composing on the road"
And I mean it, it's a perfect tool for sketching music wherever you are.Waveform 12 Pro, Cubase Pro 13, Windows 11, i7-13700H
-
- KVRian
- 1300 posts since 3 May, 2005 from Victoria, BC
This is a good idea. W12 will be getting some MIDI improvements, so I'll roll this into that. I've done a bit of research and know how to do it for macOS and Windows. Still need to look into Linux.
-
- KVRian
- 1300 posts since 3 May, 2005 from Victoria, BC
More like 7 or 8 months.