Re: [Jack-Devel] EMU 0404 with jack dbus

PrevNext  Index
DateWed, 26 Oct 2011 08:19:14 +0700
From IL'dar AKHmetgaleev <[hidden] at gmail dot com>
ToNedko Arnaudov <[hidden] at arnaudov dot name>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToNedko Arnaudov Re: [Jack-Devel] EMU 0404 with jack dbus
Follow-UpNedko Arnaudov Re: [Jack-Devel] EMU 0404 with jack dbus
На Tue, 25 Oct 2011 15:51:46 +0300
Nedko Arnaudov <[hidden]> записано:


> Your driver configuration in jackdbus differs from the one you use in
> jackd.
> 
>  * -P jackd parameter corresponds to "playback" jackdbus driver
>    parameter.
>  * --duplex jackd parameter corresponds to "duplex" jackdbus driver
>    parameter.
>  * -o jackd parameter corresponds to "outchannels" jackdbus driver
>    parameter
>  * -i jackd parameter corresponds to "inchannels" jackdbus driver
>    parameter
> 
> AFAIK changes in playback/capture/duplex parameter values can cause
> xruns.

I checked log file. Jack starts in realtime mode:
  JACK server starting in realtime mode with priority 10

Setting playback and capture parameters does nothing for me.

But when I set as device "hw:1,3 - Multichannel Playback (playback)"
which has a lot of playback ports but has no capture ports. All works
fine. Seems like my jackd command line with -P used EMU only for
playback and default (HDA) device for capture. So problem seems to
appear when jack opens device in duplex mode.

Once again starting jackd only for playback and then staritng alsa_in
for capture works fine for me. As well as starting duplex at 48000.

===8@))-<-<
Ильдар Ахметгалеев aka AkhIL
Ср. окт. 26 08:11:31 NOVT 2011
Wed Oct 26 01:11:31 UTC 2011
----------------------------------
Заходите в гости: http://akhil.ru
PrevNext  Index

1319591981.27668_0.ltw:2,a <20111026081914.47cf5103 at artmotion dot home dot net>