Jump to content
Kellaway

Line 6 With Linux?

Recommended Posts

On 1/11/2018 at 1:19 PM, shemeshg said:

Hi, Jens

 

Yes, I can see all the 8 channels, and re-amp on linux and Ardour and all thanks to you

 

As you've mentioned 

1. JACK is required since it is not plays directly using ALSA and PulseAudio,

However, Jack sink works greate

2. It will be required to recopy snd_usb_audio on every kernel update.

 

But it is huge benefit being able to Re-Amp and  not to require all of those XLR cables

 

Thanks

Shemeshg

 

Can you elaborate on how to configure jack to work with the HX stomp? I don't understand how it can work if it doesn't work with ALSA...

Share this post


Link to post
Share on other sites

Just FYI:

Since i made the 2.82 firmware update, my Helix LT identifies with device id 0x424a ( idProduct=424a ) .

Aka the patches must be adapted to work again. Not sure how other Helix devices changed because of the

new ( unified ? ) core architecture.

Did not yet noticed any further benfit other than new sounds/stomps etc.

 

Sidenote:

I don't wanna have Helix shown up in the systems pulse audio because it would not work reliable there either.

So i made an udev rule to ignore it. If someone else cares too, place into /etc/udev/rules.d/89-pulseaudio.rules:

#Ignore Helix
ATTRS{idVendor}=="0e41", ATTRS{idProduct}=="424a", ENV{PULSE_IGNORE}="1"

 

Cheers ... Jens

Share this post


Link to post
Share on other sites

Can't believe what I'm reading - is this actually working on linux :D

 

@jensverwiebe Are these instructions still the way to go as of today? Someone seem to have it working out of the box on fedora https://line6.com/support/topic/30896-helix-as-interface-on-linux/?do=findComment&comment=328378. I'm on ubuntu studio 19.10 atm, using jack, that does not seem to recognize the helix floor for anything other than midi.

 

Is there anything special to consider other than what is described in https://line6.com/support/topic/4426-line-6-with-linux/?tab=comments#comment-310804, it being a lowlatency kernel (5.3.0-46-lowlatency). I reckon I should go about changing the clone to git://kernel.ubuntu.com/ubuntu/ubuntu-eoan.git.

 

Anything else?

Share this post


Link to post
Share on other sites

@torgeirthoresen Well my Helix floor has been working out of the box for quite some time now on ubuntu 19.10 with ubuntustudio packages installed. That's with both generic and lowlatency kernels. Everything is working fine with jack, not with pulseaudio though.

Share this post


Link to post
Share on other sites

@gleogodais And by working you mean it’s discovered as a sound card and you can e.g. reamp over usb? That’s what I was aiming for coming here. If so it might be just my understanding of jack vs pulseaudio vs alsa that is lacking.. Care to explain how you go about setting things up? 

Share this post


Link to post
Share on other sites

Yes, all the channels (8 input/8output) are working! You can record DI from the guitar/mic as well as processed signal, playback sound, reamp...

I don't know how well you know this stuff, if you're new to this here are some simple steps to make it work:

Setting it up with jack is the same as any other usb sound interface with Ubuntu Studio Controls. If you want it to be your master device,  set Jack Master Device to USB Jack Master and USB device that should be master to HELIX. If you check Bridge USB Devices to Jack when Plugged In, you'll be able to see it in Patchage and make the connections.

 

Alsa focuses on the lower level audio, handling soundcards but also midi. Jack and Pulseaudio both use alsa as backend (most likely in your case). Pulseaudio is used for standard applications but is not suited for real-time use. A lot of applications like Firefox don't work with Jack (check out Pulse-Jack bridge to run Pulseaudio and Jack at the same time). Jack allows you to run audio applications with very low latency.

 

A good ressource to check out: https://help.ubuntu.com/community/UbuntuStudio/AudioHandbook ;)

 

Also, about low-latency vs generic kernel, low-latency used to work better for me but nowadays generic is definitely better the way ubuntu studio sets it up.

 

Hope this helps :)

Share this post


Link to post
Share on other sites
7 hours ago, glegodais said:

If you want it to be your master device,  set Jack Master Device to USB Jack Master and USB device that should be master to HELIX.

Hmm, sounds like what I'm already doing, but with my AudioFuse interface.I have Jack Master Device set to USB Jack Master but USB device that should be master is where I believe the issue is, because there is no Helix in the list, just my AudioFuse extrernal usb interface. Bridge USB Devices to Jack when Plugged In is checked. With e.g. Carla open when I plug the helix in I can see that it recognizes it as a midi device, as a capture/playback slot appears for the midi, but nothing else. `lsusb` shows the device is recognized though `Bus 003 Device 019: ID 0e41:4248 Line6, Inc. HELIX`

 

EdIt:

I see this in dmesg as I plug in the helix which seems like the issue you have been patching?

 

[ 5701.507029] usb 3-1: new high-speed USB device number 20 using xhci_hcd
[ 5701.520141] usb 3-1: New USB device found, idVendor=0e41, idProduct=4248, bcdDevice= 2.00
[ 5701.520143] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5701.520144] usb 3-1: Product: HELIX   
[ 5701.520145] usb 3-1: Manufacturer: LINE 6
[ 5701.520145] usb 3-1: SerialNumber:    2929049
[ 5701.521707] usb 3-1: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 16)
[ 5701.521886] usb 3-1: parse_audio_format_rates_v2v3(): unable to retrieve number of sample rates (clock 16)
[ 5701.523044] input: LINE 6 HELIX    as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.5/0003:0E41:4248.0010/input/input27

 

Screenshot_2020-04-10_08-37-08.png

Share this post


Link to post
Share on other sites

I think it's because your Helix id is 0e41:4248 I instead of 0e41:4241, I guess you have a more recent firmware

Send a patch with your Helix ID as described in this thread :

Until this is fixed upstream you can recompile the kernel usb_audio module after adding your Helix ID to sound/usb/format.c like in this patch https://github.com/torvalds/linux/commit/d4bd30532688558a7de70f0c8edd2a7a25c3963f

Share this post


Link to post
Share on other sites

Half a day later, the stars align! And I'm reamping like a boss with the helix on ubuntu studio eoan 19.10

 

7 hours ago, glegodais said:

it's because your Helix id is 0e41:4248 I instead of 0e41:4241

 

And you were quite correct, @glegodais, it needs to be 0e41x4248. Here are the steps I took to make it work.

 

For some reason I am only able to get an output signal from the helix when attaching things in jack if I choose the HELIX as the "USB device that should be master", and not with the AudioFuse set as the master, even if the helix still appears in the jack interface and I wire it correctly. Suggestions?

 

Attached photos of the working configuration if someone is curious.

 

Thanks a bunch for your help!

 

 

 

 

 

controls-working.png

carla-working.png

Share this post


Link to post
Share on other sites
On 4/9/2020 at 7:59 PM, torgeirthoresen said:

Can't believe what I'm reading - is this actually working on linux :D

 

@jensverwiebe Are these instructions still the way to go as of today? Someone seem to have it working out of the box on fedora https://line6.com/support/topic/30896-helix-as-interface-on-linux/?do=findComment&comment=328378. I'm on ubuntu studio 19.10 atm, using jack, that does not seem to recognize the helix floor for anything other than midi.

 

Is there anything special to consider other than what is described in https://line6.com/support/topic/4426-line-6-with-linux/?tab=comments#comment-310804, it being a lowlatency kernel (5.3.0-46-lowlatency). I reckon I should go about changing the clone to git://kernel.ubuntu.com/ubuntu/ubuntu-eoan.git.

 

Anything else?

 

Hi

Sorry for being late to the party ;)

Nice you sorted things out for now.

Be aware that the new device id's are already in 5.5 kernel, so if you use the HWE you should be fine.

 

2020-01-25 15:09:17 - ALSA: usb-audio: add quirks for Line6 Helix devices fw>=2.82

Here we added:

+ case USB_ID(0x0E41, 0x4248): /* Line6 Helix >= fw 2.82 */
+ case USB_ID(0x0E41, 0x4249): /* Line6 Helix Rack >= fw 2.82 */
+ case USB_ID(0x0E41, 0x424a): /* Line6 Helix LT >= fw 2.82 */
 
Thus your adaptions are only needed for older kernel ( < 5.5 ) or if you need my additional frequency trick in case you suffer from rare clicks.
I got a bit further with this sync problem, but still do not get this 100% working. As is should do for now.
 
Cheers ... Jens

 

 

 

 

Share this post


Link to post
Share on other sites

Well apparently I got the same issue,  Helix is not working when not the master device. I'm not sure if it used to work or not since I almost always use the helix as master :/

Actually it even crashed jack and there was no way to restart it without a reboot.

Share this post


Link to post
Share on other sites
19 hours ago, jensverwiebe said:

Be aware that the new device id's are already in 5.5 kernel, so if you use the HWE you should be fine

   

 

Nice! I think I'll stay safe, though, now with everything working, until ubuntu studio fixes it for me xD

 

4 hours ago, glegodais said:

Well apparently I got the same issue,  Helix is not working when not the master device. I'm not sure if it used to work or not since I almost always use the helix as master :/

Actually it even crashed jack and there was no way to restart it without a reboot.

 

Yeah, I had a few of those as well. I do to, so its not that big of a deal. I actually think pulseaudio was getting in the way somehow for me.. (?) A peek inside the ubuntustudio-controls script also revealed they seem to be killing everything with regards to sound before booting it up again to get a consistent startup. Having to wire all this up again was becoming a pain, so it made me discover https://github.com/SpotlightKid/jack-matchmaker

Share this post


Link to post
Share on other sites

Hi mates, some notes:

- @torgeir, regarding nonfunctional rmmod in your script: i guess rmmod is just not default installed on your sys, use modprobe -r instead.

- @ all: i' am able to get the endpoints working incl. the sync, by forcing it like for an Axe-FX3 for example. But the streams will not come up atm, grrrrrr.

For all interested to fiddle until we get succes, here are my changes:

 

In pcm.c i add something like this to the set_sync_ep_implicit_fb_quirk function ( your ID accordingly )

	case USB_ID(0x0e41, 0x424a): /* Line6 HELIX LT */
		ep = 0x83;
		ifnum = 3;
		goto add_sync_ep_from_ifnum;

In endpoint.c Mike Oliphant found its needed to comment out in snd_usb_endpoint_start function.

Otherwise the initialization of urbs would wait for each other ( capture/playback/sync ep ) forever.

	if (snd_usb_endpoint_implicit_feedback_sink(ep)) {

		for (i = 0; i < ep->nurbs; i++) {
			struct snd_urb_ctx *ctx = ep->urb + i;
			list_add_tail(&ctx->ready_list, &ep->ready_playback_urbs);
		}

		return 0;
	}

Then one will get in terminal output while debugging ( trick: add "#define dev_dbg dev_info" to usb.h for avoiding a complete debug build of kernel ):

jack/helix/duplex: dmesg | tail
[11568.409129] usb 9-1.3: Setting params for ep #83 (type 0, 12 urbs), ret=0
[11568.409655] usb 9-1.3: setting usb interface 2:1
[11568.409656] usb 9-1.3: Creating new playback data endpoint #3
[11568.409659] usb 9-1.3: Re-using EP 83 in iface 3,1 @000000005f5f3a5c
[11568.410006] usb 9-1.3: Setting params for ep #3 (type 0, 12 urbs), ret=0
[11568.410007] usb 9-1.3: match_endpoint_audioformats: (fmt @00000000f60f1dd9) score 2
[11568.410014] usb 9-1.3: Setting params for ep #83 (type 0, 12 urbs), ret=0
[11568.410015] usb 9-1.3: Starting data EP @00000000ef58d6e2
[11568.410478] usb 9-1.3: Starting sync EP @000000005f5f3a5c
[11568.410960] usb 9-1.3: Starting data EP @000000005f5f3a5c

jack/helix/playback:~$ dmesg | tail
[11592.501593] usb 9-1.3: setting usb interface 2:1
[11592.501596] usb 9-1.3: Re-using EP 3 in iface 2,1 @00000000ef58d6e2
[11592.501598] usb 9-1.3: Re-using EP 83 in iface 3,1 @000000005f5f3a5c
[11592.501924] usb 9-1.3: Setting params for ep #3 (type 0, 12 urbs), ret=0
[11592.501926] usb 9-1.3: match_endpoint_audioformats: (fmt @00000000f60f1dd9) score 2
[11592.501936] usb 9-1.3: Setting params for ep #83 (type 0, 12 urbs), ret=0
[11592.501937] usb 9-1.3: Starting data EP @00000000ef58d6e2
[11592.502393] usb 9-1.3: Starting sync EP @000000005f5f3a5c

jack/helix/capture: dmesg | tail
[11611.315495] usb 9-1.3: Re-using EP 83 in iface 3,1 @000000005f5f3a5c
[11611.315781] usb 9-1.3: Setting params for ep #83 (type 0, 12 urbs), ret=0
[11611.316087] usb 9-1.3: Starting data EP @000000005f5f3a5c

This all looks exact how it should be and like a Boss Katana for example will show up, but the helix will not yet come to life. Ideas are welcome.

As i think we all have a lot time for such experimenting now, we may come to an result asap i hope.

 

Cheers ... Jens

 

 

Share this post


Link to post
Share on other sites

Interestingly I've just tried Kubuntu 20.4 in a virtual machine and my helix is showing up without any additional configuration. Going to upgrade my workstation and see how well it works.

image.png.bbfdccd8c878befbe916ecd05719bac2.png

 

I've updated the to 20.4 on my main workstation and Helix is connected and working. I'm new to using audio on linux, I've only just moved across from windows so am still learning all about it but Helix seems to work straight out of the box with Kubuntu 204. The screenshot below is from my main workstation.

 

Screenshot_20200425_143327.png

 

Share this post


Link to post
Share on other sites

Hi all, 

 

Before I update my helix rack to v 2.91, has anyone done this already? Just wanted to check the USB ID hasn't changed again

 

I'm partially working under Arch with the current 5.6 kernel branch using jack2

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...