How To Properly Connect Pod Hd Pro To A Linux System

[frmat]

To whom it may concern; here's how you get your POD HD Pro to function properly with a linux based OS.

 

First off, you need a supported OS to run inside of your Linux OS, so get yourself a disc image (.iso) of Windows/OS-X. Note that I have only tried this with Windows XP Pro 32-bit under Ubuntu 12.04, so I really have no idea whether or not it works the same for OS-X and/or other hosts.

 

Next, you'll need to set up a virtual system using a neat application called VirtualBox. Instructions on how to do this can be found in this video:

(Virtualbox can be downloaded from https://www.virtualbox.org/)

 

Now, once you've got your virtual system up and running and have installed the guest additions and what not, there are a few steps you need to take in order to enable USB support in you guest OS:

 

1. Shut down your virtual machine.

2. Connect your Pod.

3. In the Virtualbox UI, go to the virtual machine's "settings" page.

 

4. Under the "USB" tab, make sure that the option "Enable USB controller" is checked.

    Make sure the option "Enable USB 2.0 (EHCI) controller" is NOT checked.

 

5. Below the two aforementioned options is a list of USB device filters (probably empty).

    Click the small icon on the right hand side to add a filter, you should see your Pod listed along with any other connected devices.

    Create a filter for the Pod (no need to change any filter settings), and make sure it is checked.

 

6. There is a user group created by VirtualBox, called "vboxusers". You need to add yourself to this group.

    If you do not have the "Users and Groups" application in your user interface, open a terminal and enter the following command:

    sudo adduser "username" vboxusers, "username" being whatever your username is (without the quotation marks).

 

7. Reboot your computer.

 

8. Run your virtual machine and connect you Pod. If it isn't recognized by the guest OS, look under "Devices"»"USB devices" in the

    top menu bar. Make sure the Pod is checked.

 

That should be just about it, although I may have left something out.

 

[TheRealZap]

nice of you to share... but using a virtual machine, is hardly real use in the linux environment...

to anyone reading this, i'd suggest saving the headaches and just installing a supported OS....

but i do realize that some people insist on using whatever, so your suggestion is a workaround of sorts.

[frmat]

Of course it isn't. Perhaps I should have named the topic differently. It is my understanding that use in the actual Linux environment will not be possible until Line 6 decides to develop software to support it.

However, the obvious benefit of this setup is not having to reboot into a different OS to connect your Pod. Also, the guest OS in virtualbox can share dedicated folders with the host system, so that you have easy acess to anything that might be relevant to your work.

[snhirsch]

Of course it isn't. Perhaps I should have named the topic differently. It is my understanding that use in the actual Linux environment will not be possible until Line 6 decides to develop software to support it.

However, the obvious benefit of this setup is not having to reboot into a different OS to connect your Pod. Also, the guest OS in virtualbox can share dedicated folders with the host system, so that you have easy acess to anything that might be relevant to your work.

 

I wouldn't hold my breath for native Linux support.  But, the VM approach is quite workable.  I've been happily running HD500 and Variax Workbench under VMware Workstation since last fall (along with Fender FUSE and a bunch of other MI related apps).

 

The one "gotcha" is that under Windows XP the VMware audio device prevents Line6 Monkey from initializing.  This just means I need to deactivate the sound card and restart on the rare occasions when I need to flash firmware.  There are no conflicts under normal use of either workbench.

[dbgrant]

I've been using VirtualBox, Windows 7 guest in Ubuntu 12.10 host with no problems. I posted the method and one or two workarounds (similar to frmat's here) in this thread...

 

http://line6.com/support/message/390334

 

Long live the penguin. Cheers!

 

db

[spaceatl]

[helvede]

Hei!

I can report that the "Line 6 POD HD500X" works too here on a amd64 arch linux box with at the moment 3.12.0-1 stock arch kernel and "virtualbox-bin 4.3.0-1" from aur && "virtualbox-guest-iso 4.3.2-1" && "virtualbox-host-modules 4.3.2-4" with "POD HD500X Edit 2.23" and "Line6 Monkey 1.65"

I'm quite happy about that. BUT a NATIVE LINUX Software would be great!! just wanted to say that. probaly we should start some signing that we (and line 6) see how many Linux users with Line6 porducts are out there ...

thanks "frmat" for the hint with unchecking the ehci box, that lead to success.

 

windows is NO alternativ for me!

[hitmaker]

I run into a problem at step 5...

 

In this case, 'Pod X3 Live' is not listed as a device in the add filter menu within virtualbox settings. (btw I can confirm it is definitely connected and turned on)

 

Any ideas?

 

I'm running the VM inside of Ubuntu 13.10 on a lenovo B570 laptop

 

 

Best wishes

Sean

[dgiorgetti80]

Hi guys, thanks for the helpfull tips.

I managed to run HD500x edit and Monkey with WinXP on a VM (on Ubuntu 12.04).

But I have big problems in recording. I tried with Audacity and with Renoise but for both the result is the same: they see the device (POD HD500x) but the recording does not work at all (it is stuck, time does not proceed).

Anyone ever managed to use POD HD stuff also as ASIO interface on a VM?

Thanks

 

[joel_brown]

Isn't Linux a server thing ?  I never heard of anyone running it at home other than as a curiosity.

[TheRealZap]

not really... there is even ubuntu studio which is a distro made entirely for music creation....

also mac osx is linux based, as well as the new chromebooks....

 

its more than a server thing... but not quite mainstream.

 

Isn't Linux a server thing ?  I never heard of anyone running it at home other than as a curiosity.

[dgiorgetti80]

For me it's the only OS since years, that's why I'm a bit disappointed I can't have my new POD HD working on it (other audio stuff usually works pretty smoothly). I don't want to go back to Win just because of that.

[joel_brown]

According to the Ubuntu forums, Mac OSX is based on BSD Unix not Linux.  I guess you could make the connection that they are both Unix.  Although BSD is Berkley and Linux is based on the teaching version of Unix called Minix.

 

Sounds pretty far from mainstream on a desktop...  But I guess it must do something you like to be worth that.

[gunpointmetal]

Linux runs super lightweight usually and if you have the know-how it can be configured to be really, really powerful in an audio production environment...except nobody makes compatible hardware!

[zaboomafoo]

According to the Ubuntu forums, Mac OSX is based on BSD Unix not Linux.  I guess you could make the connection that they are both Unix.  Although BSD is Berkley and Linux is based on the teaching version of Unix called Minix.

 

Sounds pretty far from mainstream on a desktop...  But I guess it must do something you like to be worth that.

 

I wouldn't say that linux is based od minix.

http://en.wikipedia.org/wiki/MINIX#MINIX_and_Linux

 

Anyway, this is not the place to go into that type of discussion :) .

 

I can only say that linux works well on a desktop or laptop (fedora, ubuntu, ,,,). It provides very much all the software and features a regular user would need (office, internet, etc). It is great for developers. It also works well for recording (Ardour), although not all hardware is supported (mainly because some manufacturers ignore it). There is also good support for graphical design / 3D modeling (blender). I am using linux as my main platform for more than 10 years now. Using windows in VM as described above only to do thing like update firmware on my hd500, which I will probablty not need to do any more based on what is happening with hd line :).

 

zbf

[edfardos]

I've got the Line6 Edit software (Spider MkII) running in wine, and there is some midi communication according to the analyzer, but it cannot send patches back and forth.  Other windows-midi software works fine, so I don't think it's my cables/setup.   Here's my notes, in case somebody wants to pickup the ball.  It appears to be opening the correct midi ports, but the Line6 software has no way of specifying a port, so make sure your first linux midi ports connect to your device.

 

 

in order to make the audiophile the first midi device run:

 

   # rmmod snd_seq_dummy  (gets rid of midithrough)

 

# aconnect -o

client 16: 'M Audio Audiophile 24/96' [type=kernel]

    0 'M Audio Audiophile 24/96 MIDI'

 

# aconnect -i

client 0: 'System' [type=kernel]

    0 'Timer           '

    1 'Announce        '

client 16: 'M Audio Audiophile 24/96' [type=kernel]

    0 'M Audio Audiophile 24/96 MIDI'

 

 

 

in/out both map to 16:0 in bugtrace  - so that's good

 

run it like this:

 

   WINEDEBUG=+midi wine SpiderValveEdit.exe

 

 

$ WINEDEBUG=+midi wine SpiderValveEdit.exe

p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory

fixme:wincodecs:PngDecoder_Block_GetCount stub

fixme:thread:start_thread Started native thread 00000041

fixme:thread:start_thread Started native thread 00000042

fixme:thread:start_thread Started native thread 00000043

fixme:thread:start_thread Started native thread 00000044

trace:midi:ALSA_midMessage (0000, 0064, 00000000, 00000000, 00000000);

trace:midi:ALSA_MidiInit Initializing the MIDI variables.

trace:midi:ALSA_AddMidiPort OUT (0:System:kernel:0:Timer:0)

trace:midi:ALSA_AddMidiPort IN  (0:System:kernel:1:Announce:0)

trace:midi:ALSA_AddMidiPort OUT (16:M Audio Audiophile 24/96:kernel:0:M Audio Audiophile 24/96 MIDI:90002)

trace:midi:ALSA_AddMidiPort MidiOut[0]  name='L"M Audio Audiophile 24/96 MIDI"' techn=1 voices=0 notes=0 chnMsk=ffff support=0

        ALSA info: midi dev-type=90002, capa=0

trace:midi:ALSA_AddMidiPort IN  (16:M Audio Audiophile 24/96:kernel:0:M Audio Audiophile 24/96 MIDI:90002)

trace:midi:ALSA_AddMidiPort MidiIn [0]  name='L"M Audio Audiophile 24/96 MIDI"' support=0

        ALSA info: midi dev-type=90002, capa=0

trace:midi:ALSA_MidiInit End

trace:midi:ALSA_midMessage (0000, 0035, 00000000, 00000000, 00000000);

trace:midi:ALSA_modMessage (0000, 0064, 00000000, 00000000, 00000000);

trace:midi:ALSA_modMessage (0000, 0001, 00000000, 00000000, 00000000);

trace:midi:ALSA_modMessage (0000, 0002, 00000000, 0032F20C, 00000054);

trace:midi:modGetDevCaps (0000, 0x32f20c, 00000054);

trace:midi:ALSA_midMessage (0000, 0036, 00000000, 0032F440, 0000004C);

trace:midi:midGetDevCaps (0000, 0x32f440, 0000004C);

trace:midi:ALSA_midMessage (0000, 0036, 00000000, 0032F41C, 0000004C);

trace:midi:midGetDevCaps (0000, 0x32f41c, 0000004C);

trace:midi:ALSA_midMessage (0000, 0036, 00000000, 0076B0A8, 0000004C);

trace:midi:midGetDevCaps (0000, 0x76b0a8, 0000004C);

trace:midi:ALSA_midMessage (0000, 0037, 0032F3EC, 00145CA4, 00030000);

trace:midi:midOpen (0000, 0x145ca4, 00030000);

trace:midi:midiOpenSeq Outport port 0 created successfully

trace:midi:midiOpenSeq Input port 1 created successfully

trace:midi:midOpen Input port :1 connected 16:0

trace:midi:midOpen Created thread for midi-in

trace:midi:MIDI_NotifyClient wDevID = 0000 wMsg = 961 dwParm1 = 0000 dwParam2 = 0000

trace:midi:ALSA_midMessage (0000, 0039, 00008000, 0076B110, 00000040);

trace:midi:midPrepare (0000, 0x76b110, 64);

trace:midi:ALSA_midMessage (0000, 003B, 00008000, 0076B110, 00000040);

trace:midi:midAddBuffer (0000, 0x76b110, 64);

trace:midi:ALSA_midMessage (0000, 0039, 00008000, 0076B150, 00000040);

trace:midi:midPrepare (0000, 0x76b150, 64);

trace:midi:ALSA_midMessage (0000, 003B, 00008000, 0076B150, 00000040);

trace:midi:midAddBuffer (0000, 0x76b150, 64);

trace:midi:ALSA_midMessage (0000, 0039, 00008000, 0076B190, 00000040);

trace:midi:midPrepare (0000, 0x76b190, 64);

trace:midi:ALSA_midMessage (0000, 003B, 00008000, 0076B190, 00000040);

.

.

.

trace:midi:ALSA_modMessage (0000, 0003, 0032F3BC, 00143F94, 00030000);

trace:midi:modOpen (0000, 0x143f94, 00030000);

trace:midi:midRecThread Thread startup

trace:midi:midRecThread Thread loop

trace:midi:modOpen Output port :0 connected 16:0

trace:midi:MIDI_NotifyClient wDevID = 0000 wMsg = 967 dwParm1 = 0000 dwParam2 = 0000

trace:midi:ALSA_modMessage (0000, 0005, 00008001, 0076F858, 00000040);

trace:midi:modPrepare (0000, 0x76f858, 64);

trace:midi:ALSA_modMessage (0000, 0008, 00008001, 0076F858, 00000040);

trace:midi:modLongData (0000, 0x76f858, 00000040);

trace:midi:modLongData dwBufferLength=6 !

trace:midi:modLongData                  F0 7E 7F ... 06 01 F7

trace:midi:modLongData destination 16:0

trace:midi:MIDI_NotifyClient wDevID = 0000 wMsg = 969 dwParm1 = 76F858 dwParam2 = 0000

trace:midi:ALSA_modMessage (0000, 0006, 00008001, 0076F858, 00000040);

trace:midi:modUnprepare (0000, 0x76f858, 64);

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:ALSA_modMessage (0000, 0004, 00008001, 00000000, 00000000);

trace:midi:modClose (0000);

trace:midi:MIDI_NotifyClient wDevID = 0000 wMsg = 968 dwParm1 = 0000 dwParam2 = 0000

trace:midi:ALSA_midMessage (0000, 003D, 00008000, 00000000, 00000000);

trace:midi:midStop (0000);

trace:midi:ALSA_midMessage (0000, 0038, 00008000, 00000000, 00000000);

trace:midi:midClose (0000);

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

fixme:midi:midRecThread Unexpected event received, type = b from 16:0   #pressed send on device

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

 

 

 

.... 

the third to the last line is me "sending" a patch via the tap-tempo button on the HD100 head.

 

I desperately want to get this running on Linux.  Windows isn't an option for me anymore.

 

 

fwiw,

-edfardos

[smrybacki]

Holy crap!  For a minute there, I thought I was at work in 1983!

 

 

I've got the Line6 Edit software (Spider MkII) running in wine, and there is some midi communication according to the analyzer, but it cannot send patches back and forth.  Other windows-midi software works fine, so I don't think it's my cables/setup.   Here's my notes, in case somebody wants to pickup the ball.  It appears to be opening the correct midi ports, but the Line6 software has no way of specifying a port, so make sure your first linux midi ports connect to your device.

 

 

in order to make the audiophile the first midi device run:

 

   # rmmod snd_seq_dummy  (gets rid of midithrough)

 

# aconnect -o

client 16: 'M Audio Audiophile 24/96' [type=kernel]

    0 'M Audio Audiophile 24/96 MIDI'

 

# aconnect -i

client 0: 'System' [type=kernel]

    0 'Timer           '

    1 'Announce        '

client 16: 'M Audio Audiophile 24/96' [type=kernel]

    0 'M Audio Audiophile 24/96 MIDI'

 

 

 

in/out both map to 16:0 in bugtrace  - so that's good

 

run it like this:

 

   WINEDEBUG=+midi wine SpiderValveEdit.exe

 

 

$ WINEDEBUG=+midi wine SpiderValveEdit.exe

p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory

fixme:wincodecs:PngDecoder_Block_GetCount stub

fixme:thread:start_thread Started native thread 00000041

fixme:thread:start_thread Started native thread 00000042

fixme:thread:start_thread Started native thread 00000043

fixme:thread:start_thread Started native thread 00000044

trace:midi:ALSA_midMessage (0000, 0064, 00000000, 00000000, 00000000);

trace:midi:ALSA_MidiInit Initializing the MIDI variables.

trace:midi:ALSA_AddMidiPort OUT (0:System:kernel:0:Timer:0)

trace:midi:ALSA_AddMidiPort IN  (0:System:kernel:1:Announce:0)

trace:midi:ALSA_AddMidiPort OUT (16:M Audio Audiophile 24/96:kernel:0:M Audio Audiophile 24/96 MIDI:90002)

trace:midi:ALSA_AddMidiPort MidiOut[0]  name='L"M Audio Audiophile 24/96 MIDI"' techn=1 voices=0 notes=0 chnMsk=ffff support=0

        ALSA info: midi dev-type=90002, capa=0

trace:midi:ALSA_AddMidiPort IN  (16:M Audio Audiophile 24/96:kernel:0:M Audio Audiophile 24/96 MIDI:90002)

trace:midi:ALSA_AddMidiPort MidiIn [0]  name='L"M Audio Audiophile 24/96 MIDI"' support=0

        ALSA info: midi dev-type=90002, capa=0

trace:midi:ALSA_MidiInit End

trace:midi:ALSA_midMessage (0000, 0035, 00000000, 00000000, 00000000);

trace:midi:ALSA_modMessage (0000, 0064, 00000000, 00000000, 00000000);

trace:midi:ALSA_modMessage (0000, 0001, 00000000, 00000000, 00000000);

trace:midi:ALSA_modMessage (0000, 0002, 00000000, 0032F20C, 00000054);

trace:midi:modGetDevCaps (0000, 0x32f20c, 00000054);

trace:midi:ALSA_midMessage (0000, 0036, 00000000, 0032F440, 0000004C);

trace:midi:midGetDevCaps (0000, 0x32f440, 0000004C);

trace:midi:ALSA_midMessage (0000, 0036, 00000000, 0032F41C, 0000004C);

trace:midi:midGetDevCaps (0000, 0x32f41c, 0000004C);

trace:midi:ALSA_midMessage (0000, 0036, 00000000, 0076B0A8, 0000004C);

trace:midi:midGetDevCaps (0000, 0x76b0a8, 0000004C);

trace:midi:ALSA_midMessage (0000, 0037, 0032F3EC, 00145CA4, 00030000);

trace:midi:midOpen (0000, 0x145ca4, 00030000);

trace:midi:midiOpenSeq Outport port 0 created successfully

trace:midi:midiOpenSeq Input port 1 created successfully

trace:midi:midOpen Input port :1 connected 16:0

trace:midi:midOpen Created thread for midi-in

trace:midi:MIDI_NotifyClient wDevID = 0000 wMsg = 961 dwParm1 = 0000 dwParam2 = 0000

trace:midi:ALSA_midMessage (0000, 0039, 00008000, 0076B110, 00000040);

trace:midi:midPrepare (0000, 0x76b110, 64);

trace:midi:ALSA_midMessage (0000, 003B, 00008000, 0076B110, 00000040);

trace:midi:midAddBuffer (0000, 0x76b110, 64);

trace:midi:ALSA_midMessage (0000, 0039, 00008000, 0076B150, 00000040);

trace:midi:midPrepare (0000, 0x76b150, 64);

trace:midi:ALSA_midMessage (0000, 003B, 00008000, 0076B150, 00000040);

trace:midi:midAddBuffer (0000, 0x76b150, 64);

trace:midi:ALSA_midMessage (0000, 0039, 00008000, 0076B190, 00000040);

trace:midi:midPrepare (0000, 0x76b190, 64);

trace:midi:ALSA_midMessage (0000, 003B, 00008000, 0076B190, 00000040);

.

.

.

trace:midi:ALSA_modMessage (0000, 0003, 0032F3BC, 00143F94, 00030000);

trace:midi:modOpen (0000, 0x143f94, 00030000);

trace:midi:midRecThread Thread startup

trace:midi:midRecThread Thread loop

trace:midi:modOpen Output port :0 connected 16:0

trace:midi:MIDI_NotifyClient wDevID = 0000 wMsg = 967 dwParm1 = 0000 dwParam2 = 0000

trace:midi:ALSA_modMessage (0000, 0005, 00008001, 0076F858, 00000040);

trace:midi:modPrepare (0000, 0x76f858, 64);

trace:midi:ALSA_modMessage (0000, 0008, 00008001, 0076F858, 00000040);

trace:midi:modLongData (0000, 0x76f858, 00000040);

trace:midi:modLongData dwBufferLength=6 !

trace:midi:modLongData                  F0 7E 7F ... 06 01 F7

trace:midi:modLongData destination 16:0

trace:midi:MIDI_NotifyClient wDevID = 0000 wMsg = 969 dwParm1 = 76F858 dwParam2 = 0000

trace:midi:ALSA_modMessage (0000, 0006, 00008001, 0076F858, 00000040);

trace:midi:modUnprepare (0000, 0x76f858, 64);

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:ALSA_modMessage (0000, 0004, 00008001, 00000000, 00000000);

trace:midi:modClose (0000);

trace:midi:MIDI_NotifyClient wDevID = 0000 wMsg = 968 dwParm1 = 0000 dwParam2 = 0000

trace:midi:ALSA_midMessage (0000, 003D, 00008000, 00000000, 00000000);

trace:midi:midStop (0000);

trace:midi:ALSA_midMessage (0000, 0038, 00008000, 00000000, 00000000);

trace:midi:midClose (0000);

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

fixme:midi:midRecThread Unexpected event received, type = b from 16:0   #pressed send on device

trace:midi:midRecThread Thread loop

trace:midi:midRecThread Thread loop

 

 

 

.... 

the third to the last line is me "sending" a patch via the tap-tempo button on the HD100 head.

 

I desperately want to get this running on Linux.  Windows isn't an option for me anymore.

 

 

fwiw,

-edfardos

 

[edfardos]

Oh, and until there's a real Linux client, you can easily backup and restore individual patches like this:

 

 

backup a patch:

cat /dev/midi1 > patchname.bin

<press "Dump Current" in midi menu on device>

ctrl-C

 

restore a patch:

cat patchname > /dev/midi1

  tone changes, panel displays patch name

  save the patch into a slot in a bank (hold down a letter button)

 

 

You can even edit the patch names in a hex editor if ya like.  It'd be nice to know what the rest of the numbers mean in the sysex data, but, Line6 doesn't appear to want to support new operating environments like Linux.

 

--edfardos

[CeeJayTheFirst]

Just to bring this thread back from the dead...

 

I'm interested in gifting myself with a nice addition to my rig: the Pod Hd Pro X. 

From what I've seen i this thread it is possible to edit the presets on the Pod (?) but the feature that I'm more interested in knowing if it works is the digital interface for direct recording. So does it work?

If it doesn't, then can I connect this device to a sound card (PCI like ESI Juli@ or USB like Scarllett 2i2/2i4) and then to the computer?

[MikeF1972]

Isn't Linux a server thing ?  I never heard of anyone running it at home other than as a curiosity.

 

I've been using Linux as my primary OS on all of my computers since 2003. I never touch Windows or MacOS. Would love a Linux port of the Line 6 software, but yeah, not holding my breath for that one.

[progresivjose]

Hei!

I can report that the "Line 6 POD HD500X" works too here on a amd64 arch linux box with at the moment 3.12.0-1 stock arch kernel and "virtualbox-bin 4.3.0-1" from aur && "virtualbox-guest-iso 4.3.2-1" && "virtualbox-host-modules 4.3.2-4" with "POD HD500X Edit 2.23" and "Line6 Monkey 1.65"

I'm quite happy about that. BUT a NATIVE LINUX Software would be great!! just wanted to say that. probaly we should start some signing that we (and line 6) see how many Linux users with Line6 porducts are out there ...

thanks "frmat" for the hint with unchecking the ehci box, that lead to success.

 

windows is NO alternativ for me!

 

Hello... i want to know how did you do it? because i'm running Arch Linux 4.6.3-1-ARCH in a Dell xps 13 and cannont connect the POD with the virtual box.

 

When i do lsusb i got this:

Bus 001 Device 002: ID 8087:8000 Intel Corp. 

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 002 Device 005: ID 8087:07dc Intel Corp. 

Bus 002 Device 004: ID 0bda:5604 Realtek Semiconductor Corp. 

Bus 002 Device 003: ID 06cb:0af8 Synaptics, Inc. 

Bus 002 Device 008: ID 0e41:4159 Line6, Inc. 

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

Any other thing that i have to do that is not listed in the first post?

[hmoller]

at least in kernel 4.4 are included line6 modules. In ubuntu if you go to /lib/modules/4.4.0-36-generic/kernel/sound/usb/line6 you will see the modules:

snd-usb-line6
snd-usb-podhd
snd-usb-pod
snd-usb-toneport
snd-usb-variax

you should be able to load them with: modprobe
example:
sudo modprobe snd-usb-podhd

unfortunnately I haven't been able to bring my hd500x running, I don't know if it is because of the X or not. modprobe work's fine but I don't see it with

cat /proc/asound/cards

nor I see it in alsamixer.

hope this help, let us know how it goes.

[Beanow]

I will be going down the same POD HD500X rabbit hole of drivers soon.

Seeing how this thread is several years old, I will probably need to learn how to write these drivers myself.

[hmoller]

Hi,

  the last info I could get is that the driver worked ok with a podXT before Ubuntu 12.04. I don't know if HD500 worked some time. here is te sourceforge of teh driver https://sourceforge.net/projects/line6linux/

Please let us know if you succeed.

 

I will be going down the same POD HD500X rabbit hole of drivers soon.

Seeing how this thread is several years old, I will probably need to learn how to write these drivers myself.

 

[Beanow]

If that driver is the one included in the 4.4.0 kernel it won't work with the HD500X yet.

But it references HD300, HD400 and HD500. So there's hope.

https://sourceforge.net/p/line6linux/code/HEAD/tree/driver/trunk/podhd.c#l105

Those list USB ID's different from mine.

Bus 003 Device 006: ID 0e41:4159 Line6, Inc.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass       255 Vendor Specific Subclass
  bDeviceProtocol       255 Vendor Specific Protocol
  bMaxPacketSize0        64
  idVendor           0x0e41 Line6, Inc.
  idProduct          0x4159
  bcdDevice            0.00
  iManufacturer           1 Line 6
  iProduct                2 POD HD500X
  iSerial                 0
  bNumConfigurations      1
  ...

[hmoller]

Hi, I have good news.

We could patch the line6usb drivers and make my pod hd500x capture and playback in linux with kernel above or equal 4.9. I'm writing a guide on how to do it, when ready I will let you know. With a small change I believe it could work with pod hd pro, but I don't have one to test it.

[hmoller]

Hi with the help of the guy that did the POD X3 patch, we created a patch for POD HD500X and we are working to be merged in Kernel.

Here is the preliminary instruction on how to patch it in kernel 4.9+ and compile the module:

https://sites.google.com/site/hmoller/pod-hd500x-linux

 

I also believe that this could be easily replicated for HD PRO, POD HD PROX and HD Desktop but I don't have this devices to test it so we could also merged it in the kernel. So, if you have any of this devices and want to try, you would need to make some changes in the patch. changing the device_id, and where 500X appears change it with your device. If it still doesn't work, I can guide you in some small changes. Tell me how is it going to include it in the patch.

 

Finnaly, any other HD user (300,400,500), it would be useful to test if the changes doesn't affected you, so when the new kernel arrive you won't be affected. So, please try it and tell me if it stop working.

 

[cruisinon2]

Bueller? Bueller?

[cschooley]

In case somebody finds this googling:

 

It's been a while and the linux kernel now supports and includes modules (aka "drivers" as the Windows people like to say). If your distro runs a kernel after 4.9 (I think) it should "just work" (as the Mac People like to say) as a sound card/recording device.

 

Different Linux distros ship different kernels. For me, running Linux Mint 18 kernel 4.4 is the latest supported by linux distro maintainers.

 

You have 2 options:

 

1. google how (and the risks) of updating kernels on your particular distro

2. wait until your distro updates the kernel to a version that includes the POD drivers.

 

In my case I updated using my Distro's software updater (linux mint) to kernel 4.15 and had no issues getting it to work after a reboot into the new kernel. No other issues either.

 

Linux FTW.

[equinox23]

On 9/25/2018 at 8:31 PM, cschooley said:

In case somebody finds this googling:

 

It's been a while and the linux kernel now supports and includes modules (aka "drivers" as the Windows people like to say). If your distro runs a kernel after 4.9 (I think) it should "just work" (as the Mac People like to say) as a sound card/recording device.

 

Different Linux distros ship different kernels. For me, running Linux Mint 18 kernel 4.4 is the latest supported by linux distro maintainers.

 

You have 2 options:

 

1. google how (and the risks) of updating kernels on your particular distro

2. wait until your distro updates the kernel to a version that includes the POD drivers.

 

In my case I updated using my Distro's software updater (linux mint) to kernel 4.15 and had no issues getting it to work after a reboot into the new kernel. No other issues either.

 

Linux FTW.

 

 

did anyone managed to make it work?

i have lubuntu 16.04.01 with kernel 4.15. snd modules are effectively present, and i did sudo modprobe  (with all the correct dependencies) but still no pod hd is detected among the sound cards  by /proc/asound/cards..

obviously the item is up and running and connected via usb (lsusb listed it)