Sustain pedal issue with undesired repeated notes (m-audio keystation 88es + qjackctl + qsynth)
6 Jun
2010
6 Jun
'10
3:08 p.m.
Hi,
I have a problem I can't face alone on the digital piano I made on
Debian Lenny with qsynth (v0.2.5-2.2), qjackctl (v0.3.2-1) and an
m-audio keystation 88es keyboard.
When I play the piano, some notes will repeat themselves after a few
seconds only if I keep the sustain pedal pressed, just like a delay
effect would do.
I reported that only 4 notes are concerned for the moment, they have
different repeat delays:
G : ~7.5 sec (G4)
G# : ~7 sec (G#4)
A : ~6.5 sec (A4)
A# : ~6 sec (A#4)
Note that the notes above, relatively to the middle C of a piano
keyboard called C3, goes from G4 to A#4.
Could this be due to an hardware issue in the m-audio keyboard?
Thanks a lot for any idea on how to track down and correct this (if
possible).
Nicolas.
6 Jun
6 Jun
4:15 p.m.
Nicolas BERCHER wrote:
I have a problem I can't face alone on the digital piano I made on
Debian Lenny with qsynth (v0.2.5-2.2), qjackctl (v0.3.2-1) and an
m-audio keystation 88es keyboard.
When I play the piano, some notes will repeat themselves after a few
seconds only if I keep the sustain pedal pressed, just like a delay
effect would do.
I reported that only 4 notes are concerned for the moment, they have
different repeat delays:
G : ~7.5 sec (G4)
G# : ~7 sec (G#4)
A : ~6.5 sec (A4)
A# : ~6 sec (A#4)
Note that the notes above, relatively to the middle C of a piano
keyboard called C3, goes from G4 to A#4.
Could this be due to an hardware issue in the m-audio keyboard?
Thanks a lot for any idea on how to track down and correct this (if
possible).
Try putting a MIDI monitor program between the keyboard's MIDI output
and QSynth's input port in QJackCtl. Look for the repeats there.
If you have KDE: http://kmidimon.sourceforge.net/
For Gnome/GTK: http://home.gna.org/gmidimonitor/
Best,
dp
11:46 p.m.
New subject: Sustain pedal issue with undesired repeated notes (m-audio keystation 88es + qjackctl + qsynth)
On Sun, Jun 06, 2010 at 10:15:03AM -0400, Dave Phillips wrote:
Nicolas BERCHER wrote:
For none of the above (my preference): aseqdump :-)
-ken
I have a problem I can't face alone on the digital piano I made on
Debian Lenny with qsynth (v0.2.5-2.2), qjackctl (v0.3.2-1) and an
m-audio keystation 88es keyboard.
When I play the piano, some notes will repeat themselves after a few
seconds only if I keep the sustain pedal pressed, just like a delay
effect would do.
I reported that only 4 notes are concerned for the moment, they have
different repeat delays:
G : ~7.5 sec (G4)
G# : ~7 sec (G#4)
A : ~6.5 sec (A4)
A# : ~6 sec (A#4)
Note that the notes above, relatively to the middle C of a piano
keyboard called C3, goes from G4 to A#4.
Could this be due to an hardware issue in the m-audio keyboard?
Thanks a lot for any idea on how to track down and correct this (if
possible).
Try putting a MIDI monitor program between the keyboard's MIDI output
and QSynth's input port in QJackCtl. Look for the repeats there.
If you have KDE: http://kmidimon.sourceforge.net/
For Gnome/GTK: http://home.gna.org/gmidimonitor/
8 Jun
8 Jun
10:57 a.m.
New subject: Sustain pedal issue with undesired repeated notes (m-audio keystation 88es + qjackctl + qsynth)
On 06.06.2010 23:44, Ken Restivo wrote:
On Sun, Jun 06, 2010 at 10:15:03AM -0400, Dave
Phillips wrote:
Thank you for answers.
Yes, I also prefer command line tools! ;-)
So, I checked what's going on:
$ aseqdump --list
Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0
20:0 SB Live! Value [CT4870] EMU10K1 MPU-401 (UART)
24:0 USB Keystation 88es USB Keystation 88es MIDI 1
$ aseqdump -p 24:0
Waiting for data. Press Ctrl+C to end.
Source_ Event_________________ Ch _Data__
24:0 Control change 0 64 127
24:0 Note on 0 82 82
24:0 Note on 0 82 0
24:0 Control change 0 64 0
The above sequence dumped by aseqdump shows only one note event (lines
2+3: press+release) but I heard a delayed note as mentioned in my first
mail.
The keyboard seems to do things right, so I think it comes from qsynth.
Isn't that strange? I mean many people around there use qsynth, am I the
only one to have this kind of problem?
Once again, I appreciate any advice!
Thanks,
Nicolas.
Nicolas BERCHER wrote:
For none of the above (my preference): aseqdump :-)
-ken
I have a problem I can't face alone on the
digital piano I made on
Debian Lenny with qsynth (v0.2.5-2.2), qjackctl (v0.3.2-1) and an
m-audio keystation 88es keyboard.
When I play the piano, some notes will repeat themselves after a few
seconds only if I keep the sustain pedal pressed, just like a delay
effect would do.
I reported that only 4 notes are concerned for the moment, they have
different repeat delays:
G : ~7.5 sec (G4)
G# : ~7 sec (G#4)
A : ~6.5 sec (A4)
A# : ~6 sec (A#4)
Note that the notes above, relatively to the middle C of a piano
keyboard called C3, goes from G4 to A#4.
Could this be due to an hardware issue in the m-audio keyboard?
Thanks a lot for any idea on how to track down and correct this (if
possible).
Try putting a MIDI monitor program between the keyboard's MIDI output
and QSynth's input port in QJackCtl. Look for the repeats there.
If you have KDE: http://kmidimon.sourceforge.net/
For Gnome/GTK: http://home.gna.org/gmidimonitor/
11:12 a.m.
New subject: Sustain pedal issue with undesired repeated notes (m-audio keystation 88es + qjackctl + qsynth)
Nicolas BERCHER wrote:
On 06.06.2010 23:44, Ken Restivo wrote:
Hmm, have never had QSynth repeat a note unless I actually repeated a
note. Interesting. I don't know the innards of MIDI events, so don't
know what the various numbers above mean.
WAGging around: Is your USB MIDI connection sharing a USB bus with other
USB devices? Maybe some other USB device is doing something weird with
the bus and something isn't getting handled right?
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
On Sun, Jun 06, 2010 at 10:15:03AM -0400, Dave
Phillips wrote:
Thank you for answers.
Yes, I also prefer command line tools! ;-)
So, I checked what's going on:
$ aseqdump --list
Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0
20:0 SB Live! Value [CT4870] EMU10K1 MPU-401 (UART)
24:0 USB Keystation 88es USB Keystation 88es MIDI 1
$ aseqdump -p 24:0
Waiting for data. Press Ctrl+C to end.
Source_ Event_________________ Ch _Data__
24:0 Control change 0 64 127
24:0 Note on 0 82 82
24:0 Note on 0 82 0
24:0 Control change 0 64 0
The above sequence dumped by aseqdump shows only one note event (lines
2+3: press+release) but I heard a delayed note as mentioned in my first
mail.
The keyboard seems to do things right, so I think it comes from qsynth.
Isn't that strange? I mean many people around there use qsynth, am I the
only one to have this kind of problem? Nicolas BERCHER wrote:
For none of the above (my preference): aseqdump :-)
-ken
I have a problem I can't face alone on the
digital piano I made on
Debian Lenny with qsynth (v0.2.5-2.2), qjackctl (v0.3.2-1) and an
m-audio keystation 88es keyboard.
When I play the piano, some notes will repeat themselves after a few
seconds only if I keep the sustain pedal pressed, just like a delay
effect would do.
I reported that only 4 notes are concerned for the moment, they have
different repeat delays:
G : ~7.5 sec (G4)
G# : ~7 sec (G#4)
A : ~6.5 sec (A4)
A# : ~6 sec (A#4)
Note that the notes above, relatively to the middle C of a piano
keyboard called C3, goes from G4 to A#4.
Could this be due to an hardware issue in the m-audio keyboard?
Thanks a lot for any idea on how to track down and correct this (if
possible).
Try putting a MIDI monitor program between the keyboard's MIDI output
and QSynth's input port in QJackCtl. Look for the repeats there.
If you have KDE: http://kmidimon.sourceforge.net/
For Gnome/GTK: http://home.gna.org/gmidimonitor/
11:55 a.m.
New subject: Sustain pedal issue with undesired repeated notes (m-audio keystation 88es + qjackctl + qsynth)
On 08.06.2010 11:12, david wrote:
Nicolas BERCHER wrote:
# lsusb
Bus 002 Device 005: ID 0763:0192 Midiman M-Audio Keystation 88es
Bus 002 Device 002: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 002 Device 003: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0bda:0103 Realtek Semiconductor Corp. USB 2.0
Card Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I guess you're right: I have 2 USB buses (one onboard (2nd) and one in
front (1st), inside a memory cards reader) and the midi keyboard shares
the 2nd bus with mouse and azerty keyboard...
I noticed there's no way to plug an usb device on the 1st bus: it only
cares about memory cards.
So I unplugged both mouse & azerty keyboard but it doesn't change anything.
Do you think this problem could come from an hardware failure into my SB
Live sound card?
Nicolas.
On 06.06.2010 23:44, Ken Restivo wrote:
Hmm, have never had QSynth repeat a note unless I actually repeated a
note. Interesting. I don't know the innards of MIDI events, so don't
know what the various numbers above mean.
WAGging around: Is your USB MIDI connection sharing a USB bus with
other USB devices? Maybe some other USB device is doing something
weird with the bus and something isn't getting handled right?
On Sun, Jun 06, 2010 at 10:15:03AM -0400, Dave
Phillips wrote:
Thank you for answers.
Yes, I also prefer command line tools! ;-)
So, I checked what's going on:
$ aseqdump --list
Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0
20:0 SB Live! Value [CT4870] EMU10K1 MPU-401 (UART)
24:0 USB Keystation 88es USB Keystation 88es MIDI 1
$ aseqdump -p 24:0
Waiting for data. Press Ctrl+C to end.
Source_ Event_________________ Ch _Data__
24:0 Control change 0 64 127
24:0 Note on 0 82 82
24:0 Note on 0 82 0
24:0 Control change 0 64 0
The above sequence dumped by aseqdump shows only one note event
(lines 2+3: press+release) but I heard a delayed note as mentioned in
my first mail.
The keyboard seems to do things right, so I think it comes from qsynth.
Isn't that strange? I mean many people around there use qsynth, am I
the only one to have this kind of problem? Nicolas BERCHER wrote:
> I have a problem I can't face alone on the digital piano I made on
> Debian Lenny with qsynth (v0.2.5-2.2), qjackctl (v0.3.2-1) and an
> m-audio keystation 88es keyboard.
>
> When I play the piano, some notes will repeat themselves after a few
> seconds only if I keep the sustain pedal pressed, just like a delay
> effect would do.
> I reported that only 4 notes are concerned for the moment, they have
> different repeat delays:
> G : ~7.5 sec (G4)
> G# : ~7 sec (G#4)
> A : ~6.5 sec (A4)
> A# : ~6 sec (A#4)
> Note that the notes above, relatively to the middle C of a piano
> keyboard called C3, goes from G4 to A#4.
>
> Could this be due to an hardware issue in the m-audio keyboard?
>
> Thanks a lot for any idea on how to track down and correct this (if
> possible).
Try putting a MIDI monitor program between the keyboard's MIDI output
and QSynth's input port in QJackCtl. Look for the repeats there.
If you have KDE: http://kmidimon.sourceforge.net/
For Gnome/GTK: http://home.gna.org/gmidimonitor/
For none of the above (my preference): aseqdump :-)
-ken
12:13 p.m.
New subject: Sustain pedal issue with undesired repeated notes (m-audio keystation 88es + qjackctl + qsynth)
On Tue, 08 Jun 2010 11:55:01 +0200, Nicolas BERCHER wrote
On 08.06.2010 11:12, david wrote:
> WAGging around: Is your USB MIDI connection sharing a USB bus with
> other USB devices? Maybe some other USB device is doing something
> weird with the bus and something isn't getting handled right?
No, please. This is highly unlikely. Iff something on the bus would
spoof the device ID of the Midi interface things would go crazzy long
before a note on event would be recognized ...
# lsusb
Bus 002 Device 005: ID 0763:0192 Midiman M-Audio Keystation 88es
Bus 002 Device 002: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 002 Device 003: ID 0461:4d15 Primax Electronics, Ltd Dell
Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1
root hub Bus 001 Device 004: ID 0bda:0103 Realtek Semiconductor
Corp. USB 2.0 Card Reader Bus 001 Device 001: ID 1d6b:0002 Linux
Foundation 2.0 root hub
I guess you're right: I have 2 USB buses (one onboard (2nd) and one
in front (1st), inside a memory cards reader) and the midi keyboard
shares the 2nd bus with mouse and azerty keyboard...
Yes, but that's absolutely normal. USB is a _bus_ after all (i.e. many
devices can talk over it).
I noticed
there's no way to plug an usb device on the 1st bus: it only cares
about memory cards. So I unplugged both mouse & azerty keyboard but
it doesn't change anything.
As to be expected :-)
Do you think this problem could come from an hardware
failure into
my SB Live sound card?
How should that happen? If no midi note event shows up in the dump
the problem must be in qsynth (or the sound font it uses). What sound
found do you use, BTW?
Cheers, Ralf Mattes
Nicolas.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
--
R. Mattes -- Systemeinheitsstreichler
Hochschule fuer Musik Freiburg
rm(a)inm.mh-freiburg.de
12:57 p.m.
New subject: [Bulk] Re: Sustain pedal issue with undesired repeated notes (m-audio keystation 88es + qjackctl + qsynth)
On 08.06.2010 12:13, R. Mattes wrote:
Argh, I didn't thought it could come from the sound fount I use!
(Indeed, the hardware failure I suspected was "a kind of memory
corruption (fixed pattern interacting only with the 4 notes mentioned?)
leading to a wrong pointer which induces to loop through the wave
table... thus resulting in delayed notes... ok, it might sound crazy but
I thought about it!)
I have multiple sound fonts in qsynth settings (setup/soundfont tab):
1) /usr/share/sounds/sf2/FluidR3_GS.sf2 (Debian package fluid-soundfont-gs)
2) /usr/share/sounds/sf2/FluidR3_GM.sf2 (Debian package fluid-soundfont-gm)
3) AI-APiano02trans.sf2 (from www.sf2-files.com)
4) WST25FStein_00Sep22.SF2 (from www.pianosounds.com)
(... I have to admit that I don't master yet the way I choose the one I
want to play with and configure the presets things the way I want!)
Nicolas.
On Tue, 08 Jun 2010 11:55:01 +0200, Nicolas BERCHER
wrote
I agree and I thought that the midi keyboard driver would go crazy if
things goes wrong on the usb bus (which is upstream relative to the midi
driver and then the midi events...). But I still tested it!
On 08.06.2010 11:12, david wrote:
> WAGging around: Is your USB MIDI connection sharing a USB bus with
> other USB devices? Maybe some other USB device is doing something
> weird with the bus and something isn't getting handled right?
>
No, please. This is highly unlikely. Iff something on the bus would
spoof the device ID of the Midi interface things would go crazzy long
before a note on event would be recognized ...
Do you think
this problem could come from an hardware failure into
my SB Live sound card?
How should that happen? If no midi note event shows up in the dump
the problem must be in qsynth (or the sound font it uses). What sound
found do you use, BTW?
11:23 a.m.
Hi,
On Tue, 08 Jun 2010 10:57:13 +0200
Nicolas BERCHER <nbercher(a)yahoo.fr> wrote:
So, I checked what's going on:
$ aseqdump --list
Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0
20:0 SB Live! Value [CT4870] EMU10K1 MPU-401 (UART)
24:0 USB Keystation 88es USB Keystation 88es MIDI 1
$ aseqdump -p 24:0
Waiting for data. Press Ctrl+C to end.
Source_ Event_________________ Ch _Data__
24:0 Control change 0 64 127
24:0 Note on 0 82 82
24:0 Note on 0 82 0
24:0 Control change 0 64 0
The above sequence dumped by aseqdump shows only one note event
(lines 2+3: press+release) but I heard a delayed note as mentioned in
my first mail.
Actually, there are two note events and both are NOTE ON, one with
velocity of 82 and the other 0. The velocity 0 should be interpreted as
NOTE OFF.
I had a similar problem and solved it by putting kmidimon between my
keyboard and sequencer.
Could it be that qsynth doesn't handle NOTE ON with
velocity of 0 as NOTE OFF? Although I imagine that translation should
be happening at a lower level... just a guess.
David
11:37 a.m.
On 08.06.2010 11:21, David Santamauro wrote:
Hi,
On Tue, 08 Jun 2010 10:57:13 +0200
Nicolas BERCHER<nbercher(a)yahoo.fr> wrote:
Yes it is, you're right, but it happens only for 4 notes among 88 I can
play!
If this putting kmidimon between my keyboard and qsynth can solve the
problem, I'd also like to understand why. Does it mean there exist
multiple midi standard to describe note on/off events?
Nicolas.
So, I checked what's going on:
$ aseqdump --list
Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0
20:0 SB Live! Value [CT4870] EMU10K1 MPU-401 (UART)
24:0 USB Keystation 88es USB Keystation 88es MIDI 1
$ aseqdump -p 24:0
Waiting for data. Press Ctrl+C to end.
Source_ Event_________________ Ch _Data__
24:0 Control change 0 64 127
24:0 Note on 0 82 82
24:0 Note on 0 82 0
24:0 Control change 0 64 0
The above sequence dumped by aseqdump shows only one note event
(lines 2+3: press+release) but I heard a delayed note as mentioned in
my first mail.
Actually, there are two note events and both are NOTE ON, one with
velocity of 82 and the other 0. The velocity 0 should be interpreted as
NOTE OFF.
I had a similar problem and solved it by putting kmidimon between my
keyboard and sequencer.
Could it be that qsynth doesn't handle NOTE ON with
velocity of 0 as NOTE OFF? Although I imagine that translation should
be happening at a lower level... just a guess.
12:13 p.m.
On Tue, 08 Jun 2010 11:37:23 +0200
Nicolas BERCHER <nbercher(a)yahoo.fr> wrote:
On 08.06.2010 11:21, David Santamauro wrote:
Sorry, I re-read the initial post -- 4 notes, hrmmm. That points
to a hardware issue but aseqdump doesn't show additional events.
Although I haven't delved into the code, the translation of NOTE ON (0)
to NOTE OFF should be happening at a much lower level than user-space
software. There is one standard for midi note on/off and it is clear
that note on (0) must be interpreted as note off.
Have you tried playing it back through a different sound generator,
possibly external gear attached to your 20:0 port?
Just as a test, what is registered when you route your keyboard into
kmidimon and route kmidimon into qsynth (all defaults, simple piano
patch)
- does kmidimon show 1 note-on/note-off only
- does qsynth output correctly?
David
Hi,
On Tue, 08 Jun 2010 10:57:13 +0200
Nicolas BERCHER<nbercher(a)yahoo.fr> wrote:
Yes it is, you're right, but it happens only for 4 notes among 88 I
can play!
If this putting kmidimon between my keyboard and qsynth can solve the
problem, I'd also like to understand why. Does it mean there exist
multiple midi standard to describe note on/off events?
Nicolas. So, I checked what's going on:
$ aseqdump --list
Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0
20:0 SB Live! Value [CT4870] EMU10K1 MPU-401 (UART)
24:0 USB Keystation 88es USB Keystation 88es
MIDI 1 $ aseqdump -p 24:0
Waiting for data. Press Ctrl+C to end.
Source_ Event_________________ Ch _Data__
24:0 Control change 0 64 127
24:0 Note on 0 82 82
24:0 Note on 0 82 0
24:0 Control change 0 64 0
The above sequence dumped by aseqdump shows only one note event
(lines 2+3: press+release) but I heard a delayed note as mentioned
in my first mail.
Actually, there are two note events and both are NOTE ON, one with
velocity of 82 and the other 0. The velocity 0 should be
interpreted as NOTE OFF.
I had a similar problem and solved it by putting kmidimon between my
keyboard and sequencer.
Could it be that qsynth doesn't handle NOTE ON with
velocity of 0 as NOTE OFF? Although I imagine that translation
should be happening at a lower level... just a guess.
1:39 p.m.
On 08.06.2010 12:11, David Santamauro wrote:
Sorry, I re-read the initial post -- 4 notes, hrmmm.
That points
to a hardware issue but aseqdump doesn't show additional events.
Although I haven't delved into the code, the translation of NOTE ON (0)
to NOTE OFF should be happening at a much lower level than user-space
software. There is one standard for midi note on/off and it is clear
that note on (0) must be interpreted as note off.
Ok, thanks for the precious details.
Have you tried playing it back through a different
sound generator,
possibly external gear attached to your 20:0 port?
I don't own any external generator.
I've tested timidity a few months ago, but its latency was about a few
seconds, horrible...!
Just as a test, what is registered when you route your
keyboard into
kmidimon and route kmidimon into qsynth (all defaults, simple piano
patch)
- does kmidimon show 1 note-on/note-off only
- does qsynth output correctly?
I can't manage to do this because kmidimon doesn't show any output
entry
in qjackctl's "connections" panel.
I found nothing to switch on/off into kmidimon configuration to do so...
usually jack-aware-software show their input(s)/output(s) automatically
in there, what's going wrong with my kmidimon?
Nicolas.
1:53 p.m.
On Tue, 08 Jun 2010 13:39:47 +0200
Nicolas BERCHER <nbercher(a)yahoo.fr> wrote:
On 08.06.2010 12:11, David Santamauro wrote:
If the kmidimon jack ports don't show up in qjackctl automatically
under the ALSA tab, kmidimon has a menu item called "Connections".
Under that you can follow the "Configure Connections" and your device
should be available under "Available Input Connections" and qsynth (if
running) should be available from the drop-down "Output Connection".
David
Just as a test, what is registered when you route
your keyboard into
kmidimon and route kmidimon into qsynth (all defaults, simple piano
patch)
- does kmidimon show 1 note-on/note-off only
- does qsynth output correctly?
I can't manage to do this because kmidimon doesn't show any output
entry in qjackctl's "connections" panel.
I found nothing to switch on/off into kmidimon configuration to do
so... usually jack-aware-software show their input(s)/output(s)
automatically in there, what's going wrong with my kmidimon?
Nicolas. 
10 Jun
10 Jun
10:25 a.m.
New subject: KMidimon ports (was Re: Sustain pedal issue with undesired repeated notes...)
On Tuesday, June 8, 2010, Nicolas BERCHER wrote:
There is nothing very wrong, only maybe slightly outdated. Recent KMidimon
releases (since 0.7.0 published one year ago) have a MIDI OUT port, in
addition to the MIDI IN one that has been always there. They are shown in the
ALSA tab of qjackctl. KMidimon uses the ALSA sequencer, not Jack.
About the MIDI THRU routing (copying the events received from the MIDI IN port
to the MIDI OUT port), I'm sorry but KMidimon can't do that. The MIDI OUT
port is used only for playback of either the events recorded from the MIDI IN
port, or the events loaded from a SMF or WRK file.
Regards,
Pedro
Just as a
test, what is registered when you route your keyboard into
kmidimon and route kmidimon into qsynth (all defaults, simple piano
patch)
- does kmidimon show 1 note-on/note-off only
- does qsynth output correctly?
I can't manage to do this because kmidimon doesn't show any output entry
in qjackctl's "connections" panel.
I found nothing to switch on/off into kmidimon configuration to do so...
usually jack-aware-software show their input(s)/output(s) automatically
in there, what's going wrong with my kmidimon?
1:37 p.m.
New subject: KMidimon ports (was Re: Sustain pedal issue with undesired repeated notes...)
On Thu, 10 Jun 2010 10:25:14 +0200
Pedro Lopez-Cabanillas <pedro.lopez.cabanillas(a)gmail.com> wrote:
About the MIDI THRU routing (copying the events received from the
MIDI IN port to the MIDI OUT port), I'm sorry but KMidimon can't do
that. The MIDI OUT port is used only for playback of either the
events recorded from the MIDI IN port, or the events loaded from a
SMF or WRK file.
apologies, yes, I was mistaken. I used QMidiRoute viewing the event
log. Sorry for the confusion.
David
8 Jun
8 Jun
12:15 p.m.
On 08.06.2010 11:21, David Santamauro wrote:
Hi,
On Tue, 08 Jun 2010 10:57:13 +0200
Nicolas BERCHER<nbercher(a)yahoo.fr> wrote:
I forgot to tell you that the third dump line, which correspond to the
key release, appeared *after* the undesired delayed note (I've kept it
pressed about ten seconds).
So I think that the keyboard events are well interpreted by qsynth since
I can play piano in a standard way: notes can ring as long as I want
when I press/release the keys!
Nicolas
So, I checked what's going on:
$ aseqdump --list
Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0
20:0 SB Live! Value [CT4870] EMU10K1 MPU-401 (UART)
24:0 USB Keystation 88es USB Keystation 88es MIDI 1
$ aseqdump -p 24:0
Waiting for data. Press Ctrl+C to end.
Source_ Event_________________ Ch _Data__
24:0 Control change 0 64 127
24:0 Note on 0 82 82
24:0 Note on 0 82 0
24:0 Control change 0 64 0
The above sequence dumped by aseqdump shows only one note event
(lines 2+3: press+release) but I heard a delayed note as mentioned in
my first mail.
Actually, there are two note events and both are NOTE ON, one with
velocity of 82 and the other 0. The velocity 0 should be interpreted as
NOTE OFF.
12:22 p.m.
On Tue, 08 Jun 2010 12:15:13 +0200
Nicolas BERCHER <nbercher(a)yahoo.fr> wrote:
On 08.06.2010 11:21, David Santamauro wrote:
Aha ... sounds like an attack issue with the soundfont. You press a
key, there is an initial attack, the sample loops and reattacks.
- do the notes repeat if you play them staccato, i.e., key
on/off < the time seen for the repeated notes to trigger?
- Have you tried a different soundfont and/or patch and is the
behavior identical regardless?
David
Hi,
On Tue, 08 Jun 2010 10:57:13 +0200
Nicolas BERCHER<nbercher(a)yahoo.fr> wrote:
I forgot to tell you that the third dump line, which correspond to
the key release, appeared *after* the undesired delayed note (I've
kept it pressed about ten seconds).
So I think that the keyboard events are well interpreted by qsynth
since I can play piano in a standard way: notes can ring as long as I
want when I press/release the keys! So, I checked what's going on:
$ aseqdump --list
Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0
20:0 SB Live! Value [CT4870] EMU10K1 MPU-401 (UART)
24:0 USB Keystation 88es USB Keystation 88es
MIDI 1 $ aseqdump -p 24:0
Waiting for data. Press Ctrl+C to end.
Source_ Event_________________ Ch _Data__
24:0 Control change 0 64 127
24:0 Note on 0 82 82
24:0 Note on 0 82 0
24:0 Control change 0 64 0
The above sequence dumped by aseqdump shows only one note event
(lines 2+3: press+release) but I heard a delayed note as mentioned
in my first mail.
Actually, there are two note events and both are NOTE ON, one with
velocity of 82 and the other 0. The velocity 0 should be
interpreted as NOTE OFF.
1:26 p.m.
On 08.06.2010 12:21, David Santamauro wrote:
On Tue, 08 Jun 2010 12:15:13 +0200
Nicolas BERCHER<nbercher(a)yahoo.fr> wrote:
No, that's why, fortunately, I can play of the songs I want on this fake
digital piano without any delay trouble (occurs on 4 specific notes only
if pedal/key pressed longer than 6~7 seconds)!
On 08.06.2010 11:21, David Santamauro wrote:
Aha ... sounds like an attack issue with the soundfont. You press a
key, there is an initial attack, the sample loops and reattacks.
- do the notes repeat if you play them staccato, i.e., key
on/off< the time seen for the repeated notes to trigger?
Hi,
On Tue, 08 Jun 2010 10:57:13 +0200
Nicolas BERCHER<nbercher(a)yahoo.fr> wrote:
I forgot to tell you that the third dump line, which correspond to
the key release, appeared *after* the undesired delayed note (I've
kept it pressed about ten seconds).
So I think that the keyboard events are well interpreted by qsynth
since I can play piano in a standard way: notes can ring as long as I
want when I press/release the keys!
So, I checked what's going on:
$ aseqdump --list
Port Client name Port name
0:0 System Timer
0:1 System Announce
14:0 Midi Through Midi Through Port-0
20:0 SB Live! Value [CT4870] EMU10K1 MPU-401 (UART)
24:0 USB Keystation 88es USB Keystation 88es
MIDI 1 $ aseqdump -p 24:0
Waiting for data. Press Ctrl+C to end.
Source_ Event_________________ Ch _Data__
24:0 Control change 0 64 127
24:0 Note on 0 82 82
24:0 Note on 0 82 0
24:0 Control change 0 64 0
The above sequence dumped by aseqdump shows only one note event
(lines 2+3: press+release) but I heard a delayed note as mentioned
in my first mail.
Actually, there are two note events and both are NOTE ON, one with
velocity of 82 and the other 0. The velocity 0 should be
interpreted as NOTE OFF.
- Have you tried a different soundfont and/or patch
and is the
behavior identical regardless?
The use of another piano sound font solved the problem.
It is sad for, as a beginner in midi and jack world, to began by using a
corrupted sound font...!
I have to do some tests in order to be sure that the problem was caused
by a particular corrupted sound font before I mark this thread SOLVED!
I really thank all of you, you were all of great help!
Nicolas
1:46 p.m.
On 08.06.2010 13:29, David Santamauro wrote:
On Tue, 08 Jun 2010 13:26:03 +0200
Nicolas BERCHER<nbercher(a)yahoo.fr> wrote:
The use of another piano sound font solved the problem.
Which soundfont was the problem? I can double check the symptoms if I
have the same one.
That's my main problem: I do not master bank stuff and I think I messed
things up in the qsynth channel I configured.
Moreover, the m-audio 88es keyboard is not really user friendly when it
comes to switch from a sound to another... so I feel a little... lost in
space!
I think I have to "read the f****** manual" once again and read some
qsynth documentation too.
Nicolas
PS About documentation: Does any one know why there is so few
documentation about jackd (not qjackctl)?
I've spent hours looking for documentation and a way to start a
jackd/fluidsynth as a system v script (/etc/init.d/) on a Linux box (no
X server) in order to play piano.
5:11 p.m.
New subject: [SOLVED] Sustain pedal issue with undesired repeated notes (m-audio keystation 88es + qjackctl + qsynth)
On 08.06.2010 13:26, Nicolas BERCHER wrote:
On 08.06.2010 12:21, David Santamauro wrote:
I confirm that a corrupted soundfont was the origin of undesired delayed
notes.
Thanks to everybody for being so responsive!
Nicolas
- Have you tried a different soundfont and/or
patch and is the
behavior identical regardless?
The use of another piano sound font solved the
problem.
It is sad for, as a beginner in midi and jack world, to began by using
a corrupted sound font...!
I have to do some tests in order to be sure that the problem was
caused by a particular corrupted sound font before I mark this thread
SOLVED!
I really thank all of you, you were all of great help!
Nicolas
11:30 a.m.
On 06.06.2010 15:07, Nicolas BERCHER wrote:
Hi,
I have a problem I can't face alone on the digital piano I made on
Debian Lenny with qsynth (v0.2.5-2.2), qjackctl (v0.3.2-1) and an
m-audio keystation 88es keyboard.
When I play the piano, some notes will repeat themselves after a few
seconds only if I keep the sustain pedal pressed, just like a delay
effect would do.
I reported that only 4 notes are concerned for the moment, they have
different repeat delays:
G : ~7.5 sec (G4)
G# : ~7 sec (G#4)
A : ~6.5 sec (A4)
A# : ~6 sec (A#4)
Note that the notes above, relatively to the middle C of a piano
keyboard called C3, goes from G4 to A#4.
Could this be due to an hardware issue in the m-audio keyboard?
Edit: the problem
described above also appears when I don't use the
sustain pedal, but let the key pressed to let the note ring.
N.
12:16 p.m.
On 08.06.2010 11:30, Nicolas BERCHER wrote:
On 06.06.2010 15:07, Nicolas BERCHER wrote:
I have an MSI Wind notebook, it doesn't have a powerful dsp but can play
a little with correct latency.
The problem is the same, on the same notes and the same delays.
Note that it the two computers I've tested doesn't share the same
qsynth/qjackctl versions, jackd are really close and might only concern
Debian patches (0.118+svn3796-2 and 0.118+svn3796-1).
Nicolas.
Hi,
I have a problem I can't face alone on the digital piano I made on
Debian Lenny with qsynth (v0.2.5-2.2), qjackctl (v0.3.2-1) and an
m-audio keystation 88es keyboard.
When I play the piano, some notes will repeat themselves after a few
seconds only if I keep the sustain pedal pressed, just like a delay
effect would do.
I reported that only 4 notes are concerned for the moment, they have
different repeat delays:
G : ~7.5 sec (G4)
G# : ~7 sec (G#4)
A : ~6.5 sec (A4)
A# : ~6 sec (A#4)
Note that the notes above, relatively to the middle C of a piano
keyboard called C3, goes from G4 to A#4.
Could this be due to an hardware issue in the m-audio keyboard?
Edit: the problem
described above also appears when I don't use the
sustain pedal, but let the key pressed to let the note ring.
N.
5626
days inactive
5630
days old
linux-audio-user@lists.linuxaudio.org
22 comments
7 participants
participants (7)
-
Dave Phillips -
david -
David Santamauro -
Ken Restivo -
Nicolas BERCHER -
Pedro Lopez-Cabanillas -
R. Mattes