Bug 53801 (azakid)
Summary: | line6usb - POD Studio UX2 Playback problem. Very robotic and slightly slower than usual | ||
---|---|---|---|
Product: | Drivers | Reporter: | azakid |
Component: | Sound(ALSA) | Assignee: | Jaroslav Kysela (perex) |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | CC: | aluiziob.oliveira, henri.bauer, papylhomme, tehwerner, tiwai |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://launchpad.net/~azakid | ||
Kernel Version: | 3.8.0-999-generic | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | A document of the information provided |
Description
azakid
2013-02-14 00:42:30 UTC
It's a staging driver I really don't take care of. If it worked with a certain version, could you bisect it? (In reply to comment #1) > It's a staging driver I really don't take care of. > If it worked with a certain version, could you bisect it? Well I believed it only worked with kernel releases before 3.8.0. For example it worked within Ubuntu 12.10 (fully updated). I have tested previous 3.8.0 kernel releases to see if the issue still persists and it does, so I believe the issue may have occurred in the early stages of the 3.8.0 kernel. I ran into this issue after a system upgrade. Jack works well using the onboard soundcard, but I get a really crappy sound (as illustrated on the youtube video) with a POD Studio UX1. As said by azakid@ymail.com, the problem appeared "around" the 3.8 release, I'll try to bisect it more precisely during the week. Distribution: Arch Linux Version: Linux zubrowska 3.8.4-1-ARCH #1 SMP PREEMPT Wed Mar 20 22:10:25 CET 2013 x86_64 GNU/Linux The problem appeared with the first 3.8 release, everything works fine using a 3.7.10 kernel. I tried to use the driver sources from the 3.7.10 tag to build a 3.8 kernel, with no luck (apparently changes were mainly code cleanup: http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/log/?qt=grep&q=line6), the sound is still distorted. So it seems the problem lies in another part, alsa, usb, ... Currently the alsa bug tracker is offline, but I'll open a bug there to see if the distortion shape trigger something from the dev, they may recognize a "class" of problem. Any idea how I can be useful to help in solving this problem ? Could you try to bisect between 3.7 and 3.8? I don't think the problem is in ALSA part, since line6 is a completely different driver from the generic usb-audio. But the full bisection would be still safer. Ok, so the next step is to use directly git bisect with the two tags as starting and ending point ? I'm afraid it will result in a shitload of kernel compilation :D Just in case I encounter some compilation or other unrelated problems with a given patch, what do I need to do to restart the bisection with the next commit, git bisect skip, and then bisect start again, or do I flag it as a bad commit ? And regarding the compilation process, make mrpoper && make at each step or is there any other faster way (maybe avoiding cleaning the tree) ? I am wondering if anyone has progressed or found anything new relating to my bug report. I have found out based on my YouTube video that users are having issues with the Line6 Toneport GX as well as the UX2 and UX1 devices. Ubuntu 13.04 has officially released with the 3.8 kernel. Last time I checked (just over a week ago) the issue still existed. I hope for this problem to be fixed soon in the next major kernel release, as it affects users other than myself on many other Line6 sound devices. Thank you all for co-operating in diagnosing and ultimately aiming to fix the problem. Hi, I am one of the other users affected. The sound on my Line 6 UX2 is the same as on the video http://youtu.be/mzmESXZ_R3g since my (full) upgrade to kubuntu 13.4 (3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux) last week. No problem before, and no problem on the built-in Sound card. If there is any information I can provide to shrink the search space, I'ld be happy to provide it. I also experienced the same issue when I tested the Ubuntu Studio with a 3.8 kernel. Never had this issue before, with prior versions of the kernel. This can become problematic as all major distribution will migrate to 3.8.x kernel series. Thank you both for replying. I hope a kernel developer with experience in this field will be able to help. It will also be great if anyone can state that this bug affects them on my Launchpad bug report, as it will help highlight that this is an important issue that needs to be resolved. I am very certain that this issue occurred in the early development stages of the 3.8.0 kernel. I also can confirm that this issue is more widespread as it affects many users, even with different Line6 sound devices. Thank you all for your help and I just hope that someone would be able to track down and resolve this issue. I am not sure what other information anyone can provide, so it would be helpful if someone such as a developer could guide people to prove detailed information such as mine maybe. I tried to provide additional info by (after installing launchpadlib) running $ apport-collect 1103018 but I am getting: ERROR: hook /usr/share/apport/general-hooks/cloud_archive.py crashed: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apport/report.py", line 197, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/general-hooks/cloud_archive.py", line 18, in add_info if '~cloud' in packaging.get_version(package) and \ File "/usr/lib/python2.7/dist-packages/apport/packaging_impl.py", line 123, in get_version raise ValueError('package %s does not exist' % package) ValueError: package linux does not exist Hmm. I'm not sure how to help with that error. Nothing new has happened. I'm just hoping a kernel developer will take a look at this information in the hope that this issue can be addressed. Thank you for the information and help. Is this still a problem with the recent version (4.0.x or later)? LINE6 driver has been merged to the official sound driver tree recently, so there is a good chance that the issues have been fixed. Everything is working fine for me using Linux 4.0.5 on Arch Linux (and has been for a while, I forgot about this report) Good to hear :) Hi there. This topic hasn't been updated for an year and a half now but I am experiencing the exact same issues described here with Ubuntu 16.04.1 LTS and kernel version 4.0-47. I might try to migrate to Arch Linux, since it seems that you guys made it work on Arch, but I would prefer to stay with xubuntu or debian. Is there someone who managed to fix it on a debian based distro? Thanks! |