Hello everyone!
Nama has a sort of multiband compressor by using three parallel tracks, all
processed by filters. Now we've discovered, that our current filter settings
aren't good for multiband compression as used in a mastering setup. Yes, I
know, people debate wether to use it or not, but it's always nice to have the
opportunity and leave it up to the users.
We currently use the Glame highpass, lowpass and bandpass IIR LADSPA plugins
with unique IDs 1890-1892. The current settings are:
lowpass: 106Hz 2 stages
bandpass: 520Hz(center) 800Hz(bandwidt) 2 stages
highpass: 1030Hz 2 stages
These settings give a good full band, but I've heard, that the bands aren't
the best choices. I've found some reeferences to using:
160Hz as the first divider and 3500Hz for the second divider.
could someone suggest good settings to achieve this. Either with these
plugins or with different filters, if easily available and in form of a LADSPA
plugin. Ecasound has LV2 support, but it's not capable of all the LV2
features.
I'd also do just fine with a formula to calculate it myself, if there is
such a thing, that really meets the audible requirements.
Fons, last time you were kind enough to supply the settings. How did you
arrive at these values? Did you check graphically? I'm pretty sure, that you
wouldn't have.
Warm regards and thanks a lot
Julien
----------------------------------------
Music, creative writing, technical information:
http://juliencoder.de/
I can see this being a problem if the multiple devices were all input devices, such as the "multiple Soundblasters" mentioned in a previous post, but if there is a single device used for input, and another device that is used strictly for listening, what problems can be caused? I fail to see how it could cause a problem, even if the clock on the monitor audio chain drifts.
michael noble <looplog(a)gmail.com> wrote:
>_______________________________________________
>Linux-audio-user mailing list
>Linux-audio-user(a)lists.linuxaudio.org
>http://lists.linuxaudio.org/listinfo/linux-audio-user
Hi folks,
I was recently stuck on an issue that I could not readily find
solutions for online. So I thought documenting the solution here may
be of use to someone in the future.
Problem: when attempting to start two independent instances of
fluidsynth in server mode from the command line, I get the following
error:
fluidsynth: error: Failed to bind server socket
After a bit of research, it seems that the problem is a result of the
fact that in server mode (and probably in other modes as well, though
I am not sure) fluidsynth communicates with the shell through a socket
on the local machine. From what I saw in the source, there is no
automatic checking to see if the default port is already bound, so the
second instances tries to grab the same socket as the first, and fails
with the above error. There is a setting "shell.port", which needs to
be set explicity in this case (see man page). the -o command line
option allows one to define settings. In the end, the following two
commands give me the kind of environment I need (notice the "-o
shell.port="):
$ fluidsynth -a jack -m alsa_seq --portname=fluidsynth_piano
--no-shell -s -g 1 \
-o audio.jack.id=fl_piano -o shell.port=9800 piano.sf2 &
$ fluidsynth -a jack -m alsa_seq --portname=fluidsynth_drums
--no-shell -s -g 1 \
-o audio.jack.id=fl_drums -o shell.port=9801 drums1_harris.sf2 &
I do not know if this problem occurs when using Qsynth, I am doing
this in a text only environment.
Machine info:
$ uname -a
Linux mervag 3.12.1-1-ARCH #1 SMP PREEMPT Thu Nov 21 08:18:42 CET 2013
x86_64 GNU/Linux
$ jackd -V
jackdmp 1.9.9.5
Hi all. I'm still having occasional audio glitch problems, and I frequently get 1 or more errors in a log file like this:
[31mERROR: [0ma2j_process_incoming: threw away MIDI event - not reserved at time 157016825
Is this a A2JMIDIBridge error? If so, should this cause a complete audio drop-out at that point? It seems I only have difficulties when recording audio with Nama from a softsynth playing from MIDI data. I have no problems either with playback of MIDI sequences, playback of audio, or recording audio directly from a live sound-source. There was some posts a while back about A2JMIDI not providing proper MIDI time stamps. Could this be part of the issue? Is there any reason to be concerned with Nama/Ecasound creating MIDI ports even when they're not being used? I'm just throwing out thoughts here, because I'm not sure where to look for answers or how to test further. It even occurs when recording a softsynth live, but of course I'm still using MIDI data to drive it. Any suggestions would be appreciated. Thanks much.
Kevin
Hello,
jpmidi is a Midi-file player that uses Jack-Midi and synchronises to
Jack-Transport.
It is currently a hosted by Julien here : http://juliencoder.de/jpmidi/
After using it for a while with the command line, i needed an advanced
feature : being able to control it remotely with UDP or TCP commands.
This what i call a server mode.
I've been modifying the code, and added a '-s' option so jpmidi is
started in server mode, and waits for commands on port 2013.
Well the whole thing is still buggy sometimes, especially with the
port which is not released correctly, but it worked.
I plan to continue developping on this feature. May you be interested
in contributing, let me know.
The project is now hosted on sourceforge :
https://sourceforge.net/projects/jpmidi/
Raphaël
Hi all! I'm wanting to use Aeolus's MIDI controller 98 function to change individule stops. However, In order to easily send single controller values, I'm wondering about using program change instead. Can I configure it that way now, or would that require code changes? I know program change is currently used for presets, but could this be user-selectable perhaps, so that one could use it for registration instead? Or again, is that already possible? Since I can't see, I'll have to have sighted assistance with it, so if this can be done currently, any guidance would be helpful.I very much appreciate the text interface! Thank you very much for that. I'm hoping to be able to include registrations in my song files using MIDISH as well. I hope to have a recording to share shortly. Thank you for this instrument! I'm enjoying it very much.
Kevin
Hello dear all LAUers.
Time ago I did some research about open source/free software licences:
types, pros and cons, etc. I'm reviewing it and, given that I follow
and love many of the great projects and applications coded by members
of this list, I would love to here you're opinions (pros, cons) and
experience in practice and why you chose X licence for your project(s)
(business model or enterprise view in mind, 'cause you like it...).
I see that the most commons are GPL2 (some don't like yet the v3) and
GPL3. And nowadays with so many services in the cloud also AGPL, and
MIT or Apache as well with HTML and Javascript libs and artifacts.
Thanks as always for sharing your work and knowledge.
--
Carlos sanchiavedraz
* Musix GNU+Linux
http://www.musix.es
For what it's worth, I did finally discover why Simple Sysexer,
JSynthLib, and just about every other method I've tried (including even
hardware, such as the MDR sysex recorder built into the Yamaha SY99)
were unable to transmit my patch bank to the Siel DK600, but the Linux
'amidi' command could: It's made up of alternating Midi CC's and sysex
dumps in the same file, about 90 of them ("CC...sysex...CC...sysex...").
Apparently, since the Siel DK600 cannot receive whole patch banks and it
needs to be prepared to receive just one patch with a Midi CC command,
if you want to dump all 90 patches, you need a file that contains just
such a weird chain of CC's and single patch dumps. It comes to only
about 4kB, but such a file confuses just about any higher level utility,
or at the very least makes them skip the necessary CC's and just send
the sysexes. Amidi is raw enough that it doesn't care what it's
transmitting, so it just works.
But that brings me back to amidi's wanting to try to just grab the Midi
device, which makes it not work when Jack is running. So what I need is
a Jack-aware app (or at least an Alsa Midi app that doesn't grab the
device exclusively) that's smart enough to work with Jack but still dumb
enough to not care if what it's transmitting.
--
+ 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