Re: [Jack-Devel] jackd2 does not start with Terratec 6fire USB

On 29.10.2011 15:16, richard lucassen wrote:
> On Sat, 29 Oct 2011 08:59:42 -0400
> Paul Davis<[hidden]>  wrote:
>
>>> Starting jackd on -d hw:0 is ok, everything works fine AFAICS. I can
>>> use qjackctl and play files.
>>>
>>> OTOH: Starting jackd on hw:1 gives the following output:
>> try adding the -S flag to the alsa driver ie.  /usr/bin/jackd -v -r -d
>> alsa -d hw:1 -S
> Nope, same problem.
>
> $ /usr/bin/jackd -v -r -d alsa -d hw:1 -S
> jackdmp 1.9.7
> Copyright 2001-2005 Paul Davis and others.
> Copyright 2004-2011 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
> Cannot create thread 1 Operation not permitted
> Cannot create thread 1 Operation not permitted
> JACK server starting in non-realtime mode
> Cannot lock down memory area (Cannot allocate memory)
> Jack: Create non RT thread
> Jack: ThreadHandler: start
> Jack: playback device hw:1
> Jack: capture device hw:1
> Jack: JackDriver::Open capture_driver_name = hw:1
> Jack: JackDriver::Open playback_driver_name = hw:1
> Jack: Check protocol client 8 server = 8
> Jack: JackEngine::ClientInternalOpen: name = system
> Jack: JackEngine::AllocateRefNum ref = 0
> Jack: JackPosixSemaphore::Allocate name = jack_sem.1001_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
> control device hw:1
> control device hw:1
> audio_reservation_init
> Acquire audio card Audio1
> creating alsa driver ... hw:1|hw:1|1024|2|48000|0|0|nomon|swmeter|-|

hello,
what if you start jackd with period/buffer size of 3 ?

just guessing...


cheers,
doc
> 16bit control device hw:1
> configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2
> periods
> ALSA: final selected sample format for capture: 16bit little-endian
> ALSA: cannot set period size to 1024 frames for capture
> ALSA: cannot configure capture channel
> Jack: JackDriver::Close
> Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0
> Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
> Jack: JackEngine::ClientCloseAux ref = 0
> Jack: JackGraphManager::RemoveAllPorts ref = 0
> Jack: JackPosixSemaphore::Destroy
> Jack: ~JackDriver
> Cannot initialize driver
> Jack: no message buffer overruns
> Jack: ThreadHandler: exit
> Jack: JackPosixThread::Stop
> JackServer::Open() failed with -1
> Jack: Succeeded in unlocking 82241434 byte memory area
> Jack: JackShmMem::delete size = 0 index = 0
> Jack: ~JackDriver
> Jack: Succeeded in unlocking 994 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
>
>> if that doesn't work, try using -P (playback only) i.e.
>> /usr/bin/jackd -v -r -d alsa -P hw:1
> I had already tried that as well, but no way. Strange thing is that:
>
> $ mplayer -ao alsa:device=hw=1.0 somefile.flac
>
> works like a charm.
>

1319894674.5089_0.ltw:2,a <4EABFE6F.3040606 at gmx dot net>