On 01/02/2013 12:49 PM, Nedko Arnaudov wrote:
> Is the device reservation code useful on RPi? We could have a configure
> option for disabling it.
I'm no dbus expert but without the device reservation code JACK fails to
start with an error that it failed to acquire the audio device. Maybe
this is because I'm not running X? So no fully fledged user session?
> On 01/02/2013 12:49 PM, Nedko Arnaudov wrote:
>> Is the device reservation code useful on RPi? We could have a configure
>> option for disabling it.
> I'm no dbus expert but without the device reservation code JACK fails
> to start with an error that it failed to acquire the audio
> device. Maybe this is because I'm not running X? So no fully fledged
> user session?
AFAIK, and as Robin already pointed, if you build without --dbus, you
get no dbus dependent code in jack components.
> On 01/02/2013 01:05 PM, Nedko Arnaudov wrote:
> [Talking about https://github.com/jackaudio/jack2/pull/25]
>> The jack1/jack2 ABI breakage that happened because of the packed
>> structs is much more worrisome.
> I've tested the code above on my Debian unstable amd64 machine with
> jack_lsp and ardour2.
> Debian compiles all jack clients against jackd1, so I can confirm that
> at least in this case there is no (obvious) jackd1/jackd2 breakage.
I've tried the patch in a gumstix overo and it seem to work if I set the overo as slave. However, when I try
jackd -v -d alsa -d hw:2 -r 44100 &
I get the error below. The overo card is in hw:2, hw:0 is dummy and hw:1 is loopback. The same jackd command works with them but I can't get the output in the headphones with those. I've tried the https://github.com/basilnut/jack2/ but I get the old bus error that I got with the 18.104.22.168 tarball.
I'm using ./waf configure --alsa
Have anyone used jack2 with a gumstix overo?
I'm using a custom image built with the Yocto project and kernel 3.5. Another small problem is that libjack* libraries get installed in /usr/local/lib but jackd looks for them in /usr/lib/... moving then manually solved this (yes, I did ldconfig after installing it :)
Thanks in advance for reading the question.
root@overo:~# jackdmp 22.214.171.124
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackPosixThread::ThreadHandler : start
Jack: playback device hw:2
Jack: capture device hw:2
Jack: apparent rate = 44100
Jack: JackDriver::Open capture_driver_name = hw:2
Jack: JackDriver::Open playback_driver_name = hw:2
Jack: Check protocol client = 8 server = 8
Jack: JackEngine::ClientInternalOpe[ 191.658294] twl4030-codec twl4030-codec: can't set twl4030-hifi hw params: -22
n: name = system
Jack: JackEngine::AllocateRefNum ref = 0
Jack: JackPosixSemaphore::Allocate name = jack_sem.0_default_system val = 0
Jack: JackEngine::NotifyAddClient: name = system
Jack: JackGraphManager::SetBufferSize size = 1024
Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0
Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Jack: JackDriver::SetupDriverSync driver sem in flush mode
creating alsa driver ... hw:2|hw:2|1024|2|44100|0|0|nomon|swmeter|-|32bit
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: cannot set hardware parameters for capture
ALSA: cannot configure capture channel
Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0
Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Jack: JackEngine::ClientInternalClose ref = 0
Jack: JackEngine::ClientCloseAux ref = 0
Jack: JackGraphManager::RemoveAllPorts ref = 0
Jack: JackPosixSemaphore::Destroy name = jack_sem.0_default_system
Cannot initialize driver
Jack: no message buffer overruns
Jack: JackPosixThread::ThreadHandler : exit
JackServer::Open failed with -1
Jack: Succeeded in unlocking 82725920 byte memory area
Jack: JackShmMem::delete size = 0 index = 0
Jack: Succeeded in unlocking 1040 byte memory area
Jack: JackShmMem::delete size = 0 index = 1
Jack: Cleaning up shared memory
Jack: Cleaning up files
Jack: Unregistering server `default'
Failed to open server
On Mon, Jun 10, 2013 at 07:47:13AM -0700, katutxakurra wrote:
> creating alsa driver ... hw:2|hw:2|1024|2|44100|0|0|nomon|swmeter|-|32bit
> configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
> ALSA: final selected sample format for capture: 32bit integer little-endian
> ALSA: use 2 periods for capture
> ALSA: cannot set hardware parameters for capture
> ALSA: cannot configure capture channel
ALSA doesn't like what you've requested for capture. Either disable
capture (use -P) or figure out what jackd is asking for and why it
cannot be provided by the driver.
with -P I got the same error.
There is a recipe for jack_0.121.0 that uses this patch.
Do you think it could be related? I tried to make the same changes in the alsa_driver.c of jack2 but the code is different.