It shows up in qjackctl as hw:2 but gives mw errors: 12:06:31.694 Patchbay deactivated. 12:06:31.726 Statistics reset. Cannot connect to server socket err = Arquivo ou diretório não encontrado Cannot connect to server socket jack server is not running or cannot be started 12:06:31.754 ALSA connection graph change. 12:06:31.934 ALSA connection change. 12:06:40.357 Startup script... 12:06:40.357 artsshell -q terminate Cannot connect to server socket err = Arquivo ou diretório não encontrado Cannot connect to server socket jack server is not running or cannot be started 12:06:40.771 Startup script terminated with exit status=256. 12:06:40.771 JACK is starting... 12:06:40.771 /usr/local/bin/jackd -v -r -dalsa -dhw:2 -r44100 -p256 -n3 12:06:40.773 JACK was started with PID=3103. no message buffer overruns no message buffer overruns jackdmp 1.9.5 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2009 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 non-realtime mode Jack: Create non RT thread Jack: ThreadHandler: start Jack: JackSocketServerChannel::Open Jack: Bind: addr.sun_path /dev/shm/jack_default_500_0 Jack: JackSocketServerChannel::BuildPoolTable size = 1 Jack: JackEngine::Open Jack: Connect: addr.sun_path /dev/shm/jack_default_500_0 Jack: playback device hw:2 Jack: capture device hw:2 Jack: apparent rate = 44100 Jack: frames per period = 256 Jack: JackDriver::Open capture_driver_name = hw:2 Jack: JackDriver::Open playback_driver_name = hw:2 Jack: JackEngine::ClientInternalOpen: name = system Jack: JackEngine::AllocateRefNum ref = 0 Jack: JackFifo::Allocate name = /dev/shm/jack_fifo.500_default_system Jack: JackEngine::NotifyAddClient: name = system Jack: JackGraphManager::SetBufferSize size = 256 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|256|3|44100|0|0|nomon|swmeter|-|32bit Using ALSA driver USB-Audio running on card 2 - EDIROL PCR-1 at usb-0000:00:1a.0-1.2.1, full speed ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode 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: JackFifo::Destroy name = /dev/shm/jack_fifo.500_default_system Jack: ~JackDriver Cannot initialize driver Jack: JackEngine::Close Jack: JackClientSocket::Close Jack: JackServerSocket::Close /dev/shm/jack_default_500_0 Jack: no message buffer overruns Jack: JackPosixThread::Stop Jack: ThreadHandler: exit JackServer::Open() failed with -1 Jack: Succeeded in unlocking 82213408 byte memory area Jack: JackShmMem::delete size = 0 index = 0 Jack: ~JackDriver Jack: JackEngine::~JackEngine 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 start server 12:06:40.898 JACK was stopped with exit status=255. 12:06:40.898 Post-shutdown script... 12:06:40.898 killall jackd jackd: nenhum processo abortado 12:06:41.317 Post-shutdown script terminated with exit status=256. 12:06:42.826 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info. Cannot connect to server socket err = Arquivo ou diretório não encontrado Cannot connect to server socket jack server is not running or cannot be started 2010/7/27, Jeremy Jongepier <jeremy@xxxxxxxxxxxxxx>: > On 07/27/2010 04:27 PM, Bernardo Barros wrote: >> What was it? I'm considering selling my soundcards and buy a "right" one. >> > > Edirol UA-25EX if you'd like to stick with Edirol. > Otherwise any other class compliant USB1 soundcard. But is the PCR-1 not > a class compliant device either? I've just checked the manual and it > seems to be an USB1 device. > > Best, > > Jeremy > _______________________________________________ > Linux-audio-user mailing list > Linux-audio-user@xxxxxxxxxxxxxxxxxxxx > http://lists.linuxaudio.org/listinfo/linux-audio-user > _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
