Has anyone had any luck with any of the Pod Studio equipment? I recently bought the Pod Studio GX, and could not get it to work with the existing code.
The USB id for the device is 0x4153.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've got a Pod studio UX1. I've changed the line
#define LINE6_DEVID_TONEPORT_UX1 0x4141
to
#define LINE6_DEVID_TONEPORT_UX1 0x4150
where 0x4150 is the device id of my PodStudio UX1
It seem to work. At least, it play sound, but I didn't try to record anything nor changing settings so I don't know if advanced feature work.
Try to get the code, change the line
#define LINE6_DEVID_TONEPORT_GX 0x4147
to
#define LINE6_DEVID_TONEPORT_GX 0x4153
compile it and report to the dev if it work so it can be added in a next version of the driver.
( I assume that pod studio is just a rebranded version of tuneport and only the device id change. Please correct me if I'm wrong )
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I tried substituting the USB ID's for the POD STUDIO GX/TONEPORT GX but the device doesn't get recognized (of course I "rmmoded" the old module before trying)…
Maybe there is still no support for the TONEPORT GX.
I noticed the led stays green even though there is no driver loaded, while in windows it switches from red to green once the driver is loaded.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-12-30
What USB id did you use? ( the command lsusb can be used to get the id for your device)
Does the kernel log say anything interesting? (dmesg command)
How different is the TonePort GX from UX1?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anyway I managed to install the module correctly (the module was being copied to different locations under /lib/modules, had to remove them all).
The device gets recognized as a TONEPORT GX but I get my syslog spammed with such messages:
Dec 30 13:21:20 monnalisa kernel: CHECKPOINT "in callback" at 0.016198637 in /home/gzed/Scrivania/line6linux/driver/trunk/capture.c:196
Dec 30 13:21:20 monnalisa kernel: frame = 1640182
This happens whenever I try to access the audio interface for playback.
Playing back audio makes the GX ouput "click & pop".
I tried configuring jack to capture from the GX and output to my integrated audio but that locked my box pretty hard (had to reset).
Let me know if there's anything more I could be trying.
Cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Another small update, I managed to record my guitar with arecord.sh and it sounded mostly ok (occasional click 'n pops).
Monitoring sounds crazy. The sampled sound sounds like a 4 bit interface doing the sampling, pretty cool lo-fi effect though :)
I still can't get the device to playback samples properly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Playback on the Toneport GX is fixed in revision 567. However, I found out that the monitoring feature works perfectly on one machine (DiTech desktop), but produces the ugly sound you described on a different machine (Acer laptop). Both systems run openSUSE-11.2 (64 bit), I didn't yet figure out the reason for the different behaviour. Do you have the chance to test your Toneport GX with another computer?
Be aware, though, that the driver is currently in an instable state since I'm currently working on some new features.
Kind regards & good luck,<br>
Markus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Markus,
the only machine I tested your driver on is an Acer netbook, what a coincidence!
I'll test on my main desktop (with an asus motherboard) later to see whether it fixes monitoring.
One thing I haven't tried on the Acer is lowering the monitor and pcm levels… they were both at maximum level, and this could introduce distortion according to your driver docs.
Anyway i'll check out rev 567 immediatly and I will let you know how it goes.
Thanks for your support!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Markus,
I tested rev 568 on my desktop and the monitoring issue is still there.
Trying to play back audio doesn't work well, as the samples play but there are also loud cracks/clicks 'n pops. :(
Happy new year!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just noticed that monitoring works well with the Toneport GX on my Acer laptop if a jack daemon is running in full duplex mode for the GX. This is not a solution, but maybe a useful workaround (and a hint for further debugging…).
Kind regards,
Markus
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Markus,
playback is working fine here now, however I have an input signal only on the right channel (on the left one there is a very quite signal) and it's clipping rather soon (at less than 0dB). Monitoring gives a clean signal when it's not clipping. Keep up the good work!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Has anyone had any luck with any of the Pod Studio equipment? I recently bought the Pod Studio GX, and could not get it to work with the existing code.
The USB id for the device is 0x4153.
I've got a Pod studio UX1. I've changed the line
#define LINE6_DEVID_TONEPORT_UX1 0x4141
to
#define LINE6_DEVID_TONEPORT_UX1 0x4150
where 0x4150 is the device id of my PodStudio UX1
It seem to work. At least, it play sound, but I didn't try to record anything nor changing settings so I don't know if advanced feature work.
Try to get the code, change the line
#define LINE6_DEVID_TONEPORT_GX 0x4147
to
#define LINE6_DEVID_TONEPORT_GX 0x4153
compile it and report to the dev if it work so it can be added in a next version of the driver.
( I assume that pod studio is just a rebranded version of tuneport and only the device id change. Please correct me if I'm wrong )
I tried substituting the USB ID's for the POD STUDIO GX/TONEPORT GX but the device doesn't get recognized (of course I "rmmoded" the old module before trying)…
Maybe there is still no support for the TONEPORT GX.
I noticed the led stays green even though there is no driver loaded, while in windows it switches from red to green once the driver is loaded.
What USB id did you use? ( the command lsusb can be used to get the id for your device)
Does the kernel log say anything interesting? (dmesg command)
How different is the TonePort GX from UX1?
Hi,
I swapped those IDs in usbdefs.h:
#define LINE6_DEVID_PODSTUDIO_GX 0x4147
#define LINE6_DEVID_TONEPORT_GX 0x4153
Anyway I managed to install the module correctly (the module was being copied to different locations under /lib/modules, had to remove them all).
The device gets recognized as a TONEPORT GX but I get my syslog spammed with such messages:
Dec 30 13:21:20 monnalisa kernel: CHECKPOINT "in callback" at 0.016198637 in /home/gzed/Scrivania/line6linux/driver/trunk/capture.c:196
Dec 30 13:21:20 monnalisa kernel: frame = 1640182
This happens whenever I try to access the audio interface for playback.
Playing back audio makes the GX ouput "click & pop".
I tried configuring jack to capture from the GX and output to my integrated audio but that locked my box pretty hard (had to reset).
Let me know if there's anything more I could be trying.
Cheers
another log snippet:
Dec 30 12:59:38 monnalisa kernel: usb 3-2: configuration #1 chosen from 1 choice
Dec 30 13:01:40 monnalisa kernel: usbcore: deregistering interface driver line6usb
Dec 30 13:01:49 monnalisa kernel: line6usb: module is from the staging directory, the quality is unknown, you have been warned.
Dec 30 13:01:49 monnalisa kernel: line6usb driver version 0.8.0 (revision 529)
Dec 30 13:01:49 monnalisa kernel: usbcore: registered new interface driver line6usb
Dec 30 13:02:52 monnalisa kernel: usb 3-2: USB disconnect, address 3
Dec 30 13:02:54 monnalisa kernel: usb 3-2: new full speed USB device using uhci_hcd and address 4
Dec 30 13:02:54 monnalisa kernel: usb 3-2: configuration #1 chosen from 1 choice
Dec 30 13:11:28 monnalisa kernel: usbcore: deregistering interface driver line6usb
Dec 30 13:13:48 monnalisa kernel: line6usb driver version 0.8.1
Dec 30 13:13:48 monnalisa kernel: line6usb 3-2:1.0: Line6 TonePort GX found
Dec 30 13:13:48 monnalisa kernel: line6usb 3-2:1.0: Line6 TonePort GX now attached
Dec 30 13:13:48 monnalisa kernel: Line6 device 0: TonePort GX:0
Dec 30 13:13:48 monnalisa kernel: Line6 device 1: (not used)
Dec 30 13:13:48 monnalisa kernel: Line6 device 2: (not used)
Dec 30 13:13:48 monnalisa kernel: Line6 device 3: (not used)
Dec 30 13:13:48 monnalisa kernel: Line6 device 4: (not used)
Dec 30 13:13:48 monnalisa kernel: Line6 device 5: (not used)
Dec 30 13:13:48 monnalisa kernel: Line6 device 6: (not used)
Dec 30 13:13:48 monnalisa kernel: Line6 device 7: (not used)
Dec 30 13:13:48 monnalisa kernel: usbcore: registered new interface driver line6usb
Dec 30 13:13:48 monnalisa kernel: CHECKPOINT "before submit out" at 0.000006285 in /home/gzed/Scrivania/line6linux/driver/trunk/playback.c:255
Dec 30 13:13:48 monnalisa kernel: frame = -1
Dec 30 13:13:48 monnalisa kernel: CHECKPOINT "after submit out" at 0.000046723 in /home/gzed/Scrivania/line6linux/driver/trunk/playback.c:263
Dec 30 13:13:48 monnalisa kernel: CHECKPOINT "before submit out" at 0.000062228 in /home/gzed/Scrivania/line6linux/driver/trunk/playback.c:255
Dec 30 13:13:48 monnalisa kernel: frame = -1
Dec 30 13:13:48 monnalisa kernel: CHECKPOINT "after submit out" at 0.000082552 in /home/gzed/Scrivania/line6linux/driver/trunk/playback.c:263
Dec 30 13:13:48 monnalisa kernel: CHECKPOINT "out callback" at 0.010282802 in /home/gzed/Scrivania/line6linux/driver/trunk/playback.c:356
Dec 30 13:13:48 monnalisa kernel: frame = 1188290
Another small update, I managed to record my guitar with arecord.sh and it sounded mostly ok (occasional click 'n pops).
Monitoring sounds crazy. The sampled sound sounds like a 4 bit interface doing the sampling, pretty cool lo-fi effect though :)
I still can't get the device to playback samples properly.
Playback on the Toneport GX is fixed in revision 567. However, I found out that the monitoring feature works perfectly on one machine (DiTech desktop), but produces the ugly sound you described on a different machine (Acer laptop). Both systems run openSUSE-11.2 (64 bit), I didn't yet figure out the reason for the different behaviour. Do you have the chance to test your Toneport GX with another computer?
Be aware, though, that the driver is currently in an instable state since I'm currently working on some new features.
Kind regards & good luck,<br>
Markus
Markus,
the only machine I tested your driver on is an Acer netbook, what a coincidence!
I'll test on my main desktop (with an asus motherboard) later to see whether it fixes monitoring.
One thing I haven't tried on the Acer is lowering the monitor and pcm levels… they were both at maximum level, and this could introduce distortion according to your driver docs.
Anyway i'll check out rev 567 immediatly and I will let you know how it goes.
Thanks for your support!
Hi Markus,
I tested rev 568 on my desktop and the monitoring issue is still there.
Trying to play back audio doesn't work well, as the samples play but there are also loud cracks/clicks 'n pops. :(
Happy new year!
I just noticed that monitoring works well with the Toneport GX on my Acer laptop if a jack daemon is running in full duplex mode for the GX. This is not a solution, but maybe a useful workaround (and a hint for further debugging…).
Kind regards,
Markus
Revision 569 works considerably better on my Acer (still not perfect, some occasional clicks remain). Could you please try it?
Kind regards,
Markus
Hi Markus,
playback is working fine here now, however I have an input signal only on the right channel (on the left one there is a very quite signal) and it's clipping rather soon (at less than 0dB). Monitoring gives a clean signal when it's not clipping. Keep up the good work!