Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Search the Community

Showing results for tags 'linux'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community Support
    • Multi-Effects Units
    • Variax Instruments
    • Amplifiers
    • Computer Based Recording
    • Live Sound
    • Pedals/Controllers
    • Dream Rig - Line 6 Product Integration
  • General Discussion
    • Tone Discussion
    • Line 6 Lounge

Categories

  • General FAQ
    • Operating System-specific Information
  • Tutorial Videos
  • Effects/Controllers
    • HELIX/HX
    • DL4 MkII Stompbox Modeler
    • M5
    • FBV Controllers (MKII / 3)
  • Amplifiers
    • Catalyst
    • Powercab
    • Spider V
  • POD
    • POD Go
    • POD Express
    • Pocket POD
  • Guitars
    • JTV / Shuriken / Variax Standard / Workbench HD
  • Relay G10 Digital Wireless
  • Recording
    • Helix Native
    • Metallurgy
    • Echo Farm/Amp Farm
    • POD Farm 1/2.0/2.5
    • Computer Audio Set Up and Troubleshooting
  • Legacy Products
    • POD
    • Amps
    • 1st Gen Variax Guitars / Bass / Workbench
    • Effects and Controllers
    • AMPLIFi Series
    • Live Sound
    • Digital Wireless
    • Mobile Products
    • POD Studio / Tone Port / GuitarPort
    • Software
    • Dream Rig

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Registered Products

Found 13 results

  1. # Running PODHD Pro X under linux Because we love linux ! Tested on : Ubuntu 22-04 (jammy) ## 1) Get the righ ID of the PODHD PRO X: run the command : ``` > sudo dmesg | grep 'idVendor=0e41' [ 3239.784010] usb 3-1.3.1: New USB device found, idVendor=0e41, idProduct=415a, bcdDevice= 0.00 ``` 0x0e41 = Line 6 Manufacturer ID __0x415a__ = __PODHD Pro X ID__ ## 2) Linux kernel source Get your current kernel version: ``` > uname -r 6.8.0-47-generic ``` Download the most closest version of your kernel: For me is 6.8.0 and extract under __/usr/src/__ ``` > wget https://mirrors.edge.kernel.org/pub/linux/kernel/v6.x/linux-6.6.8.tar.gz > tar -xvf linux-6.6.8.tar.gz > mv linx-6.6.8/ /usr/src/. ``` ## 3) Make Module Prepare Remove root permission ``` > cd /usr/src/ > chown -R $(whoami):$(whoami) linux_6.8.0/ ``` Copy your current kernel config inside the source ``` > cd /usr/src/linux_6.8.0 > cp /boot/config-$(uname -r) .config ``` make module_prepare ``` > cd /usr/src/linux_6.8.0 > cp /boot/config-$(uname -r) .config > make oldconfig > make modules_prepare ``` ## 4) Modify PODHD. C file For working you have to simply modify the value of LINE6_PODHDDESKTOP inside the file : > linux-6.8.0/sound/usb/line6/podhd.c > replace __0x4156__ by __0x415a__ ``` /* table of devices that work with this driver */ static const struct usb_device_id podhd_id_table[] = { /* TODO: no need to alloc data interfaces when only audio is used */ { LINE6_DEVICE(0x5057), .driver_info = LINE6_PODHD300 }, { LINE6_DEVICE(0x5058), .driver_info = LINE6_PODHD400 }, { LINE6_IF_NUM(0x414D, 0), .driver_info = LINE6_PODHD500 }, { LINE6_IF_NUM(0x414A, 0), .driver_info = LINE6_PODX3 }, { LINE6_IF_NUM(0x414B, 0), .driver_info = LINE6_PODX3LIVE }, { LINE6_IF_NUM(0x4159, 0), .driver_info = LINE6_PODHD500X }, { LINE6_IF_NUM(0x415a, 0), .driver_info = LINE6_PODHDDESKTOP }, {} }; ``` ## 5) Rebuild module ``` > cd linux-6.8.0/sound/usb/line6 > make -C /lib/modules/$(uname -r)/build M=$(pwd) modules ``` if all is ok you have successfully build the modules for the PODHD Pro X. ``` > ll *.ko -rw-r--r-- 1 root root 1567408 Oct 23 15:56 snd-usb-line6.ko -rw-r--r-- 1 root root 418600 Oct 23 16:22 snd-usb-podhd.ko -rw-r--r-- 1 root root 417152 Oct 23 15:56 snd-usb-pod.ko -rw-r--r-- 1 root root 438232 Oct 23 15:56 snd-usb-toneport.ko -rw-r--r-- 1 root root 384128 Oct 23 15:56 snd-usb-variax.ko ``` ## 6) unload old module . verify if you have line modules loaded ``` > sudo lsmod | grep snd_usb snd_usb_podhd 16384 0 snd_usb_line6 49152 3 snd_usb_podhd snd_usb_audio 499712 5 snd_usbmidi_lib 53248 1 snd_usb_audio snd_hwdep 20480 3 snd_usb_audio,snd_hda_codec,snd_usb_line6 snd_ump 45056 1 snd_usb_audio snd_rawmidi 57344 4 snd_seq_midi,snd_usbmidi_lib,snd_usb_line6,snd_ump mc 81920 1 snd_usb_audio ``` For me __snd_usb_pod_hd__ and __snd_usb_line6__ must be unloaded ``` > sudo rmmod snd_usb_podhd > sudo rmmod snd_usb_line6 ``` ## 7) Insert new module. Insert first line6 and after podhd ``` > sudo insmod ./snd-usb-line6.ko > sudo insmod ./snd-usb-podhd.ko ``` ## 8) Big thanks to : Markus Grabner <grabner@icg.tugraz.at> who is at the origin of this driver. README.md podhd.c
  2. Hello, I searched the internet for help on using Helix Edit on Linux. I have no problem running the native Helix plugin under Arch Linux using Yabridge, which works flawlessly. However, I still need to perform firmware updates for my Helix Floor and enjoy the convenience of editing presets using Helix Edit. Since I couldn’t find anything online, I decided to come up with a solution myself. I can confirm that I was successful in running Helix Edit on Linux. Below are the steps to achieve it: 1. Install Wine and Required Dependencies Make sure you have Wine and its required dependencies installed. - sudo pacman -S wine wine-mono wine-gecko winetricks - yay -S wineasio - register the ASIO driver within Wine: wine regsvr32 wineasio.dll 2. Install Line 6 Helix Edit in Wine Download the Helix Edit installer Run the installer using Wine: wine path/to/helixedit_installer.exe Follow the installation prompts. 3. Workaround for USB Connection Using USB Passthrough with VirtualHere (USB Sharing): Since Wine doesn't natively support USB devices like the Line 6 Helix, a solution is to use a USB-over-network tool like VirtualHere, which allows USB devices to be shared with Wine over a virtual connection. Steps for VirtualHere: Installation: - yay -S virtualhere-server-bin - yay -S virtualhere-client Run the VirtualHere USB Server on your Linux machine: sudo ./vhuitarm -b Or use the appropriate version for your machine. Run the VirtualHere Client in Wine: wine path/to/virtualhere_client.exe The USB device (Helix) will now appear in VirtualHere, and you can "attach" it inside Wine (Alternative to VirtualHere) Configuring USB Device Access via usbip: For a more manual solution, you can use USB/IP to share your USB device and try to access it from Wine. Install usbip: sudo pacman -S usbip Load the necessary kernel modules: sudo modprobe vhci-hcd Find the USB device: usbip list -l Bind the USB device (replace <busid> with the correct ID from the previous command): sudo usbip bind -b <busid> The device should now be accessible within Wine.
  3. So I know there are a LOT of forums and discussions on this topic, but i need to know how to get this to work. I am currently running Reaper and I'm trying to use my Helix as an audio interface. I just can't seem to figure it out. Any help or advice will be greatly appreciated, thanks in advance.
  4. Hello Line6 Team, I am currently writing an open source software (LGPLv2) to use the podhd 500x under Linux in a similar manner as "POD HD 500X edit". Would it be possible to have the protocol data sheet to complete my implementation? I am currently supporting basic features, i.e. reading and writing pedals settings, but I am lacking some understanding of the whole protocol. Thanks in advance, Aurryon The code https://github.com/StarAurryon/lpedit Note: Protocol reverse engineering is perfectly legal if we listen to the usb port, which is what I am doing. As a EU citizen I would also be allowed to reverse the assembly in the name of interoperability: which I am not doing now as it is harder
  5. After a lot of of messing around, I finally got my Line6 Helix LT multi-effects working on Linux (Ubuntu 20.04)! Here's what I did. Install a distribution with the latest Linux kernel. I am currently running Ubuntu 20.04 with Linux kernel version 5.3. I think these instructions should work for any distribution with kernel 5.x+, but I'm not sure. Install the JACK audio connection kit. This took me a bit to understand, but here's what I learned. ALSA is the low-level driver used for Linux audio, but most user applications do not interface with ALSA directly, they use a "sound server." JACK is exactly that, it's a server that runs on top of ALSA. It turns out that the Helix would not work for me directly in my ALSA sound settings, but it would work for me if I used JACK. Read on... After you have installed jack, you'll want to fire up the graphical user interface for it called QJackCtl. It's ugly but it works. Once you get into the GUI, click the setup button and look for the "interfaces" dropdown. Choose the "Helix" interface in the dropdown. If it's not there, make sure you've connected the USB port to your computer, etc. Once you get this far, you'll sometimes need to select JACK as the audio server in the application that you want to use the Helix in. For me, it was Bitwig studio. I went into the settings, set the audio engine to use JACK, and BOOM! My sounds were coming straight into the software from USB. I could also use the helix as an output!
  6. After Jack session on Ubuntu 20.04, I have no sound in pulseaudio with the hx stomp whereas the volume gage indicates activities in application and sound card output. if I come back to jack I have sound with my hx stomp using pulseaudio sink. Any ideas Linux users?
  7. Hey all, first post so I hope I'm doing this right. I've recently joined the cult of Linux, and am looking to make primarily electronic music through Ubuntu 18.04. I know that some more common audio interfaces have plug-and-play compatibility, but I'm interested in connecting my Helix directly to my DAW (Ardour) via its USB cable. At the time of posting this I haven't actually started messing with configuring this on my own, but figured I should crowdsource experiences others may have had: has anyone had any experience/luck getting the Helix to work with any Linux distro in this way? I tried looking in the Knowledge Base but didn't find any relevant information for this situation.
  8. Hi All, I created a patch for Linux Kernel 5.3 to enable HX stomp/Helix I need some help to confirm that is working properly. In particular would be really helpful if you can try the kernel 5.3 and confirm the USB ID for Helix devices case USB_ID(0x0E41, 0x4242): /* Line6 Helix Rack */ case USB_ID(0x0E41, 0x4244): /* Line6 Helix LT */ case USB_ID(0x0E41, 0x4246): /* Line6 HX-Stomp */ case USB_ID(0x0E41, 0x424a): /* Line6 Helix LT - firmware >= 2.8 */ This is displayed in dmesg when the device is discovered (open dmesg -w and then plug the device) [ 322.404503] usb 1-6: new high-speed USB device number 13 using xhci_hcd [ 322.531804] usb 1-6: New USB device found, idVendor=0e41, idProduct=4246, bcdDevice= 2.00 [ 322.531806] usb 1-6: New USB device strings: Mfr=1, Product=3, SerialNumber=2 [ 322.531806] usb 1-6: Product: HX Stomp [ 322.531807] usb 1-6: Manufacturer: LINE 6 [ 322.531808] usb 1-6: SerialNumber: 3021888 [ 322.535789] usb 1-6: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 16) [ 322.535907] usb 1-6: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 16) In particular if the device is supported the last two lines will show as unable to retrieve number of sample rates set it to default as 48Khz What I need is a list of helix like devices and the list of idVendor, IdProduct. Can you help me? Also for Line6 did the new update to support the new Mac Os X bring some news for Linux Users as well?? Thanks Nick
  9. I want to play guitar using linux and my POD Studio UX1. Output works perfectly fine, the interface is detected and gives a great tone for everything i play on my computer. However, input from the UX1 is not working. Jack is started and seems to be wired correctly but i get no instrument input. Does the UX1 instument input have problems with linux in general or am I missing something? On Windows with POD Farm it worked. Thanks for helping!
  10. The upcoming Helix Native plugin looks very cool, and I see it will be offered in the typical array of formats: "Compatible with AAX, AU, and VST3 platforms" Is there any hope the Line 6 devs will include a native Linux VST3 plugin build, given Steinberg's release of the VST SDK with Linux support? http://cdm.link/2017/03/steinberg-brings-vst-linux-good-things/ https://github.com/steinbergmedia/vst3sdk Similarly, any plans for an LV2 build if not a native VST3 build? The combination of the Helix Native plugin with Linux Native DAW applications (Bitwig, Ardour, Renoise, etc.) would be pretty killer.
  11. Hi ! I'm currently trying to get rid of windows on my PC. For now I can do everything I used to do on Windows on my Linux, except for... music. I love to use my sonicport on my iPad and I would love to be able to use it on my Linux PC. I know that there are a lot of Linux(s) distros out there but almost all of them (the most used ones) are based on Debian. I think it would be a (really) good start for porting line6 linux drivers... Can you please tell me if it is worth waiting for a Linux driver development or .... not ? Thanks. Patrick
  12. Hi all! I am a proud owner of a PodXTLive and I'm really happy with it! I'm also a developer and my project is to create a VST Host under Raspberry Pi2.. all is going well, but (as far as I know) there aren't Line6 drivers for Linux based on ARM architecture.. There is someone that can help me with the project or that can give me some hint or ideas to make it work? Raspberry Pi2 would be perfect for a vst host and It would be nice to make my PodXTLive do the sound processing like I do (for example) on windows! Thank you all and I hope to get a clear answer just to understand if I have to give up and try with some other solution. Luca
  13. 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.
×
×
  • Create New...