[SOLVED] Line 6 Pod X3

Discuss your workplace, instruments, amps, and any other gear.

Moderators: MattKingUSA, khz

Post Reply
finotti
Established Member
Posts: 528
Joined: Thu Sep 01, 2011 9:07 pm
Has thanked: 86 times
Been thanked: 23 times

[SOLVED] Line 6 Pod X3

Post by finotti »

I know this is a long shot, but has anyone been able to use the Line 6 Pod X3 USB interface with Linux?

I know that the kernel now has support for it (since 4.8 or 4.9 -- I'm using 4.9), but I can't get it to work with jack.

It seems it's recognized by the kernel.

Code: Select all

# lsmod | grep pod
snd_usb_podhd           3865  0
snd_usb_line6          21723  3 snd_usb_podhd
snd                    56967  23 snd_oxygen_lib,snd_oxygen,snd_hwdep,snd_seq,snd_hda_codec,snd_usb_audio,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_usb_podhd,snd_usb_line6,snd_usbmidi_lib,snd_seq_device,snd_pcm
usbcore               165880  13 ath9k_htc,usbhid,snd_usb_audio,usb_storage,ehci_hcd,cdc_acm,snd_usb_podhd,snd_usb_line6,xhci_pci,snd_usbmidi_lib,uas,xhci_hcd,ehci_pci 
I also see entries in pulseaudio and alsamixer (although then entries in the latter are weird), and see the hardware (recognized as Pod X3) in qjackctl, but I cannot start the server. I'm getting:

Code: Select all

01:10:44.298 Statistics reset.
01:10:44.304 ALSA connection change.
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
01:10:44.395 ALSA connection graph change.
01:11:07.248 JACK is starting...
01:11:07.249 /usr/bin/jackd -dalsa -r48000 -p1024 -n3 -D -Chw:PODX3,0 -Phw:DGX,0
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
no message buffer overruns
no message buffer overruns
01:11:07.264 JACK was started with PID=19919.
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 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio1
Acquire audio card Audio0
creating alsa driver ... hw:DGX,0|hw:PODX3,0|1024|3|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
ALSA: cannot set period size to 1024 frames for capture
ALSA: cannot configure capture channel
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server
01:11:07.328 JACK was stopped
01:11:09.379 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 = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
01:11:38.772 JACK is starting...
01:11:38.772 /usr/bin/jackd -dalsa -r48000 -p1024 -n3 -D -Chw:PODX3 -Phw:DGX
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
no message buffer overruns
01:11:38.784 JACK was started with PID=19932.
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 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio1
Acquire audio card Audio0
creating alsa driver ... hw:DGX|hw:PODX3|1024|3|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 24bit little-endian in 3bytes format
ALSA: cannot set period size to 1024 frames for capture
ALSA: cannot configure capture channel
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server
01:11:38.845 JACK was stopped
01:11:40.970 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 = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for 4294967295, skipping unlock 
Any suggestions would be appreciated.
Last edited by finotti on Tue Jan 31, 2017 8:02 pm, edited 1 time in total.
CrocoDuck
Established Member
Posts: 1133
Joined: Sat May 05, 2012 6:12 pm
Been thanked: 17 times

Re: Line 6 Pod X3

Post by CrocoDuck »

Let's see what alsa thinks. Repost the output of

Code: Select all

aplay -l

Code: Select all

arecord -l

Code: Select all

amidi -l
finotti
Established Member
Posts: 528
Joined: Thu Sep 01, 2011 9:07 pm
Has thanked: 86 times
Been thanked: 23 times

Re: Line 6 Pod X3

Post by finotti »

Here they are:

Code: Select all

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: DGX [Xonar DGX], device 0: Multichannel [Multichannel]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: DGX [Xonar DGX], device 1: Digital [Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: PODX3 [POD X3], device 0: POD X3 [POD X3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Code: Select all

$ arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: DGX [Xonar DGX], device 0: Multichannel [Multichannel]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: DGX [Xonar DGX], device 1: Digital [Digital]
  Subdevices: 1/1                                                                                                                    
  Subdevice #0: subdevice #0                                                                                                         
card 1: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio]                                                                      
  Subdevices: 0/1                                                                                                                    
  Subdevice #0: subdevice #0                                                                                                         
card 2: PODX3 [POD X3], device 0: POD X3 [POD X3]                                                                                    
  Subdevices: 1/1                                                                                                                    
  Subdevice #0: subdevice #0

Code: Select all

$ amidi -l                                                                                                                  
Dir Device    Name
Attached is a picture of alsamixer (all I/O) with the X3.

Thanks for your help!
Attachments
alsamixer_x3.png
alsamixer_x3.png (28.87 KiB) Viewed 1188 times
CrocoDuck
Established Member
Posts: 1133
Joined: Sat May 05, 2012 6:12 pm
Been thanked: 17 times

Re: Line 6 Pod X3

Post by CrocoDuck »

The Pod seems correctly recognized. What are you using to launch JACK? If qjackctl, make sure you select the Pod in Setup > Advanced > Input Device (and Output Device). If you don't see its name, it should go by hw:2,0.

Perhaps, the problem is that you are using the Pod for input and the DGX for output. Although this is possible, using different devices for input and output usually doesn't work too well. Your Pod seems capable of full duplex tho... Give it a try.
finotti
Established Member
Posts: 528
Joined: Thu Sep 01, 2011 9:07 pm
Has thanked: 86 times
Been thanked: 23 times

Re: Line 6 Pod X3

Post by finotti »

CrocoDuck wrote:The Pod seems correctly recognized. What are you using to launch JACK? If qjackctl, make sure you select the Pod in Setup > Advanced > Input Device (and Output Device). If you don't see its name, it should go by hw:2,0.

Perhaps, the problem is that you are using the Pod for input and the DGX for output. Although this is possible, using different devices for input and output usually doesn't work too well. Your Pod seems capable of full duplex tho... Give it a try.
Thanks for the help! Indeed, it worked!

Thank you so much for all your help and this and my other threads. I've learned a lot from your comments and resources you've provided!
Post Reply