-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status always note_on, switched velocity with note #42
Comments
I think what you are seeing may be "running status": http://www.somascape.org/midi/tech/spec.html#runstat Please run the script midiin_callback.py from the examples, select the MIDI port, your keyboard is attached to and play some notes. Then post the output here. Also, without seeing the code you are using, I can't reproduce your problems, so please post a minimal example that demonstrates the problem, if you can. |
Thank you for the response! I use expanded version of midiin_callback.py in my code, some results from running given file (constantly key 96 is pressed): [MidiLink Mini:MidiLink Mini MIDI 1 20:0] 1555538410.931765 [144, 96, 0] |
So, you are saying the output above is from the unchanged Also, which OS are you on and which API backend are you using (JACK, ALSA, CoreMidi, WindowsMM)? |
This is output from unchanged midiin_callback file. The easiest way to reproduce this on my device is constantly pressing very fast one key for some time. I use ALSA and work on Raspbian GNU/Linux 8.0 (jessie). |
Do you have another MIDI interface to test with? Is this the MIDI interface you are using? https://www.thomann.de/de/miditech_midilink_mini.htm The buyers' comments don't exactly fill me with confidence in the reliability of this interface. |
Yes, this is exactly the interface I am using and unfortunately the only I can test with for now. |
I'll try to test this on a Rasberry Pi (also with Raspbian 8) tomorrow. |
Thank you very much for help. |
Sorry, I have not been able to reproduce this. I tested this on my own Raspberry Pi, which also has Raspbian 8 installed, with the Python 3.4 version installed from the distribution packages. I created a virtualenv and installed I suspect your MIDI interface is to blame. Can you test it with
|
I attach the output from |
Yes, it seems either your keyboards (unlikely) or the MIDI interface are sending garbage. These cheap cable-integrated MIDI interfaces can be hit-and-miss and often, even if they work for "nomal" MIDI events (notes, controllers, etc.), they mess up System Exclusive messages. If you're looking not to spend too much, I'd try to buy a used, older USB audio interface with MIDI ports (and some standard MIDI cables), even if you don't plan on using the audio capabilities, you can still use its MIDI interface. I'm closing this issue now. If you have new data that suggest that |
Hello,
I have encountered two problems during working with library. I work with 2 pianos - Yamaha piaggero np-11 and Casio CTK-700 and midi/usb cable.
First, on both pianos all midi events (note_on and note_off) come with status as note_on.
Second problem appears only with working on piano with changeable velocity - sometimes fields with velocity and note are switched for few seconds.
I work on Rasbperry Pi 3 (Raspbian 8.0) and Python 3.4.2.
Thank you very much for all help and very nice implementation.
The text was updated successfully, but these errors were encountered: