Thread: [Line6linux-user] HD300 and Jack
Status: Pre-Alpha
Brought to you by:
mgrabner
Menu
▾
▴
line6linux-user
|
From: Cristiano A. <cri...@ti...> - 2014-05-28 07:47:49
|
Hi all, I am very new to Jack and Linux audio in general, so I apologize if my questions are silly. I own a POD HD300, and I would like to use it as a sound card to loopback my guitar sound in the computer speakers...recording would also be nice. The POD gets appropriately recognized by the system and its device driver functions properly. In fact, I can hear sound using Pulse, of course with huge latency. I would like to use Jack for this (already properly installed and set it up for real time scheduling). Here is /proc/asound/cards: $ cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfcaf4000 irq 46 1 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xfeafc000 irq 17 2 [PODHD300 ]: line6usb - POD HD300 Line6 POD HD300 at USB 8-2:1.0 As you can see, device number 2 is my POD, and the device line6usb is used. I have also checked lsmod, and the driver is loaded in the kernel properly. Does this mean that the driver is there and that ALSA support the device? I have configured Jack from QJackCtl such that the interface I am using is my POD (interface box in the Setup window - interface which is different than the one used in Pulse). Now, I cannot really go on. The POD does not appear in the system tab of QJackCtl for some reason, only in the MIDI tab of the QjackCtl Connection window (therefore I cannot make a connection with the output playback, which appears in the audio tab instead). I have also noticed that it does not even appear in gnome-alsa-mixer, while the other audio devices do. Finally, if I do not make connections, and instead I configure the Setup window such that "input device" is the POD, and "output device" is the audio card connected to the speakers, the whole system freezes as soon as I start the Jack server. Any idea? Thanks a lot for helping Best Cristiano Scopri istella, il nuovo motore per il web italiano. Istella garantisce risultati di qualità e la possibilità di condividere, in modo semplice e veloce, documenti, immagini, audio e video. Usa istella, vai su http://www.istella.it?wtk=amc138614816829636 [1] Links: ------ [1] http://www.istella.it?wtk=amc138614816829636 Scopri istella, il nuovo motore per il web italiano. Istella garantisce risultati di qualità e la possibilità di condividere, in modo semplice e veloce, documenti, immagini, audio e video. Usa istella, vai su http://www.istella.it?wtk=amc138614816829636 |
|
From: Stefan H. <ste...@gm...> - 2014-05-28 08:42:33
|
On Wed, May 28, 2014 at 9:47 AM, Cristiano Alessandro <cri...@ti...> wrote: > $ cat /proc/asound/cards > > 0 [Intel ]: HDA-Intel - HDA Intel > HDA Intel at 0xfcaf4000 irq 46 > 1 [NVidia ]: HDA-Intel - HDA NVidia > HDA NVidia at 0xfeafc000 irq 17 > 2 [PODHD300 ]: line6usb - POD HD300 > Line6 POD HD300 at USB 8-2:1.0 Great, the driver is working and the sound card is available. First, launch pavucontrol and disable the HD300 in the Configuration tab. This ensures that PulseAudio will not interfere while JACK is using the device. If you wish to hear the guitar on your PC speakers, also disable your PC sound card in pavucontrol. Now launch qjackctl. If you want to use the HD300 for playback and capture, select HD300 as the Interface and make sure Audio is Duplex. Set Frames/Period to 128, Sample Rate to 48000, and Periods/Buffer to 2. Now click click Start to launch the JACK daemon. This is the configuration that I use. But it sounds like you want to use the HD300 as the capture (in) device and your PC soundcard as the playback (out) device. In that case you need select the Input Device and Output Device separately. I'm not sure how great JACK is at using two different sound devices - the reason is that they have independent sampling clocks which will drift apart over time. In my setup where everything goes through the HD300 I connect either headphones to the HD300's headphone socket or a PA speaker to the HD300's L/Mono socket. Hope this helps, Stefan |
|
From: Cristiano A. <cri...@ti...> - 2014-05-28 18:40:42
|
Hi Stefan, thanks for your reply. I have followed your suggestions and everything seems to be running. I can start the Jack server, and I can even define different audio cards for input and output. It works! However nothing comes out of the speakers. I have checked Alsa mixer and all the lines are in maximum volume. I am sure that the signals arrives to the PC, because I can record in Ardour and I can see the waveform, but I cannot hear anything. Not even if I play the track recorded in Ardour. Any idea? Thanks Cristiano On 05/28/2014 10:42 AM, Stefan Hajnoczi wrote: > On Wed, May 28, 2014 at 9:47 AM, Cristiano Alessandro > <cri...@ti...> wrote: > > Great, the driver is working and the sound card is available. > > First, launch pavucontrol and disable the HD300 in the Configuration > tab. This ensures that PulseAudio will not interfere while JACK is > using the device. > > If you wish to hear the guitar on your PC speakers, also disable your > PC sound card in pavucontrol. > > Now launch qjackctl. If you want to use the HD300 for playback and > capture, select HD300 as the Interface and make sure Audio is Duplex. > Set Frames/Period to 128, Sample Rate to 48000, and Periods/Buffer to > 2. Now click click Start to launch the JACK daemon. This is the > configuration that I use. > > But it sounds like you want to use the HD300 as the capture (in) > device and your PC soundcard as the playback (out) device. In that > case you need select the Input Device and Output Device separately. > I'm not sure how great JACK is at using two different sound devices - > the reason is that they have independent sampling clocks which will > drift apart over time. > > In my setup where everything goes through the HD300 I connect either > headphones to the HD300's headphone socket or a PA speaker to the > HD300's L/Mono socket. > > Hope this helps, > Stefan |
|
From: Cristiano A. <cri...@ti...> - 2014-05-28 18:48:27
|
ok, after some more testing I have understood the problem! It seems that Jack does not recognize the audio card of my PC. In the Setup window of QJackCtl I select duplex, and I can see the interfaces of both the POD and the built-in audio card. Thus I select the POD as input and the audio card as output device. However, when I open the Connection window, the built-in card does not show up. In the audio tab I can only see the menu for ardour and a menu "system" that refers to the POD (yes, I am sure...if I disconnect the system output to the system input I cannot hear sound from the headphones attached to the POD, and if I disconnect system out to ardour input, ardour does not get the guitar signal). Any help would be highly appreciated! Thanks Cristiano On 05/28/2014 08:22 PM, Cristiano Alessandro wrote: > Hi Stefan, > > thanks for your reply. > I have followed your suggestions and everything seems to be running. I > can start the Jack server, and I can even define different audio cards > for input and output. It works! > > However nothing comes out of the speakers. I have checked Alsa mixer > and all the lines are in maximum volume. I am sure that the signals > arrives to the PC, because I can record in Ardour and I can see the > waveform, but I cannot hear anything. Not even if I play the track > recorded in Ardour. > Any idea? > > Thanks > Cristiano > > > > On 05/28/2014 10:42 AM, Stefan Hajnoczi wrote: >> On Wed, May 28, 2014 at 9:47 AM, Cristiano Alessandro >> <cri...@ti...> wrote: >> >> Great, the driver is working and the sound card is available. >> >> First, launch pavucontrol and disable the HD300 in the Configuration >> tab. This ensures that PulseAudio will not interfere while JACK is >> using the device. >> >> If you wish to hear the guitar on your PC speakers, also disable your >> PC sound card in pavucontrol. >> >> Now launch qjackctl. If you want to use the HD300 for playback and >> capture, select HD300 as the Interface and make sure Audio is Duplex. >> Set Frames/Period to 128, Sample Rate to 48000, and Periods/Buffer to >> 2. Now click click Start to launch the JACK daemon. This is the >> configuration that I use. >> >> But it sounds like you want to use the HD300 as the capture (in) >> device and your PC soundcard as the playback (out) device. In that >> case you need select the Input Device and Output Device separately. >> I'm not sure how great JACK is at using two different sound devices - >> the reason is that they have independent sampling clocks which will >> drift apart over time. >> >> In my setup where everything goes through the HD300 I connect either >> headphones to the HD300's headphone socket or a PA speaker to the >> HD300's L/Mono socket. >> >> Hope this helps, >> Stefan > |
|
From: Stefan H. <ste...@gm...> - 2014-05-28 19:25:58
|
On Wed, May 28, 2014 at 8:48 PM, Cristiano Alessandro <cri...@ti...> wrote: > ok, after some more testing I have understood the problem! > It seems that Jack does not recognize the audio card of my PC. In the > Setup window of QJackCtl I select duplex, and I can see the interfaces > of both the POD and the built-in audio card. Thus I select the POD as > input and the audio card as output device. However, when I open the > Connection window, the built-in card does not show up. In the audio tab > I can only see the menu for ardour and a menu "system" that refers to > the POD (yes, I am sure...if I disconnect the system output to the > system input I cannot hear sound from the headphones attached to the > POD, and if I disconnect system out to ardour input, ardour does not get > the guitar signal). Does the Interface list widget in qjackctl Setup turn gray (disabled) when you select input and output devices that are not the same soundcard? Just to clarify, you need the following connections to record into Ardour and hear what Ardour plays: System Out connected to Ardour In. Ardour Out connected to System In. When you record in Ardour you should see the guitar waveform. When you play back the recorded waveform or an imported audio file in Ardour, you should hear it from your PC speakers. Do either of these work? Stefan |
|
From: Patrick C. <pm...@ve...> - 2014-05-28 13:05:57
|
On 05/28/2014 03:47 AM, Cristiano Alessandro wrote: > > I own a POD HD300, and I would like to use it as a sound card to > loopback my guitar sound in the computer > $ cat /proc/asound/cards > > 0 [Intel ]: HDA-Intel - HDA Intel > HDA Intel at 0xfcaf4000 irq 46 > 1 [NVidia ]: HDA-Intel - HDA NVidia > HDA NVidia at 0xfeafc000 irq 17 > 2 [PODHD300 ]: line6usb - POD HD300 > Line6 POD HD300 at USB 8-2:1.0 > Out of curiosity, what Linux distro and kernel are you using? It bothers me that the driver appears to work with Mint 13 and the current Ubuntu Studio version, but does not with AV Linux 6.0.1. The driver is there, and loads properly, but my PodXT doesn't show up as a soundcard. I'm ready to dump my PodXT for an Eleven Rack but I get the sense that that won't work either (no driver at all and no evidence that anyone is using it under Linux). |
|
From: Stefan H. <ste...@gm...> - 2014-05-28 13:17:22
|
On Wed, May 28, 2014 at 3:06 PM, Patrick Chase <pm...@ve...> wrote: > > On 05/28/2014 03:47 AM, Cristiano Alessandro wrote: >> >> I own a POD HD300, and I would like to use it as a sound card to >> loopback my guitar sound in the computer >> $ cat /proc/asound/cards >> >> 0 [Intel ]: HDA-Intel - HDA Intel >> HDA Intel at 0xfcaf4000 irq 46 >> 1 [NVidia ]: HDA-Intel - HDA NVidia >> HDA NVidia at 0xfeafc000 irq 17 >> 2 [PODHD300 ]: line6usb - POD HD300 >> Line6 POD HD300 at USB 8-2:1.0 >> > > Out of curiosity, what Linux distro and kernel are you using? It bothers > me that the driver appears to work with Mint 13 and the current Ubuntu > Studio version, but does not with AV Linux 6.0.1. The driver is there, > and loads properly, but my PodXT doesn't show up as a soundcard. Are there any relevant messages in dmesg showing the USB device connecting and the line6usb driver loading? Are you checking for the soundcard using cat /proc/asound/cards? What does lsusb | grep 0e41 say? Stefan |
|
From: Cristiano A. <cri...@ti...> - 2014-05-28 15:23:51
|
I am on Ubuntu 12.04 LTS. And I had to install no drivers myself, it was already there... Cristiano > Out of curiosity, what Linux distro and kernel are you using? It bothers > me that the driver appears to work with Mint 13 and the current Ubuntu > Studio version, but does not with AV Linux 6.0.1. The driver is there, > and loads properly, but my PodXT doesn't show up as a soundcard. I'm > ready to dump my PodXT for an Eleven Rack but I get the sense that that > won't work either (no driver at all and no evidence that anyone is using > it under Linux). Scopri istella, il nuovo motore per il web italiano. Istella garantisce risultati di qualità e la possibilità di condividere, in modo semplice e veloce, documenti, immagini, audio e video. Usa istella, vai su http://www.istella.it?wtk=amc138614816829636 [1] Links: ------ [1] http://www.istella.it?wtk=amc138614816829636 Scopri istella, il nuovo motore per il web italiano. Istella garantisce risultati di qualità e la possibilità di condividere, in modo semplice e veloce, documenti, immagini, audio e video. Usa istella, vai su http://www.istella.it?wtk=amc138614816829636 |
|
From: Patrick C. <pm...@ve...> - 2014-05-28 15:51:42
|
On 05/28/2014 09:17 AM, Stefan Hajnoczi wrote: >> >> Out of curiosity, what Linux distro and kernel are you using? It bothers >> me that the driver appears to work with Mint 13 and the current Ubuntu >> Studio version, but does not with AV Linux 6.0.1. The driver is there, >> and loads properly, but my PodXT doesn't show up as a soundcard. > Are there any relevant messages in dmesg showing the USB device > connecting and the line6usb driver loading? > > Are you checking for the soundcard using cat /proc/asound/cards? > > What does lsusb | grep 0e41 say? Hi Stephan. USB looks fine, but it's not available as a soundcard. Details on my troubleshooting is in the AV Linux support forum here: http://www.remastersys.com/forums/index.php?topic=3291 Bottom-line is that the drivers are there, they load properly, the USB device attaches and disconnects as expected, but the device does not show up as a soundcard and is not available in alsamixer. I suspect either a kernel support issue or an alsa support issue (i.e. drivers OK, but not supported). It works out-of-the-box with the included kernel module in Mint 13 (kernel 3.2.0-23) and Ubuntu Studio 12.04 (all in 64-bit fwiw). I can't remember which kernel AV Linux uses but can check. I had planned on trying alternate kernels anyway (to get this working). Thanks in advance for any guidance you can provide. -Patrick |
|
From: Stefan H. <ste...@gm...> - 2014-05-28 15:58:59
|
On Wed, May 28, 2014 at 5:51 PM, Patrick Chase <pm...@ve...> wrote: > > On 05/28/2014 09:17 AM, Stefan Hajnoczi wrote: >>> >>> >>> Out of curiosity, what Linux distro and kernel are you using? It bothers >>> me that the driver appears to work with Mint 13 and the current Ubuntu >>> Studio version, but does not with AV Linux 6.0.1. The driver is there, >>> and loads properly, but my PodXT doesn't show up as a soundcard. >> >> Are there any relevant messages in dmesg showing the USB device >> connecting and the line6usb driver loading? >> >> Are you checking for the soundcard using cat /proc/asound/cards? >> >> What does lsusb | grep 0e41 say? > > > Hi Stephan. USB looks fine, but it's not available as a soundcard. Details > on my troubleshooting is in the AV Linux support forum here: > > http://www.remastersys.com/forums/index.php?topic=3291 > > Bottom-line is that the drivers are there, they load properly, the USB > device attaches and disconnects as expected, but the device does not show up > as a soundcard and is not available in alsamixer. I suspect either a kernel > support issue or an alsa support issue (i.e. drivers OK, but not supported). > It works out-of-the-box with the included kernel module in Mint 13 (kernel > 3.2.0-23) and Ubuntu Studio 12.04 (all in 64-bit fwiw). > > I can't remember which kernel AV Linux uses but can check. I had planned on > trying alternate kernels anyway (to get this working). > > Thanks in advance for any guidance you can provide. Hard to say what the issue is. Personally, I don't use the svn source tree. Instead I check out the linux.git release tag for the appropriate kernel version (check uname -r) and compile the module. That way I know the driver is running on the kernel version it was intended for. The downside is that you don't get fixes that were committed in svn after the kernel release. But since development is not very active anyway, that's only an issue if you are using a very old kernel version. Anyway, if you want to get to the bottom of it, try adding printk() calls or use perf-probe(1) to see which functions in the driver are getting called. If it doesn't register an ALSA sound card then something must be going pretty wrong during initialization. Stefan |
|
From: Cristiano A. <cri...@ti...> - 2014-05-28 19:39:30
|
> Does the Interface list widget in qjackctl Setup turn gray (disabled) > when you select input and output devices that are not the same > soundcard? Yes it does. > > Just to clarify, you need the following connections to record into > Ardour and hear what Ardour plays: > > System Out connected to Ardour In. Ardour Out connected to System In. Connections are fine! > > When you record in Ardour you should see the guitar waveform. I can see it! > > When you play back the recorded waveform or an imported audio file in > Ardour, you should hear it from your PC speakers. This is the bit that does not work. When I play back I can hear the sound in the headphones connected to the POD. Essentially, the list "system" (input and output) refer to the POD, not to the sound card. Any idea? Cristiano |
|
From: Stefan H. <ste...@gm...> - 2014-05-28 19:44:56
|
On Wed, May 28, 2014 at 9:39 PM, Cristiano Alessandro <cri...@ti...> wrote: >> >> When you record in Ardour you should see the guitar waveform. > I can see it! >> >> When you play back the recorded waveform or an imported audio file in >> Ardour, you should hear it from your PC speakers. > > This is the bit that does not work. When I play back I can hear the > sound in the headphones connected to the POD. Essentially, the list > "system" (input and output) refer to the POD, not to the sound card. Okay, sounds like a JACK problem. I only use JACK with the HD300 as input and output, so I never encountered this problem. Maybe there is a JACK IRC channel or mailing list where you can ask for help. Stefan |
|
From: Patrick C. <pm...@ve...> - 2014-06-04 03:49:43
|
On 05/28/2014 11:58 AM, Stefan Hajnoczi wrote: > On Wed, May 28, 2014 at 5:51 PM, Patrick Chase <pm...@ve...> wrote: >> Hi Stephan. USB looks fine, but it's not available as a soundcard. >> Details on my troubleshooting is in the AV Linux support forum here: >> http://www.remastersys.com/forums/index.php?topic=3291 Bottom-line is >> that the drivers are there, they load properly, the USB device >> attaches and disconnects as expected, but the device does not show up >> as a soundcard and is not available in alsamixer. I suspect either a >> kernel support issue or an alsa support issue (i.e. drivers OK, but >> not supported). It works out-of-the-box with the included kernel >> module in Mint 13 (kernel 3.2.0-23) and Ubuntu Studio 12.04 (all in >> 64-bit fwiw). I can't remember which kernel AV Linux uses but can >> check. I had planned on trying alternate kernels anyway (to get this >> working). Thanks in advance for any guidance you can provide. > Hard to say what the issue is. Personally, I don't use the svn source > tree. Instead I check out the linux.git release tag for the > appropriate kernel version (check uname -r) and compile the module. > > That way I know the driver is running on the kernel version it was > intended for. The downside is that you don't get fixes that were > committed in svn after the kernel release. But since development is > not very active anyway, that's only an issue if you are using a very > old kernel version. > > Anyway, if you want to get to the bottom of it, try adding printk() > calls or use perf-probe(1) to see which functions in the driver are > getting called. If it doesn't register an ALSA sound card then > something must be going pretty wrong during initialization. > Hi Stefan. I can tell you that AV Linux 6.02 is using kernel 3.6.11.2. I bet if I found an old AV Linux version that used a 3.2 kernel it would work. Anyway, before switching to Ubuntu Studio, yes I would like to get to the bottom of it. The AV Linux guys may be able to fix this if they knew what was happening. Can you tell me where to add printk() calls? Or can you point me to a tutorial or similar? I'm at the edge of my knowledge here. Thanks. |
|
From: Stefan H. <ste...@gm...> - 2014-06-04 04:38:37
|
On Wed, Jun 4, 2014 at 5:49 AM, Patrick Chase <pm...@ve...> wrote: > > On 05/28/2014 11:58 AM, Stefan Hajnoczi wrote: >> >> On Wed, May 28, 2014 at 5:51 PM, Patrick Chase <pm...@ve...> wrote: >>> >>> Hi Stephan. USB looks fine, but it's not available as a soundcard. >>> Details on my troubleshooting is in the AV Linux support forum here: >>> http://www.remastersys.com/forums/index.php?topic=3291 Bottom-line is that >>> the drivers are there, they load properly, the USB device attaches and >>> disconnects as expected, but the device does not show up as a soundcard and >>> is not available in alsamixer. I suspect either a kernel support issue or an >>> alsa support issue (i.e. drivers OK, but not supported). It works >>> out-of-the-box with the included kernel module in Mint 13 (kernel 3.2.0-23) >>> and Ubuntu Studio 12.04 (all in 64-bit fwiw). I can't remember which kernel >>> AV Linux uses but can check. I had planned on trying alternate kernels >>> anyway (to get this working). Thanks in advance for any guidance you can >>> provide. >> >> Hard to say what the issue is. Personally, I don't use the svn source >> tree. Instead I check out the linux.git release tag for the >> appropriate kernel version (check uname -r) and compile the module. >> >> That way I know the driver is running on the kernel version it was >> intended for. The downside is that you don't get fixes that were >> committed in svn after the kernel release. But since development is >> not very active anyway, that's only an issue if you are using a very >> old kernel version. >> >> Anyway, if you want to get to the bottom of it, try adding printk() >> calls or use perf-probe(1) to see which functions in the driver are >> getting called. If it doesn't register an ALSA sound card then >> something must be going pretty wrong during initialization. >> > > Hi Stefan. I can tell you that AV Linux 6.02 is using kernel 3.6.11.2. I bet > if I found an old AV Linux version that used a 3.2 kernel it would work. If you have a working and a non-working version, then the most straightforward way to solve the mystery is bisection. http://git-scm.com/book/en/Git-Tools-Debugging-with-Git#Binary-Search https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html git-bisect(1) performs a binary search on the commit history between two commits. At each step in the search you compile and test the kernel. In the end it leaves you at the commit when the bug was introduced. There are plenty of tutorials online about using git-bisect(1). It can be time-consuming due to the kernel compilation time, but it will identify the exact commit where the bug was introduced. Good luck! Stefan |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X