5 Sep
2008
5 Sep
'08
7:45 p.m.
This is a maintenance release, trying to solve the performance problems
reported by some people for the first public release announced last week.
Thank you very much for your comments!
Virtual MIDI Piano Keyboard is a MIDI event generator and receiver. It doesn't
produce any sound by itself, but can be used to drive a MIDI synthesizer
(either hardware or software, internal or external). You can use the
computer's keyboard to play MIDI notes, and also the mouse. You can use the
Virtual MIDI Piano Keyboard to display the played MIDI notes from another
instrument or MIDI file player.
Changelog:
2008-09-05 0.1.1
* Bugfix: crash at startup when no MIDI input devices were available.
* Changed default key bindings map: the new default one is equal to
Impulse Tracker and other programs. More keys are mapped now.
* Several optimizations in keyboard handling code and display updates.
2008-08-31 0.1.0
* First public release
Copyright (C) 2008, Pedro Lopez-Cabanillas
License: GPL v3
Web site:
http://vmpk.sourceforge.net
http://sourceforge.net/projects/vmpk
Sources:
http://downloads.sourceforge.net/vmpk/vmpk-0.1.1.tar.bz2
http://downloads.sourceforge.net/vmpk/vmpk-0.1.1.tar.gz
Windows setup package:
http://downloads.sourceforge.net/vmpk/vmpk-0.1.1-setup.exe
openSUSE RPM packages:
http://software.opensuse.org/search?baseproject=ALL&p=1&q=vmpk
Regards,
Pedro
6 Sep
6 Sep
2:13 a.m.
Am Freitag, den 05.09.2008, 23:45 +0200 schrieb Pedro Lopez-Cabanillas:
This is a maintenance release, trying to solve the
performance problems
reported by some people for the first public release announced last week.
Thank you very much for your comments!
Hello
Nice, now vmpk is fast enough. :)
One more sugestion I have, could you make it posible that vampk dont
loose the mouse event when I move the mouse out of the widget with the
button pressed ?
regards hermann
10 Sep
10 Sep
7:29 p.m.
Hi,
On Saturday, September 6, 2008, hermann meyer wrote:
Nice, now vmpk is fast enough. :)
One more sugestion I have, could you make it posible that vampk dont
loose the mouse event when I move the mouse out of the widget with the
button pressed ?
I think that you are asking for a feature usually named "mouse grabbing". It
is very common, and not difficult to implement. For instance, when you click
on a knob, the value is changed when you keep the mouse button pressed and
move the cursor up/down or left/right even outside the widget. On the other
hand, I don't see the advantage of mouse grabbing for the piano keys. Can you
please explain an use case where this feature is needed ?
Regards,
Pedro
11 Sep
11 Sep
2:11 p.m.
Am Mittwoch, den 10.09.2008, 23:29 +0200 schrieb Pedro Lopez-Cabanillas:
Hi,
On Saturday, September 6, 2008, hermann meyer wrote:
Yes, I like to play with one hand the keybord and the other with the
mouse. Most I simply pressed the mouse and move it up and down to play
singel notes to the chords I play with the left hand.
regards hermann
Nice, now vmpk is fast enough. :)
One more sugestion I have, could you make it posible that vampk dont
loose the mouse event when I move the mouse out of the widget with the
button pressed ?
I think that you are asking for a feature usually named "mouse grabbing". It
is very common, and not difficult to implement. For instance, when you click
on a knob, the value is changed when you keep the mouse button pressed and
move the cursor up/down or left/right even outside the widget. On the other
hand, I don't see the advantage of mouse grabbing for the piano keys. Can you
please explain an use case where this feature is needed ?
Regards,
Pedro
12 Sep
12 Sep
9:19 a.m.
Am Mittwoch, den 10.09.2008, 23:29 +0200 schrieb Pedro Lopez-Cabanillas:
Hi,
On Saturday, September 6, 2008, hermann meyer wrote:
To make it more clear, I mean the way vkeybd make it. Dont only grab the
mouse, I mean play the note when I enter the widget and stop to play
when I leave the widget, play when I enter, stop when . . . . . So it
isn't mouse grabbing at all.
hermann
Nice, now vmpk is fast enough. :)
One more sugestion I have, could you make it posible that vampk dont
loose the mouse event when I move the mouse out of the widget with the
button pressed ?
I think that you are asking for a feature usually named "mouse grabbing". It
is very common, and not difficult to implement. For instance, when you click
on a knob, the value is changed when you keep the mouse button pressed and
move the cursor up/down or left/right even outside the widget. On the other
hand, I don't see the advantage of mouse grabbing for the piano keys. Can you
please explain an use case where this feature is needed ?
Regards,
Pedro
2:42 p.m.
On Friday, September 12, 2008, hermann meyer wrote:
Am Mittwoch, den 10.09.2008, 23:29 +0200 schrieb Pedro
Lopez-Cabanillas:
Ah, it has more sense now for me. Yes, I also like the way vkeybd handles the
mouse. It is much nicer than a simple mouse grabbing, and I would like to
implement this behavior in vmpk.
I've opened a feature request (tracker item) in SF for this issue:
http://sourceforge.net/tracker/index.php?func=detail&aid=2107732&gr…
Please feel free to add comments, or add new feature requests if you wish. And
thanks again for reviewing the program and for your feedback.
Regards,
Pedro
Hi,
On Saturday, September 6, 2008, hermann meyer wrote:
To make it more clear, I mean the way vkeybd make it. Dont only grab the
mouse, I mean play the note when I enter the widget and stop to play
when I leave the widget, play when I enter, stop when . . . . . So it
isn't mouse grabbing at all. Nice, now vmpk is fast enough. :)
One more sugestion I have, could you make it posible that vampk dont
loose the mouse event when I move the mouse out of the widget with the
button pressed ?
I think that you are asking for a feature usually named "mouse grabbing".
It is very common, and not difficult to implement. For instance, when you
click on a knob, the value is changed when you keep the mouse button
pressed and move the cursor up/down or left/right even outside the
widget. On the other hand, I don't see the advantage of mouse grabbing
for the piano keys. Can you please explain an use case where this feature
is needed ?
Regards,
Pedro 
10 Sep
10 Sep
12:21 p.m.
Pedro Lopez-Cabanillas wrote:
This is a maintenance release, trying to solve the
performance problems
reported by some people for the first public release announced last week.
Thank you very much for your comments!
Mmmm, I like it! Just one request:
Can you make the MIDI channel count go from 1 to 16 and not from zero to
15? I think it is more standard in MIDI speak, so that the drum channel
is at channel 10, and not 9..
Ciao!
--
salvuz
POST FATA RESVRGO
Linux registered user #291700 | machine #174619
get counted on ---> http://counter.li.org/ <---
7:34 p.m.
Hi Salvatore,
On Wednesday, September 10, 2008, Salvatore Di Pietro wrote:
Mmmm, I like it! Just one request:
Can you make the MIDI channel count go from 1 to 16 and not from zero to
15? I think it is more standard in MIDI speak, so that the drum channel
is at channel 10, and not 9..
Ciao!
Many thanks for reviewing the program, and for your kind message.
Of course you are right. The MIDI channel numbers should start from 1, not 0.
This is a bug in VMPK, and will be fixed for the next release.
Regards,
Pedro
5950
days inactive
5957
days old
linux-audio-user@lists.linuxaudio.org
7 comments
3 participants
participants (3)
-
hermann meyer -
Pedro Lopez-Cabanillas -
Salvatore Di Pietro