Filipe Coelho | 22 Apr 18:55 2014

[LAU] The first beta of Carla Plugin Host 2.0 is here!

Just bringing the news...

Carla 2.0 is a full rework of the first Carla release.
It's currently under development with a planned release later this year.
Today the first beta is released, and we'll show you what to expect when 
the final version arrives.

To download binaries or source code, jump into the KXStudio downloads 
section. [1]
If you're using the KXStudio repositories, you can simply install 
"carla-git" and "carla-plugins-lv2" instead.
Bug reports and feature requests are welcome! Jump into the Carla's 
Github project page for those. [2]

DISCLAIMER: This is a beta release! Although all features mentioned here 
are working right now, they may be incomplete, have bugs or even eat 
your cat!
You've been warned. ;)

See the top link for some highlights + screenshots.

See you in LAC! :D


Carlo Ascani | 22 Apr 15:10 2014

[LAU] New song made in Linux, A Boring Job

Hi guys,
here is a short song I made during my launch break
(it took me about 20 minutes to complete).

Nothing special, a very short chippy-style tune.
Grab it if you want to play with it:

(direct download)

As usually, the full vanilla Ardour 3 session is under bickbucket:

Feel obligated :D to remix it!

All audio samples are under a
Creative Commons License (see COPYING).

The song is entirely based on those samples:



Carlo Ascani |
skype: carloratm
Philippe Coatmeur | 22 Apr 14:12 2014

[LAU] Microlabel : You made music, now what?


Hi everyone

Microlabel is a small CMS that I made to present my music and make it available to everyone.


  • Baseless : Just drop your correctly tagged music files in the MUSIC dir
    • and Microlabel will build one index page
    • and one page per album
  • Easy link sharing : Copy / paste the link, and the file will play on click
  • Nice URLs
  • Displays Youtube videos
  • Displays musicians latest tweets
  • Displays any image found in the album's dir as a gallery
  • Full Valid HTML / JS / CSS (No flash)
  • Multilingual interface
Please let me know if it is of any use, or if there are bugs, or features that you would like implemented.

Please, let your music fly.


-- Philippe Coatmeur * * *
Linux-audio-user mailing list
Jonathan E Brickman | 20 Apr 22:48 2014

[LAU] Firewire to USB adapter?

Anyone know how well Firewire interfaces perform, when connected to a USB 2.0 port (or even a USB 3 port?) using something like this:

I suppose one of those could possibly solve the USB timing problems; anyone have experiences? 

Jonathan E. Brickman
Ponderworthy Music | | (785)233-9977 |
Linux-audio-user mailing list
Jonathan E Brickman | 20 Apr 22:01 2014

[LAU] A "silence signal"?

Is there such a thing as a "silence signal" in Jack?  In the real world obviously not, silence is the absence of sound pressure, but in Jack shouldn't it be possible to fill the channel with 48 kHz (or whatever) of zeroes?  And more importantly, does anyone have an easy way to do this???  (Or is it already being done?)  I am hearing some faint things in my output that I cannot explain, and a 'silence generator' (if the concept in fact makes sense) would help me figure this out.

Jonathan E. Brickman
Ponderworthy Music | | (785)233-9977 |
Linux-audio-user mailing list
Jonathan E Brickman | 20 Apr 21:48 2014

[LAU] Firewire at last

Almost a week ago, I finally got around to ordering Firewire, in the form of the Behringer FCA202.  And I have to admit that I am quite shocked with how well this unit, the least expensive new Firewire interface of which I am aware, is working.  I had not before heard of any expression "Once you try Firewire, you don't go back," but certainly I won't be going back by choice.  It was a simple lock-and-load, no adjustments other than telling the modules to load at boot and setting the Jack driver to firewire, and the result was astonishing, beautiful quality sound, zero hiccups, no problems at all, all load levels.  And I don't have to worry about its USB A port!  Yahoo!!!!!

And it is interesting, it is by way of this FCA202 that I learned that although the Zitas were working, there was additional latency occurring in the jack-to-zita offload.  It was audible but barely, which presumably means something like 4-6ms.  My testbed for that is playing a MIDI keyboard in piano mode while simultaneously sending the MIDI data to drive the synth; I play live like that fairly often, and although the tiniest difference in attack is acceptable, the Zita method was giving me a bit more, which I brought to almost-AOK by giving the Zita process 80-level priority in schedtool, but which the FCA202 knocked out of the park.  I played through the FCA202 this morning, and it was astonishing, the detail of the tone quality, in both highs and lows.  And I haven't even tried 96 kHz yet :-)  I do not know frankly know whether my Yoshimis and Fluidsynths will play ball well with 96 kHz, I do not know whether it is a very tested configuration.

Jonathan E. Brickman
Ponderworthy Music | | (785)233-9977 |
Linux-audio-user mailing list
Aurélien Leblond | 20 Apr 18:20 2014

[LAU] ams-lv2 ingen patches

> The ingen patches in this page are no longer available:
> I'd like to try them.
> Can someone re-upload them please?
> Thanks!

Hi Filipe,

I re-uploaded them at this URL (and updated the website)

Linux-audio-user mailing list
Linux-audio-user <at>
Philippe Coatmeur | 20 Apr 12:35 2014

[LAU] Two songs made in Qtractor : Takkadum & Kleb Station

Hi there

Takkadum was made mid 2011 right before Automation was available, around 0.4.something, I guess

18 tracks : 10 MIDI tracks and 8 audio ones (using flac containers) ;

  • One 3 channels bus to sidechain-compress the 303-style bass (nekobee) with the kick (a free 808 Sound font played by fluidsynth) using SC3
  • the other cheap DR55 Beat elements are made with Rudolf 556
  • A Hexter synth is doubling the bass in the subs
  • The organ is a Calf organ
  • The Lead synth is a Calf Monosynth
  • The guitar is a g10 double coil Ibanez in a focusrite preamp
  • The microphone is a chinese Neumann knockoff in a focusrite preamp
  • The girl asking "what" ? in the background is called Fatima-Zohra
  • Everybody is EQ'd with LADSPA C* 10 bands Equalizer from CAPS
  • Everybody is comp'd with Calf compressor DSSI
  • There is a LADSPA "Fast lookahead limiter" on the master out bus
  • The final bounce, a "normalize" and a quick and dirty fade out are made in Audacity
Kleb Station (summer 2011 too) uses pretty much the same setup with more instruments plugged in, a little automation (it was just out, and already worked really good) and sidechain-ducked bass ; I play on all the tracks.

BTW the CMS linked is a personal developpement, that automatically builds album pages by reading the tags (and optional - cover & stuff - images). It's yours if you want it.

I used GNU / Linux to make music since around the time Jack was introduced. I spent coutless nights teaching myself how to use just about every single system available, and I always came back to Qtractor. Everything makes sense in Qtractor. And when it seems that it doesn't, a quick message on Rui Nuno's blog and you're out of the hole.

The development is steady, focusing only on the core of the matter, and the result is a solid system, usable right now.

Qtractor does not even try to be everything, it wants to be useful in the middle of the huge Linux audio production ecosystem, talking nice to everybody, implementing new techs & protocols silently, never breaking what's worked so far, bringing it all together. For me, it's the standard against witch I can compare everything else.

Philippe (xaccrocheur)

-- Philippe Coatmeur * * *
Linux-audio-user mailing list
Kevin Cosgrove | 20 Apr 01:27 2014

[LAU] MIDI hardware with Linux

Could someone point me to some reference material to get MIDI 
hardware up and running on my Linux system?  I knew how to do this 
just fine about 3 rev's of Ardour and 1 major rev of the kernel ago.
Unfortunately, all the documentation I'm finding is 7-10 years old.

I'm trying to figure out how to interconnect the *MIDI* of the following:

- M-Audio Delta 1010 hardware MIDI ports
- Mackie Control Universal hardware MIDI ports
- Alesis QS8 hardware synth
- a2jmidid software MIDI interface
- Ardour jack-MIDI ports

What can you folks advise?


Len Ovens | 19 Apr 19:13 2014

Re: [LAU] MIDI over firewire on Linux?

On Sat, 19 Apr 2014, Jonathan E Brickman wrote:

> Thanks!  Do you know of any good such devices which are not very pricey?  I
> found a few out there after reading your post, but they seemed all to be in
> the high-port-count and higher-cost ranges.

Cheapest Audio plus midi has got to be the old ens1370 based cards... free 
if you can find it. Best 16 bit sound for the price. If you don't have a 
pci slot, then the next price range is going to be USB devices... because 
most new systems don't have a FW plug, so an adaptor is required. Also, 
USB covers more people's systems so scale brings prices lower too. USB 
midi ports can be had for less than $30. And of course there are lots of 
USB audio solutions out there including built right into the mic stuff, 
again under $100. USB audio is much more picky about system tuning for low 

Assuming you already have a FW port, it is a better solution than USB, but 
even a 2+2+midi FW unit will cost more than the USB 2+2+midi unit. The 
Focusrite line starts with the pro 14 at $260. They call it 8in and 6 out, 
but I only see 6 physical inputs (and two of those are s/pdif i/o so only 
4 i/o for analog) at $260... yet they sell the 2i2 for usb for $150 or so. 
Presonus is the same, their "Firestudio mobile" is similar features and 
price to the pro 14 and the price matches too. (just note that it seems to 
need breakout cables to get at all the ports... including MIDI) Their 
audiobox USB (2+2+midi) can be had for $140.

So, yes FW costs more, but works better/easier. In the end you have to 
decide how important moneywise these things are to you. The presonus USB 
has been very good and stable... except in USB3 ports on Intel USB3 ports 
which are... broken at least for low latency audio (Intel agrees).

Len Ovens

Linux-audio-user mailing list
Rafael Vega | 19 Apr 17:10 2014

[LAU] Marking soundcard outputs as "default"


I recently started using ALSA Jack plug-in bridge and have this issue: My laptop's sound card has 4 outputs: 1->L, 2->R, 3->Unused?, and 4->"woofer".

When any of the ALSA programs I use (flash player, for example) connect to Jack, they expose 2 outputs and auto connect to the sound card's 1st and 2nd output. I would like them to auto connect so that the 4th output (the woofer) is also used. right now, every time I hit play on grooveshark, for example, I have to go to patchage an make connections from output 1 and 2 in alsa bridge client to 4th output in the sound card.

Is there any way to make this automatic? perhaps by marking outputs 1, 2 and 4 as "default" or "autoconnect"? Maybe there is a hook that detects new clients and I can write a script that connects alsa clients the way I want?

Now that I think about it, this should not apply only to alsa bridge client but any jack client!


Linux-audio-user mailing list