18 Apr
2010
18 Apr
'10
6:04 p.m.
All,
Even though Qsynth's green light is flashign on each pas hit from the
Alesis Control Pad, barely a sound is coming out. Out of 20 hits maybe
one sound comes out and that's it (drum sound on channel 10 or any
other sound for that matter). On the other hand when connected to
Hydrogen, the Alesis Control Pad plays each single sound, complete with
velocity and all.
The pads from a M-Audio Axiom 25 keyboard works fine with Qsynth.
Why is this so ? Why does the Control Pad plays so so well with
Hydrogen but barely can emit a sound when connected to Qsynth/using
fluidsynth ? It'd be real nice to be able to use drumsticks in playing
some soundfonts !
Thanks for any suggestion/hint/idea,
Cheers.
18 Apr
18 Apr
6:24 p.m.
Hey,
1. Are you sure that your soundfont has a sample on every key? Ie: Check
WHICH
notes are being sent from the Alesis Control Pad, and compare them to the
pads on your
Axiom? (Use KMidiMon or GMidiMon or ... for testing?)
2. Have you tried using VMPK (Virtual Midi Piano Keyboard) to send MIDI
notes
to QSynth to see how that reacts? (dropping notes yes/no?)
Good luck.. -Harry
On Sun, Apr 18, 2010 at 11:06 PM, lanas <lanas(a)securenet.net> wrote:
All,
Even though Qsynth's green light is flashign on each pas hit from the
Alesis Control Pad, barely a sound is coming out. Out of 20 hits maybe
one sound comes out and that's it (drum sound on channel 10 or any
other sound for that matter). On the other hand when connected to
Hydrogen, the Alesis Control Pad plays each single sound, complete with
velocity and all.
The pads from a M-Audio Axiom 25 keyboard works fine with Qsynth.
Why is this so ? Why does the Control Pad plays so so well with
Hydrogen but barely can emit a sound when connected to Qsynth/using
fluidsynth ? It'd be real nice to be able to use drumsticks in playing
some soundfonts !
Thanks for any suggestion/hint/idea,
Cheers.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
19 Apr
19 Apr
6:59 a.m.
On Sun, 18 Apr 2010 23:24:13 +0100,
Harry Van Haaren <harryhaaren(a)gmail.com> wrote :
1. Are you sure that your soundfont has a sample on
every key? Ie:
Check WHICH
notes are being sent from the Alesis Control Pad, and compare them to
the pads on your
Axiom? (Use KMidiMon or GMidiMon or ... for testing?)
As I've reported, hitting the same pad 20 times will bring out one
(faint) sound. I do not think the Alesis Control Pad is changing MIDI
note number during these 20 hits on the very same pad.
I also do not think the Control Pad has cross-pad noise (it is
adjustable) as cross-pad noise does not happen when using Hydrogen nor
does it happen when using the Control Pad to trigger the sounds of a
M-Audio Prokeys 88 keyboard with built-in sounds.
Clearly, the Alesis Control Pad seems to be working fine.
2. Have you tried using VMPK (Virtual Midi Piano
Keyboard) to send
MIDI notes
to QSynth to see how that reacts? (dropping notes yes/no?)
Qsynth also works fine when played by the keys and pad of both M-Audio
keybaords (Axion 25 and Prokeys 88).
Good luck.. -Harry
Ouside of luck, there must be a good friggin' reason why it is not
possible to reliably trigger Qsynth sounds (with velocity!) from an
Alesis Control Pad.
On Sun, Apr 18, 2010 at 11:06 PM, lanas
<lanas(a)securenet.net> wrote:
> All,
>
> Even though Qsynth's green light is flashign on each pas hit from
> the Alesis Control Pad, barely a sound is coming out. Out of 20
> hits maybe one sound comes out and that's it (drum sound on channel
> 10 or any other sound for that matter). On the other hand when
> connected to Hydrogen, the Alesis Control Pad plays each single
> sound, complete with velocity and all.
>
> The pads from a M-Audio Axiom 25 keyboard works fine with Qsynth.
>
> Why is this so ? Why does the Control Pad plays so so well with
> Hydrogen but barely can emit a sound when connected to Qsynth/using
> fluidsynth ? It'd be real nice to be able to use drumsticks in
> playing some soundfonts !
>
> Thanks for any suggestion/hint/idea,
>
> Cheers.
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
>
7:22 a.m.
On 19/04/2010, lanas <lanas(a)securenet.net> wrote:
As I've reported, hitting the same pad 20 times
will bring out one
(faint) sound. I do not think the Alesis Control Pad is changing MIDI
note number during these 20 hits on the very same pad.
Is there some controller, knob or setting that the Control Pad is
sending which FluidSynth is interpreting as patch volume (or filter
cutoff) but the other two are ignoring?
20 Apr
20 Apr
1:35 p.m.
Le Lundi, 19 Avril 2010 12:22:10 +0100,
Gwenhwyfaer <gwenhwyfaer(a)gmail.com> a écrit :
On 19/04/2010, lanas <lanas(a)securenet.net>
wrote:
No, everything works fine in its own way. Fluidsynth/qsynth works fine
with the percussion pads of the Axion 25 (as well as the keyboard) and
the Alesis Control Pad works fine with Hydrogen, as well as Zynaddsubfx
and the triggering of the built-in sounds of the M-Audio Prokeys88.
Each one works just fine. It is only when the Control Pad is used with
fluidsynth/qsynth that barely a sound is produced. It seems as if the
Control Pad. being a percussive instrument, is well understood by
Hydrogen whereas fluidsynth, primarily for keybaords, do nto understand
how a percussion-only intrument works, and there seems to be a
difference. In what, I don't know. Maybe the notes on/off are not the
same. Maybe the duration of the MIDI event is way too short whne it is
allright for Hydrogen.
I hope that the Control Pad will be able in the end to play soundfonts !
As I've reported, hitting the same pad 20
times will bring out one
(faint) sound. I do not think the Alesis Control Pad is changing
MIDI note number during these 20 hits on the very same pad.
Is there some controller, knob or setting that the Control Pad is
sending which FluidSynth is interpreting as patch volume (or filter
cutoff) but the other two are ignoring? 
19 Apr
19 Apr
12:46 p.m.
On Monday, April 19, 2010, you wrote:
Even though Qsynth's green light is flashign on
each pas hit from the
Alesis Control Pad, barely a sound is coming out. Out of 20 hits maybe
one sound comes out and that's it (drum sound on channel 10 or any
other sound for that matter). On the other hand when connected to
Hydrogen, the Alesis Control Pad plays each single sound, complete with
velocity and all.
The pads from a M-Audio Axiom 25 keyboard works fine with Qsynth.
Why is this so ? Why does the Control Pad plays so so well with
Hydrogen but barely can emit a sound when connected to Qsynth/using
fluidsynth ? It'd be real nice to be able to use drumsticks in playing
some soundfonts !
Thanks for any suggestion/hint/idea,
Cheers.
Looks like this is the same, similar, or related to this ticket:
http://fluidsynth.resonance.org/trac/ticket/55
There have been some changes in FluidSynth 1.1.1 for this issue, but the
reporter did not answer the request to verify the changes, so maybe the
problem is still there. Which FluidSynth version are you using?
Regards,
Pedro
20 Apr
20 Apr
1:35 p.m.
Le Lundi, 19 Avril 2010 18:45:34 +0200,
Pedro Lopez-Cabanillas <pedro.lopez.cabanillas(a)gmail.com> a écrit :
On Monday, April 19, 2010, you wrote:
>
> The pads from a M-Audio Axiom 25 keyboard works fine with Qsynth.
> Why is this so ? Why does the Control Pad plays
so so well with
> Hydrogen but barely can emit a sound when connected to Qsynth/using
> fluidsynth ? It'd be real nice to be able to use drumsticks in
> playing some soundfonts !
Looks like this is the same, similar, or related to
this ticket:
http://fluidsynth.resonance.org/trac/ticket/55
It really does.
There have been some changes in FluidSynth 1.1.1 for
this issue, but
the reporter did not answer the request to verify the changes, so
maybe the problem is still there. Which FluidSynth version are you
using?
# fluidsynth --version
FluidSynth version 1.1.1
I would like to try the setting in the bug report, but oddly
enough I haven't found where the config file, for neither fluidsynth or
qsynth. Usually on Linux/UNIX systems it's either /etc or the home
directory in a . directory or file. Can I simply create one in /etc ?
What would be the format ?
I'm willing to try any new version or patches. I've compiled
fluidsynth for this system, so I can apply patches if needed. I would
like to get into the code but I simply do not have the time.
Thanks.
21 Apr
21 Apr
5:57 a.m.
On Tuesday, April 20, 2010, lanas wrote:
Le Lundi, 19 Avril 2010 18:45:34 +0200,
Pedro Lopez-Cabanillas <pedro.lopez.cabanillas(a)gmail.com> a écrit :
You need to start FluidSynth 1.1.1 with a command line like:
fluidsynth -a alsa -m alsa_seq -p fluidsynth \
-o synth.min-note-length=10 \
SoundFont.sf2
10 is the default value for the note duration.
On Monday, April 19, 2010, you wrote:
It really does.
The pads from a M-Audio Axiom 25 keyboard works
fine with Qsynth.
Why is this so ? Why does the Control Pad plays so so well with
Hydrogen but barely can emit a sound when connected to Qsynth/using
fluidsynth ? It'd be real nice to be able to use drumsticks in
playing some soundfonts !
Looks like this is the same, similar, or related to this ticket:
http://fluidsynth.resonance.org/trac/ticket/55 There have been some changes in FluidSynth 1.1.1
for this issue, but
the reporter did not answer the request to verify the changes, so
maybe the problem is still there. Which FluidSynth version are you
using?
# fluidsynth --version
FluidSynth version 1.1.1
I would like to try the setting in the bug report, but oddly
enough I haven't found where the config file, for neither fluidsynth or
qsynth. Usually on Linux/UNIX systems it's either /etc or the home
directory in a . directory or file. Can I simply create one in /etc ?
What would be the format ?
The "config file" is a simple text file containing FluidSynth shell commands,
like the ones you can type into its own internal shell, for instance router
commands. See "man fluidsynth" for more information. You can provide a config
file in several ways...
a) per session, in the command line:
fluidsynth -f mycommands
b) per user account, in a file named '.fluidsynth' at the user's home:
$HOME/.fluidsynth
c) a system wide file:
/etc/fluidsynth.conf
But the setting 'synth.min-note-length' (and others like
'synth.sample-rate'
as well) must be given in the command line, not in a command file, because
they need to be known when the synth is created, and the command files are
parsed and executed later.
I'm willing to try any new version or patches.
I've compiled
fluidsynth for this system, so I can apply patches if needed. I would
like to get into the code but I simply do not have the time.
I would like to help fixing this issue, but I don't have an "Alesis Control
Pad" and I can't reproduce the problem.
Maybe you can provide the means to reproduce it. For instance, recording a
small amount of events from the pad into a standard MIDI file, and testing
this MIDI file against FluidSynth and other synths. If the recorded MIDI file
produces the same results with FluidSynth as a live playing session, then
please attach this file to the ticket 55 or send it by mail to me or to the
fluidsynth mailing list.
You can record a standard MIDI file with 'arecordmidi' (from ALSA utils) or
with KMidimon. To play back the recorded file, there is 'aplaymidi' (also
from ALSA utils) or KMidimon.
Regards,
Pedro
4922
days inactive
4925
days old
linux-audio-user@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Gwenhwyfaer -
Harry Van Haaren -
lanas -
Pedro Lopez-Cabanillas