Hi, i can't start JACK with buffersizes below 512 frames when using the ALSA firewire stack. This is the output of JACK: -------- no message buffer overruns no message buffer overruns no message buffer overruns jackdmp 1.9.11 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 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 80 self-connect-mode is "Don't restrict self connect requests" Jack: JackPosixThread::StartImp : create non RT thread Jack: JackPosixThread::ThreadHandler : start Jack: playback device hw:1 Jack: capture device hw:1 Jack: frames per period = 128 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.1000_default_system val = 0 Jack: JackEngine::NotifyAddClient: name = system Jack: JackGraphManager::SetBufferSize size = 128 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 audio_reservation_init Acquire audio card Audio1 creating alsa driver ... hw:1|hw:1|128|2|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit integer little-endian ALSA: cannot set period size to 128 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::ClientInternalClose ref = 0 Jack: JackEngine::ClientCloseAux ref = 0 Jack: JackGraphManager::RemoveAllPorts ref = 0 Jack: JackPosixSemaphore::Destroy name = jack_sem.1000_default_system Jack: ~JackDriver Cannot initialize driver Jack: no message buffer overruns Jack: JackPosixThread::Stop Jack: JackPosixThread::ThreadHandler : exit JackServer::Open failed with -1 Jack: Succeeded in unlocking 82274202 byte memory area Jack: JackShmMem::delete size = 0 index = 0 Jack: ~JackDriver Jack: Succeeded in unlocking 1186 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 -------- However JACK starts with 512 and higher buffersizes. The same applies when using the FFADO backend. Also using JACK with the onboard audio works with i.e. -p128. I think it's not JACK related and wondered if this is a known limitation of the ALSA firewire part involved and if and how it could be changed. Greetings Thomas ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
