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

"IL'dar AKHmetgaleev" <[hidden]> writes:

> На Tue, 25 Oct 2011 00:31:42 +0300
> Nedko Arnaudov <[hidden]> записано:
>
>> "IL'dar AKHmetgaleev" <[hidden]> writes:
>> 
>> > Jack dbus plays sound with my EMU 0404 PCI-E with a lot of xruns and
>> > lags in sound. jacd with almost same settings plays well but can't
>> > capture. alsa_in captures well from same device.
>> 
>> "almost" is the key
>> 
>> > Perhaps I did somethign wrong with jack_control. How I can reset
>> > config to default?
>> 
>> jack_control can't reset parameters yet. ladiconf can. The simpliest
>> way to reset all parameters is to delete ~/.config/jack/conf.xml and
>> reactivate jackdbus. "jack_control exit" will tell jackdbus process to
>> quit. Next time jackdbus is [auto]activated, it will use
>> defaults. laditools control apps have "reactivate jack[dbus]" in their
>> context menu.
>> 
>> To reset parameter in ladiconf, double-click in the second column
>> ("Status") and then press OK button.
>
> I put all to default and sound become good. But after I set sampling
> rate back to 44100 lags appears again. jacd and mplayer works right with
> 44100.

Are you using exactly same version of jackd and jackdbus? I've seen
another similar (xruns) report caused by using latest svn/git version of
jack2.

jackd and jackdbus use *exactly* same JACK server code
(libjackserver). With exactly same configuration, there is no known
reason for jackdbus to behave differently when compared to jackd.

You mention mplayer. It is not clear why you think mplayer relates.

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>

1319533391.5009_0.ltw:2,a <871uu1fnqr.fsf at arnaudov dot name>