line6linux-user Mailing List for Line6 Linux software (Page 2)
Status: Pre-Alpha
Brought to you by:
mgrabner
Menu
▾
▴
line6linux-user — mailing list for users of Line6 Linux software
You can subscribe to this list here.
| 2008 |
Jan
(3) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
(2) |
Aug
(7) |
Sep
(3) |
Oct
|
Nov
(2) |
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(2) |
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
(5) |
Nov
(2) |
Dec
|
| 2012 |
Jan
(5) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
(3) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
(16) |
| 2013 |
Jan
(42) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(12) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(1) |
Nov
|
Dec
|
| 2017 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(5) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
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: 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 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 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: Patrick C. <pm...@ve...> - 2014-01-20 05:15:23
|
Been working on this for a while. I have a Mint 13 (Maya) box that I
sometimes boot into the newest UbuntuStudio -- both work fine with the
PODxt using the line6usb driver module provided in staging.
But AVLinux and kxstudio do not. The driver is available as a module and
loads. USB recognises the device. But the PODxt does not show up as a
soundcard. My other internal soundcard works fine so I believe that ALSA
and the core sound drivers are all OK. I'm unsure how to proceed because
everything appears in order. I've tried unloading and reloading the
module and also installed the driver package from the repository.
Everything seems to be working correctly, but the recognized USB device
does not appear as an available soundcard.
Where should I look next to keep troubleshooting?
From AVLinux:
# uname -a
Linux darkglow 3.6.11.2-avl1 #113 SMP PREEMPT Fri May 10 07:15:26 EDT
2013 i686 GNU/Linux
Module is available:
$ cat /boot/config-$(uname -r) | grep -i line6
CONFIG_LINE6_USB=m
# CONFIG_LINE6_USB_DEBUG is not set
# CONFIG_LINE6_USB_DUMP_CTRL is not set
# CONFIG_LINE6_USB_DUMP_MIDI is not set
# CONFIG_LINE6_USB_DUMP_PCM is not set
# CONFIG_LINE6_USB_RAW is not set
# CONFIG_LINE6_USB_IMPULSE_RESPONSE is not set
Module is loaded:
# lsmod | grep -i line6
line6usb 56695 0
snd_rawmidi 12126 2 line6usb,snd_seq_midi
snd_pcm 48030 5
snd_aloop,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,line6usb
snd 34878 15
snd_hda_codec_realtek,snd_aloop,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_seq_device,line6usb
usbcore 94358 9
usblp,usb_storage,ohci_hcd,ehci_hcd,gspca_main,usbhid,gspca_zc3xx,xhci_hcd,line6usb
# cat /sys/module/line6usb/version
0.9.1beta (904)
Driver is in staging:
# ls /lib/modules/3.6.11.2-avl1/kernel/drivers/staging/line6
line6usb.ko
$ lsusb
...
Bus 005 Device 003: ID 0e41:5044 Line6, Inc. PODxt
...
$ dmesg
[ 542.915477] usb 5-1: USB disconnect, device number 2
[ 542.916166] line6usb 5-1:1.0: Line6 PODxt now disconnected
[ 910.466347] usb 5-1: new full-speed USB device number 3 using ohci_hcd
[ 910.634793] usb 5-1: New USB device found, idVendor=0e41, idProduct=5044
[ 910.634797] usb 5-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[ 910.634799] usb 5-1: Product: PODxt
[ 910.634801] usb 5-1: Manufacturer: Line 6
[ 910.636816] line6usb 5-1:1.0: Line6 PODxt found
[ 910.638845] line6usb 5-1:1.0: Line6 PODxt now attached
In UbuntuStudio, my soundcards have this entry and the device is
selectable in the mixers and using software like Ardour or Audacity.
ubuntu-studio@ubuntu-studio:~$ cat /proc/asound/cards
0 [PODxt ]: line6usb - PODxt
Line6 PODxt at USB 5-1:1.0
thanks in advance for any assistance.
-Patrick
|
|
From: CK F. <fra...@go...> - 2014-01-10 03:45:58
|
Problem making UX8 from source checked out in the last 12 hours. Make barfs on: (...)/line6linux-code/driver/branches/ux8/toneport.c: In function ‘toneport_setup’: (...)/line6linux-code/driver/branches/ux8/toneport.c:423:11: error: too few arguments to function ‘line6_send_raw_message_async’ (...)/line6linux-code/driver/branches/ux8/driver.h:198:12: note: declared here make[4]: *** [(...)/line6linux-code/driver/branches/ux8/toneport.o] Error 1 make[3]: *** [_module_(...)/line6linux-code/driver/branches/ux8] Error 2 make[2]: *** [sub-make] Error 2 make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-4-amd64' Anyone else seeing this? |
|
From: Marc B. <kle...@ho...> - 2013-07-27 13:31:24
|
Hi, I've got a line6 POD XT Live and ubuntustudio 13.04 and I'm having some trouble getting things to work. The USB driver itself seems to load fine; when connecting the USB cable, I can see MIDI being dumped whenever I work any of the controls on the pedalboard. When I try recording any audio in audacity, however, I'm getting the following message: "Error while opening sound device. Please check the input device settings and the project sample rate." Quality settings of Audacity are at 44k1/16 bits but I'm getting the same message at 32 bit float and 48kHz as well. When starting audacity from the command line, some errors are logged to the console (and as both mention sample rate, they seem to be related): ===snip=== Expression 'SetApproximateSampleRate( pcm, hwParams, sr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1968 Expression 'PaAlsaStreamComponent_InitialConfigure( &self->capture, inParams, self->primeBuffers, hwParamsCapture, &realSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2643 Expression 'PaAlsaStream_Configure( stream, inputParameters, outputParameters, sampleRate, framesPerBuffer, &inputLatency, &outputLatency, &hostBufferSizeMode )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2767 Expression 'SetApproximateSampleRate( pcm, hwParams, sr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1968 Expression 'PaAlsaStreamComponent_InitialConfigure( &self->capture, inParams, self->primeBuffers, hwParamsCapture, &realSr )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2643 Expression 'PaAlsaStream_Configure( stream, inputParameters, outputParameters, sampleRate, framesPerBuffer, &inputLatency, &outputLatency, &hostBufferSizeMode )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2767 Expression 'stream->capture.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4525 ===/snip=== I have also tried using the device via JACK, which gives this message: Invalid container address 'driver':'channel':'(null)' supplied to method 'ResetParameterValue'.. (org.jackaudio.Error.InvalidArgs) What could be going on? Where do I proceed troubleshooting? Best, Marc |
|
From: Germán B. <zil...@gm...> - 2013-05-20 05:20:46
|
Hello, as the title says... I'm on a bit of a problem here. I'm running Ubuntu Studio and trying to get my POD Studio UX2 working here (It's actually the las sthing that attaches me to Winbugs, so I'd be greately happy if I could make this work!!) I installed line6usb drivers from the sources in the trunk using wget and my terminal, and mi Studio UX2 is known by my computer now... the thing is that I can't seem to be able to open a jack server with it so I can't make no playing and no recording :S Most of the times I plug it in and it gets on nicely, but with the annoying thing that one of the clip lights is turned on (Not quite sure what that means if I'm not playing or even not with the guitar plugged in...). Anyway, something that I've noticed is that, yesterday I plugged in my UX2 and got recognized without any of the clip buttons lightened up... miraculously I press "Start" on Qjackctl and the server started flawlessly!!! And when I selected JACK output with Audacious I could actually hear audio from my headphones connected to the UX2 (Made me so happy :') ). At some point I tried to lower down the volume on the control of my hardware, no more sound was played and crashed my audacious... (same thing happened later by modifying the volume controls on my computer instead of on my UX2) Now somehow I couldn't go back to plug my UX2 in and don't get any clip light on or Jack server up... Help please!! *Here's what I get when I try to start Qjackctl:* 10:07:16.231 Patchbay desactivada. 10:07:16.364 Reiniciar estadísticas. 10:07:16.372 Cambios en las conexiones ALSA. 10:07:16.392 D-BUS: Disponible (org.jackaudio.service aka jackdbus). 10:07:16.635 D-BUS: El servidor JACK no puede iniciarse. Disculpa Cannot connect to server socket err = No existe el archivo o el directorio Cannot connect to server request channel jack server is not running or cannot be started Cannot connect to server socket err = No existe el archivo o el directorio Cannot connect to server request channel jack server is not running or cannot be started 10:07:16.685 Cambió el gráfico de conexiones ALSA. Sat May 18 10:07:16 2013: Starting jack server... Sat May 18 10:07:16 2013: JACK server starting in realtime mode with priority 10 Sat May 18 10:07:16 2013: control device hw:2 Sat May 18 10:07:16 2013: control device hw:2 Sat May 18 10:07:16 2013: [1m[31mERROR: Failed to acquire device name : Audio2 error : Cannot allocate memory[0m Sat May 18 10:07:16 2013: [1m[31mERROR: Audio device hw:2 cannot be acquired...[0m Sat May 18 10:07:16 2013: [1m[31mERROR: Cannot initialize driver[0m Sat May 18 10:07:16 2013: [1m[31mERROR: JackServer::Open failed with -1[0m Sat May 18 10:07:16 2013: [1m[31mERROR: Failed to open server[0m Sat May 18 10:07:17 2013: Saving settings to "/home/german/.config/jack/conf.xml" ... 10:07:18.893 No puede conectarse al servidor JACK como cliente. - La operación global falló. - No puede conectarse al servidor. Por favor revise la ventana de mensajes para mas información. Cannot connect to server socket err = No existe el archivo o el directorio Cannot connect to server request channel jack server is not running or cannot be started *Here's what I get on arecord -l:* german@Asd:~$ arecord -l **** Lista de CAPTURE dispositivos hardware **** tarjeta 0: SB [HDA ATI SB], dispositivo 0: ALC269VB Analog [ALC269VB Analog] Subdispositivos: 1/1 Subdispositivo #0: subdevice #0 tarjeta 2: PODStudioUX2 [POD Studio UX2], dispositivo 0: POD Studio UX2 [POD Studio UX2] Subdispositivos: 1/1 Subdispositivo #0: subdevice #0 *And here's what I get on aplay -l:* german@Asd:~$ aplay -l **** Lista de PLAYBACK dispositivos hardware **** tarjeta 0: SB [HDA ATI SB], dispositivo 0: ALC269VB Analog [ALC269VB Analog] Subdispositivos: 1/1 Subdispositivo #0: subdevice #0 tarjeta 1: Generic [HD-Audio Generic], dispositivo 3: HDMI 0 [HDMI 0] Subdispositivos: 1/1 Subdispositivo #0: subdevice #0 tarjeta 2: PODStudioUX2 [POD Studio UX2], dispositivo 0: POD Studio UX2 [POD Studio UX2] Subdispositivos: 1/1 Subdispositivo #0: subdevice #0 So... the hardware is detected... but somehow jack can't communicate with it so well... Any hint? *Now when the Jack server starts succesfully and I try to route something to the UX2 now I get this:* Sat May 18 10:29:35 2013: [1m[31mERROR: ALSA: poll time out, polled for 8706070 usecs[0m Sat May 18 10:29:35 2013: [1m[31mERROR: JackAudioDriver:rocessAsync: read error, stopping...[0m 10:29:51.928 Cambió el gráfico de conexiones ALSA. Sat May 18 10:29:51 2013: [1m[31mERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out[0m Sat May 18 10:29:51 2013: [1m[31mERROR: Driver is not running[0m Sat May 18 10:29:51 2013: [1m[31mERROR: Cannot create new client[0m Sat May 18 10:30:39 2013: [1m[31mERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out[0m Sat May 18 10:30:39 2013: [1m[31mERROR: Driver is not running[0m Sat May 18 10:30:39 2013: [1m[31mERROR: Cannot create new client[0m Sat May 18 10:31:39 2013: [1m[31mERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out[0m Sat May 18 10:31:39 2013: [1m[31mERROR: Driver is not running[0m Sat May 18 10:31:39 2013: [1m[31mERROR: Cannot create new client[0m Sat May 18 10:31:44 2013: [1m[31mERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out[0m Sat May 18 10:31:44 2013: [1m[31mERROR: Driver is not running[0m Sat May 18 10:31:44 2013: [1m[31mERROR: Cannot create new client[0m Sat May 18 10:32:08 2013: [1m[31mERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out[0m Sat May 18 10:32:08 2013: [1m[31mERROR: Driver is not running[0m Sat May 18 10:32:08 2013: [1m[31mERROR: Cannot create new client[0m 10:32:12.864 Cambió el gráfico de conexiones ALSA. Sat May 18 10:32:13 2013: [1m[31mERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out[0m Sat May 18 10:32:13 2013: [1m[31mERROR: Driver is not running[0m Sat May 18 10:32:13 2013: [1m[31mERROR: Cannot create new client[0m Sat May 18 10:32:37 2013: [1m[31mERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out[0m Sat May 18 10:32:37 2013: [1m[31mERROR: Driver is not running[0m Sat May 18 10:32:37 2013: [1m[31mERROR: Cannot create new client[0m Sat May 18 10:32:42 2013: [1m[31mERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out[0m Sat May 18 10:32:42 2013: [1m[31mERROR: Driver is not running[0m Sat May 18 10:32:42 2013: [1m[31mERROR: Cannot create new client[0m (qjackctl.real:2541): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion `GTK_IS_WIDGET (widget)' failed (qjackctl.real:2541): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion `GTK_IS_WIDGET (widget)' failed Sat May 18 10:38:19 2013: [1m[31mERROR: JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out[0m Sat May 18 10:38:19 2013: [1m[31mERROR: Driver is not running[0m Sat May 18 10:38:19 2013: [1m[31mERROR: Cannot create new client[0m (qjackctl.real:2541): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion `GTK_IS_WIDGET (widget)' failed (qjackctl.real:2541): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion `GTK_IS_WIDGET (widget)' failed And when I try to open Rakarrack a message window appears that says that no jack server is detected :S I'm a bit confused, and now jack don't start at all and I don't have the clip light on... -.- |
|
From: Steve U. <st...@co...> - 2013-01-21 14:50:49
|
Hi, It looks like the HD300 file format has a lot in common with the HD500. I figured out much of the contents of the .h5e files some time ago, and wrote some basic code to dump the contents of those files, or load them into an HD500 using USB. Its quite a while since I had any free time to work on this. My latest code can be found at http://www.soft-switch.org/downloads/line6 if anyone else would like to work on it. Regards, Steve On 01/17/2013 03:26 PM, jea...@fr... wrote: > > > > > Hi > > here my first notes about HD 300 : > > First file format (h3e) > ---------- > > all value are hex > > Byte offset Field Value > -- > 0 - 4 File Sig "H3EP" > 4 -27 Unknown > 28 -37 Name Ascii codes > 38 ?? always 0 ? > 39 Amps on ? 80 for amp on, 81 Amp on + > gate, C0 Amp on + wha on > 3A > 3B Amps code ? Set to 0C in Brit 800 > file, 00 in BlackFace one > 3C > 3D Cab code ? Set to 12 for brit 800 no > cab, 0D in brit 800 +screamer , 00 in BlackFace one > 3E - 3F Drive Value 00 for 0, 40 > 00 for 50%, 7F FF for 100% > 40 -41 Bass Value 00 for 0, 40 > 00 for 50%, 7F FF for 100% > 42 -43 Mid Value 00 for 0, 40 00 > for 50%, 7F FF for 100% > 44 -45 Treble Value 00 for 0, 40 > 00 for 50%, 7F FF for 100% > 46 -47 CH Volume Value 00 for 0, 40 00 > for 50%, 7F FF for 100% > 48 -49 Presence Value 00 for 0, 40 00 > for 50%, 7F FF for 100% > 4A -4B ?? > 4C Mic code ? 04 for 4308 Ribbon ? > 4D -4F > 50 -51 Bypass Volume Value 00 for 0, 40 > 85 for 50%, 7F FF for 100% > 52 -53 > 54 -55 ??? > 5C -65 ???? Change from all 00 to 3F FF > repeated 5 time if when changing wha to weeper, change when editing > bias setting > 66 -71 ??? > 72 FX1 code ? Set 04 When screamer is > set on and routed pre, 06 when on and set post, 0 if FX2 off > 73 -79 FX 1 param ? > 74 FX2 code ? Set to 04 when Analog > Chorus is on, 0 if FX3 off > 75 -81 FX2 param ? > 82 FX3 code ? Set to 04 when Digital > Delay is on, 0 if FX3 off > 83 -C7 Unknown > > > -------- > > then midi code i've found : > > Mode button : > To effect mode : > F0 00 01 0C 14 00 63 00 04 15 00 00 02 F7 > > To Preset mode : > F0 00 01 0C 14 00 63 00 04 15 00 00 00 F7 > > To looper mode > F0 00 01 0C 14 00 63 00 04 15 00 00 01 F7 > > Preset Mode > A switch > B0 00 00 > B0 20 00 > C0 04 > B0 07 7F > > B switch : > B0 00 00 > B0 20 00 > C0 05 > B0 07 7F > > C switch : > B0 00 00 > B0 20 00 > C0 06 > B0 07 7F > > > D switch : > B0 00 00 > B0 20 00 > C0 07 > B0 07 7F > > > FX mode : > > Amp off then on > F0 00 01 0C 14 00 63 00 02 14 00 00 00 F7 > F0 00 01 0C 14 00 63 00 02 14 00 00 01 F7 > > Fx1 off then on > F0 00 01 0C 14 00 63 00 10 03 00 00 00 F7 > F0 00 01 0C 14 00 63 00 10 03 00 00 01 F7 > > Fx 2 on then off > F0 00 01 0C 14 00 63 00 11 03 00 00 01 F7 > F0 00 01 0C 14 00 63 00 11 03 00 00 00 F7 > > Fx 3 on then off > F0 00 01 0C 14 00 63 00 12 03 00 00 01 F7 > F0 00 01 0C 14 00 63 00 12 03 00 00 00 F7 > > Tap 3 times > F0 00 01 0C 14 00 63 00 02 06 07 56 55 F7 > F0 00 01 0C 14 00 63 00 02 06 08 07 27 F7 > > Tap 4 times > F0 00 01 0C 14 00 63 00 02 06 09 0E 02 F7 > F0 00 01 0C 14 00 63 00 02 06 08 2E 18 F7 > F0 00 01 0C 14 00 63 00 02 06 08 2E 18 F7 > > > Vol pedal up then down > > B0 07 7F > B0 07 7E > B0 07 7C > B0 07 79 > B0 07 77 > B0 07 73 > B0 07 6F > B0 07 6B > B0 07 66 > B0 07 62 > B0 07 5D > B0 07 59 > B0 07 53 > B0 07 4E > B0 07 49 > B0 07 44 > B0 07 3F > B0 07 39 > B0 07 33 > B0 07 2C > B0 07 25 > B0 07 1D > B0 07 14 > B0 07 0C > B0 07 02 > B0 07 00 > B0 07 04 > B0 07 0B > B0 07 11 > B0 07 19 > B0 07 20 > B0 07 27 > B0 07 2D > B0 07 33 > B0 07 3A > B0 07 40 > B0 07 45 > B0 07 4A > B0 07 4E > B0 07 53 > B0 07 58 > B0 07 5D > B0 07 61 > B0 07 65 > B0 07 6B > B0 07 70 > B0 07 74 > B0 07 78 > B0 07 7C > B0 07 7F > > > Amp change : > F0 00 01 0C 14 00 63 00 00 0A 00 00 06 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 07 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 08 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 09 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 0A F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 0B F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 0C F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 0D F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 0E F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 0F F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 10 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 11 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 12 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 13 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 14 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 15 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 16 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 17 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 18 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 19 F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 1A F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 1B F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 1C F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 1D F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 1E F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 1E F7 > F0 00 01 0C 14 00 63 00 00 0A 00 00 1E F7 > > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122712 > > > _______________________________________________ > Line6linux-user mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/line6linux-user |
|
From: <jea...@fr...> - 2013-01-21 14:13:23
|
Hi, What about this patch ? best regards ----- Mail original ----- De: "jeanseb" <jea...@fr...> À: "Stefan Hajnoczi" <ste...@gm...> Cc: "Jelmer Vernooij" <je...@sa...>, lin...@li... Envoyé: Vendredi 11 Janvier 2013 22:52:31 Objet: Re: [Line6linux-user] Which version for HD300 Hi again, I've added debian patch system (with quilt) to the debian package and reverted the use of usb_device macro for debian only. Here a patch against curent Cvs. Module now find the card (and compile contrary to squeeze package if not to late for being back wheezy). Work fine with alsa and jack. best regards Le Fri, 11 Jan 2013 09:03:05 +0100, Stefan Hajnoczi <ste...@gm...> a écrit : > On Fri, Jan 11, 2013 at 7:34 AM, <jea...@fr...> wrote: > > Thanks, > > > > I've take a looj to code of usb-skeleton driver on > > http://lxr.linux.no , macro module_usb_driver seem to have been > > introduce by 3.3 kernel. > > > > This macro does nothing but creating empty side effect for > > registering driver. Do I will try to make a pacth with the good > > preprocessor test kernel version and reintroduce the > > module_init/exit stuff this WE. > > The simplest solution is probably to build a vanilla kernel. Try > 3.8-rc2, I'm using the upstream driver with my POD HD300 successfully. > > Use Debian's make-kpkg and it'll build a .deb for you that installs > just like a distro kernel. > > Stefan ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Line6linux-user mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/line6linux-user |
|
From: Markus G. <gr...@ic...> - 2013-01-20 21:21:49
|
Am Sonntag, 13. Januar 2013, 22:23:13 schrieb Markus Grabner: > Am Dienstag, 8. Januar 2013, 23:54:20 schrieb Mariusz Kozlowski: > > On Tue, Jan 08, 2013 at 09:21:49PM +0100, Markus Grabner wrote: > > > In the meantime, you could try to find out the minimum values for the > > > startup delays (POD_STARTUP_DELAY[1|2] in pod.h) such that the driver > > > works on your system. The first value is the initial delay after the > > > device is connected, the second value is the delay between the following > > > initialization steps. Since we are currently touching the code, we > > > should > > > use the chance to make device initialization faster if possible. > > > > Ok so this is how I tested it: > > > > 1. <change pod.h> && make > > 2. <try to play some samples via POD alsa interface> > > 3. while true; do sudo insmod line6usb.ko; sleep 4; sudo rmmod line6usb; > > done > > > > And that's left for a few miutes to see if anything blows up. > > > > D1 D2 > > 1000 + 100 -> works ok > > 100 + 50 -> works ok > > 50 + 10 -> oops on insmod from time to time > > 0 + 20 -> oops on insmod > > 0 + 0 -> sometimes works, sometimes oops > > > > Tests with values of D1 below 100 produce lots of additional communication > > until firmware version request arrives. That is not seen for values above > > 100 but maybe certain combination of D1 + D2 triggers that additional > > messages. > > > > So 100 + 50 seems reasonable. > > Thanks for testing! I tried these settings, but they didn't work for me. I > did the following: > *) compile and install the driver > *) connect the PODxt Live with main powers switched off > *) switch on main powers of PODxt Live > > Then the message "Invalid Code Error 8" is displayed on the device (which > was actually the reason for implementing the delayed startup procedure in > the first place). D1=200 and D1=300 have the same problem, only with D1=400 > the device starts up correctly. D2=50 works fine. I will test with these > values for a while and then commit them with a broad safety margin. I didn't experience any problems with these values, but considering a safety margin, I will keep the old values (D1=1000, D2=100) which are well tested by others. I just committed the new initialization procedure to the trunk. Kind regards, Markus |
|
From: jeanseb <jea...@fr...> - 2013-01-20 14:51:58
|
Hi, you ca find last verison of the parser at http://jeanseb.valette.free.fr Le Fri, 18 Jan 2013 17:47:57 +0100, Stefan Hajnoczi <ste...@gm...> a écrit : > On Fri, Jan 18, 2013 at 3:47 PM, <jea...@fr...> wrote: > > You will find in PJ a test parser for h3e preset file. > > > > Name have to be tested as i reported them from the doc in same > > order (it workd for the 2 first amp and Brit J800 that i had > > tested) , FX model is a guess to be check (i will try to buil > > preset file with != FX)this WE). > > > > For FX 400 effect I've include them in same order, but they may not > > be "reserved" value, so last effect should be shift (or not). > > > > For the design ofa full php site, i guess, for the data model, we > > had to build a parent class for file handling and children class > > for != kind of files (hd 300, hd 400 , hd 500). > > > > Then a controler that produce an array of object (amp, cab, > > fx ...) and a viewer that parse the and display it content. > > > > Saving will be a matter of of choosing a format and give the array > > to a controlller that call the good model class. > > Nice start! > > If you want testers throw the php file onto a server or free hosting > and post a link on the Line6 POD forum. I'm sure people will try > their files and report back if something doesn't work. > > If the parsing code gets more complicated it may be worth writing > command-line tools and calling them from PHP (make them output both > human-readable info and JSON). I think Markus was working on this for > previous POD generations: > http://line6linux.svn.sourceforge.net/viewvc/line6linux/apps/trunk/toneview/tone.cpp?revision=513&view=markup > http://line6linux.svn.sourceforge.net/viewvc/line6linux/apps/trunk/filedump_test/ > > Stefan |
|
From: <jea...@fr...> - 2013-01-17 07:27:09
|
Hi here my first notes about HD 300 : First file format (h3e) ---------- all value are hex Byte offset Field Value -- 0 - 4 File Sig "H3EP" 4 -27 Unknown 28 -37 Name Ascii codes 38 ?? always 0 ? 39 Amps on ? 80 for amp on, 81 Amp on + gate, C0 Amp on + wha on 3A 3B Amps code ? Set to 0C in Brit 800 file, 00 in BlackFace one 3C 3D Cab code ? Set to 12 for brit 800 no cab, 0D in brit 800 +screamer , 00 in BlackFace one 3E - 3F Drive Value 00 for 0, 40 00 for 50%, 7F FF for 100% 40 -41 Bass Value 00 for 0, 40 00 for 50%, 7F FF for 100% 42 -43 Mid Value 00 for 0, 40 00 for 50%, 7F FF for 100% 44 -45 Treble Value 00 for 0, 40 00 for 50%, 7F FF for 100% 46 -47 CH Volume Value 00 for 0, 40 00 for 50%, 7F FF for 100% 48 -49 Presence Value 00 for 0, 40 00 for 50%, 7F FF for 100% 4A -4B ?? 4C Mic code ? 04 for 4308 Ribbon ? 4D -4F 50 -51 Bypass Volume Value 00 for 0, 40 85 for 50%, 7F FF for 100% 52 -53 54 -55 ??? 5C -65 ???? Change from all 00 to 3F FF repeated 5 time if when changing wha to weeper, change when editing bias setting 66 -71 ??? 72 FX1 code ? Set 04 When screamer is set on and routed pre, 06 when on and set post, 0 if FX2 off 73 -79 FX 1 param ? 74 FX2 code ? Set to 04 when Analog Chorus is on, 0 if FX3 off 75 -81 FX2 param ? 82 FX3 code ? Set to 04 when Digital Delay is on, 0 if FX3 off 83 -C7 Unknown -------- then midi code i've found : Mode button : To effect mode : F0 00 01 0C 14 00 63 00 04 15 00 00 02 F7 To Preset mode : F0 00 01 0C 14 00 63 00 04 15 00 00 00 F7 To looper mode F0 00 01 0C 14 00 63 00 04 15 00 00 01 F7 Preset Mode A switch B0 00 00 B0 20 00 C0 04 B0 07 7F B switch : B0 00 00 B0 20 00 C0 05 B0 07 7F C switch : B0 00 00 B0 20 00 C0 06 B0 07 7F D switch : B0 00 00 B0 20 00 C0 07 B0 07 7F FX mode : Amp off then on F0 00 01 0C 14 00 63 00 02 14 00 00 00 F7 F0 00 01 0C 14 00 63 00 02 14 00 00 01 F7 Fx1 off then on F0 00 01 0C 14 00 63 00 10 03 00 00 00 F7 F0 00 01 0C 14 00 63 00 10 03 00 00 01 F7 Fx 2 on then off F0 00 01 0C 14 00 63 00 11 03 00 00 01 F7 F0 00 01 0C 14 00 63 00 11 03 00 00 00 F7 Fx 3 on then off F0 00 01 0C 14 00 63 00 12 03 00 00 01 F7 F0 00 01 0C 14 00 63 00 12 03 00 00 00 F7 Tap 3 times F0 00 01 0C 14 00 63 00 02 06 07 56 55 F7 F0 00 01 0C 14 00 63 00 02 06 08 07 27 F7 Tap 4 times F0 00 01 0C 14 00 63 00 02 06 09 0E 02 F7 F0 00 01 0C 14 00 63 00 02 06 08 2E 18 F7 F0 00 01 0C 14 00 63 00 02 06 08 2E 18 F7 Vol pedal up then down B0 07 7F B0 07 7E B0 07 7C B0 07 79 B0 07 77 B0 07 73 B0 07 6F B0 07 6B B0 07 66 B0 07 62 B0 07 5D B0 07 59 B0 07 53 B0 07 4E B0 07 49 B0 07 44 B0 07 3F B0 07 39 B0 07 33 B0 07 2C B0 07 25 B0 07 1D B0 07 14 B0 07 0C B0 07 02 B0 07 00 B0 07 04 B0 07 0B B0 07 11 B0 07 19 B0 07 20 B0 07 27 B0 07 2D B0 07 33 B0 07 3A B0 07 40 B0 07 45 B0 07 4A B0 07 4E B0 07 53 B0 07 58 B0 07 5D B0 07 61 B0 07 65 B0 07 6B B0 07 70 B0 07 74 B0 07 78 B0 07 7C B0 07 7F Amp change : F0 00 01 0C 14 00 63 00 00 0A 00 00 06 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 07 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 08 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 09 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 0A F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 0B F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 0C F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 0D F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 0E F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 0F F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 10 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 11 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 12 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 13 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 14 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 15 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 16 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 17 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 18 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 19 F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 1A F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 1B F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 1C F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 1D F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 1E F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 1E F7 F0 00 01 0C 14 00 63 00 00 0A 00 00 1E F7 |
|
From: jeanseb <jea...@fr...> - 2013-01-17 05:39:40
|
Hi, I was a developper sometime ago... (i worked on eci adsl user mode driver for linux)... I'm on sourceforge and i had taken a look to the apps dir of trunk, it compils but that's all ! Idea of web based converter is good, but i'm afraid their is no docs on file format ? I could help a little if reading and writting the pod parameter are include in the driver. I've seen some stuff in the sys dir but how to use them ? jeanseb @ sf ----- Mail original ----- De: "Stefan Hajnoczi" <ste...@gm...> À: "jeanseb valette" <jea...@fr...> Cc: lin...@li... Envoyé: Mardi 15 Janvier 2013 14:38:04 Objet: Re: [Line6linux-user] line6 edit equivalent On Tue, Jan 15, 2013 at 11:02 AM, <jea...@fr...> wrote: > is the a tool that allows to edit preset on POD HD 300 for linux ? As far as I know, no. POD HD300 Edit works in a Windows virtual machine under KVM - you can pass the USB devices into the virtual machine. There is also the beginning of Linux edit tools here: https://line6linux.svn.sourceforge.net/svnroot/line6linux/apps/branches/qtbased/ But unless you are a developer who is willing to spend time hacking on the tools, it probably won't be useful in its current form. A little off-topic but it would be neat if someone wrote a web-based Line 6 patch viewer/converter. For example, you upload a .h5e file and it displays the settings. That's really useful in conjunction with customtone.com where patch settings are not displayed. And then you have the option of exporting to another patch file for HD Pro, HD400, HD300, etc. Not all patches can be converted due to differences in features between HD500, HD Pro, etc but a lot can be converted. I'm not aware of MIDI APIs for web browsers though, so I think a web-based tool couldn't control the POD interactively or upload/download patches from the device. Stefan |
|
From: Markus G. <gr...@ic...> - 2013-01-16 21:23:47
|
Am Mittwoch, 16. Januar 2013, 19:08:15 schrieb Markus Grabner: > Am Mittwoch, 16. Januar 2013, 06:45:14 schrieb Stefan Hajnoczi: > > On Tue, Jan 15, 2013 at 8:14 PM, Markus Grabner <gr...@ic...> > > wrote: > > >> I have pasted my notes for POD HD300 below to get you started. > > > > > > Very interesting! Some codes are identical to the PODxt, but most are > > > transmitted as MIDI sysex messages (F0...). There seems to be a pattern: > > > > > > F0 00 01 0C 14 00 63 00 <a> <b> <x1> <x2> <x3> F7 > > > > > > where <a> encodes a parameter group (e.g., 20 -> FX1 parameters), <b> a > > > parameter, and <x1>...<x3> the parameter value. It shouldn't be too hard > > > to > > > add this to libline6comm. > > > > Note that the device also understands Continuous Controller messages. > > They affect the same settings as the SysEx messages. > > Even better :-) Then it should be quite easy to integrate POD HD support. > Can you please have a look at > > https://line6linux.svn.sourceforge.net/svnroot/line6linux/apps/branches/qtba > sed/libline6comm/tablecodeparam.csv > > and let me know if the POD HD codes are similar to the PODxt ones? There is > no documentation for this file, but I think you get the idea. > Alternatively, you can look up the PODxt codes from the manual: > > http://line6.com/support/manuals/podxtlive Sometimes the most obvious options are the last to be recongnized :-) I just downloaded the POD HD manual and compared the MIDI CC messages. Only very few seem to be identical to the PODxt (tap tempo and tuner mode), but the list seems to be incomplete (there aren't any model parameters). So your input on this is still appreciated! Thanks & kind regards, Markus |
|
From: Markus G. <gr...@ic...> - 2013-01-16 18:08:58
|
Am Mittwoch, 16. Januar 2013, 06:45:14 schrieb Stefan Hajnoczi: > On Tue, Jan 15, 2013 at 8:14 PM, Markus Grabner <gr...@ic...> wrote: > >> I have pasted my notes for POD HD300 below to get you started. > > > > Very interesting! Some codes are identical to the PODxt, but most are > > transmitted as MIDI sysex messages (F0...). There seems to be a pattern: > > > > F0 00 01 0C 14 00 63 00 <a> <b> <x1> <x2> <x3> F7 > > > > where <a> encodes a parameter group (e.g., 20 -> FX1 parameters), <b> a > > parameter, and <x1>...<x3> the parameter value. It shouldn't be too hard > > to > > add this to libline6comm. > > Note that the device also understands Continuous Controller messages. > They affect the same settings as the SysEx messages. Even better :-) Then it should be quite easy to integrate POD HD support. Can you please have a look at https://line6linux.svn.sourceforge.net/svnroot/line6linux/apps/branches/qtbased/libline6comm/tablecodeparam.csv and let me know if the POD HD codes are similar to the PODxt ones? There is no documentation for this file, but I think you get the idea. Alternatively, you can look up the PODxt codes from the manual: http://line6.com/support/manuals/podxtlive > Not sure if the official Line6 HD Edit software uses SysEx or CC. I > figure they implemented both because they ran out of CC messages > and/or the CC 7-bit data value wasn't enough for some parameter types. It would indeed be interesting to see where it makes a difference. The PODxt transmits delay time and modulation speed in two CC messages since 7 bit don't give sufficient resolution, but Line6 seems to have taken this somewhat further on the POD HD. Thanks & kind regards, Markus |
|
From: Stefan H. <ste...@gm...> - 2013-01-16 05:45:22
|
On Tue, Jan 15, 2013 at 8:14 PM, Markus Grabner <gr...@ic...> wrote: >> I have pasted my notes for POD HD300 below to get you started. > Very interesting! Some codes are identical to the PODxt, but most are > transmitted as MIDI sysex messages (F0...). There seems to be a pattern: > > F0 00 01 0C 14 00 63 00 <a> <b> <x1> <x2> <x3> F7 > > where <a> encodes a parameter group (e.g., 20 -> FX1 parameters), <b> a > parameter, and <x1>...<x3> the parameter value. It shouldn't be too hard to > add this to libline6comm. Note that the device also understands Continuous Controller messages. They affect the same settings as the SysEx messages. The device usually only sends SysEx messages when you press buttons. There are one or two exceptions where it sends the SysEx and CC messages. This means that edit software can use CC messages instead of the longer SysEx equivalents. Due to the smaller CC message namespace, they can be discovered by trying out all combinations. Using the MIDI implementation chart for other POD models is also a good starting point because a lot of the CC messages remain the same. Not sure if the official Line6 HD Edit software uses SysEx or CC. I figure they implemented both because they ran out of CC messages and/or the CC 7-bit data value wasn't enough for some parameter types. I haven't documented the CC messages though. Stefan |
|
From: Markus G. <gr...@ic...> - 2013-01-15 19:15:03
|
On Tuesday 15 January 2013 17:10:13 Stefan Hajnoczi wrote: > On Tue, Jan 15, 2013 at 4:24 PM, <jea...@fr...> wrote: > > I could help a little if reading and writting the pod parameter are > > include in the driver. > > > > I've seen some stuff in the sys dir but how to use them ? The sysfs files will be removed in a future version of the driver, so please don't use them. > Almost all of the POD functionality is accessed via MIDI. That's actually the preferred way to communicate with the device. As Stefan already noted, there is a prototype implementation of a library and a simple command line tool to interact with PODxt devices: https://line6linux.svn.sourceforge.net/svnroot/line6linux/apps/branches/qtbased If you don't like Qt, don't be afraid :-), the basic stuff there is strictly independent on any GUI toolkit. I recommend that you read https://line6linux.svn.sourceforge.net/svnroot/line6linux/apps/branches/qtbased/doc/design.tex as an introduction to the content of the repository (the project also contains rules to create a PDF file from this, so you don't have to compile the LaTeX- code by hand). In short, there are two components which are relevant to add support for the POD HD: *) libline6comm: interprets/creates the device-specific byte stream *) line6shell: a simple command line interface to the library for testing The shell in its current state should already be powerful enough to support development of new device classes. If you like to jump in, feel free to ask questions since the design document is only a rough guidance. > I have pasted my notes for POD HD300 below to get you started. Very interesting! Some codes are identical to the PODxt, but most are transmitted as MIDI sysex messages (F0...). There seems to be a pattern: F0 00 01 0C 14 00 63 00 <a> <b> <x1> <x2> <x3> F7 where <a> encodes a parameter group (e.g., 20 -> FX1 parameters), <b> a parameter, and <x1>...<x3> the parameter value. It shouldn't be too hard to add this to libline6comm. Kind regards, Markus |
|
From: Stefan H. <ste...@gm...> - 2013-01-15 16:10:21
|
On Tue, Jan 15, 2013 at 4:24 PM, <jea...@fr...> wrote: > Idea of web based converter is good, but i'm afraid their is no docs on file > format ? Yes, in general working on POD stuff requires reverse-engineering either USB traffic captures, MIDI dumps, or .h5e patch files. > I could help a little if reading and writting the pod parameter are > include in the driver. > > I've seen some stuff in the sys dir but how to use them ? Almost all of the POD functionality is accessed via MIDI. I have pasted my notes for POD HD300 below to get you started. The device sends MIDI messages when you press buttons, switch amp models, etc so it's pretty easy to figure out the MIDI mapping using the amidi(1) utility to dump MIDI messages. Stefan POD -> Host: Volume pedal: B0 07 XX (XX - 0 to 7F) Tap tempo: F0 00 01 0C 14 00 63 00 02 XX XX XX XX F7 (XX - ?) Mode: F0 00 01 0C 14 00 63 00 04 15 00 00 XX F7 (XX - 00 preset, 01 looper, 02 stomp) Preset: C0 XX (XX - 00 Preset 1A, ..., 7F Preset 32D) Looper Pre/Post: F0 00 01 0C 14 00 63 00 04 01 00 00 XX F7 (XX - 00 Pre, 01 Post) Amp Stomp Off/On: F0 00 01 0C 14 00 63 00 02 14 00 00 XX F7 (XX - 00 Off, 01 On) FX1 Stomp Off/On: F0 00 01 0C 14 00 63 00 10 03 00 00 XX F7 (XX - 00 Off, 01 On) FX2 Stomp Off/On: F0 00 01 0C 14 00 63 00 11 03 00 00 XX F7 (XX - 00 Off, 01 On) FX3 Stomp Off/On: F0 00 01 0C 14 00 63 00 12 03 00 00 XX F7 (XX - 00 Off, 01 On) Wah Pedal Off/On: ? Amp Model: B0 0B XX F0 00 01 0C 14 00 63 00 00 0A 00 00 XX F7 XX - Model 01 - BF Dbl Nrm 02 - Hiway 100 03 - Super O 04 - Gibtone185 05 - B-Man Nrm 06 - BF Lux Nrm 07 - Divide9/15 08 - PhD Mtrway 09 - Class A-15 0A - ClassA30TB 0B - J-45 Brt 0C - P-75 Brt 0D - Brit J-800 0E - BomberUber 0F - Treadplate 10 - ANGL FBall 11 - BF Dbl Vib 12 - B-Man Brt 13 - BF Lux Vib 14 - J-45 Nrm 15 - P-75 Nrm 16 - L6Elektrik 17 - Plexi Nrm 18 - Plexi Brt 19 - Solo Clean 1A - SoloCrunch 1B - Solo OD 1C - L6 Doom 1D - L6 Epic 1E - Flip Top Amp Type Full/Preamp: F0 00 01 0C 14 00 63 00 02 25 00 00 XX F7 (XX - 00 Full, 01 Preamp) Cab Model: F0 00 01 0C 14 00 63 00 02 13 00 00 XX F7 XX - Model 01 - 212-BlkF 02 - 412-Hway 03 - 6x9-Supr 04 - 112-FdCl 05 - 410-Twd 06 - 112-'Lux 07 - 112-12H 08 - 212-Port 09 - 112-Blue 0A - 212-SvBl 0B - 412-Gr25 0C - 412-Bk30 0D - 412-T75 0E - 412-Uber 0F - 412-Trd 10 - 412-XXL 11 - 115-Flip 12 - None Mic Model: F0 00 01 0C 14 00 63 00 02 24 00 00 XX F7 XX - Model 00 - 57 On Xs 01 - 57 OffXs 02 - 409 Dyn 03 - 421 Dyn 04 - 4038 Rbn 05 - 121 Rbn 06 - 67 Cond 07 - 87 Cond Early Reflections: F0 00 01 0C 14 00 63 00 00 13 XX XX XX F7 (XX - ?) Presence: F0 00 01 0C 14 00 63 00 02 1D XX XX XX F7 (XX - ?) Master: F0 00 01 0C 14 00 63 00 02 2A XX XX XX F7 (XX - ?) Sag: F0 00 01 0C 14 00 63 00 02 27 XX XX XX F7 (XX - ?) Hum: F0 00 01 0C 14 00 63 00 02 26 XX XX XX F7 (XX - ?) Bias: F0 00 01 0C 14 00 63 00 02 28 XX XX XX F7 (XX - ?) Bias Excursion: F0 00 01 0C 14 00 63 00 02 29 XX XX XX F7 (XX - ?) Bypass Volume: F0 00 01 0C 14 00 63 00 02 15 XX XX XX F7 (XX - ?) Amp Drive: F0 00 01 0C 14 00 63 00 02 01 XX XX XX F7 (all XXs identical) B0 0D XX (XX - 00 to 7F) Amp Bass: B0 0E XX F0 00 01 0C 14 00 63 00 02 02 XX XX XX F7 (all XXs identical) (XX - 00 to 7F) Amp Mid: B0 0F XX F0 00 01 0C 14 00 63 00 02 03 XX XX XX F7 (all XXs identical) (XX - 00 to 7F) Amp Treble: B0 10 XX F0 00 01 0C 14 00 63 00 02 04 XX XX XX F7 (all XXs identical) (XX - 00 to 7F) Channel Volume: B0 11 XX F0 00 01 0C 14 00 63 00 02 05 XX XX XX F7 (all XXs identical) (XX - 00 to 7F) FX Only Off/On: F0 00 01 0C 14 00 63 00 04 16 00 00 XX F7 (XX - 00 Off, 01 On) FX1 Model: F0 00 01 0C 14 00 63 00 10 00 00 00 XX F7 XX - Model: 01 - Screamer 0B - Tube Drive 0C - ClassicDis 0D - Heavy Dist 0E - ColorDrive 0F - Overdrive 10 - L6 Drive 11 - L6 Dist 12 - Boost Comp 13 - Red Comp 14 - Blue Comp 16 - Vetta Comp 18 - Fuzz Pi 19 - OctaveFuzz 1A - Jet Fuzz 1B - SubOctFuzz 1D - FacialFuzz 1E - Jumbo Fuzz 02 - Spring 23 - ParmetrcEQ 24 - 4BndShftEQ 27 - Tron Down 28 - Tron Up 29 - Q Filter 2A - Ring Mod 2B - Dimension 2C - FreqShiftr 2D - RotaryDrum 03 - SmrtHarmny 2F - PitchGlide 31 - SynthStrng 32 - Growler 33 - SynthOMatic 34 - BassOctavr 35 - V-Tron 5E - VintagePre 5F - HardGate FX1 Routing Pre/Post: F0 00 01 0C 14 00 63 00 10 01 00 00 XX F7 (XX - 00 Pre, 01 - Post) FX1 Param1: F0 00 01 0C 14 00 63 00 20 01 XX XX XX F7 FX1 Param2: F0 00 01 0C 14 00 63 00 20 02 XX XX XX F7 FX1 Param3: F0 00 01 0C 14 00 63 00 20 03 XX XX XX F7 FX1 Param4: F0 00 01 0C 14 00 63 00 20 04 XX XX XX F7 FX1 Param5: F0 00 01 0C 14 00 63 00 20 05 XX XX XX F7 FX2 Model: F0 00 01 0C 14 00 63 00 11 00 00 00 XX F7 XX - Model 04 - AnlgChorus 36 - AnlgFlange 37 - U-Vibe 38 - Phaser 39 - DualPhaser 3A - Barberpole 3B - PanndPhasr 3C - ScriptPhas 3D - Pitch Vibr 05 - Seeker 3E - Throbber 3F - Spin Cycle 40 - Obi Wah 41 - Voice Box 06 - Opto-Trem 42 - Bias Tremo 43 - PattrnTrem 44 - Panner FX2 Pre/Post: F0 00 01 0C 14 00 63 00 11 01 00 00 XX F7 (XX - 00 Pre, 01 Post) FX2 Tap Control: F0 00 01 0C 14 00 63 00 11 04 00 00 XX F7 (XX - 00 Don't Control, 01 - Control) FX2 Param1: F0 00 01 0C 14 00 63 00 21 00 XX XX XX F7 FX2 Param2: F0 00 01 0C 14 00 63 00 21 01 XX XX XX F7 FX2 Param3: F0 00 01 0C 14 00 63 00 21 02 XX XX XX F7 FX2 Param4: F0 00 01 0C 14 00 63 00 21 03 XX XX XX F7 FX2 Param5: F0 00 01 0C 14 00 63 00 21 05 XX XX XX F7 FX3 Model: F0 00 01 0C 14 00 63 00 12 00 00 00 XX F7 XX - Model 07 - Digi Delay 45 - DigDlyWMod 46 - AnalogEcho 47 - AnlgEchMod 48 - EchoPlattr 49 - EchPltrStd 4A - LoResDelay 4B - Stereo Dly 4C - Ping Pong 4D - Dynmic Dly 08 - Tape Echo 4E - TapeEchStd 4F - Tube Echo 50 - TubeEchStd 09 - AutoVolume 52 - Sweep Echo 53 - SwpEchStud 54 - Reverse FX3 Pre/Post: F0 00 01 0C 14 00 63 00 12 01 00 00 XX F7 (XX - 00 Pre, 01 Post) FX3 Tap Control: F0 00 01 0C 14 00 63 00 12 04 00 00 XX F7 - (XX - 00 Don't Control, 01 Control) FX3 Time: F0 00 01 0C 14 00 63 00 22 00 XX XX XX F7 (XX - ?) FX3 Tempo: F0 00 01 0C 14 00 63 00 02 06 XX XX XX F7 (XX - ?) FX3 Param1: F0 00 01 0C 14 00 63 00 22 01 XX XX XX F7 (XX - ?) FX3 Param2: F0 00 01 0C 14 00 63 00 22 02 XX XX XX F7 (XX - ?) FX3 Param3: F0 00 01 0C 14 00 63 00 22 03 XX XX XX F7 (XX - ?) FX3 Param4: F0 00 01 0C 14 00 63 00 22 04 XX XX XX F7 (XX - ?) Reverb Model: F0 00 01 0C 14 00 63 00 13 00 00 00 XX F7 XX - Model 0A - Plate 55 - Room 56 - Chamber 57 - Hall 58 - Cave 5A - Octo 5B - Tile 5C - Echo Reverb Pre/Post: F0 00 01 0C 14 00 63 00 13 01 00 00 XX F7 (XX - 00 Pre, 01 Post) Reverb Pre-delay: F0 00 01 0C 14 00 63 00 23 02 XX XX XX F7 (XX - ?) Reverb Decay: F0 00 01 0C 14 00 63 00 23 01 XX XX XX F7 (XX - ?) Reverb Tone: F0 00 01 0C 14 00 63 00 23 03 XX XX XX F7 (XX - ?) Reverb Mix: F0 00 01 0C 14 00 63 00 23 05 XX XX XX F7 (XX - ?) Gate Mode: F0 00 01 0C 14 00 63 00 02 0C 00 00 XX F7 (XX - ?) XX - Model 00 - Off 01 - Gate 02 - Noise Reduction 03 - Gate + Noise Reduction Gate Threshold: F0 00 01 0C 14 00 63 00 02 0A XX XX XX F7 (XX - ?) Gate Decay: F0 00 01 0C 14 00 63 00 02 0B XX XX XX F7 (XX - ?) Wah Model: F0 00 01 0C 14 00 63 00 02 12 00 00 XX F7 (XX - ?) XX - Model 00 - Vetta 01 - Fassel 02 - Chrome 03 - Weeper 04 - Cnductor 05 - Colorful Volume Pre/Post: F0 00 01 0C 14 00 63 00 02 07 00 00 XX F7 (XX - 00 Pre, 01 Post) Volume Min: F0 00 01 0C 14 00 63 00 02 08 XX XX XX F7 (XX - ?) Volume Max: F0 00 01 0C 14 00 63 00 02 09 XX XX XX F7 (XX - ?) Live: F0 00 01 0C 14 00 63 00 04 18 00 00 XX F7 XX - Model 00 - ComboFrt 01 - ComboAmp 02 - StackFrt 03 - StackAmp AutoFX: F0 00 01 0C 14 00 63 00 04 02 00 00 XX F7 (XX - 00 Disabled, 01 AmpSetFX) USB Monitor Volume: F0 00 01 0C 14 00 63 00 04 19 XX XX XX F7 (XX - ?) Footswitch Mode: F0 00 01 0C 14 00 63 00 04 1B 00 00 XX F7 (XX - 00 Normal, 01 Hold4Lpr) AC Rate: F0 00 01 0C 14 00 63 00 04 1C 00 00 XX F7 (XX - 32 50Hz, 3C 60Hz) Tap Tempo Light: F0 00 01 0C 14 00 63 00 04 04 00 00 XX F7 (XX - 00 AlwaysOn, 01 Flash 8) |
|
From: Stefan H. <ste...@gm...> - 2013-01-15 13:38:12
|
On Tue, Jan 15, 2013 at 11:02 AM, <jea...@fr...> wrote: > is the a tool that allows to edit preset on POD HD 300 for linux ? As far as I know, no. POD HD300 Edit works in a Windows virtual machine under KVM - you can pass the USB devices into the virtual machine. There is also the beginning of Linux edit tools here: https://line6linux.svn.sourceforge.net/svnroot/line6linux/apps/branches/qtbased/ But unless you are a developer who is willing to spend time hacking on the tools, it probably won't be useful in its current form. A little off-topic but it would be neat if someone wrote a web-based Line 6 patch viewer/converter. For example, you upload a .h5e file and it displays the settings. That's really useful in conjunction with customtone.com where patch settings are not displayed. And then you have the option of exporting to another patch file for HD Pro, HD400, HD300, etc. Not all patches can be converted due to differences in features between HD500, HD Pro, etc but a lot can be converted. I'm not aware of MIDI APIs for web browsers though, so I think a web-based tool couldn't control the POD interactively or upload/download patches from the device. Stefan |
|
From: <jea...@fr...> - 2013-01-15 10:02:42
|
Hi, is the a tool that allows to edit preset on POD HD 300 for linux ? Thanks. |
|
From: Markus G. <gr...@ic...> - 2013-01-13 21:23:55
|
Am Dienstag, 8. Januar 2013, 23:54:20 schrieb Mariusz Kozlowski: > On Tue, Jan 08, 2013 at 09:21:49PM +0100, Markus Grabner wrote: > > In the meantime, you could try to find out the minimum values for the > > startup delays (POD_STARTUP_DELAY[1|2] in pod.h) such that the driver > > works on your system. The first value is the initial delay after the > > device is connected, the second value is the delay between the following > > initialization steps. Since we are currently touching the code, we should > > use the chance to make device initialization faster if possible. > > Ok so this is how I tested it: > > 1. <change pod.h> && make > 2. <try to play some samples via POD alsa interface> > 3. while true; do sudo insmod line6usb.ko; sleep 4; sudo rmmod line6usb; > done > > And that's left for a few miutes to see if anything blows up. > > D1 D2 > 1000 + 100 -> works ok > 100 + 50 -> works ok > 50 + 10 -> oops on insmod from time to time > 0 + 20 -> oops on insmod > 0 + 0 -> sometimes works, sometimes oops > > Tests with values of D1 below 100 produce lots of additional communication > until firmware version request arrives. That is not seen for values above > 100 but maybe certain combination of D1 + D2 triggers that additional > messages. > > So 100 + 50 seems reasonable. Thanks for testing! I tried these settings, but they didn't work for me. I did the following: *) compile and install the driver *) connect the PODxt Live with main powers switched off *) switch on main powers of PODxt Live Then the message "Invalid Code Error 8" is displayed on the device (which was actually the reason for implementing the delayed startup procedure in the first place). D1=200 and D1=300 have the same problem, only with D1=400 the device starts up correctly. D2=50 works fine. I will test with these values for a while and then commit them with a broad safety margin. Kind regards, Markus |
|
From: Markus G. <gr...@ic...> - 2013-01-13 20:51:09
|
Am Samstag, 12. Januar 2013, 18:23:31 schrieb Nagy Gyorgy: > Dear POD users, > > I had problem: PODxt Pro was not visible as a sound card. ( See thread > in subject for details ) > > My problem was also solved in "line6linux problem with pod xt live" > thread of this list, see as: > > > https://line6linux.svn.sourceforge.net/svnroot/line6linux/driver/branches/in > it > > @Nagy: Could you also test this branch please? Mariusz reported > > similar problems as you did in December, so this version might work for > you as well. > > > My POD works great by now! Thanks for reporting, I submitted the patch to the Linux kernel maintainers. Kind regards, Markus |
|
From: Nagy G. <nag...@uw...> - 2013-01-12 17:23:52
|
Dear POD users, I had problem: PODxt Pro was not visible as a sound card. ( See thread in subject for details ) My problem was also solved in "line6linux problem with pod xt live" thread of this list, see as: > https://line6linux.svn.sourceforge.net/svnroot/line6linux/driver/branches/init > > @Nagy: Could you also test this branch please? Mariusz reported similar problems as you did in December, so this version might work for you as well. My POD works great by now! Thank you Markus very much for your help and for keep developing Line6 drivers! Regards, György Nagy 2012-12-29 21:18 keltezéssel, Markus Grabner írta: > On Thursday 27 December 2012 10:01:07 Nagy Gyorgy wrote: >> Dear my POD-mate, >> >> I have a driver problem vith my PODxt Pro device. >> >> Sort description: >> PODxt Pro does not show up as a sound card, but its line6usb module >> loaded by device connection. >> The mixer also can not show the POD. It is not visible by JACK too. > I just checked with the most recent version from the subversion trunk, and > playback, capture, and the mixer all worked without problems under Linux > kernel 3.4.11. Here are some things you could try: > *) If the device is plugged into a USB hub, plug it directly into a USB port > of your computer instead. > *) Try to plug the device into different USB ports. > *) If you have a Windows installation on the same computer, check whether the > device works with the native Line6 software. > *) execute the script "sysinfo.sh" contained in the driver source directory as > root and send its output "sysinfo.txt" to me. > > Kind regards, > Markus > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122912 > _______________________________________________ > Line6linux-user mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/line6linux-user > |
|
From: jeanseb <jea...@fr...> - 2013-01-11 21:52:56
|
Hi again, I've added debian patch system (with quilt) to the debian package and reverted the use of usb_device macro for debian only. Here a patch against curent Cvs. Module now find the card (and compile contrary to squeeze package if not to late for being back wheezy). Work fine with alsa and jack. best regards Le Fri, 11 Jan 2013 09:03:05 +0100, Stefan Hajnoczi <ste...@gm...> a écrit : > On Fri, Jan 11, 2013 at 7:34 AM, <jea...@fr...> wrote: > > Thanks, > > > > I've take a looj to code of usb-skeleton driver on > > http://lxr.linux.no , macro module_usb_driver seem to have been > > introduce by 3.3 kernel. > > > > This macro does nothing but creating empty side effect for > > registering driver. Do I will try to make a pacth with the good > > preprocessor test kernel version and reintroduce the > > module_init/exit stuff this WE. > > The simplest solution is probably to build a vanilla kernel. Try > 3.8-rc2, I'm using the upstream driver with my POD HD300 successfully. > > Use Debian's make-kpkg and it'll build a .deb for you that installs > just like a distro kernel. > > Stefan |
1 message has been excluded from this view by a project administrator.
