Reliable USB Interface for guitar recording in Ubuntu Studio

Talk about your MIDI interfaces, microphones, keyboards...

Moderators: khz, MattKingUSA

bulevardi
Established Member
Posts: 40
Joined: Tue Oct 07, 2014 8:46 pm
Contact:

Reliable USB Interface for guitar recording in Ubuntu Studio

Postby bulevardi » Tue Oct 07, 2014 9:03 pm

Hi,

I'm looking for a USB interface for recording guitar on Ubuntu Studio.

I have a Behringer UCG102 guitar link cable, but does only seem to work on Windows. (however, I'm planning to change all my stuff to Linux someday in the near future)
In Linux I always get errors in Qjackctl that he cannot find the server, in whatever settings I try. (I'm a total n00b in Linux, but I already took the effort to try a lot of workarounds on linux forums, but they didn't seem to work out)
I borrowed my brother's Line6 Ux2 Pod Studio, same problem. Qjackctl recognizes the USB device, but cannot seem to connect.
Even tried in GNUGuitarinux, same problems.

Now (unless someone can really help me to get the Behringer UCG102 to work), I'm looking for something else to buy, but before I do, I want to make sure I have something that has no (or minimum as possible workarounds) to get an easy plug and play connection. I was looking into several device support databases like the following:
http://www.ffado.org/?q=devicesupport%2 ... OR&filter2[]=perfect
https://wiki.ubuntu.com/HardwareSupport ... SoundCards

But most of the devices don't show up in both lists, does't feel reliable. When I google some of them, I mostly find topics of users searching for help to get them installed... doesn't sound trustworthy!

So, anyone experienced with a good USB interface?
I was thinking about something simple like:
- Focusrite Solo (or 212)
- Roland (Edirol) UA-4FX (discontinued?)
- USBPre 2
- Presonus Audiobox ?
(don't want to spend big money if there is a chance it won't work out later on)

My aim is to record simple stuff first, experiment with the Audacity and Ardour software preinstalled on Ubuntu Studio.

Thanks in advance!

artek
Established Member
Posts: 107
Joined: Tue Nov 06, 2012 10:37 pm

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby artek » Wed Oct 08, 2014 4:57 pm

I have a Behringer UCG102 guitar link cable.

It seems that you use wrong search engine, try search "ucg102 linux" on google or duckduckgo
there is a link to thread on ubuntu forum
http://ubuntuforums.org/showthread.php?t=1457334

bulevardi
Established Member
Posts: 40
Joined: Tue Oct 07, 2014 8:46 pm
Contact:

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby bulevardi » Wed Oct 08, 2014 5:19 pm

artek wrote:It seems that you use wrong search engine, try search "ucg102 linux" on google or duckduckgo
there is a link to thread on ubuntu forum
http://ubuntuforums.org/showthread.php?t=1457334

Thanks, but I already tried these 'solutions' I found on ubuntuforums, and other forums or places on the net I googled which offered workarounds. Didn't really help actually :s

artek
Established Member
Posts: 107
Joined: Tue Nov 06, 2012 10:37 pm

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby artek » Wed Oct 08, 2014 5:59 pm

Can you dump the outcome in a terminal of aplay -l and arecord -l ? :)

bulevardi
Established Member
Posts: 40
Joined: Tue Oct 07, 2014 8:46 pm
Contact:

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby bulevardi » Wed Oct 08, 2014 8:00 pm

artek wrote:Can you dump the outcome in a terminal of aplay -l and arecord -l ? :)


**** Lijst van PLAYBACK hardware-apparaten ****
kaart 0: Intel [HDA Intel], apparaat 0: ALC888 Analog [ALC888 Analog]
Sub-apparaten: 1/1
Sub-apparaat #0: subdevice #0
kaart 0: Intel [HDA Intel], apparaat 1: ALC888 Digital [ALC888 Digital]
Sub-apparaten: 1/1
Sub-apparaat #0: subdevice #0
kaart 1: NVidia [HDA NVidia], apparaat 3: HDMI 0 [HDMI 0]
Sub-apparaten: 1/1
Sub-apparaat #0: subdevice #0
kaart 1: NVidia [HDA NVidia], apparaat 7: HDMI 0 [HDMI 0]
Sub-apparaten: 1/1
Sub-apparaat #0: subdevice #0
kaart 1: NVidia [HDA NVidia], apparaat 8: HDMI 0 [HDMI 0]
Sub-apparaten: 1/1
Sub-apparaat #0: subdevice #0
kaart 1: NVidia [HDA NVidia], apparaat 9: HDMI 0 [HDMI 0]
Sub-apparaten: 1/1
Sub-apparaat #0: subdevice #0
kaart 2: CODEC [USB Audio CODEC], apparaat 0: USB Audio [USB Audio]
Sub-apparaten: 1/1
Sub-apparaat #0: subdevice #0

Translated from Dutch to English: kaart means card; and apparaat means device ;)

bulevardi
Established Member
Posts: 40
Joined: Tue Oct 07, 2014 8:46 pm
Contact:

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby bulevardi » Wed Oct 08, 2014 8:06 pm

When starting QJackctl, and normal settings with the "standard" in/output, I get a message that he couldn't connect with the server:

22:01:40.857 Patchbay uitgeschakeld.
22:01:40.857 Initialisatie van statistieken.
22:01:40.896 ALSA verbindingen aangepast.
22:01:41.242 DBUS : Service is beschikbaar (org.jackaudio.service ook gekend als jackdbus).
Cannot connect to server socket err = Bestand of map bestaat niet
Cannot connect to server request channel
jack server is not running or cannot be started
22:01:41.251 ALSA verbindingen aangepast.
(qjackctl:2348): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed
(qjackctl:2348): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed
22:01:55.097 DBUS : JACK server kon niet worden gestart. Sorry
Wed Oct 8 22:01:44 2014: Starting jack server...
Wed Oct 8 22:01:44 2014: JACK server starting in realtime mode with priority 10
Wed Oct 8 22:01:44 2014: Acquired audio card Audio0
Wed Oct 8 22:01:44 2014: creating alsa driver ... hw:0|hw:0|16|2|44100|0|0|nomon|swmeter|-|32bit
Wed Oct 8 22:01:44 2014: configuring for 44100Hz, period = 16 frames (0.4 ms), buffer = 2 periods
Wed Oct 8 22:01:44 2014: ALSA: final selected sample format for capture: 32bit integer little-endian
Wed Oct 8 22:01:44 2014: ALSA: use 2 periods for capture
Wed Oct 8 22:01:44 2014: ALSA: final selected sample format for playback: 32bit integer little-endian
Wed Oct 8 22:01:44 2014: ALSA: use 2 periods for playback
Wed Oct 8 22:01:49 2014: ERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Wed Oct 8 22:01:49 2014: ERROR: Driver is not running
Wed Oct 8 22:01:49 2014: ERROR: Cannot open client name = dbusapi
Wed Oct 8 22:01:49 2014: ERROR: failed to create dbusapi jack client
Wed Oct 8 22:01:49 2014: ERROR: Unknown request 4294967295
Wed Oct 8 22:01:49 2014: ERROR: CheckSize error size = 0 Size() = 12
Wed Oct 8 22:01:49 2014: ERROR: CheckRead error
Cannot connect to server socket err = Bestand of map bestaat niet
Cannot connect to server request channel
jack server is not running or cannot be started
Wed Oct 8 22:01:55 2014: Released audio card Audio0
Wed Oct 8 22:01:55 2014: Saving settings to "/home/bulevardi/.config/jack/conf.xml" ...
(qjackctl:2348): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed
(qjackctl:2348): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed
22:02:00.641 Kon niet verbinden als client met de JACK server. - Gehele toepassing gefaald. - Kan niet met de server verbinden. Gelieve het berichten venster te lezen voor meer info.
Cannot connect to server socket err = Bestand of map bestaat niet
Cannot connect to server request channel
jack server is not running or cannot be started


When I choose USB Audio Codec as input I get this:
22:03:16.884 DBUS : JACK server kon niet worden gestart. Sorry
Cannot connect to server socket err = Bestand of map bestaat niet
Cannot connect to server request channel
jack server is not running or cannot be started
Wed Oct 8 22:03:16 2014: Starting jack server...
Wed Oct 8 22:03:16 2014: JACK server starting in realtime mode with priority 10
Wed Oct 8 22:03:16 2014: Acquired audio card Audio2
Wed Oct 8 22:03:16 2014: creating alsa driver ... hw:CODEC|hw:CODEC|16|2|44100|0|0|nomon|swmeter|-|32bit
Wed Oct 8 22:03:16 2014: configuring for 44100Hz, period = 16 frames (0.4 ms), buffer = 2 periods
Wed Oct 8 22:03:16 2014: ALSA: final selected sample format for capture: 16bit little-endian
Wed Oct 8 22:03:16 2014: ERROR: ALSA: cannot set period size to 16 frames for capture
Wed Oct 8 22:03:16 2014: ERROR: ALSA: cannot configure capture channel
Wed Oct 8 22:03:16 2014: ERROR: Cannot initialize driver
Wed Oct 8 22:03:16 2014: ERROR: JackServer::Open failed with -1
Wed Oct 8 22:03:16 2014: ERROR: Failed to open server
Wed Oct 8 22:03:18 2014: Saving settings to "/home/bulevardi/.config/jack/conf.xml" ...
22:03:20.979 Kon niet verbinden als client met de JACK server. - Gehele toepassing gefaald. - Kan niet met de server verbinden. Gelieve het berichten venster te lezen voor meer info.
Cannot connect to server socket err = Bestand of map bestaat niet
Cannot connect to server request channel
jack server is not running or cannot be started

Pablo
Established Member
Posts: 1269
Joined: Thu Apr 17, 2008 9:57 pm

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby Pablo » Wed Oct 08, 2014 8:54 pm

16 frames/period is far too low. No wonder that Jack fails to start. The latency you want is unattainable with a USB soundcard, anyway. Even with a PCI soundcard would be tricky.

Start with 1024 frames/period to discard problems due to period too low. You will have time to reduce the latency, if needed (and don't reduce it more than needed by your ears because it is useless and it increases the risk of xruns).

bulevardi
Established Member
Posts: 40
Joined: Tue Oct 07, 2014 8:46 pm
Contact:

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby bulevardi » Wed Oct 08, 2014 9:43 pm

Pablo wrote:16 frames/period is far too low. No wonder that Jack fails to start. The latency you want is unattainable with a USB soundcard, anyway. Even with a PCI soundcard would be tricky.

Start with 1024 frames/period to discard problems due to period too low. You will have time to reduce the latency, if needed (and don't reduce it more than needed by your ears because it is useless and it increases the risk of xruns).

The default was 1024. (did not work)
I went down to 256, 128, and so on to lower it... as others advise here:
http://ubuntuforums.org/showthread.php?t=1457334&page=2

Still not working.

potatopete
Established Member
Posts: 7
Joined: Wed Oct 08, 2014 9:52 am

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby potatopete » Thu Oct 09, 2014 10:51 am

I used to use a Behringer UCG102 guitar link, and I remember all sorts of frustration before I got it to work. However, it definitely, absolutely can work (though the bizarre thing was I only used to be able to hear any input if I also had Rakkarack running!)

I moved onto using an Alesis io2 express some time ago (which is brilliant and works out of the box), but when I get home later I'll take a screenshot of the qjackctl config that I used with the Behringer for you.

bulevardi
Established Member
Posts: 40
Joined: Tue Oct 07, 2014 8:46 pm
Contact:

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby bulevardi » Thu Oct 09, 2014 2:10 pm

potatopete wrote:I used to use a Behringer UCG102 guitar link, and I remember all sorts of frustration before I got it to work. However, it definitely, absolutely can work (though the bizarre thing was I only used to be able to hear any input if I also had Rakkarack running!)

I moved onto using an Alesis io2 express some time ago (which is brilliant and works out of the box), but when I get home later I'll take a screenshot of the qjackctl config that I used with the Behringer for you.

Alrighty :)
Take your time!
I'm not at home at the moment, can't check it in Linux immediately with Rakkarack, but will do ASAP. (means: this weekend, i'm quite busy when I'm home with 2 young kids)

artek
Established Member
Posts: 107
Joined: Tue Nov 06, 2012 10:37 pm

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby artek » Thu Oct 09, 2014 4:11 pm

Can you run jackd manually

Code: Select all

jackd -v -dalsa -dhw:CODEC -p2048 -n3
?
and post output messages?

tbx59
Posts: 2
Joined: Thu Oct 09, 2014 6:15 pm

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby tbx59 » Thu Oct 09, 2014 6:17 pm

potatopete wrote:I used to use a Behringer UCG102 guitar link, and I remember all sorts of frustration before I got it to work. However, it definitely, absolutely can work (though the bizarre thing was I only used to be able to hear any input if I also had Rakkarack running!)

I moved onto using an Alesis io2 express some time ago (which is brilliant and works out of the box), but when I get home later I'll take a screenshot of the qjackctl config that I used with the Behringer for you.


I've been trying to get my alesis io2 to work and it only shows up in jack as midi. I know you said it worked out of the box for you, but could you perhaps look at your settings as that might help mine work. thank you.

asbak
Established Member
Posts: 647
Joined: Thu Sep 11, 2014 3:04 pm

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby asbak » Thu Oct 09, 2014 8:21 pm

Edirol UA-25 works OK under jackd2, probably under jackd1 too but I haven't tested this.
Behringer UMC404 works OK under jackd2. (Apart from the occasional CPU runaway, possibly caused by a build of jackd2 I'm using).

I own both and use the UMC404 to run my bass through Guitarix. Other UMC series models may work too but I haven't tried those.
My samplerates are usually at 44.1 or 48Khz, 3 for buffer, 128 or 256 for periods and you want your priority at > 85. You may also want to ensure that DBUS is disabled.

I can't guarantee you will necessarily get perfect results though, there are a lot of variables involved.

Try something like this at the terminal, don't use qjackctl

Disable Pulseaudio:
edit /etc/pulse/client.conf
Enable this line or add it (you can reverse the procedure later if necessary)
autospawn = no

pulseaudio --kill
(you can start it later again with pulseaudio --start)

jack_control stop
jack_control status (to confirm it is stopped)

jackd -R -P85 -dalsa -dhw:CODEC -p16 -r44100 -p256 -n3

You could try varying the -p256 to -p512 and the -r44100 to -r48000

If none of this works you may be out of luck with that interface or else there is some kind of issue with the version of jack that you're running.

potatopete
Established Member
Posts: 7
Joined: Wed Oct 08, 2014 9:52 am

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby potatopete » Thu Oct 09, 2014 10:25 pm

bulevardi wrote:Alrighty :)
Take your time!
I'm not at home at the moment, can't check it in Linux immediately with Rakkarack, but will do ASAP. (means: this weekend, i'm quite busy when I'm home with 2 young kids)


No worries, I'll just leave this here and you can get to it when you have a spare few minutes! :)

I've dug the UCG102 out of the bottom of a flight case and gone through this myself tonight just to I make sure I'm remembering this all right. Apologies if I explain this in too basic a way, and say things that you already know!

Plug the UCG102 into a USB port and connect your guitar and headphones. Then open qjackctl (but don't click on Start yet). Click Setup. In Setup I have this...

qjackctl1.png


Change yours so it's the same as mine (you can change the Input and Output Devices by clicking on the boxes with the '>' in, and choosing the right device from the menu that appears).

In the 'preset name' at the top type a name for the preset and click Save. Then click on 'ok' in the bottom corner.

Now you can click on Start and hopefully Jack will start with no errors...

...assuming that's the case, strum your guitar and see if you can hear a sound in your headphones. At this point, I can't hear a thing so what I do next is open Rakkerack. Strum your guitar again. Noise! (hopefully!) I have no idea why this USB interface only works this way, it took me a while to figure this out.

Anyway, you may only hear something in your left headphone, if that's the case click on 'Connect' in qjackctl and in the Audio tab expand rakarrack in the left hand column and system in the right hand column. Click on out_2 under rakarrack so it's highlighted and then on playback_2 under system so it's also highlighted and then click on Connect in the bottom left corner. Strum your guitar again and this time you should hear it in both headphones.

qjackctl2.png


In Rackerrack you can click 'FX on' in the top corner if you want and have a play with the presets, or leave it off if you're going to connect your guitar up to your own effects pedals once you get down to recording.

Recording in Ardour:

Once you've opened up a new session in Ardour and added a new Audio track, click on the box just below the name of the track in the mixer strip to the left of your tracks (I've called my new track 'Guitar!', and in my case I'd be clicking the box that has the number 2 in it. If you hover the mouse over it a yellow box would appear that says 'INPUT to trackname'):

ardour1.png


In the Connections Matrix, make sure 'hardware' is the selected tab on the left hand side and click on the green circle in that is next to capture_2 so it isn't there any more.
Then click on the 'other' tab and click in the boxes next to rakarrack out_1 and out_2 so there ARE green circles in them. You should be able to record your guitar to the audio track now.

I hope this works for you!
You do not have the required permissions to view the files attached to this post.

bulevardi
Established Member
Posts: 40
Joined: Tue Oct 07, 2014 8:46 pm
Contact:

Re: Reliable USB Interface for guitar recording in Ubuntu St

Postby bulevardi » Fri Oct 10, 2014 7:24 am

artek wrote:Can you run jackd manually

Code: Select all

jackd -v -dalsa -dhw:CODEC -p2048 -n3
?
and post output messages?

It doesn't start jackd, but gives the following output:
bulevardi@bulevardi:~$ jackd -v -dalsa -dhw:CODEC -p2048 -n3
jackdmp 1.9.10
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2013 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
no message buffer overruns
no message buffer overruns
no message buffer overruns
JACK server starting in realtime mode with priority 10
Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackPosixThread::ThreadHandler : start
Jack: playback device hw:CODEC
Jack: capture device hw:CODEC
Jack: frames per period = 2048
Jack: JackDriver::Open capture_driver_name = hw:CODEC
Jack: JackDriver::Open playback_driver_name = hw:CODEC
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 = 2048
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 Audio2
creating alsa driver ... hw:CODEC|hw:CODEC|2048|3|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 2048 frames (42.7 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 3 periods for playback
Jack: JackSocketServerChannel::Open
Jack: JackServerSocket::Bind : addr.sun_path /dev/shm/jack_default_1000_0
Jack: JackSocketServerChannel::BuildPoolTable size = 1
Jack: JackEngine::Open
Jack: JackClientSocket::Connect : addr.sun_path /dev/shm/jack_default_1000_0
Jack: JackEngine::ClientInternalOpen: name = freewheel
Jack: JackEngine::AllocateRefNum ref = 1
Jack: JackPosixSemaphore::Allocate name = jack_sem.1000_default_freewheel val = 0
Jack: JackEngine::NotifyAddClient: name = freewheel
Jack: JackDriver::ClientNotify ref = 1 driver = system name = freewheel notify = 0
Jack: JackDriver::ClientNotify ref = 0 driver = freewheel name = system notify = 0
Jack: JackConnectionManager::DirectConnect first: ref1 = 1 ref2 = 1
Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 1 ref2 = 1
Jack: JackDriver::SetupDriverSync driver sem in flush mode
Jack: JackGraphManager::SetBufferSize size = 2048
Jack: JackAlsaDriver::Attach fBufferSize 2048 fSampleRate 48000
Jack: JackEngine::PortRegister ref = 0 name = system:capture_1 type = 32 bit float mono audio flags = 22 buffer_size = 2048
Jack: JackGraphManager::AllocatePortAux port_index = 1 name = system:capture_1 type = 32 bit float mono audio
Jack: JackConnectionManager::AddOutputPort ref = 0 port = 1
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackAlsaDriver::Attach fCapturePortList[i] 1
Jack: JackEngine::PortRegister ref = 0 name = system:capture_2 type = 32 bit float mono audio flags = 22 buffer_size = 2048
Jack: JackGraphManager::AllocatePortAux port_index = 2 name = system:capture_2 type = 32 bit float mono audio
Jack: JackConnectionManager::AddOutputPort ref = 0 port = 2
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackAlsaDriver::Attach fCapturePortList[i] 2
Jack: JackEngine::PortRegister ref = 0 name = system:playback_1 type = 32 bit float mono audio flags = 21 buffer_size = 2048
Jack: JackGraphManager::AllocatePortAux port_index = 3 name = system:playback_1 type = 32 bit float mono audio
Jack: JackConnectionManager::AddInputPort ref = 0 port = 3
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackAlsaDriver::Attach fPlaybackPortList[i] 3
Jack: JackEngine::PortRegister ref = 0 name = system:playback_2 type = 32 bit float mono audio flags = 21 buffer_size = 2048
Jack: JackGraphManager::AllocatePortAux port_index = 4 name = system:playback_2 type = 32 bit float mono audio
Jack: JackConnectionManager::AddInputPort ref = 0 port = 4
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackEngine::ClientNotify: no callback for notification = 9
Jack: JackAlsaDriver::Attach fPlaybackPortList[i] 4
Jack: Clock source : system clock via clock_gettime
Jack: JackServer::Start
Jack: JackThreadedDriver::Start
Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackPosixThread::ThreadHandler : start
Jack: JackThreadedDriver::Init real-time
Jack: JackPosixThread::AcquireRealTimeImp priority = 10
Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackPosixThread::ThreadHandler : start
Jack: JackSocketServerChannel::ClientCreate socket
Jack: JackSocketServerChannel::BuildPoolTable size = 2
Jack: JackSocketServerChannel::BuildPoolTable fSocketTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackRequest::Notification
Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel notify = 18
Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel notify = 18
Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel notify = 18
Jack: JackDriver::ClientNotify ref = 1 driver = freewheel name = freewheel notify = 18
Jack: JackEngine::ClientNotify: no callback for notification = 4
Jack: JackEngine::ClientNotify: no callback for notification = 4
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
.... (keeps giving this note)


Return to “Computer Related Hardware”

Who is online

Users browsing this forum: No registered users and 1 guest