OK. This has been a busy day ;)
In response to Jussi Laako report, I've rushed yet another release today:
qjackctl 0.2.7b is out.
This time it tries to fix those OSS driver issues as briefly discussed
here on jackit-devel list (see below) and advances the setting of
Periods/Buffer, although not officially available yet.
It's important to note that, for you to try now the OSS driver support
with current JACK CVS, please set Periods/Buffer to zero (0), otherwise
the server won't start, complaining about an invalid command line option
Once this parameter is available from jackd, as Jussi promised, you can
change it to some meaningful value.
Bear with me on:
Enjoy, as always.
rncbc aka Rui Nuno Capela
> Jussi Laako wrote:
>> I will add the -n (--nperiods) parameter to the OSS driver shortly.
> OK. Soon, the -n,--nperiods corresponding setting will get enabled on
> the setup dialog, whenever the oss driver gets selected. Pretty simple,
>> Found a few features from the qjackctl-0.2.7:
>> - If duplex is selected, both defined devices should
>> be specified at the commandline (-C & -P, unless either
>> is "(default)"), if capture is selected, device should be
>> specified using -C and number of output channels should
>> be set to zero "-o 0" and vice versa for the playback
>> only thing.
>> - If number of input or output channels is set to zero,
>> it should (?) also be passed to the jack commandline
>> (halfduplex operation).
>> - If "(default)" is selected as device, no corresponding
>> -C or -P should be specified (cosmetic).
>> So -C or -P defines non-default device and "-i 0" defines playback-only
>> and "-o 0" defines capture-only. This is a minor difference with these
>> parameters compared to ALSA driver.
> OK. I'll queue all this fixes very shortly. As you noticed, my
> assumptions were just based on the ALSA driver. Thanks for clearing
> this out, Jussi.
Get latest updates about Open Source Projects, Conferences and News.