I cannot connect audacity and jack. There is no "jack" option for
source or sink in audacity and audacity does not show up in the
connection window of qjackctl
I cannot select jack as the default input or output in system settings.
In the past I have had no trouble with any of that.
I have connected "capture_1" to "playback_1" and playback_2" that orks
well with lo latency.
On ubuntu 18.04, audacity 2.21 and jackd2
What am I missing?
Worik
--
If not me then who? If not now then when? If not here then where?
So, here I stand, I can do no other
root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)
Hey hey,
is there any - easy way - of interfacing a PBX (phone system) software like
Asterisk or Freeswitch with JACK? Preferrably with the commandline only. The
usecase is simply to use the computer with microphone and speakers as the
handset, possibly directly connecting other JACK applications into the phone
conversation.
I know that an FXO card is required to hook up the computer to the phone
network and that the machine can then serve as a voicemail or routiing system.
I also know that Asterisk has - more likely had - a JACK module, but
apparently this has never been intended to work perfectly, nor has it been
maintained in years.
I'd be grateful for any tips and hints.
Best wishes,
Jeanette
--------
* Website: http://juliencoder.de - for summer is a state of sound
* SoundCloud: https://soundcloud.com/jeanette_c
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* GitHub: https://github.com/jeanette-c
* Twitter: https://twitter.com/jeanette_c_s
You should take me as I am
'Cause I can promise you
Baby, what you see is what ytou get <3
(Britney Spears)
Hi all.
I've been using Ubuntu Studio since 14.04, always run with Jack as the main audio server and generally never had any issues. Upgraded to Ubuntu Studio 18.04 and everything was fine for some months but within the last week or so I can't get the Jack Server to Stop from within QJackCtl, the application just hangs, making it quite a pain to change between using my internal and external devices!
Any idea what may be causing this or steps to fault find the issue?
Currently I have set QJackCtl to not connect on startup, so I can killall qjackctl, kill -9 jackdbus(pid), restart qjackctl, select correct config and start the server running. So I can get on with my work but obviously it would be nice if things worked as they should again.
Regards, Dale.
On Sat, July 7, 2018 11:39 am, Dale Powell wrote:
> I've tried with the d-bus settings both enabled and disabled with no
> overall joy but have to admit I've always been confused into exactly what
> affect these really have on the system....
I believe the setting "Enable D-Bus interface" is to control whether the
QJackControl application exposes D-Bus controls, and the "Enable JACK
D-Bus interface" controls whether the D-Bus enabled version of jackd is
started or the original non-D-bus version.
--
Chris Caudle
Has anyone figured out the effect of "Stereo in/IR" control on the ir.lv2
plugin? From the naming I would have expected similar to the "Dry" and
"Wet" level controls, but the two sliders (labeled from 0% to 150%) do not
have the same effect. I can set the Stereo In and IR slider both to 0%
and still hear the IR effect on the bus, when I set either to 150% I do
not hear an obvious change.
I am not using the envelope controls currently, do they perhaps interact
with those controls in some way? I noticed that when I hit the "Reset"
button the envelope and length controls both went back to 100%, the stereo
in and IR controls both went back to 100%, but even with the envelope
active I could not tell what effect the stereo in and IR controls had.
Any hints?
--
Chris Caudle
