13 Dec
2012
13 Dec
'12
6:04 p.m.
Could just be me and my ongoing discoveries of weirdness...but has
anyone else had the experience of finding that Linux studio apps seem to
require much higher velocity from keyboards than the same keyboards do
in the world of physical gear?
I'm using a Yamaha SY99 as a master keyboard, and I'm finding that with
most of the soundfonts I've tried in FluidSynth, I'm having to play the
keyboard *hard* to get multisamples that have been setup to play a
certain sample only at high velocities to switch into their higher
velocity sound. I never have to play that hard when I'm using the SY99
by itself, or when using it to drive any other keyboard or drum machine.
Is it just some kind of Alsa Midi thing, or do soundfont creators out
there just really like banging their keyboards?
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ Sr. UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ James Franck Institute + Shakespeare. Now, thanks to the Internet,
+ Materials Research Ctr + we know this is not true." -Robert Wilensky
13 Dec
13 Dec
6:38 p.m.
Il giorno Thu, 13 Dec 2012 11:04:50 -0600 (CST)
Brent Busby <brent(a)keycorner.org> ha scritto:
Could just be me and my ongoing discoveries of
weirdness...but has
anyone else had the experience of finding that Linux studio apps seem
to require much higher velocity from keyboards than the same
keyboards do in the world of physical gear?
I'm using a Yamaha SY99 as a master keyboard, and I'm finding that
with most of the soundfonts I've tried in FluidSynth, I'm having to
play the keyboard *hard* to get multisamples that have been setup to
play a certain sample only at high velocities to switch into their
higher velocity sound. I never have to play that hard when I'm using
the SY99 by itself, or when using it to drive any other keyboard or
drum machine.
Is it just some kind of Alsa Midi thing, or do soundfont creators out
there just really like banging their keyboards?
Hi, I once had the same problem with a sampled piano, So I started
playing with qmidicurves http://sourceforge.net/projects/qmidicurves/.
There are probably other ways to do it but this is pretty
straightforward.
--
Asa Marco <marcoasa90(a)gmail.com> 朝
7:24 p.m.
On Thu, 13 Dec 2012, Asa Marco wrote:
Hi, I once had the same problem with a sampled piano,
So I started
playing with qmidicurves http://sourceforge.net/projects/qmidicurves/.
There are probably other ways to do it but this is pretty
straightforward.
Thanks!
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ Sr. UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ James Franck Institute + Shakespeare. Now, thanks to the Internet,
+ Materials Research Ctr + we know this is not true." -Robert Wilensky
8:38 p.m.
On 12/13/2012 08:47 AM, Asa Marco wrote:
Il giorno Thu, 13 Dec 2012 11:04:50 -0600 (CST)
Brent Busby <brent(a)keycorner.org> ha scritto:
Well, my Yamaha PSR-225 has that problem with it's built-in sounds - I
have to pound it to get its loud samples, despite the three different
curve settings it has built in. Maybe it's a Yamaha thing?
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
Could just be me and my ongoing discoveries of
weirdness...but has
anyone else had the experience of finding that Linux studio apps seem
to require much higher velocity from keyboards than the same
keyboards do in the world of physical gear?
I'm using a Yamaha SY99 as a master keyboard, and I'm finding that
with most of the soundfonts I've tried in FluidSynth, I'm having to
play the keyboard *hard* to get multisamples that have been setup to
play a certain sample only at high velocities to switch into their
higher velocity sound. I never have to play that hard when I'm using
the SY99 by itself, or when using it to drive any other keyboard or
drum machine.
Is it just some kind of Alsa Midi thing, or do soundfont creators out
there just really like banging their keyboards?
Hi, I once had the same problem with a sampled piano, So I started
playing with qmidicurves http://sourceforge.net/projects/qmidicurves/.
There are probably other ways to do it but this is pretty
straightforward.
16 Dec
16 Dec
5:13 a.m.
On Thu, 13 Dec 2012, Asa Marco wrote:
Hi, I once had the same problem with a sampled piano,
So I started
playing with qmidicurves http://sourceforge.net/projects/qmidicurves/.
There are probably other ways to do it but this is pretty
straightforward.
On the suggestion of some others on the list, I checked the velocity
output of my Yamaha SY99 against my Ensoniq ESQ-1... (There were some
posts awhile back saying it might be a Yamaha thing to send weak
velocity data). Well, it's true, in fact, they seem to be opposites!
While the SY99 seems to never send quite high enough velocities to
FluidSynth for what most soundfonts seem to be expecting (even on the
SY99's most compensated action setting), the ESQ-1 plays everything too
loud, even on its softest action setting. So there does seem to be a
big difference in the way different keyboards scale these things. And
oddly I never noticed this in all the years I've been sequencing in a
pure physical gear environment -- if you want problems you've never had
before, use a computer....
So, I took your advice and installed QmidiCurves, and now I can have
whatever velocity curve I want. The author seems to have created the
Makefiles with a lot of Debian/Ubuntu assumptions though, so for anyone
wanting to compile on Gentoo:
- if not already installed, emerge x11-libs/qwt:5 (the 5.x version)
from Portage which is needed as a dependency
- download and extract...
- in QMIDICurves.pro, change LIBPATH to /usr/lib
and change LIBS to -lqwt (not -lqwt-qt4)
and add this line: INCLUDEPATH += /usr/include/qwt
- qmake -recursive CONFIG+=debug_and_release QMIDICurves.pro
- fgrep -lr 'qwt-qt4/' | xargs sed -i 's|qwt-qt4/|qwt5/|g'
- lrelease lang-en.ts lang-fr.ts
(strangely, the Makefile doesn't do this itself)
- 'make release'
This will produce a 'QMIDICurves' binary that's ready to go. There is
no Makefile driven 'make install' that actually does anything, so just
put it in your /usr/local/bin and it works. It will create an Alsa Midi
input and output visible in your connection manager.
I should probably make an ebuild for this sometime Real Soon Now...
Also, the unlabeled icons in the upper right are:
move point, create point, delete point (not mentioned in the docs)
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ Sr. UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ James Franck Institute + Shakespeare. Now, thanks to the Internet,
+ Materials Research Ctr + we know this is not true." -Robert Wilensky
13 Dec
13 Dec
6:47 p.m.
Perhaps the SY99 does provide different keyboard velocity curves [1]? I
own the first version of the DX7 and it's keyboard comes with the issue
you described, but for all external gear and for the DX7 itself too. I
like it, since it enables to control the averaged wanted dynamic good
for my needs. I avoided to use update or customized DX7 software, but I
guess velocity curves can be add to all Yamaha synth since the 80s, so
assumed the SY99 shouldn't provide it by default, there for sure are
EPROMS or discs etc. available. IIRC even when I hit a key as fast/heavy
as possible, the velocity doesn't reach 127, but 116 or something like
that only. I suspect that you are accustomed to your SY99 sounds and
your drum machine, but that the default setting is optimised to averaged
dynamic ranges that fit to the kind of keyboard mechanic velocity
resolution and MIDI velocity resolution. It's very likely that there is
an app, that allows to transform incoming velocity data. This perhaps
isn't as good as a keyboard that provides different velocity curves, but
might satisfy your needs. Some virtual synth perhaps do provide velocity
curves too.
[1] "See page 253 of your SY99 owner's manual, Utility Mode/2. Velocity
Set on how to set up the velocity curves, this may help some. I have not
checked my SY99 for velocity output, but for years my SY77 routinely
transmits around 115 to 118 maximum velocity and it has not been a
problem using it as a master keyboard/controller for the last 16 years
with a wide variety of synths./modules. Hope this helps." -
http://www.yamahaforums.co.uk/forum/viewtopic.php?f=55&t=1285
7:25 p.m.
On Thu, 13 Dec 2012, Ralf Mardorf wrote:
Perhaps the SY99 does provide different keyboard
velocity curves [1]?
It does, but even on its most responsive setting, I still have to bang.
It's all the soundfonts I've seen too...
--
+ Brent A. Busby + "We've all heard that a million monkeys
+ Sr. UNIX Systems Admin + banging on a million typewriters will
+ University of Chicago + eventually reproduce the entire works of
+ James Franck Institute + Shakespeare. Now, thanks to the Internet,
+ Materials Research Ctr + we know this is not true." -Robert Wilensky
7:47 p.m.
On 12/13/12, Brent Busby <brent(a)keycorner.org> wrote:
On Thu, 13 Dec 2012, Ralf Mardorf wrote:
Try aseqdump and see what kind of velocities you get when applying
various pressure to your keys.
You first need to find the alsa MIDI port number of name of your
keyboard (example form my box):
$ aconnect -io
client 20: 'LPD8' [type=kernel]
0 'LPD8 MIDI 1 '
$ aseqdump -p 20
OR
$ aseqdump -p "LPD8"
Waiting for data. Press Ctrl+C to end.
Source Event Ch Data
20:0 Note on 0, note 43, velocity 104
20:0 Note off 0, note 43, velocity 127
Another tool which, among other things, can be used for adjusting
curves is mididings:
http://das.nasophon.de/mididings/
Information about how to use it to set your curves is here:
http://das.nasophon.de/mididings/doc/units.html#modifiers
Perhaps the SY99 does provide different keyboard
velocity curves [1]?
It does, but even on its most responsive setting, I still have to bang.
It's all the soundfonts I've seen too...
4296
days inactive
4299
days old
linux-audio-user@lists.linuxaudio.org
7 comments
5 participants
participants (5)
-
Asa Marco -
Brent Busby -
david -
Egor Sanin -
Ralf Mardorf