Hi everyone!
To launch jack I run:
/usr/bin/jackd -P80 -dalsa -r44100 -p256 -n2 -Xseq -D -Chw:5,1 -Phw:5,0
This is what I have in my .jackdrc.
In command line, there is no problem. It works perfectly. But if I try
to launch Jack with this parameters through QJackCtl, I get this in the
message window:
creating alsa driver ...
hw:5,1|hw:5,1|256|3|44100|0|0|nomon|swmeter|-|32bit
The 5.0 output becomes 5.1. I don't understand why.
Does anyone have an idea of what happen ?
Sound card: Fast Track Pro
OS: Ubuntu 12.04
Jack: jackdmp 1.9.8
QjackCtl: 0.3.8
pulseaudio-module-jack installed and Fast Track Pro disabled in PulseAudio
Anton Curl
Hi guys, is there a Linux audio user group in Karlsruhe/Germany. If no,
would anyone living in the area like to initiate one with me?
I live in Heidelberg but no one on this list seems to live there too, so
I'm expanding my search, and riding by train doesn't take that long.
Gerald
Hi all,
ever again someone comes up with a question regarding what AI works with
what laptop, so I just thought I would share my results.
Last September I bought a Lenovo w540 laptop, spec'd with
i7 4700mq processor
1TB Samsung Evo 850 SSD system drive
500 GB HDD in Optical drive caddy
8 GB RAM
I configured it to dual boot Windows 8.1 (for my wife;) and kxstudio.
kxstudio runs with the lowlatency 3.13 kernel.
I already owned a TC Impact Twin Firewire interface that I intended to try
out on Linux.
I only just now got to connect the two, the w540 doesn't have Firewire
onboard so I bought a 2 port express card for 20 Euros (brand is inLine,
chipset VIA VT6315).
I can now happily report back that I'm running the TC Impat Twin with ffado
and Jack at 64 frames, 2 buffers, with 2.6msec latency, and it's very
stable till now. That is with HT turned on (I did not yet try it with HT
turned off). At 32 frames I immediately get hundrets of xruns.
The ffado mixer doesn't offer control over the Impact Twin, except for the
sample rate and clock master. That means neither configuring the TC for
standalone operation, nor zerolatency operation will work on Linux (for
now).
In Jack all 14 I/O and the Midi ports of the interface are shown correctly.
I launched a ~50 track ardour 3 project with various LV2 Plugins (IR, Calf
reverbs EQs and Compressors, Invada stuff, Linuxdsp stuff etc.) and got no
xruns at all.
All in all I'm very happy, and I want to thank all the amazing folks out
there that are working hard to make Pro audio work on Linux possible. I'm
only a semi pro "user" (supporting financially a few projects, where I
can), but started out with Linux audio work in 2004, and it is remarkable
where this amazing community got in those 10 years.
Cheers
Moshe
Hello!
There were lot's of Berliners at LAC 2015 and after talking to some of them
we thought it would be nice to start a linux audio user group here in
Berlin.
This is an open call to all Berlin based Linux Audio users and developers!
Let's meet, talk and share knowledge :)
So far we have a mailing list[1] and an empty twitter account[2] (thanks to
Sam :))
Our first meeting will probably be held at C-Base in the next weeks.
We have no agenda yet, everyone is welcome, but me and Sam are more focused
on electronic music stuff.
Any suggestions on the date?
[1] (as soon as the DNS starts working properly we send you the link to
subscribe)
[2] http://twitter.com/LAudioBerlin
Cheers!
--
Bruno Gola <brunogola(a)gmail.com>
http://bgo.la/
Hi!
I already told you about Sebkha-Chott several times on this list,
usually speaking about our releases (always under GNU/Linux, from the
beginning to the end).
Actually, Sebkha-Chott also uses GNU/Linux on stage to manage sound,
lights and video of the whole show (see details below).
I usually don't post shows list or tour schedule here (maybe I should),
but this time it's a big and international festival, so it might be that
some of you will be interested in it.
So Sebkha-Chott will play at Brutal Assault Festival #20 in Jaromer
(Cz), for the third time, but for the first time, we will use the
GNU/Linux live setup they have on tour. The final schedule is not known
yet, but it will be between 5th and 8th of August. If some of you live
near Cz, are metalheads, that's the place you should be (if you ask me,
this year's line-up is really great, the best I've known since I know
this festival).
http://www.sebkhachott.net/15-years-of-sebkha-chott-kourt
Here it is (please note the video and lights part of the system won't
probably play at Brutal Assault due to very tight changeover schedule).
*Description of Sebkha-Chott's live setup*
*Distribution*
All machines, including RPI, are running Debian systems, mostly Jessie.
http://www.debian.org
*Session Handling*
Session handling is managed through ladish and on some control machine
small shell scripts.
http://ladish.org
*Audio*
/Routing/
All the routing is managed through ladish, jack is configured with the
restrict self-connect option.
/Mixing/
The mixing/processing of any audio signals coming from the instruments
on stage or from "virtual sources" inside the machines (synths,
samplers) is done through a bunch of Non-Mixer (probably not uptodate)
instances, running independently one from the other. All these
Non-Mixers finally ends up in the FOH mix or on of the three monitors
mix (which goes to in-ear monitors system). We highly recommend
Non-Mixer for this type of setup, as you don't need a timeline, and
Non-Mixer is really lightweighted, OSC controllable, and flexible.
Ecasound might have done the job too, still.
http://non-mixer.tuxfamily.org/
/Live Looping/
The "instrumental line-up" contains 2 basses, 2 guitars, 3 vocals and a
drumkit, each of them goes to a single looper (for the drums, we only
loop a stereo submix). We use Sooperlooper (probably not uptodate, and
(uglily) patched so that Jack Transport Synchronization with SL as a
master works with it and is recalled when at session load).
http://essej.net/sooperlooper/
/Synths/
Additionnally to the physical instruments, 5 synths are running, 3 of
them polyphonic, 2 of them monophonic. We use Alsa Modular Synth
(probably no uptodate) for this. You might get the patches on github
(see below)
http://alsamodular.sourceforge.net/
/Samplers/
A virtual drumkit is also used, with really-non-drumistic sounds. We use
tapeutape (patched not uptodate version) for this purpose.
http://hitmuri.net/index.php/Software/Tapeutape
/Clic/
We use Klick to send clic in every monitor.
https://github.com/dsacre/klick
*Lights*
Lights are controlled using QLC+. We use four profiles projectors and 4
LED "barres", which are split into 8 RGB segments each, each segment
mightbe controlled independently from the others.
http://qlcplus.sourceforge.net/
*Video**s*
Videos and Moving images are displayed on three V-form screens. Those
videos are displayed using a self-developped software called PytaVSL
(derivating from VSL, a set of pd patches we used on a children show)
and based on Pi3D. This runs on RPIs (old ones, not the big beasts you
might get for 30$!!!).
This lays on a mapped-layers principle, each of them might be mapped
with images or videos, the content can be changed with OSC control, and
you can move or change properties (including visibility/inivisibility)
of a layer using OSC too.
By now, PytaVSL is not recommended for anyone except us (or you will
have to put your hands in it, and you'll see then we're no real devs!!!).
https://github.com/orlammd/pytaVSLhttps://github.com/tipam/pi3d
*Controls*
/MIDI/OSC Routing/
The whole thing is controlled via a centralized OSC/Midi router. We use
Mididings for this purpose, and we highly recommend it, it's a really
good piece of software which makes everything possible in such a setup.
The version we used has been patched to be able to route/filter/manage
OSC messages too. I propose this dirty patch to Dominic and I know he
has worked on this, but I couldn't tell what's the current state of the
software, as we do not use an uptodate version on this neither!
/PedalBoards/
We use DIY pedalboards to trig the sequencers, loopers, and to change
instruments sounds (including synths). These pedalboards are made of a
"règle de maçon", push-buttons and a Teensy2.0 programmation board. It
basically sends an OSC message /pedalBoard/button #number when you press
a button. These messages are then managed by Mididings. There are two
pieces of software for this, one on the board, one on the receiving
computer.
https://github.com/AMMD/Poly_PedalBoard
/Touchscreen Interfaces/
All the mixers, the LASDPA plugs, and in some case the synths are
controlled using touchscreen interfaces. We've developped a programm for
this purpose called Ghislame. Initially developped in C++/Fltk, we
ported it to python/kivy and finally it now uses a JS engine. Initial
versions controlled more things (loopers, synths, mixers, lights), but
in a quite weighted way. Current version (JS) only controls Mixers and
Plugs, but does it much more fluently.
One of these touchscreen interfaces is placed at FOH, so that mix of the
show might be done from FOH. The other ones are sprayed on stage so that
musicians might control their monitoring and some other things easily.
https://github.com/jean-emmanuel/oschtmlguihttps://github.com/AMMD/kvGhislamehttps://github.com/AMMD/Ghislame
/Visual Monitoring/
Several small laptops are placed on stage with LiveDings (Mididings
frontend) and slgui (SooperLooper GUI) running on them.
*Sequencers*
/Midi Sequencing/
seq24 in a really really patched version is used to sequence MIDI. It's
used in matricial mode, and the patches we've done acts on many things:
arbitrary number of beats in a measure, abitrary number of measures in a
sequence, n-tuples, 16x13 matrix (instead of 8x2), play/stop
controllable by Program Changes, and other crappy things. I really don't
recommend our patched version which contains many bugs we learned to
prevent! It's the very first software we've been patching, and....
wel.... seq24 is synced to Jack Transport as a slave. As far as I know
this doesn't work anymore with more recent version of seq24, and as a
result, our version is not uptodate. We will certainly change about this
when we'll have time. We attend much from Non-Sequencer on that point! ;)
/OSC Sequencing/
Over the Midi Sequencing, OSC sequencers are running. One controls the
lights, one controls the videos, another one might send messages to
audio machines (including seq24), and one runs over them all and might
send the BIG SEQUENCE messages!
We use a self-developped software called pyOSCseq. This sequencer can
run looped sequence (as any other sequencer) but also can send on-shots
sequence (many uses in theater context).
https://github.com/jean-emmanuel/pyOSCseq
/Jack Transport/
Jack Transport is used to synchronize every tempi/triggers and so on.
Sooperlooper is Jack Timebase Master, and the other pieces of software
that might be sync to are slaves. Considering that Sebkha-Chott'music is
composed of many sequences in many metrics and tempis, with highly
contrasted way of passing from one to the other, this point was a very
critical point at the beginning of our work with machines (in 2008).
--
ORL
AMMD - Freak & Free Arts Coo[r]p
www.ammd.net - 095 234 72 48
(I never paied attention that reply-to is not positionned by LAU...)
Here's what I've been writing.
Le 04/05/2015 20:56, Bruno Ruviaro a écrit :
> On Monday, May 4, 2015, Ivan K <ivan_521521(a)yahoo.com
> <mailto:ivan_521521@yahoo.com>> wrote:
>
> I have some question regarding versions of Ardour
> that people are using.
>
> Currently, I am running Fedora 20, and their
> software repository has two versions of Ardour available:
>
> ardour-2.8.16-12.fc20
> ardour-3.5.403-1.fc20
>
> I seem to recall that in the past, despite
> Ardour3 being available, some people were still preferring
> to use Ardour2. This seems to be supported by the
> fact that Fedora offers both versions.
>
> Why might one prefer Ardour2 over Ardour3?
>
>
> I think some people stayed with A2 just because it was working well
> for them and didn't want to run risks or change their workflow.
I'm one of these people.
Actually, I've been using Ardour2 for many years, but I was OK to switch
to A3, especially because I was lacking several things (for example the
fact that MIDI bindings weren't recalled after closing the session).
Still I use Ardour for audio recording only, I have other habits
concerning MIDI, and feel in ease with the modular approach allowed by
Jack, so it was not absolutely necessary for me to swtich to A3.
I tried (and am always trying, by the way), but I've experienced many
bugs, including the big ones around MIDI things (MIDI being un-editable,
then MIDI files being lost, and so on), and finally, I kept on Ardour2
for the moment, because, once again, I don't need Ardour to care about
the MIDI.
As I work in a studio and also for audio-engineers schools, I prefer to
have something which works reliably and that I trust in, than a more
bleeding-edge soft, and as far as I've tried for now (but I must say I
didn't try A3 for 4 monthes), it lead me to stay on A2.
I use Debian, and use the stable version when it's about schools, for
example.
There is something else too. I'm not so keen of A3 GUI. It's not that
far from A2, but I'd like the sobriety of A2, and, more precisely, I
really don't like the way Zoom/Scrolling is done in A3, and I really
miss the scroll bars (mightbe I can custom my preferences so that it
looks like that, I didn't try) of A2.
To end up, but that's not really an Ardour pb, much more my workflow
problem, but I feel A3 quite less usable in i3wm, as you need to recall
much more key bindings to be able to close the windows you've opened (i3
doesn't provide window decoration) as there is no "OK" nor "cancel".
Well, that's my reasons. By that time, I would be sad not to have
Ardour2 (still, I've not tried A4).
(to be honest, for my own audio-engineering works, I use non-mixer /
non-timeline, and sometimes ecasound)
Cheers.
Aurélien
--
ORL
AMMD - Freak & Free Arts Coo[r]p
www.ammd.net - 095 234 72 48
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
this is something that has annoyed me endlessly for years, and i still
haven't found a solution.
the issue is minor (that's why i haven't asked before), but annoying
nevertheless.
so:
i'm using qjackctl with the "system tray icon" enabled.
when i close the application window, qjackctl keeps running and is
accessible via the system tray.
cool. that's what i want.
however, every single time i close the main qjackctl window, a balloon
pops up in my notification area, telling me that the "program will
keep running in the system tray" and how to really shut it down.
the first time i read this, this information was informative (i
suppose, it has been years). but no longer.
i already know that the program will keep running. that's why i'm
using the system tray. there's no need to tell me again and again
(even within a single session!).
there *must* be simple way to "not show this message again", without
completely disabling tray notifications. but how?
btw, this is on Debian/sid with xfce4.
fgasdmr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJU0eVfAAoJELZQGcR/ejb4SY0P/3NphEAkGRawvdm4espj7i1J
CIIGtUFTyvsKwFXEqXtAdlHz3/mt9pv1H17LEWdIxOfJ+ziY5dOC1HbAnNSPXmte
91AGmrFCNC8uKSrvCx+kySJEiU4AbNaSY0g8ORKMvOuCPAdO//9qXFBcSRaPX5eb
rT7xtGKK+NYTmFSiPIypjW0ttGabtIjJE+Pg8e674rep+Q63ovxPBTBzkVcvJt4J
udTKPc8+V7vZvC0Q0y4/vwiih5l0+7RypNxuapm+KY8zSgSkGUc2Wug2XMPhaLid
Zmej+Kn/72PZflC5p7uo9JOZkXcShO7SX6296oaFqhFdtxlkUxmggZf/D6eeIGhA
91bACU/+GVgfXE8QUXX0XaifvstBaEwUMdpLIB9lLhC6sdROpl6hHFz/JMJSJYqt
pX0oFI1YNzaT65E0BzOfQa4yxuyNO4BoYZ/C7wg4WtSMd/zHaiK5z9K0nxh1ruDM
5BNgeYNtvQ++FO3V0/eVkOwqab6hdS8/MfLRbro/BmJbNsg4MTDUxHZiL1AzXhIz
6l/SbMsdExY3NgbDQiVmfoW6P9MGDrBO/7n6DZj6g7O5lmtEdR9jhPKpFN3ApJzr
+yVkxrcppph9eNMMUtAWnXh+XBGuuvfdrhakHoAZIaDGa3P7f6GsBjufyrysKGT1
SRBESzDoiLj+5K3rCOYr
=ertZ
-----END PGP SIGNATURE-----
Hi all,
I'm a bit stuck trying to figure this out... I want to run SooperLooper in
several laptops (in a laptop orchestra context), and be able to sync them.
The laptops will be connected to a local network (wifi, or possibly via
ethernet).
>From what I read, I could try doing this either with a MIDI clock, or with
Jack Transport (via NetJack? Though I don't need to send any audio to/from
laptops).
I've installed Rui's QmidiNet and QmidiCtl, but when I try to start them, I
get an error message (setsockopt(IP_ADD_MEMBERSHIP): Invalid argument;
socket(in): your kernel is probably missing multicast support.
).
Are these the right tools for the job? How can I send a MIDI clock to
several other laptops over a local network? Should I be trying NetJack
instead?
Any hints appreciated.... thanks!
Bruno
[*] I've ruled ou NetJack for Jack Transport sync, as it syncs all clients
to one soundcard, where in my case each laptop will be playing with their
own separate soundcard and speaker.
Hi there,
I didn't have access to the LA-lists for a number of months now, and the
list admin was not helpful. I subscribed with this crappy mail provider
now and hope that it will work. Sorry for advertisement and other crap
that might go along with it.
I do have some trouble setting up alsa the way I want it.
The machine is a laptop that I carry around and use at home.
What I want to have:
1) If on the road, the internal card (PCH) should be the default.
2) If at home, the usb card (UA25) should be the default.
I had this working rather reliably at some point, but it doesn't work
anymore.
I have the following in /etc/modprobe.d/alsa-base.conf to prevent race
conditions on boot:
options snd slots=snd_usb_audio,snd_hda_intel
options snd_usb_audio index=0
options snd_hda_intel index=1
However, I experience weird things with /etc/asound.conf, it gets
overwritten on every boot with garbage.
This is what it looks like when I boot without external interface:
defaults.ctl.card 1
defaults.pcm.card 1
defaults.pcm.card 1
defaults.pcm.card 1
defaults.pcm.card 1
defaults.pcm.card 1
When the external interface is plugged in on boot, it looks somewhat
like this (off the top of my head):
defaults.ctl.card 0
defaults.pcm.card 1
defaults.ctl.card 1
defaults.pcm.card 0
defaults.pcm.card 1
defaults.pcm.card 1
defaults.pcm.card 1
defaults.pcm.card 1
Obviously total garbage, and I have no idea what service tries to be
smart here. Any ideas? At least ~/.asoundrc does not get overwritten.
Also, is there a reliable way to do what I want?
Right now I have this in my ~/.asoundrc, but it does not do what I
want. I suspected that alsa would set the only device actually there as
default, but it does not, so with this setup I have no sound on the
road:
defaults.ctl.card 0
defaults.pcm.card 0
Thanks in advance for your help.
Regards,
hollunder
