Sustainer is a tiny ALSA MIDI daemon that provides sustain pedal functionality to softsynths that don't support the sustain pedal (such as PHASEX, AMS, Specimen, etc.).
http://restivo.org/projects/sustainer/
I use the sustain pedal a lot in live performance for holding down pads while tweaking knobs or playing other parts (or both). It was annoying me that so many of my favorite softsynths for making pads, didn't support the sustain pedal though.
I didn't feel like hacking all the softsynths that didn't have sustain pedal functionality, so I decided to solve it the Unix way by making a tiny utility to do what I wanted. I needed this to scratch my personal itch, and I'm publishing it so that others may enjoy it if they need something like this.
I don't use JACK MIDI yet; I'm one of those luddites still on version 0.103 of JACK and refusing to take any risks on newer versions. But JACK MIDI is very straightforward, so at some point I'll convert this utility to native JACK MIDI.
-ken
Hello,
i'm developing some software for company i'm working in, for playing back the
recordings of a telephone calls, radio transmissions and stuff. The
application obviously uses jack audio server and is running on a SuSE 10.3.
Audio has to be played back to the six separate mono outputs, and i am
searching for a sound card supported by a jack. The card should be PCI or
USB. I don't need a hardware mix, and the sound quality can be low, as a
recordings are did in a 4 or 8 kHz - no sound card can make the output worse
i think :)
I've found m-audio 2496 to be fairly reasonable, but i'm wondering if some of
inputs can be configured as an output.
thanks,
--
Jozef Henzl
Hello
I'd like to ask a few questions about Ardour and Linuxsampler.
I have compiled them both, and notice something.
Linuxsampler gives me "Detected features: disabled at compile time" when I
started in in commandline.
It should have given me "Detected features: MMX SSE SSE2". I think it is
caused by the configure script
failing to detect my cpu because there is "#define ARCH_X86 0" in my
config.h.
So I fixed it by adding ARCH_X86 1 in it and recompiled.
In ardour I cannot choose the denormal handling options because they are
greyed out.
And starting ardour2 from the commandline gives me
ardour: [INFO]: Ardour will be limited to 1024 open files
loading system configuration file /usr/local/etc/ardour2/ardour_system.rc
loading user configuration file /home/shani/.ardour2/ardour.rc
ardour: [INFO]: No H/W specific optimizations in use
Warning: Unable to create "trees" RDF storage.
Performance can be improved by upgrading librdf.
I figure that ardour too did not detect my cpu correctly at compile time.
But I'm not sure what to do here.
My question is, is it the fault of my system not giving the appropriate info
so that the configure script
could not detect the cpu?
For Linuxsampler, is there an appropriate way to fix it instead of editing
the config.h manually.
Perhaps I should have used --build=something when running ./configure?
Ardour, I run scons with DIST_TARGET = 'x86_64' though, so why did it not
able to detect my cpu?
Oh, I've seen "Warning: Unable to create "trees" RDF storage" message a
lot, is there something wrong?
Thank you
> Message: 3
> Date: Wed, 1 Oct 2008 16:20:02 +0400
> From: "alex stone" <compose59(a)gmail.com>
> Subject: [LAU] Standalone mixer.
> To: linux-audio-user(a)lists.linuxaudio.org
> Message-ID:
> <caa95e270810010520i5582ee87r9f36959aad51e577(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Evening all.
>
> I'm searching for a standalone mixer to work with jack, so i can route some
> bits through it. Any number of channel strips would be ok, but the bigger
> the better.
>
> I'm also looking for a single gain strip, with meter, that will do the same
> thing for one stereo input / stereo output. (I'll settle for two mono gain
> meter strips as well.)
>
> I'm using dual boot Linux/Ubuntustudio Hardy, 32 and 64bit..
>
> Any help would be welcome, and i'm using patchage, and Ingen, for patchbay,
> and plugin management respectively.
>
Hi,
I have turned an old analogue electric organ into a MIDI controller. All the
old push buttons, switches, pots, drawbars can now trigger MIDI events.
Because I would like to make the MIDI messages static (i.e. they are linked
with particular buttons and faders and will not be changed) I have thought of
using an external application (keykit in this case) to work on incoming MIDI
events of the MIDI controller, filter them and trigger newly defined MIDI
events with it.
I would like to make the MIDI messages transmitted by the controller as short
as possible. I have thought of assigning the Bx (Control Change) command to
the buttons and faders, but this would mix with/overwrite other control
change commands sent by other MIDI devices.
It has to be possible to distinguish between the buttons/faders by the MIDI
message that each one triggers.
How about the System Common Message F4 and F5 which are not yet defined in the
MIDI standard? Could I add some extra data bytes to identify the type (button
or fader), the number and value?
Like this:
F4 125 70 (Fader 125 sends value 70)
keykit would recognize this fader and set volume level for channel 2 for
fluidsynth.
Or, in another situation, increase sustain value for channel 3 for fluidsynth.
or:
F5 10 1 (Button 10 sends value ON)
keykit would recognize the button and turn on sustain for channel 1.
Thanks for any hint and kind regards,
Crypto.
I'm having a bit of an experiment with jconv, and several wavs i have.
So far i have gain and input/output sorted out....but,
I have a Q.
What are the increments for delay, offset, and length measured in?
Milliseconds?
Alex.
I just sent a note to the announce list with details (no details here
'cause I got blasted last time for duplicate mailings). But, if you're
in a hurry just jump to the mma home page and grab the latest:
http://www.mellowood.ca/mma/
--
**** Listen to my CD at http://www.mellowood.ca/music/cedars ****
Bob van der Poel ** Wynndel, British Columbia, CANADA **
EMAIL: bob(a)mellowood.ca
WWW: http://www.mellowood.ca