Am 18.10.2019 18:57, schrieb David Klann:
On Fri, 2019-10-18 at 11:58 -0400, al davis wrote:
On Fri, 18 Oct 2019 15:44:21 +0000
Mark Murdock <[email protected]> wrote:
> However for production we use Audacity, and when I start Audacity it does
> not recognize the sound card, and thus does not work. If I go to Help -
> Audio Device Info, Audacity says "No Devices Found." Any ideas?
Rivendell takes over a sound card, so you can't use it for anything
else at the same time. This is by design.
This is true. The other option is to use the audio routing app JACK (
https://jackaudio.org/). JACK enables sharing of audio resources
between
higher-level applications (and is supported in Rivendell).
The Rivendell wiki has some information about implementing JACK on a
Rivendell
computer. In my opinion the current best practice is to let Rivendell
start
the JACK service daemon and use the JACK Clients entries in
RDAdmin->Manage
Hosts-><host>->JACK Settings.
One significant caveat when using JACK and Rivendell 3.X is that
jackd(1) MUST
run as Linux user `root`.
MUST.?? I've added a line in systemd configfile "user=rd" and can run
all other application
like audacity, VLC, qjackctl,stereotool... as normal user. But after the
switch from 3.0 to 3.1 i got some
problems with laggy response inside the voicetracker and rdlibrary/edit
marker... as written in my post 7 days ago..
Previous Rivendell versions could work around this
constraint, but it's not possible without code changes in Rivendell
3.X. This
means that all applications using JACK must also run as Linux user
`root`.
This, to me, is another significant reason to use Rivendell computers
only for
Rivendell applications, and use different computers for general audio
applications.
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
