Hi all,
For a sound playback system I'm putting together, based on a Raspberry Pi 3,
I'm looking to have 4 channels of input and output, and to have the system
to run automatically at startup.
For this, I'm wondering how to (best) execute zita-a2j and zita-j2a; I've
tried two methods that don't work:
1. ask Qjackctl to execute the following script after startup:
sleep 5
zita-j2a -d hw:CODEC_1
2. execute this script:
qjackctl (with auto-start)
sleep 10
zita-j2a -d hw:CODEC_1
Executing the zita-j2a manually after Qjackctl has finished starting the
jack server does work.
Any pointers greatly appreciated!
Cheers, Steven
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html
Fernando Lopez-Lezcano discussed the pitfalls of using the MOTU AVB
external audio interfaces with Linux in his paper [1] and also in the
keynote at LAC-19.
Let's start another thread around this card.
Fernando mentioned that different firmwares expose different issues, but
downgrading is possible. Issues are:
1. Channels are not persistent and swap around.
2. Total number of channels has been reduced in newer firmwares.
3. An endless card aquisition loop between Jack and Pulseaudio caused by
the long time the card needs to switch sampling rate.
4. Seemingly erratic behavior, opening the device fails, fails again,
again, then works suddenly.
I have a couple of questions and experiences.
Is there a table of the firmware versions somewhere (linuxaudio wiki?)
which tell me which versions has which features (removed)?
Are all the Class Compliant models having the same quirks as listed
above? For example the
MOTU UltraLite AVB versus the MOTU 624 AVB?
Is it possible to use the Thunderbolt port to connect the card to a
Linux computer?
Why can't I tell ALSA to use only the first 2, 4 whatever channels of
the device? I can only open the device if all channels are connected. Is
this always like that or is that a limitation of MOTU's implementation?
On my laptop with only one USB bus, If I connected the MOTU 624 AVB and
then another high speed usb device, the computer could not connect the
later, because the MOTU reserved all the bandwith for itself. Connecting
the other device and then the MOTU worked.
[1] http://lac.linuxaudio.org/2019/doc/lopez.pdf
Max
Hi everyone,
LAC is just a few days ahead now! If you can't make it to the conference,
we'll be video streaming paper presentations. Instructions on how this will
work can be found on the conference website:
https://lac.linuxaudio.org/2019/#streaming
Feel free to ask if you have any questions!
Cheers,
The LAC-19 Team
I sent a long email about testing Ubuntu Studios Controls.
Since it got dumped because it was too long thanks to inserting screen
captures, I then wrote a fixed version and the subject changed creating
broken thread. I'll paraphrase (and I hope this reply is going to the
original thread. Sorry.)
Short version:
- Ubuntu Studio Controls doesn't know about ffado.
- I attempted to force things from the command line, but was unsuccessful.
In fact, I'm not sure I can even get Ubuntu Studo Controls to do nothing.
- Ubuntu Studio Controls also has a problem with retaining the selections
for bridging, etc. If you check them off, then logout/login or reboot they
are back to default (checked). The last time I logged in and started Carla,
there were 12 in/out's for the AF12 and 2 captures for the on board sound
card...
At first during my messing around I could only get the long form of the
port names to show up (i.e. 00148605c4409ac_Unknown_out,
00148605c4409ac_Unknown0_out, etc.) and not human readable names like
capture_1, etc. But, something I did is now causing the human readable
version to appear...don't what caused this and not sure if it will be there
when I boot tomorrow...
I've been doing some experiments with the system I have.
The system: the mobo has onboard 8 channels (front panel L/R, rear panel
L/R, rear panel line out L/R, rear panel sub L/R) and a Echo AF12 on
firewire.
At this point UBS Controls can select between the on board and the AF12 (I
assume when the AF12 is selected and 12 channels appear in Carla or
Patchage this is via ALSA)
Observations:
- alsamixer shows both onboard and AF12
- when AF12 is selected in alsamixer, alsamixer shows nothing
- when on board is selected in alsamixer, alsamixer shows the 8 outputs
- when selected in UBS Controls the associated ports are shown in
Carla/Patchage
- when on board is selected, 8 ports are shown, but only the front panel
L/R produce any signal when connected in Carla/Patchage
(all 8 are unmuted and at 0db in alsamixer)
anybody know how to get the other 6 outputs working?
- when AF12 is selected 12 channels are shown in Carla/Patchage
With on board selected and players/plugins started and connected between
player and front panel L/R all appears good and sounds ok.
With AF12 selected and same player/plugin combo is made sounds good, except
occasionally REALLY nasty high volume (as in speaker/ear damaging loud)
digital burst happens.
In order to test with just ffado I attempted to adapt a script I use on
another pc to force only jack. The adapted part shown below:
#!/bin/bash
set -x
killall -9 jackd jackdbus
#jack_control ds alsa dps capture none dps playback none
jack_control ds firewire dps capture none dps playback none
#jack_control dps device hw:PCH
jack_control dps rate 48000
jack_control dps nperiods 2
jack_control dps period 1024
jack_control start
pactl unload-module module-udev-detect
pactl unload-module module-alsa-card
pactl unload-module module-jackdbus-detect
pactl load-module module-jack-sink client_name=PulseOut channels=2
connect=no
pactl load-module module-jack-source client_name=PulseIn channels=2
connect=no
set +x
exit
This results in the channels of the AF12 being listed like this:
firewire_pcm
00148605c4409ac_Unknown_out
00148605c4409ac_Unknown0_out
00148605c4409ac_Unknown1_out
00148605c4409ac_Unknown2_out
00148605c4409ac_Unknown3_out
00148605c4409ac_Unknown4_out
00148605c4409ac_Unknown5_out
00148605c4409ac_Unknown6_out
00148605c4409ac_Unknown7_out
00148605c4409ac_Unknown8_out
00148605c4409ac_Unknown9_out
00148605c4409ac_Unknown10_out
00148605c4409ac_Unknown11_out
Where Unknown_out is the 1st channel of the AF12, Unknown0_out is the 2nd
channel, etc. (Unknown11_out is the midi port)
I do not know how to get human readable names as can be done in Qjack...
Anybody know how to do this from the command line? Or set the name of the
device to something other than firewire_pcm?
So far I have NOT been able to duplicate the crazy noise spikes I was
getting with alsa running the AF12.
Oh, and while alsamixer will allow the selection of the AF12, alsamixer
then says the AF12 has no controls.
So, to control the gains and such one has to figure out how to stop the
alsa control of the AF12 and then start ffado to make any changes?
Len said:
"It does not use ffado at all but rather the built in ALSA firewire module
stack. This means, do not try to use ffado-mixer, bad things will happen.
Use alsamixer or the qasmixer (which is GUI based) instead.
So far, anyone I have talked to that has had problems with fw devices in
the past few years, since fw was added to ALSA, has had those problems
because they tried to use ffado bits without first removing the alsa bits.
So I am wondering how many people have firewire devices that have found
the alsa drivers for firewire, when used correctly, don't work for them."
So, I admit to some confusion...
Until yesterday (when I added the back port) after boot the sound
system would show a 12 channel device.
At that point I would start Qjack. It's configuration is set to start
ffado with 12 channels.
I then hit start in Qjack and then 12 in/out ports would show in Qjack
> Connect.
If I understand your comment, this would be running the alsa stack AND
the ffado stack against the
firewire device? (In this case an AF12.)
So, now if I start JACK from the UBS Controls, it is using only the ALSA stack?
And the ports that show up in, say Patchage, are ALSA ports?
So, when I'm doing "pro" audio with UBS I don't need ffado now?
And, if so, how does one, for instance, send firmware updates to a fw device?
(not that I expect to do that with an AF12...they stopped making it. :( )
Mac
do a "ps -A" in commandline ... think you need to kill jackdbus, too...
> Date: Wed, 17 Apr 2019 15:49:18 -0400
> From: Mac <macdroid53(a)gmail.com>
> To: linux-audio-user <linux-audio-user(a)lists.linuxaudio.org>
> Subject: [LAU] JACK, Qjackctl, and ffado
> Message-ID:
> <CAHEqMkFrwpL7=sdF5CY4kh=kvSbwTk6peNT=MetAj3yjEXjerQ(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> I have a system running UbuntuStudio 18.04 and I use ffado with jack for my
> firewire AF12.
>
> When I boot the system and start things up with Qjackctl all is good.
> (Qjackctl runs a script that starts Calf plugins, zita-lrx, some meters,
> and connects up a variety of things the the ins/outs that ffado presents.
> Most notably the output of zita-lrx forming a tri-amp system. The input to
> zita-lrx coming from the Calf plugins. )
>
> All works fine, as long as I have no occasion to hit the stop button in
> Qjackctl. It runs another script that shuts down Calf, zita-lrx, and meters.
>
> But, if I attempt to start things again, it says it can't start.
>
> If I kill the ffado-dbus-server, then start ffado mixer (this apparently
> starts the ffado-dbus-server), then open Qjackctl again it's already
> running. At this point, if I run the script mentioned above, all is good
> again.
>
> Does this imply that I'm not shutting down correctly and leaving ffado in
> some zombie state?
>
> Is there a proper shutdown that won't cause this?
>
Hi,
I have a system running UbuntuStudio 18.04 and I use ffado with jack for my
firewire AF12.
When I boot the system and start things up with Qjackctl all is good.
(Qjackctl runs a script that starts Calf plugins, zita-lrx, some meters,
and connects up a variety of things the the ins/outs that ffado presents.
Most notably the output of zita-lrx forming a tri-amp system. The input to
zita-lrx coming from the Calf plugins. )
All works fine, as long as I have no occasion to hit the stop button in
Qjackctl. It runs another script that shuts down Calf, zita-lrx, and meters.
But, if I attempt to start things again, it says it can't start.
If I kill the ffado-dbus-server, then start ffado mixer (this apparently
starts the ffado-dbus-server), then open Qjackctl again it's already
running. At this point, if I run the script mentioned above, all is good
again.
Does this imply that I'm not shutting down correctly and leaving ffado in
some zombie state?
Is there a proper shutdown that won't cause this?
