GR-55 Driver

GR-55 Driver

[Jeffrey Scott Flesher Gmail]

I need a Driver for the Roland GR-55 Guitar Synthesizer, not sure how to
get started, so I thought this would be a good place to ask.

The GR-55 has MIDI and AUDIO

KSNAME_Wo11="WaveOut1-1"
WDM.Wo11.szPname="OUT (GR-55)"

KSNAME_Wi11="WaveIn1-1"
WDM.Wi11.szPname="IN (GR-55)"

KSNAME_Md11="Midi1-1"
WDM.Md11.szPname="GR-55"

My thinking is that there may be a driver that is similar, or someone
could already be working on a driver, if so, I would like to find out if
I could work on that project or if I could start a new project here. 

I did contact Roland about getting help in the way of Documentation; but
was told not to count on it since most of this documentation is
proprietary; so I might end up having to snoop the information to
reverse engineer it.

I have been a programmer for over 30 years, and have written Unix
drivers and interfaces back in the 80's; things have changed since then
and Linux is Unix like, but ALSA seems a lot easier than what we did
back in those days. I can get up to speed with just a point in the right
direction. Things like do I do this as a driver or a module? Are just a
few questions that I need answers to, just to get started.

Can you recommend a driver that is close enough to use as a template to
start a new driver from?

Thanks.

Jeff Flesher

Re: GR-55 Driver

[Daniel Mack]

Hi Jeff,

On Thu, May 12, 2011 at 8:20 PM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> I need a Driver for the Roland GR-55 Guitar Synthesizer, not sure how to
> get started, so I thought this would be a good place to ask.

First of all, thanks for considering contribution to the ALSA project.

> The GR-55 has MIDI and AUDIO
>
> KSNAME_Wo11="WaveOut1-1"
> WDM.Wo11.szPname="OUT (GR-55)"
>
> KSNAME_Wi11="WaveIn1-1"
> WDM.Wi11.szPname="IN (GR-55)"
>
> KSNAME_Md11="Midi1-1"
> WDM.Md11.szPname="GR-55"
>
> My thinking is that there may be a driver that is similar, or someone
> could already be working on a driver, if so, I would like to find out if
> I could work on that project or if I could start a new project here.

Given that this device is connected via USB, the first thing to find
out is whether the device is implemented in any class-compliant way.
"lsusb -v" will provide a lot of information that is needed to know
where to start.

Basically, there are two options. Either the device just needs some
entries in the quirks tables of the generic ALSA USB audio driver,
which is very likely. Or the device uses an entirely proprietary
protocol on the bus (like the usx2y, ua101, Terratec 6fire or the
older Native Instruments cards do) which means that there is need to
write a specific driver from scratch. The drivers I mentioned are all
in the mainline kernel git repository and serve well as examples for
new implementations.

So in short: the first thing to do is to share the output of "lsusb
-v" on this list.

HTH,
Daniel

Re: GR-55 Driver

[Daniel Mack]

[-- Attachment #1: Type: text/plain, Size: 6004 bytes --]

On Thu, May 12, 2011 at 10:53 PM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> Output from lsusb -v for Roland GR-55
> ******
>
> Bus 001 Device 008: ID 0582:0127 Roland Corp.
> Device Descriptor:
>  bLength                18
>  bDescriptorType         1
>  bcdUSB               2.00
>  bDeviceClass          255 Vendor Specific Class
>  bDeviceSubClass         0
>  bDeviceProtocol       255
>  bMaxPacketSize0        64
>  idVendor           0x0582 Roland Corp.
>  idProduct          0x0127
>  bcdDevice            0.01
>  iManufacturer           1
>  iProduct                2
>  iSerial                 0
>  bNumConfigurations      1
>  Configuration Descriptor:
>    bLength                 9
>    bDescriptorType         2
>    wTotalLength          167
>    bNumInterfaces          3
>    bConfigurationValue     1
>    iConfiguration          0
>    bmAttributes         0xc0
>      Self Powered
>    MaxPower                0mA
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        0
>      bAlternateSetting       0
>      bNumEndpoints           0
>      bInterfaceClass       255 Vendor Specific Class
>      bInterfaceSubClass      2
>      bInterfaceProtocol      2
>      iInterface              0
>      ** UNRECOGNIZED:  06 24 f1 01 00 00
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        0
>      bAlternateSetting       1
>      bNumEndpoints           1
>      bInterfaceClass       255 Vendor Specific Class
>      bInterfaceSubClass      2
>      bInterfaceProtocol      2
>      iInterface              0
>      ** UNRECOGNIZED:  07 24 01 01 00 01 00
>      ** UNRECOGNIZED:  0b 24 02 01 02 04 18 01 44 ac 00
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x05  EP 5 OUT
>        bmAttributes            5
>          Transfer Type            Isochronous
>          Synch Type               Asynchronous
>          Usage Type               Data
>        wMaxPacketSize     0x0070  1x 112 bytes
>        bInterval               1
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        1
>      bAlternateSetting       0
>      bNumEndpoints           0
>      bInterfaceClass       255 Vendor Specific Class
>      bInterfaceSubClass      2
>      bInterfaceProtocol      1
>      iInterface              0
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        1
>      bAlternateSetting       1
>      bNumEndpoints           1
>      bInterfaceClass       255 Vendor Specific Class
>      bInterfaceSubClass      2
>      bInterfaceProtocol      1
>      iInterface              0
>      ** UNRECOGNIZED:  07 24 01 07 00 01 00
>      ** UNRECOGNIZED:  0b 24 02 01 02 04 18 01 44 ac 00
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x84  EP 4 IN
>        bmAttributes           37
>          Transfer Type            Isochronous
>          Synch Type               Asynchronous
>          Usage Type               Implicit feedback Data
>        wMaxPacketSize     0x0070  1x 112 bytes
>        bInterval               1
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        2
>      bAlternateSetting       0
>      bNumEndpoints           2
>      bInterfaceClass       255 Vendor Specific Class
>      bInterfaceSubClass      3
>      bInterfaceProtocol      0
>      iInterface              0
>      ** UNRECOGNIZED:  06 24 f1 02 02 02
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x03  EP 3 OUT
>        bmAttributes            2
>          Transfer Type            Bulk
>          Synch Type               None
>          Usage Type               Data
>        wMaxPacketSize     0x0200  1x 512 bytes
>        bInterval               1
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x82  EP 2 IN
>        bmAttributes            2
>          Transfer Type            Bulk
>          Synch Type               None
>          Usage Type               Data
>        wMaxPacketSize     0x0200  1x 512 bytes
>        bInterval               0
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        2
>      bAlternateSetting       1
>      bNumEndpoints           2
>      bInterfaceClass       255 Vendor Specific Class
>      bInterfaceSubClass      3
>      bInterfaceProtocol      0
>      iInterface              0
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x03  EP 3 OUT
>        bmAttributes            2
>          Transfer Type            Bulk
>          Synch Type               None
>          Usage Type               Data
>        wMaxPacketSize     0x0200  1x 512 bytes
>        bInterval               1
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x81  EP 1 IN
>        bmAttributes            3
>          Transfer Type            Interrupt
>          Synch Type               None
>          Usage Type               Data
>        wMaxPacketSize     0x0040  1x 64 bytes
>        bInterval               1
>

Ok, that seems to be identical to the BOSS JS-8 layout, so it can be
handled by the generic audio driver.
Can you try the attached patch? Make sure you apply it against the
most recent ALSA tree found in the git repository at
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git.

Thanks,
Daniel

[-- Attachment #2: 0001-ALSA-snd-usb-add-quirks-for-Roland-GR-55.patch --]
[-- Type: application/octet-stream, Size: 1181 bytes --]

From d12c4279e8453682371b7ee376114e13b9f4182b Mon Sep 17 00:00:00 2001
From: Daniel Mack <zonque@gmail.com>
Date: Fri, 13 May 2011 02:12:52 +0200
Subject: [PATCH] ALSA: snd-usb: add quirks for Roland GR-55

Signed-off-by: Daniel Mack <zonque@gmail.com>
---
 sound/usb/quirks-table.h |   26 ++++++++++++++++++++++++++
 1 files changed, 26 insertions(+), 0 deletions(-)

diff --git a/sound/usb/quirks-table.h b/sound/usb/quirks-table.h
index 5c1a176..faf776b 100644
--- a/sound/usb/quirks-table.h
+++ b/sound/usb/quirks-table.h
@@ -1651,6 +1651,32 @@ YAMAHA_DEVICE(0x7010, "UB99"),
 		}
 	}
 },
+{
+	USB_DEVICE(0x0582, 0x0127),
+	.driver_info = (unsigned long) & (const struct snd_usb_audio_quirk) {
+		/* .vendor_name = "Roland", */
+		/* .product_name = "GR-55", */
+		.ifnum = QUIRK_ANY_INTERFACE,
+		.type = QUIRK_COMPOSITE,
+		.data = (const struct snd_usb_audio_quirk[]) {
+			{
+				.ifnum = 0,
+				.type = QUIRK_AUDIO_STANDARD_INTERFACE
+			},
+			{
+				.ifnum = 1,
+				.type = QUIRK_AUDIO_STANDARD_INTERFACE
+			},
+			{
+				.ifnum = 2,
+				.type = QUIRK_MIDI_STANDARD_INTERFACE
+			},
+			{
+				.ifnum = -1
+			}
+		}
+	}
+},
 
 /* Guillemot devices */
 {
-- 
1.7.1


[-- Attachment #3: Type: text/plain, Size: 0 bytes --]

Re: GR-55 Driver

[Daniel Mack]

Hi Jeff,

please, bear in mind two rules:

1. don't just reply to me, but always use the "reply-to-all" feature
in your mail client. This way, all people on the ALSA list can follow
the discussion and chime in.
2. don't top-post, always reply using proper quoting.

On Fri, May 13, 2011 at 4:30 AM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> Thanks.
>
> I'm running Ubuntu Studio 10.04 x64 with realtime kernel from
> http://ppa.launchpad.net/abogani/ppa/ubuntu lucid (linux-realtime -
> 2.6.33-29.1); my motherboard is ASUS M4A78T-E onboard VIA sound, Nvidia 460
> GTX Video card; AMD 955 X4 CPU.
> Link to kernel used
> https://launchpad.net/~abogani/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=lucid
>
> I searched for instructions on how to do this, with no good results; so I
> must ask someone that knows how.

Things are a little more complicated as modern Linux distributions use
techniques like initramfs.

For Ubuntu, you should follow one of the tutorials. Two I found are here:

 https://help.ubuntu.com/community/Kernel/Compile
 http://parabing.com/2011/04/28/ubuntu-natty-a-custom-kernel-is-what-you-want/

That looks comprehensive. Just don't download the ubuntu Kernel
sources as described but clone the ALSA repository (which you already
did).

And instead of downloading the patches as described, just use "git
apply" on the file I sent you. On case you want to revert the patching
and return to the kernel you originally cloned, just call "git reset
--hard".

> Just to make sure I do this right, since I've never compiled ALSA driver
> before; these are the instructions I used:
>
> 1. git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
> 2. cp 0001-ALSA-snd-usb-add-quirks-for-Roland-GR-55.patch /sound-2.6
> 3. cd sound-2.6
> 4. patch -p1 < ./0001-ALSA-snd-usb-add-quirks-for-Roland-GR-55.patch
> 5. make x86_64_defconfig
> 6. make
> 7. make install
>
> This worked, not tested; I still need to get the kernel to see it; I did
> this in my home directory; where should I move it?
>
> I see a file called vmlinux, 19.7 MB executable; I take it this is the new
> ALSA Driver.
>
> I do see vmlinux files that are new in these folders; which would seem to me
> that they got where they need to go with the make install command.
> /proc/4055/cwd
> /proc/4055/cwd/arch/x86/boot/compressed
>
> Now do I need to compile this into the Kernel, if so, what kernel do you
> recommend; realtime, low latency or normal; and what version?

I would first go for a normal kernel configuration, and once the
driver supports the device, care for optimisation.

HTH,
Daniel

Re: GR-55 Driver

[Jeffrey Scott Flesher Gmail]

I have read this article over a few times, trying to remove the kernel
and Reiser4 instructions; and I got a little confused; although I did
get it to compile and now it see's the GR-55 as a sound device; I tried
to jack it to the output but got no audio; what should I do to test it?

Do these instructions look correct?
# Path: /home/username/dev/sound/alsa/sound-2.6

git clone
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
cd sound-2.6
git apply 0001-ALSA-snd-usb-add-quirks-for-Roland-GR-55.patch
sudo cp -vi /boot/config-$(uname -r) .config
sudo make oldconfig
# a lot of questions, I hit enter for default

make-kpkg clean

# Since I'm not building the kernel I didn't do this:
# But since this is the only command that will write the new kernel,
# what do I do?

nice fakeroot make-kpkg --initrd --append-to-version=-lockard
--overlay-dir=/home/username/dev/kernel/source kernel-image
kernel-headers

If I was to guess; I'd change the overlay-dir to use the kernel in the
sound-2.6 folder?

nice fakeroot make-kpkg --initrd --append-to-version=-gr55
--overlay-dir=/home/username/dev/sound/alsa/sound-2.6/kernel
kernel-image kernel-headers

# is this right?

cd ..
ls -lh
sudo dpkg -i linux-*.deb
uname -r # 2.6.39-rc3-gr55+

One thing strange was that it locked up on reboot, showing rc3, but a
reset with previous kernel, I saw the gr55 version so I picked it; it
worked as stated above; just don't know why it didn't set this version
as default, maybe a step I missed.

Sorry it took so long to get back to this; I had a hard drive go bad; so
I installed Ubuntu Studio 11.04; so I'm doing this against the newest
kernel. 

Thanks

From: Daniel Mack <zonque@gmail.com>
To: Jeffrey Scott Flesher Gmail <jeffrey.scott.flesher@gmail.com>
Subject: Re: [alsa-devel] GR-55 Driver
Date: Fri, 13 May 2011 09:24:57 +0200

On Fri, May 13, 2011 at 4:30 AM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> I'm running Ubuntu Studio 10.04 x64 with realtime kernel from
> http://ppa.launchpad.net/abogani/ppa/ubuntu lucid (linux-realtime -
> 2.6.33-29.1); my motherboard is ASUS M4A78T-E onboard VIA sound, Nvidia 460
> GTX Video card; AMD 955 X4 CPU.
> Link to kernel used
> https://launchpad.net/~abogani/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=lucid
>
> I searched for instructions on how to do this, with no good results; so I
> must ask someone that knows how.

Things are a little more complicated as modern Linux distributions use
techniques like initramfs.

For Ubuntu, you should follow one of the tutorials. Two I found are here:

  https://help.ubuntu.com/community/Kernel/Compile
  http://parabing.com/2011/04/28/ubuntu-natty-a-custom-kernel-is-what-you-want/

That looks comprehensive. Just don't download the ubuntu Kernel
sources as described but clone the ALSA repository (which you already
did).

And instead of downloading the patches as described, just use "git
apply" on the file I sent you. On case you want to revert the patching
and return to the kernel you originally cloned, just call "git reset
--hard".

Hope this helps, looking forward to your results.

Thanks,
Daniel

Re: GR-55 Driver

[Daniel Mack]

On Sun, May 15, 2011 at 8:39 AM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> I have read this article over a few times, trying to remove the kernel
> and Reiser4 instructions; and I got a little confused; although I did
> get it to compile and now it see's the GR-55 as a sound device; I tried
> to jack it to the output but got no audio; what should I do to test it?

I would just use aplay with a plain wav file and see what it does. And
then try arecord to see whether you can capture any input signal.

> Do these instructions look correct?

[...]

> sudo dpkg -i linux-*.deb
> uname -r # 2.6.39-rc3-gr55+

Very good, this is the desired result.

> One thing strange was that it locked up on reboot, showing rc3, but a
> reset with previous kernel, I saw the gr55 version so I picked it; it
> worked as stated above; just don't know why it didn't set this version
> as default, maybe a step I missed.

No, it's all good. The reason why it locked up might be that you are
now using a premature kernel which has not been officially released.
At the moment, as Linus' mainline tree is in a rather stable phase
(due to a new release coming up the next days or so), what you could
also do is

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
git checkout -b alsa
git pull git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
master

As of today, that should give you give a 2.6.39-rc7+ version. But for
testing whether the patch works, the approach you took is totally fine
I think.

Daniel

Re: GR-55 Driver

[Jeffrey Scott Flesher Gmail]

Still no luck; I spent most of the day researching and trying things.

This is a file of what information I could dig up; it should be useful 
http://vetshelpcenter.com/media/trouble-shoot-gr-55.txt

Are there any programs/scripts I can install/run that will help trouble
shoot this?

Are there any good articles about trouble shooting drivers that might
help?

The system seems stable; no problems; just can not connect the to the
device. 

In Sound Preference I have Input set to GR-55 Analog Stereo, the meter
does not move, which indicates to me, that its not listening; Output set
to speakers (GR-55 doesn't really have an output device; but it shows up
as an option). 

Thanks
Jeff

-----Original Message-----
From: Daniel Mack <zonque@gmail.com>
To: Jeffrey Scott Flesher Gmail <jeffrey.scott.flesher@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] GR-55 Driver
Date: Sun, 15 May 2011 13:36:35 +0200

On Sun, May 15, 2011 at 8:39 AM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> I have read this article over a few times, trying to remove the kernel
> and Reiser4 instructions; and I got a little confused; although I did
> get it to compile and now it see's the GR-55 as a sound device; I tried
> to jack it to the output but got no audio; what should I do to test it?

I would just use aplay with a plain wav file and see what it does. And
then try arecord to see whether you can capture any input signal.

> Do these instructions look correct?

[...]

> sudo dpkg -i linux-*.deb
> uname -r # 2.6.39-rc3-gr55+

Very good, this is the desired result.

> One thing strange was that it locked up on reboot, showing rc3, but a
> reset with previous kernel, I saw the gr55 version so I picked it; it
> worked as stated above; just don't know why it didn't set this version
> as default, maybe a step I missed.

No, it's all good. The reason why it locked up might be that you are
now using a premature kernel which has not been officially released.
At the moment, as Linus' mainline tree is in a rather stable phase
(due to a new release coming up the next days or so), what you could
also do is

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
git checkout -b alsa
git pull git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
master

As of today, that should give you give a 2.6.39-rc7+ version. But for
testing whether the patch works, the approach you took is totally fine
I think.

Daniel

Re: GR-55 Driver

[Daniel Mack]

On Mon, May 16, 2011 at 1:13 AM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> Still no luck; I spent most of the day researching and trying things.
>
> This is a file of what information I could dig up; it should be useful
> http://vetshelpcenter.com/media/trouble-shoot-gr-55.txt
>
> Are there any programs/scripts I can install/run that will help trouble
> shoot this?

You most probably just have a confusion about the four cards connected
to your computer.

As you can see from your output of /proc/asound/cards, the GR55 is not
the first one, and hence not the default picked by tools like aplay or
amixer. However, it is present, which is a good sign. For further
parsing the contents of /proc/asound, you need to refer to the device
number, which is not 1 (as in "card1") but 3. What does "cat
/proc/asound/card3/stream0" show?

Just try "alsamixer -D hw:GR55" to control the volume levels, or
"amixer -D hw:GR55 controls" to dump them.

And then, try "aplay -D plughw:GR55,0,0 file.wav" for a first output test.

Does that help?


Daniel

Re: GR-55 Driver

[Jeffrey Scott Flesher Gmail]

Results:

# cat /proc/asound/card3/stream0
cat: /proc/asound/card3/stream0: No such file or directory
***
# alsamixer -D hw:GR55
This sound device does not have any controls.
***
# amixer -D hw:GR55 controls
[Nothing]
***
# cat /proc/asound/GR55/stream0
Roland GR-55 at usb-0000:00:12.2-4, high speed : USB Audio

Playback:
  Status: Stop
  Interface 0
    Altset 1
    Format: S32_LE
    Channels: 2
    Endpoint: 5 OUT (ASYNC)
    Rates: 44100
    Data packet interval: 125 us

Capture:
  Status: Stop
  Interface 1
    Altset 1
    Format: S32_LE
    Channels: 2
    Endpoint: 4 IN (ASYNC)
    Rates: 44100
    Data packet interval: 125 us
***
# cat /proc/asound/GR55/midi0
GR-55
***
# aplay -D plughw:GR55,0,0 /usr/share/sounds/alsa/Front_Center.wav
Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit
Little Endian, Rate 48000 Hz, Mono
[No sound]
***
I am facing two problems, I am unfamiliar with this piece of equipment
and as a result, I'm unsure how to test it.

Testing Audio function:
I tested it with Audacity in Windozes and it works;  in Linux I set it
up the same way: GR-55 USB Audio (hw:1,0) as recording device; no sound.
Using Logitech Webcam software I can record the guitar output; Using
Cheese, I do not get Audio.

Testing MIDI function:
I'm going to call tech support on this one; I have not found a Windows
app that seems to work with the MIDI; so I can not expect to test this
in Linux yet; I would like to be able to convert notes into sheet music;
I tried TuxGuitar, but must admit I don't know how to get it to work
with MIDI input, or if it even does.

So far I have not been impressed with how this device works in Windows;
asking questions at forums I get users say to use Windows, I have no
idea why, the quality was not that good. 

I must say it works great with just the headphones connected to the
device.

I'm thinking about getting M-Audio Fast track pro to provide an input
for the GR-55 as well as my NTG-1 mic; can you tell me the status of the
driver for this unit; I have seen talk about the driver here, but not
sure if the Fast track, and fast track pro are the same, or if this unit
will even work with the GR-55, I have ask at other forums and have
gotten no reply.

I'm going to keep on this till I get it 100%; I have patience; lets hope
you do too. 

Thanks
Jeff

-----Original Message-----
From: Daniel Mack <zonque@gmail.com>
To: Jeffrey Scott Flesher Gmail <jeffrey.scott.flesher@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] GR-55 Driver
Date: Mon, 16 May 2011 09:05:54 +0200


On Mon, May 16, 2011 at 1:13 AM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> Still no luck; I spent most of the day researching and trying things.
>
> This is a file of what information I could dig up; it should be useful
> http://vetshelpcenter.com/media/trouble-shoot-gr-55.txt
>
> Are there any programs/scripts I can install/run that will help trouble
> shoot this?

You most probably just have a confusion about the four cards connected
to your computer.

As you can see from your output of /proc/asound/cards, the GR55 is not
the first one, and hence not the default picked by tools like aplay or
amixer. However, it is present, which is a good sign. For further
parsing the contents of /proc/asound, you need to refer to the device
number, which is not 1 (as in "card1") but 3. What does "cat
/proc/asound/card3/stream0" show?

Just try "alsamixer -D hw:GR55" to control the volume levels, or
"amixer -D hw:GR55 controls" to dump them.

And then, try "aplay -D plughw:GR55,0,0 file.wav" for a first output test.

Does that help?


Daniel

Re: GR-55 Driver

[Daniel Mack]

On Mon, May 16, 2011 at 11:33 PM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> # alsamixer -D hw:GR55
> This sound device does not have any controls.
> ***
> # amixer -D hw:GR55 controls
> [Nothing]

That's possible.

> ***
> # cat /proc/asound/GR55/stream0
> Roland GR-55 at usb-0000:00:12.2-4, high speed : USB Audio
>
> Playback:
>   Status: Stop
>   Interface 0
>     Altset 1
>     Format: S32_LE
>     Channels: 2
>     Endpoint: 5 OUT (ASYNC)
>     Rates: 44100
>     Data packet interval: 125 us
>
> Capture:
>   Status: Stop
>   Interface 1
>     Altset 1
>     Format: S32_LE
>     Channels: 2
>     Endpoint: 4 IN (ASYNC)
>     Rates: 44100
>     Data packet interval: 125 us
> ***
> # cat /proc/asound/GR55/midi0
> GR-55

Looks ok.

> ***
> # aplay -D plughw:GR55,0,0 /usr/share/sounds/alsa/Front_Center.wav
> Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
> [No sound]

Can you try this with a 44100/16bit file?

> I am facing two problems, I am unfamiliar with this piece of equipment and as a result, I'm unsure how to test it.
>
> Testing Audio function:
> I tested it with Audacity in Windozes and it works;  in Linux I set it up the same way: GR-55 USB Audio (hw:1,0) as recording device; no sound.

Are you sure hw:1,0 refers to your GR-55? Check the entries in
/proc/asound/cards again, please.

> Using Logitech Webcam software I can record the guitar output; Using Cheese, I do not get Audio.

So you DO in fact get audio from the device then with some tool?

> Testing MIDI function:
> I'm going to call tech support on this one; I have not found a Windows app that seems to work with the MIDI;

For Windows, Midi-OX is a good tool to test with: http://www.midiox.com/

> so I can not expect to test this in Linux yet; I would like to be able to convert notes into sheet music; I tried TuxGuitar, but must admit I don't know how to get it to work with MIDI input, or if it even does.

For Linux, use amidi. "amidi -l" will list all available MIDI ports.
For example to dump all incoming messages, use "amidi --port hw:X,0
--dump". And to send messages, use "--send-hex" and make sure you send
valid MIDI messages, otherwise the other side won't do anything.

> I'm going to keep on this till I get it 100%; I have patience; lets hope you do too.

Well, I believe the quirks patch is correct, and there's only software
configuration issues left.


Daniel

Re: GR-55 Driver

[Jeffrey Scott Flesher Gmail]

Answers to questions:

> Are you sure hw:1,0 refers to your GR-55? Check the entries in
/proc/asound/cards again, please.

cat /proc/asound/cards
0 [U0x46d0x821    ]: USB-Audio - USB Device 0x46d:0x821
                      USB Device 0x46d:0x821 at usb-0000:00:12.2-1.1,
high speed
1 [GR55           ]: USB-Audio - GR-55
                      Roland GR-55 at usb-0000:00:12.2-4, high speed
2 [SB             ]: HDA-Intel - HDA ATI SB
                      HDA ATI SB at 0xf7ff4000 irq 16
3 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xfbcfc000 irq 19

Note that the position depends on if I start with the device on and
connected; as you see above, if I turn it on after startup; it becomes
number 3; but for all testing I always startup with it on.
***
> Can you try this with a 44100/16bit file?

# aplay -D plughw:GR55,0,0 test-441100-mono-16.wav
Playing WAVE 'test-441100-mono-16.wav' : Signed 16 bit Little Endian,
Rate 44100 Hz, Mono

This did work, I can hear it in the GR-55 Headphone; but only once; it
locks up the GR-55 after completing, and I had to disconnect the power,
the on/off switch did not work; nor did the midi interface to the
instrument. 

This may have been working all the time; since it only worked once, I
might have missed it; also both wav files worked (48 and 44 khz).

Sound Preference Matrix
Input   -- Output
GR-55   -- GR-55
***
> So you DO in fact get audio from the device then with some tool? 

Only in Windoze (Vista x64 and Windows 7).
***
> For Windows, Midi-OX is a good tool to test with...

I did test Midi-OX in Windows, it worked fine.
I also was able to capture MIDI in Pro Guitar 6.
***
I tried http://gna.org/projects/gmidimonitor/ and KMidimon with no help
***
# amidi -l

Dir Device    Name

[Nothing]
Not sure what to use for X amidi --port hw:X,0 --dump

amidi --port hw:GR55,0 --dump
ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC1D0
failed: Device or resource busy
cannot open port "hw:GR55,0": Device or resource busy

amidi --port hw:1,0 --dump
ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC1D0
failed: Device or resource busy
cannot open port "hw:1,0": Device or resource busy

amidi --port hw:0,0 --dump
ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC0D0
failed: No such file or directory
cannot open port "hw:0,0": No such file or directory

***
I updated my troubleshooting file
http://vetshelpcenter.com/media/troubleshooting-gr-55.txt
It has a lot of information in it.
***
I was thinking about writing a tool to help troubleshoot MIDI and Audio
ALSA Driver issues with QT4 using Drumstick, do you think this would
help?

Do you know of any tools written with it?
http://qt-apps.org/content/show.php/Drumstick?content=121300 

I can reverse engineer this using Snoopy Pro
http://sourceforge.net/projects/usbsnoop/
Would that help?

What next?

Thanks
Jeff


-----Original Message-----
From: Daniel Mack <zonque@gmail.com>
To: Jeffrey Scott Flesher Gmail <jeffrey.scott.flesher@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] GR-55 Driver
Date: Tue, 17 May 2011 12:11:14 +0200

On Mon, May 16, 2011 at 11:33 PM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> # alsamixer -D hw:GR55
> This sound device does not have any controls.
> ***
> # amixer -D hw:GR55 controls
> [Nothing]

That's possible.

> ***
> # cat /proc/asound/GR55/stream0
> Roland GR-55 at usb-0000:00:12.2-4, high speed : USB Audio
>
> Playback:
>   Status: Stop
>   Interface 0
>     Altset 1
>     Format: S32_LE
>     Channels: 2
>     Endpoint: 5 OUT (ASYNC)
>     Rates: 44100
>     Data packet interval: 125 us
>
> Capture:
>   Status: Stop
>   Interface 1
>     Altset 1
>     Format: S32_LE
>     Channels: 2
>     Endpoint: 4 IN (ASYNC)
>     Rates: 44100
>     Data packet interval: 125 us
> ***
> # cat /proc/asound/GR55/midi0
> GR-55

Looks ok.

> ***
> # aplay -D plughw:GR55,0,0 /usr/share/sounds/alsa/Front_Center.wav
> Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
> [No sound]

Can you try this with a 44100/16bit file?

> I am facing two problems, I am unfamiliar with this piece of equipment and as a result, I'm unsure how to test it.
>
> Testing Audio function:
> I tested it with Audacity in Windozes and it works;  in Linux I set it up the same way: GR-55 USB Audio (hw:1,0) as recording device; no sound.

Are you sure hw:1,0 refers to your GR-55? Check the entries in
/proc/asound/cards again, please.

> Using Logitech Webcam software I can record the guitar output; Using Cheese, I do not get Audio.

So you DO in fact get audio from the device then with some tool?

> Testing MIDI function:
> I'm going to call tech support on this one; I have not found a Windows app that seems to work with the MIDI;

For Windows, Midi-OX is a good tool to test with: http://www.midiox.com/

> so I can not expect to test this in Linux yet; I would like to be able to convert notes into sheet music; I tried TuxGuitar, but must admit I don't know how to get it to work with MIDI input, or if it even does.

For Linux, use amidi. "amidi -l" will list all available MIDI ports.
For example to dump all incoming messages, use "amidi --port hw:X,0
--dump". And to send messages, use "--send-hex" and make sure you send
valid MIDI messages, otherwise the other side won't do anything.

> I'm going to keep on this till I get it 100%; I have patience; lets hope you do too.

Well, I believe the quirks patch is correct, and there's only software
configuration issues left.


Daniel

Re: GR-55 Driver

[Jeffrey Scott Flesher Gmail]

Does this type of data (USBlyzer Report) help to write drivers?
http://vetshelpcenter.com/media/GR-55-USB-Anlyzer.html


-----Original Message-----
From: Daniel Mack <zonque@gmail.com>
To: Jeffrey Scott Flesher Gmail <jeffrey.scott.flesher@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] GR-55 Driver
Date: Tue, 17 May 2011 12:11:14 +0200

On Mon, May 16, 2011 at 11:33 PM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> # alsamixer -D hw:GR55
> This sound device does not have any controls.
> ***
> # amixer -D hw:GR55 controls
> [Nothing]

That's possible.

> ***
> # cat /proc/asound/GR55/stream0
> Roland GR-55 at usb-0000:00:12.2-4, high speed : USB Audio
>
> Playback:
>   Status: Stop
>   Interface 0
>     Altset 1
>     Format: S32_LE
>     Channels: 2
>     Endpoint: 5 OUT (ASYNC)
>     Rates: 44100
>     Data packet interval: 125 us
>
> Capture:
>   Status: Stop
>   Interface 1
>     Altset 1
>     Format: S32_LE
>     Channels: 2
>     Endpoint: 4 IN (ASYNC)
>     Rates: 44100
>     Data packet interval: 125 us
> ***
> # cat /proc/asound/GR55/midi0
> GR-55

Looks ok.

> ***
> # aplay -D plughw:GR55,0,0 /usr/share/sounds/alsa/Front_Center.wav
> Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
> [No sound]

Can you try this with a 44100/16bit file?

> I am facing two problems, I am unfamiliar with this piece of equipment and as a result, I'm unsure how to test it.
>
> Testing Audio function:
> I tested it with Audacity in Windozes and it works;  in Linux I set it up the same way: GR-55 USB Audio (hw:1,0) as recording device; no sound.

Are you sure hw:1,0 refers to your GR-55? Check the entries in
/proc/asound/cards again, please.

> Using Logitech Webcam software I can record the guitar output; Using Cheese, I do not get Audio.

So you DO in fact get audio from the device then with some tool?

> Testing MIDI function:
> I'm going to call tech support on this one; I have not found a Windows app that seems to work with the MIDI;

For Windows, Midi-OX is a good tool to test with: http://www.midiox.com/

> so I can not expect to test this in Linux yet; I would like to be able to convert notes into sheet music; I tried TuxGuitar, but must admit I don't know how to get it to work with MIDI input, or if it even does.

For Linux, use amidi. "amidi -l" will list all available MIDI ports.
For example to dump all incoming messages, use "amidi --port hw:X,0
--dump". And to send messages, use "--send-hex" and make sure you send
valid MIDI messages, otherwise the other side won't do anything.

> I'm going to keep on this till I get it 100%; I have patience; lets hope you do too.

Well, I believe the quirks patch is correct, and there's only software
configuration issues left.


Daniel

Re: GR-55 Driver

[Daniel Mack]

On Wed, May 18, 2011 at 5:34 PM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> Does this type of data (USBlyzer Report) help to write drivers?
> http://vetshelpcenter.com/media/GR-55-USB-Anlyzer.html

The problems you're still having are not related to the driver
anymore. The low-level part works. You're just facing a configuration
thing with the applications you're trying to use, but I don't see it
at the moment. It's most probably something trivial - can anyone else
on this list have a look at the comprehensive logs you've been
posting?


Thanks,
Daniel

Re: GR-55 Driver

[Jeffrey Scott Flesher Gmail]

Please take a second look at this information:

I do not understand what type of problem not related to the driver, that
you are referring to; if you can give me a few examples I can test that
theory; which is what I have been trying to do with my troubleshooting
file, configuration of Audacity is very simple, and works in Windows:
http://vetshelpcenter.com/media/troubleshooting-gr-55.txt

My document on driver activity in Windows, using Audacity to record
Audio, Guitar Pro 6 to record MIDI and the GR Floorboard to get Patch's,
which I have no problem getting this working; keep in mind I'm a Unix
programmer (30+ years), not Linux per say, but I'll work on that; but
I'm not a Windows End User, nor a Noobie; but I'm not in the best of
health; we all have our problems, I just don't want this interface to be
mine.
http://vetshelpcenter.com/media/GR-55-USB-Anlyzer.html

I do not see evidence that this driver patch is working as it should;
but its a good start, and I thank you for your work; now it shows up in
the system, and I do have limited access to the audio input channel; so
we are working in the right direction; but its far from saying that the
low-level part works; when I can only get one function working with
limited (still crashes) success.

Lets step back and look at this with Fresh eyes: 

This is the Roland GR-55 Guitar Synthesizer
http://www.rolandus.com/products/productdetails.php?ProductId=1148

You based this driver patch on the

BOSS JS-8
http://www.bossus.com/gear/productdetails.php?ProductId=1027

Instead of the GT-10; which seems more similar, but I do not know
anything about the difference in drivers, nor do I know that you have a
working driver for the GT-10, or that its based on the JS-8.

BOSS GT-10
http://www.bossus.com/gear/productdetails.php?ProductId=941

As such, all I can do is go along and see if I can get this to work; so
humor me, and lets see about basing this on the GT-10 and see how that
works; from what I read; they might be based on the same chip set; I
have contacted Roland, and they refuse to tell me what chip set they do
use; I can open up my GR-55 to see what chip set its using; its new, and
I hate to do this; but I did; below are my findings; but I still do not
know what chip set the GT-10 or JS-8 use; but I'm sure someone knows; so
maybe this is a better place to start.

High res image of GR-55 Motherboard interface
http://vetshelpcenter.com/media/GR-55-Motherboard.png

ROLAND WSP
R05011845
JAPAN 1026
HAL 889451

ROLAND SSC
R8A02021AB0
D4670467
BH11324
JAPAN 1035

ESMT
M12L128168A-
AZT1P00B4

I did a search with no results; so maybe this doesn't help at all; but I
had to try; my guess is that these are custom chips; Yamaha would be my
guess at manufacture; but I don't know that.

The work you do is very important to the community and I thank you.

-----Original Message-----
From: Daniel Mack <zonque@gmail.com>
To: Jeffrey Scott Flesher Gmail <jeffrey.scott.flesher@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] GR-55 Driver
Date: Wed, 18 May 2011 19:39:53 +0200

On Wed, May 18, 2011 at 5:34 PM, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com> wrote:
> Does this type of data (USBlyzer Report) help to write drivers?
> http://vetshelpcenter.com/media/GR-55-USB-Anlyzer.html

The problems you're still having are not related to the driver
anymore. The low-level part works. You're just facing a configuration
thing with the applications you're trying to use, but I don't see it
at the moment. It's most probably something trivial - can anyone else
on this list have a look at the comprehensive logs you've been
posting?


Thanks,
Daniel

Re: GR-55 Driver

[Keith A. Milner]

On Thursday 19 May 2011 22:09:44 Jeffrey Scott Flesher Gmail wrote:
> Please take a second look at this information:
> 
> I do not see evidence that this driver patch is working as it should;

I'm tempted to agree from the info on the thread.

> 
> Lets step back and look at this with Fresh eyes:
> 
> This is the Roland GR-55 Guitar Synthesizer
> http://www.rolandus.com/products/productdetails.php?ProductId=1148
> 
> You based this driver patch on the
> 
> BOSS JS-8
> http://www.bossus.com/gear/productdetails.php?ProductId=1027
> 
> Instead of the GT-10; which seems more similar, but I do not know
> anything about the difference in drivers, nor do I know that you have a
> working driver for the GT-10, or that its based on the JS-8.

I would say not. I "developed" (rather a grand term for the little I actually 
did) the quirks for the JS-8 just recently.

 I'm not sure where the GT-10 came from, but it's not derived from the JS-8. 
In fact my memory on this is poor (and I had some pointers from this mailing 
list) so the JS-8 may have been derived from the GT-10 at least in part, 
rather than the other way around

So with this, and also with the benefit of knowing what the JS-8, GT-10 and 
GR-55 are, I would agree the JS-8 probably isn't the right starting point for 
this.


> As such, all I can do is go along and see if I can get this to work; so
> humor me, and lets see about basing this on the GT-10 and see how that
> works; from what I read; they might be based on the same chip set;

On the other hand, the quirk entries for GT-10 and JS-8 are very close to 
being identical. I wonder if the GR-55 needs some specific .data like the GT-10 
does. It may be worth taking the GT-10 entry and changing it for the GR-55 
vid/pid and trying it.

Unfortunately, much as I would love a GR-55 to play with, I can't really 
justify getting one to experiment with drivers on, otherwise I would love to 
tinker with trying to get this going.

Cheers,

-- 
Keith A. Milner

Re: GR-55 Driver

[Daniel Mack]

On Mon, May 23, 2011 at 6:01 PM, Keith A. Milner
<maillist@superlative.org> wrote:

> On the other hand, the quirk entries for GT-10 and JS-8 are very close to
> being identical. I wonder if the GR-55 needs some specific .data like the GT-10
> does. It may be worth taking the GT-10 entry and changing it for the GR-55
> vid/pid and trying it.

I took the JS-8 quirks as a starting point because the USB descriptor
dumps looked identical to me. But I could have overlooked a detail,
that's possible. So as you've worked with such devices before, if you
could double-check and give some info, that would be a great help.
Without access to such (even similar) hardware, it's hard to really
help much.


Thanks,
Daniel

Re: GR-55 Driver

[Keith A. Milner]

On Monday 23 May 2011 18:08:09 Daniel Mack wrote:
> On Mon, May 23, 2011 at 6:01 PM, Keith A. Milner
> 
> <maillist@superlative.org> wrote:
> > On the other hand, the quirk entries for GT-10 and JS-8 are very close to
> > being identical. I wonder if the GR-55 needs some specific .data like the
> > GT-10 does. It may be worth taking the GT-10 entry and changing it for
> > the GR-55 vid/pid and trying it.
> 
> I took the JS-8 quirks as a starting point because the USB descriptor
> dumps looked identical to me. But I could have overlooked a detail,
> that's possible. So as you've worked with such devices before, if you
> could double-check and give some info, that would be a great help.
> Without access to such (even similar) hardware, it's hard to really
> help much.

Yes, I know what you mean.

I don't have any experience with the GT-10's USB or drivers. I'm not sure 
where those settings originated from or what the GT-10 descriptors look like. 
I just know that the GT-10 and GR-55 are very similar devices and, nominally, 
part of the same product family.

The JS-8 is from the same vendor but is really a very different product. 
Obviously, despite this, there are some internal similarities.

Unfortunately whilst I have a JS-8, I don't have either a GT-10 or GR-55 (nor 
any other Roland/Boss USB audio product) with which to compare it. I have a 
GT-3, but that is a rather old model with no USB, so it's no use here.

I found the following old thread about the GT-10. I don't know if this sheds 
any light?

http://old.nabble.com/Boss-GT-10-td17674980.html

-- 
Keith A. Milner

Re: GR-55 Driver

[Jeffrey Scott Flesher Gmail]

Its clear you need to have access to the Hardware you are writing the
driver for, so to that end, I decided to try to get you the Hardware and
Funds required to make this happen; this is my plan so far:

I started a Forum here http://mylinuxmachine.com/forum/8 
I had an idea to raise money for Hardware, as well as funds to support
the Developers, I only have one Shopping Cart setup; so I put it here:
http://lightwizzard.com/hardware.html 
http://lightwizzard.com/hardware/gr-55.html

I don't know if this will fly; but if it does, I'll get the hardware and
have it shipped to someone that wants to work on this Driver, a long
with any funds I collect; if this works good; I'll add more hardware
pages as requested. 

If this does work I'll add a shopping cart to MyLinuxMachine and move
the project there, I don't have the funds to do it now, or I would have;
a lot more thought needs to be put into this; but its a start. If you
have any suggestions let me know.

The Donation page at ALSA
http://www.alsa-project.org/main/index.php/AlsaProject:Site_support
is blank, so I had to find another way to raise money for you, and this
is the only thing I could think of.

Without Hardware and Money; its not really possible to continue to write
drivers for Hardware you do not have; I hope this is the beginning of
something that works good for everyone. I don't see any other way of
doing this at this point in time.

Jeff

-----Original Message-----
From: Daniel Mack <zonque@gmail.com>
To: Keith A. Milner <maillist@superlative.org>
Cc: alsa-devel@alsa-project.org, Jeffrey Scott Flesher Gmail
<jeffrey.scott.flesher@gmail.com>
Subject: Re: [alsa-devel] GR-55 Driver
Date: Mon, 23 May 2011 19:08:09 +0200

On Mon, May 23, 2011 at 6:01 PM, Keith A. Milner
<maillist@superlative.org> wrote:

> On the other hand, the quirk entries for GT-10 and JS-8 are very close to
> being identical. I wonder if the GR-55 needs some specific .data like the GT-10
> does. It may be worth taking the GT-10 entry and changing it for the GR-55
> vid/pid and trying it.

I took the JS-8 quirks as a starting point because the USB descriptor
dumps looked identical to me. But I could have overlooked a detail,
that's possible. So as you've worked with such devices before, if you
could double-check and give some info, that would be a great help.
Without access to such (even similar) hardware, it's hard to really
help much.


Thanks,
Daniel