Hercules PC DJ Console (Windows Edition) information

Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

Hello,

I have a Hercules PC DJ Console (Windows Edition) that I would like to
work with ALSA. The device outputs some sound at 48kHz after asoundrc
configuration, but this is not easy to do or "correct"/functional with
jackd. MIDI is not functional. I will include some information about
the device.

Note: This is a re-posting in ASCII format of an earilier HTML
formatted email message.

Output of lsusb:

jnc@baker:~$ lsusb -vv -s$(lsusb | grep Guillemot | cut -d':' -f1 |
awk '{print $2 ":" $4}')
Bus 001 Device 007: ID 06f8:b000 Guillemot Corp.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x06f8 Guillemot Corp.
  idProduct          0xb000
  bcdDevice            1.00
  iManufacturer           1
  iProduct                2
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          396
    bNumInterfaces          9
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
    MaxPower              300mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x07  EP 7 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               4
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Devices
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode           33 US
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      95
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0014  1x 20 bytes
        bInterval              10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Devices
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode           33 US
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      56
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0004  1x 4 bytes
        bInterval              10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         3 Human Interface Devices
      bInterfaceSubClass      0 No Subclass
      bInterfaceProtocol      0 None
      iInterface              0
        HID Device Descriptor:
          bLength                 9
          bDescriptorType        33
          bcdHID               1.10
          bCountryCode           33 US
          bNumDescriptors         1
          bDescriptorType        34 Report
          wDescriptorLength      41
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              10
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        4
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        5
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        5
      bAlternateSetting       1
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 9
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            9
          Transfer Type            Isochronous
          Synch Type               Adaptive
          Usage Type               Data
        wMaxPacketSize     0x0240  1x 576 bytes
        bInterval               1
        bRefresh                0
        bSynchAddress           0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        5
      bAlternateSetting       2
      bNumEndpoints           1
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 9
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes           13
          Transfer Type            Isochronous
          Synch Type               Synchronous
          Usage Type               Data
        wMaxPacketSize     0x0120  1x 288 bytes
        bInterval               1
        bRefresh                0
        bSynchAddress           0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        5
      bAlternateSetting       3
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 9
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            9
          Transfer Type            Isochronous
          Synch Type               Adaptive
          Usage Type               Data
        wMaxPacketSize     0x0240  1x 576 bytes
        bInterval               1
        bRefresh                0
        bSynchAddress           0
      Endpoint Descriptor:
        bLength                 9
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes           13
          Transfer Type            Isochronous
          Synch Type               Synchronous
          Usage Type               Data
        wMaxPacketSize     0x0120  1x 288 bytes
        bInterval               1
        bRefresh                0
        bSynchAddress           0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        6
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass         1 Audio
      bInterfaceSubClass      1 Control Device
      bInterfaceProtocol      0
      iInterface              0
      AudioControl Interface Descriptor:
        bLength                10
        bDescriptorType        36
        bDescriptorSubtype      1 (HEADER)
        bcdADC               1.00
        wTotalLength           88
        bInCollection           2
        baInterfaceNr( 0)       7
        baInterfaceNr( 1)       8
      AudioControl Interface Descriptor:
        bLength                12
        bDescriptorType        36
        bDescriptorSubtype      2 (INPUT_TERMINAL)
        bTerminalID             5
        wTerminalType      0x0101 USB Streaming
        bAssocTerminal          0
        bNrChannels             6
        wChannelConfig     0x003f
          Left Front (L)
          Right Front (R)
          Center Front (C)
          Low Freqency Enhancement (LFE)
          Left Surround (LS)
          Right Surround (RS)
        iChannelNames           0
        iTerminal               0
      AudioControl Interface Descriptor:
        bLength                14
        bDescriptorType        36
        bDescriptorSubtype      6 (FEATURE_UNIT)
        bUnitID                 6
        bSourceID               5
        bControlSize            1
        bmaControls( 0)      0x00
        bmaControls( 1)      0x03
          Mute
          Volume
        bmaControls( 2)      0x03
          Mute
          Volume
        bmaControls( 3)      0x03
          Mute
          Volume
        bmaControls( 4)      0x03
          Mute
          Volume
        bmaControls( 5)      0x03
          Mute
          Volume
        bmaControls( 6)      0x03
          Mute
          Volume
        iFeature                0
      AudioControl Interface Descriptor:
        bLength                 9
        bDescriptorType        36
        bDescriptorSubtype      3 (OUTPUT_TERMINAL)
        bTerminalID             7
        wTerminalType      0x0301 Speaker
        bAssocTerminal          0
        bSourceID               6
        iTerminal               0
      AudioControl Interface Descriptor:
        bLength                12
        bDescriptorType        36
        bDescriptorSubtype      2 (INPUT_TERMINAL)
        bTerminalID             1
        wTerminalType      0x0603 Line Connector
        bAssocTerminal          0
        bNrChannels             2
        wChannelConfig     0x0003
          Left Front (L)
          Right Front (R)
        iChannelNames           0
        iTerminal               0
      AudioControl Interface Descriptor:
        bLength                10
        bDescriptorType        36
        bDescriptorSubtype      6 (FEATURE_UNIT)
        bUnitID                 2
        bSourceID               1
        bControlSize            1
        bmaControls( 0)      0x80
          Delay
        bmaControls( 1)      0x00
        bmaControls( 2)      0x00
        iFeature                0
      AudioControl Interface Descriptor:
        bLength                12
        bDescriptorType        36
        bDescriptorSubtype      4 (MIXER_UNIT)
        bUnitID                 3
        bNrInPins               1
        baSourceID( 0)          2
        bNrChannels             2
        wChannelConfig     0x0003
          Left Front (L)
          Right Front (R)
        iChannelNames           0
        bmControls         0x00
        iMixer                  0
      AudioControl Interface Descriptor:
        bLength                 9
        bDescriptorType        36
        bDescriptorSubtype      3 (OUTPUT_TERMINAL)
        bTerminalID             4
        wTerminalType      0x0101 USB Streaming
        bAssocTerminal          0
        bSourceID               3
        iTerminal               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        7
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass         1 Audio
      bInterfaceSubClass      2 Streaming
      bInterfaceProtocol      0
      iInterface              0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        7
      bAlternateSetting       1
      bNumEndpoints           1
      bInterfaceClass         1 Audio
      bInterfaceSubClass      2 Streaming
      bInterfaceProtocol      0
      iInterface              0
      AudioStreaming Interface Descriptor:
        bLength                 7
        bDescriptorType        36
        bDescriptorSubtype      1 (AS_GENERAL)
        bTerminalLink           5
        bDelay                  1 frames
        wFormatTag              1 PCM
      AudioStreaming Interface Descriptor:
        bLength                11
        bDescriptorType        36
        bDescriptorSubtype      2 (FORMAT_TYPE)
        bFormatType             1 (FORMAT_TYPE_I)
        bNrChannels             6
        bSubframeSize           2
        bBitResolution         16
        bSamFreqType            1 Discrete
        tSamFreq[ 0]        48000
      Endpoint Descriptor:
        bLength                 9
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            9
          Transfer Type            Isochronous
          Synch Type               Adaptive
          Usage Type               Data
        wMaxPacketSize     0x0240  1x 576 bytes
        bInterval               1
        bRefresh                0
        bSynchAddress           0
        AudioControl Endpoint Descriptor:
          bLength                 7
          bDescriptorType        37
          bDescriptorSubtype      1 (EP_GENERAL)
          bmAttributes         0x01
            Sampling Frequency
          bLockDelayUnits         0 Undefined
          wLockDelay              0 Undefined
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        8
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass         1 Audio
      bInterfaceSubClass      2 Streaming
      bInterfaceProtocol      0
      iInterface              0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        8
      bAlternateSetting       1
      bNumEndpoints           1
      bInterfaceClass         1 Audio
      bInterfaceSubClass      2 Streaming
      bInterfaceProtocol      0
      iInterface              0
      AudioStreaming Interface Descriptor:
        bLength                 7
        bDescriptorType        36
        bDescriptorSubtype      1 (AS_GENERAL)
        bTerminalLink           4
        bDelay                  1 frames
        wFormatTag              1 PCM
      AudioStreaming Interface Descriptor:
        bLength                11
        bDescriptorType        36
        bDescriptorSubtype      2 (FORMAT_TYPE)
        bFormatType             1 (FORMAT_TYPE_I)
        bNrChannels             2
        bSubframeSize           2
        bBitResolution         16
        bSamFreqType            1 Discrete
        tSamFreq[ 0]        48000
      Endpoint Descriptor:
        bLength                 9
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes           13
          Transfer Type            Isochronous
          Synch Type               Synchronous
          Usage Type               Data
        wMaxPacketSize     0x00c0  1x 192 bytes
        bInterval               1
        bRefresh                0
        bSynchAddress           0
        AudioControl Endpoint Descriptor:
          bLength                 7
          bDescriptorType        37
          bDescriptorSubtype      1 (EP_GENERAL)
          bmAttributes         0x01
            Sampling Frequency
          bLockDelayUnits         0 Undefined
          wLockDelay              0 Undefined

jnc@baker:~$ cat /proc/asound/cards
0 [CK8S           ]: NFORCE - NVidia CK8S
                     NVidia CK8S with ALC655 at 0xe6001000, irq 19
1 [M8x8           ]: USB-Audio - MidiSport 8x8
                     M-Audio MidiSport 8x8 at usb-0000:00:02.0-1, full speed
2 [Console        ]: USB-Audio - Hercules DJ Console
                     Hercules Hercules DJ Console at
usb-0000:00:02.0-3, full speed
3 [Keyboard       ]: USB-Audio - MK-461C USB MIDI Keyboard
                     Evolution Electronics Ltd. MK-461C USB MIDI
Keyboard at usb-0000:00:02.2-2.4, f

jnc@baker:~$ amidi -l
Device    Name
hw:1,0,0  MidiSport 8x8 MIDI 1
hw:1,0,1  MidiSport 8x8 MIDI 2
hw:1,0,2  MidiSport 8x8 MIDI 3
hw:1,0,3  MidiSport 8x8 MIDI 4
hw:1,0,4  MidiSport 8x8 MIDI 5
hw:1,0,5  MidiSport 8x8 MIDI 6
hw:1,0,6  MidiSport 8x8 MIDI 7
hw:1,0,7  MidiSport 8x8 MIDI 8
hw:1,0,8  MidiSport 8x8 Control
hw:3,0,0  MK-461C USB MIDI Keyboard MIDI

jnc@baker:~$ amixer controls -c2
numid=1,iface=MIXER,name='PCM Playback Switch'
numid=2,iface=MIXER,name='PCM Playback Volume'
numid=3,iface=MIXER,name='Delay Control'

jnc@baker:~$ amixer scontrols -c2
amixer: Mixer hw:2 load error: Invalid argument

jnc@baker:~$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.10rc1.
Compiled on Sep 26 2005 for kernel 2.6.13.2-jnc2.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Patrick Shirkey]

Hi Eric,

It looks like the Hercules only supports 48000Hz.

This is a well documented problem with USB devices that means they 
function best
at 48000Hz due to the packet size for the USB data stream. The windows and I
assume mac  drivers provide software level resampling so that the cards appear
to run at 44100Hz but that feature is not available for JACK and it appears
from my tests that the ALSA "plug"  plugin only works if the card has built in
44100Hz support anyway.

IMO USB audio and intel8x0 need a more advanced resampling plugin for 
ALSA. But
that's a different story.

FYI: I have an maudio quattro which I have only just been able to get to work
with all four ports at one time with JACK. The reason was my CPU was too slow
until now.

I use this commandline for JACK:

jackd -v -R -d alsa -d hw:0 -s -S -P -n3 -p 4096 -zt

Even then I can't do any recording via JACK because either JACK or my disks
don't like doing realtime r/w unless they are top priority in the interrupt
stack.

You may fair better as the Hercules is USB 2.0 compatible.


Cheers.


Quoting Eric Shattow <lucent@gmail.com>:

> Hello,
>
> I have a Hercules PC DJ Console (Windows Edition) that I would like to
> work with ALSA. The device outputs some sound at 48kHz after asoundrc
> configuration, but this is not easy to do or "correct"/functional with
> jackd. MIDI is not functional. I will include some information about
> the device.
>
> Note: This is a re-posting in ASCII format of an earilier HTML
> formatted email message.
>
> Output of lsusb:
>
> jnc@baker:~$ lsusb -vv -s$(lsusb | grep Guillemot | cut -d':' -f1 |
> awk '{print $2 ":" $4}')
> Bus 001 Device 007: ID 06f8:b000 Guillemot Corp.
> Device Descriptor:
>  bLength                18
>  bDescriptorType         1
>  bcdUSB               1.10
>  bDeviceClass            0 (Defined at Interface level)
>  bDeviceSubClass         0
>  bDeviceProtocol         0
>  bMaxPacketSize0         8
>  idVendor           0x06f8 Guillemot Corp.
>  idProduct          0xb000
>  bcdDevice            1.00
>  iManufacturer           1
>  iProduct                2
>  iSerial                 0
>  bNumConfigurations      1
>  Configuration Descriptor:
>    bLength                 9
>    bDescriptorType         2
>    wTotalLength          396
>    bNumInterfaces          9
>    bConfigurationValue     1
>    iConfiguration          0
>    bmAttributes         0x80
>    MaxPower              300mA
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        0
>      bAlternateSetting       0
>      bNumEndpoints           1
>      bInterfaceClass       255 Vendor Specific Class
>      bInterfaceSubClass      0
>      bInterfaceProtocol      0
>      iInterface              0
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x07  EP 7 OUT
>        bmAttributes            2
>          Transfer Type            Bulk
>          Synch Type               None
>          Usage Type               Data
>        wMaxPacketSize     0x0010  1x 16 bytes
>        bInterval               4
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        1
>      bAlternateSetting       0
>      bNumEndpoints           1
>      bInterfaceClass         3 Human Interface Devices
>      bInterfaceSubClass      0 No Subclass
>      bInterfaceProtocol      0 None
>      iInterface              0
>        HID Device Descriptor:
>          bLength                 9
>          bDescriptorType        33
>          bcdHID               1.10
>          bCountryCode           33 US
>          bNumDescriptors         1
>          bDescriptorType        34 Report
>          wDescriptorLength      95
>         Report Descriptors:
>           ** UNAVAILABLE **
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x83  EP 3 IN
>        bmAttributes            3
>          Transfer Type            Interrupt
>          Synch Type               None
>          Usage Type               Data
>        wMaxPacketSize     0x0014  1x 20 bytes
>        bInterval              10
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        2
>      bAlternateSetting       0
>      bNumEndpoints           1
>      bInterfaceClass         3 Human Interface Devices
>      bInterfaceSubClass      0 No Subclass
>      bInterfaceProtocol      0 None
>      iInterface              0
>        HID Device Descriptor:
>          bLength                 9
>          bDescriptorType        33
>          bcdHID               1.10
>          bCountryCode           33 US
>          bNumDescriptors         1
>          bDescriptorType        34 Report
>          wDescriptorLength      56
>         Report Descriptors:
>           ** UNAVAILABLE **
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x84  EP 4 IN
>        bmAttributes            3
>          Transfer Type            Interrupt
>          Synch Type               None
>          Usage Type               Data
>        wMaxPacketSize     0x0004  1x 4 bytes
>        bInterval              10
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        3
>      bAlternateSetting       0
>      bNumEndpoints           1
>      bInterfaceClass         3 Human Interface Devices
>      bInterfaceSubClass      0 No Subclass
>      bInterfaceProtocol      0 None
>      iInterface              0
>        HID Device Descriptor:
>          bLength                 9
>          bDescriptorType        33
>          bcdHID               1.10
>          bCountryCode           33 US
>          bNumDescriptors         1
>          bDescriptorType        34 Report
>          wDescriptorLength      41
>         Report Descriptors:
>           ** UNAVAILABLE **
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x85  EP 5 IN
>        bmAttributes            3
>          Transfer Type            Interrupt
>          Synch Type               None
>          Usage Type               Data
>        wMaxPacketSize     0x0008  1x 8 bytes
>        bInterval              10
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        4
>      bAlternateSetting       0
>      bNumEndpoints           2
>      bInterfaceClass       255 Vendor Specific Class
>      bInterfaceSubClass      0
>      bInterfaceProtocol      0
>      iInterface              0
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x06  EP 6 OUT
>        bmAttributes            2
>          Transfer Type            Bulk
>          Synch Type               None
>          Usage Type               Data
>        wMaxPacketSize     0x0008  1x 8 bytes
>        bInterval               0
>      Endpoint Descriptor:
>        bLength                 7
>        bDescriptorType         5
>        bEndpointAddress     0x86  EP 6 IN
>        bmAttributes            2
>          Transfer Type            Bulk
>          Synch Type               None
>          Usage Type               Data
>        wMaxPacketSize     0x0008  1x 8 bytes
>        bInterval               0
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        5
>      bAlternateSetting       0
>      bNumEndpoints           0
>      bInterfaceClass       255 Vendor Specific Class
>      bInterfaceSubClass      0
>      bInterfaceProtocol      0
>      iInterface              0
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        5
>      bAlternateSetting       1
>      bNumEndpoints           1
>      bInterfaceClass       255 Vendor Specific Class
>      bInterfaceSubClass      0
>      bInterfaceProtocol      0
>      iInterface              0
>      Endpoint Descriptor:
>        bLength                 9
>        bDescriptorType         5
>        bEndpointAddress     0x01  EP 1 OUT
>        bmAttributes            9
>          Transfer Type            Isochronous
>          Synch Type               Adaptive
>          Usage Type               Data
>        wMaxPacketSize     0x0240  1x 576 bytes
>        bInterval               1
>        bRefresh                0
>        bSynchAddress           0
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        5
>      bAlternateSetting       2
>      bNumEndpoints           1
>      bInterfaceClass       255 Vendor Specific Class
>      bInterfaceSubClass      0
>      bInterfaceProtocol      0
>      iInterface              0
>      Endpoint Descriptor:
>        bLength                 9
>        bDescriptorType         5
>        bEndpointAddress     0x81  EP 1 IN
>        bmAttributes           13
>          Transfer Type            Isochronous
>          Synch Type               Synchronous
>          Usage Type               Data
>        wMaxPacketSize     0x0120  1x 288 bytes
>        bInterval               1
>        bRefresh                0
>        bSynchAddress           0
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        5
>      bAlternateSetting       3
>      bNumEndpoints           2
>      bInterfaceClass       255 Vendor Specific Class
>      bInterfaceSubClass      0
>      bInterfaceProtocol      0
>      iInterface              0
>      Endpoint Descriptor:
>        bLength                 9
>        bDescriptorType         5
>        bEndpointAddress     0x01  EP 1 OUT
>        bmAttributes            9
>          Transfer Type            Isochronous
>          Synch Type               Adaptive
>          Usage Type               Data
>        wMaxPacketSize     0x0240  1x 576 bytes
>        bInterval               1
>        bRefresh                0
>        bSynchAddress           0
>      Endpoint Descriptor:
>        bLength                 9
>        bDescriptorType         5
>        bEndpointAddress     0x81  EP 1 IN
>        bmAttributes           13
>          Transfer Type            Isochronous
>          Synch Type               Synchronous
>          Usage Type               Data
>        wMaxPacketSize     0x0120  1x 288 bytes
>        bInterval               1
>        bRefresh                0
>        bSynchAddress           0
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        6
>      bAlternateSetting       0
>      bNumEndpoints           0
>      bInterfaceClass         1 Audio
>      bInterfaceSubClass      1 Control Device
>      bInterfaceProtocol      0
>      iInterface              0
>      AudioControl Interface Descriptor:
>        bLength                10
>        bDescriptorType        36
>        bDescriptorSubtype      1 (HEADER)
>        bcdADC               1.00
>        wTotalLength           88
>        bInCollection           2
>        baInterfaceNr( 0)       7
>        baInterfaceNr( 1)       8
>      AudioControl Interface Descriptor:
>        bLength                12
>        bDescriptorType        36
>        bDescriptorSubtype      2 (INPUT_TERMINAL)
>        bTerminalID             5
>        wTerminalType      0x0101 USB Streaming
>        bAssocTerminal          0
>        bNrChannels             6
>        wChannelConfig     0x003f
>          Left Front (L)
>          Right Front (R)
>          Center Front (C)
>          Low Freqency Enhancement (LFE)
>          Left Surround (LS)
>          Right Surround (RS)
>        iChannelNames           0
>        iTerminal               0
>      AudioControl Interface Descriptor:
>        bLength                14
>        bDescriptorType        36
>        bDescriptorSubtype      6 (FEATURE_UNIT)
>        bUnitID                 6
>        bSourceID               5
>        bControlSize            1
>        bmaControls( 0)      0x00
>        bmaControls( 1)      0x03
>          Mute
>          Volume
>        bmaControls( 2)      0x03
>          Mute
>          Volume
>        bmaControls( 3)      0x03
>          Mute
>          Volume
>        bmaControls( 4)      0x03
>          Mute
>          Volume
>        bmaControls( 5)      0x03
>          Mute
>          Volume
>        bmaControls( 6)      0x03
>          Mute
>          Volume
>        iFeature                0
>      AudioControl Interface Descriptor:
>        bLength                 9
>        bDescriptorType        36
>        bDescriptorSubtype      3 (OUTPUT_TERMINAL)
>        bTerminalID             7
>        wTerminalType      0x0301 Speaker
>        bAssocTerminal          0
>        bSourceID               6
>        iTerminal               0
>      AudioControl Interface Descriptor:
>        bLength                12
>        bDescriptorType        36
>        bDescriptorSubtype      2 (INPUT_TERMINAL)
>        bTerminalID             1
>        wTerminalType      0x0603 Line Connector
>        bAssocTerminal          0
>        bNrChannels             2
>        wChannelConfig     0x0003
>          Left Front (L)
>          Right Front (R)
>        iChannelNames           0
>        iTerminal               0
>      AudioControl Interface Descriptor:
>        bLength                10
>        bDescriptorType        36
>        bDescriptorSubtype      6 (FEATURE_UNIT)
>        bUnitID                 2
>        bSourceID               1
>        bControlSize            1
>        bmaControls( 0)      0x80
>          Delay
>        bmaControls( 1)      0x00
>        bmaControls( 2)      0x00
>        iFeature                0
>      AudioControl Interface Descriptor:
>        bLength                12
>        bDescriptorType        36
>        bDescriptorSubtype      4 (MIXER_UNIT)
>        bUnitID                 3
>        bNrInPins               1
>        baSourceID( 0)          2
>        bNrChannels             2
>        wChannelConfig     0x0003
>          Left Front (L)
>          Right Front (R)
>        iChannelNames           0
>        bmControls         0x00
>        iMixer                  0
>      AudioControl Interface Descriptor:
>        bLength                 9
>        bDescriptorType        36
>        bDescriptorSubtype      3 (OUTPUT_TERMINAL)
>        bTerminalID             4
>        wTerminalType      0x0101 USB Streaming
>        bAssocTerminal          0
>        bSourceID               3
>        iTerminal               0
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        7
>      bAlternateSetting       0
>      bNumEndpoints           0
>      bInterfaceClass         1 Audio
>      bInterfaceSubClass      2 Streaming
>      bInterfaceProtocol      0
>      iInterface              0
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        7
>      bAlternateSetting       1
>      bNumEndpoints           1
>      bInterfaceClass         1 Audio
>      bInterfaceSubClass      2 Streaming
>      bInterfaceProtocol      0
>      iInterface              0
>      AudioStreaming Interface Descriptor:
>        bLength                 7
>        bDescriptorType        36
>        bDescriptorSubtype      1 (AS_GENERAL)
>        bTerminalLink           5
>        bDelay                  1 frames
>        wFormatTag              1 PCM
>      AudioStreaming Interface Descriptor:
>        bLength                11
>        bDescriptorType        36
>        bDescriptorSubtype      2 (FORMAT_TYPE)
>        bFormatType             1 (FORMAT_TYPE_I)
>        bNrChannels             6
>        bSubframeSize           2
>        bBitResolution         16
>        bSamFreqType            1 Discrete
>        tSamFreq[ 0]        48000
>      Endpoint Descriptor:
>        bLength                 9
>        bDescriptorType         5
>        bEndpointAddress     0x01  EP 1 OUT
>        bmAttributes            9
>          Transfer Type            Isochronous
>          Synch Type               Adaptive
>          Usage Type               Data
>        wMaxPacketSize     0x0240  1x 576 bytes
>        bInterval               1
>        bRefresh                0
>        bSynchAddress           0
>        AudioControl Endpoint Descriptor:
>          bLength                 7
>          bDescriptorType        37
>          bDescriptorSubtype      1 (EP_GENERAL)
>          bmAttributes         0x01
>            Sampling Frequency
>          bLockDelayUnits         0 Undefined
>          wLockDelay              0 Undefined
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        8
>      bAlternateSetting       0
>      bNumEndpoints           0
>      bInterfaceClass         1 Audio
>      bInterfaceSubClass      2 Streaming
>      bInterfaceProtocol      0
>      iInterface              0
>    Interface Descriptor:
>      bLength                 9
>      bDescriptorType         4
>      bInterfaceNumber        8
>      bAlternateSetting       1
>      bNumEndpoints           1
>      bInterfaceClass         1 Audio
>      bInterfaceSubClass      2 Streaming
>      bInterfaceProtocol      0
>      iInterface              0
>      AudioStreaming Interface Descriptor:
>        bLength                 7
>        bDescriptorType        36
>        bDescriptorSubtype      1 (AS_GENERAL)
>        bTerminalLink           4
>        bDelay                  1 frames
>        wFormatTag              1 PCM
>      AudioStreaming Interface Descriptor:
>        bLength                11
>        bDescriptorType        36
>        bDescriptorSubtype      2 (FORMAT_TYPE)
>        bFormatType             1 (FORMAT_TYPE_I)
>        bNrChannels             2
>        bSubframeSize           2
>        bBitResolution         16
>        bSamFreqType            1 Discrete
>        tSamFreq[ 0]        48000
>      Endpoint Descriptor:
>        bLength                 9
>        bDescriptorType         5
>        bEndpointAddress     0x81  EP 1 IN
>        bmAttributes           13
>          Transfer Type            Isochronous
>          Synch Type               Synchronous
>          Usage Type               Data
>        wMaxPacketSize     0x00c0  1x 192 bytes
>        bInterval               1
>        bRefresh                0
>        bSynchAddress           0
>        AudioControl Endpoint Descriptor:
>          bLength                 7
>          bDescriptorType        37
>          bDescriptorSubtype      1 (EP_GENERAL)
>          bmAttributes         0x01
>            Sampling Frequency
>          bLockDelayUnits         0 Undefined
>          wLockDelay              0 Undefined
>
> jnc@baker:~$ cat /proc/asound/cards
> 0 [CK8S           ]: NFORCE - NVidia CK8S
>                     NVidia CK8S with ALC655 at 0xe6001000, irq 19
> 1 [M8x8           ]: USB-Audio - MidiSport 8x8
>                     M-Audio MidiSport 8x8 at usb-0000:00:02.0-1, full speed
> 2 [Console        ]: USB-Audio - Hercules DJ Console
>                     Hercules Hercules DJ Console at
> usb-0000:00:02.0-3, full speed
> 3 [Keyboard       ]: USB-Audio - MK-461C USB MIDI Keyboard
>                     Evolution Electronics Ltd. MK-461C USB MIDI
> Keyboard at usb-0000:00:02.2-2.4, f
>
> jnc@baker:~$ amidi -l
> Device    Name
> hw:1,0,0  MidiSport 8x8 MIDI 1
> hw:1,0,1  MidiSport 8x8 MIDI 2
> hw:1,0,2  MidiSport 8x8 MIDI 3
> hw:1,0,3  MidiSport 8x8 MIDI 4
> hw:1,0,4  MidiSport 8x8 MIDI 5
> hw:1,0,5  MidiSport 8x8 MIDI 6
> hw:1,0,6  MidiSport 8x8 MIDI 7
> hw:1,0,7  MidiSport 8x8 MIDI 8
> hw:1,0,8  MidiSport 8x8 Control
> hw:3,0,0  MK-461C USB MIDI Keyboard MIDI
>
> jnc@baker:~$ amixer controls -c2
> numid=1,iface=MIXER,name='PCM Playback Switch'
> numid=2,iface=MIXER,name='PCM Playback Volume'
> numid=3,iface=MIXER,name='Delay Control'
>
> jnc@baker:~$ amixer scontrols -c2
> amixer: Mixer hw:2 load error: Invalid argument
>
> jnc@baker:~$ cat /proc/asound/version
> Advanced Linux Sound Architecture Driver Version 1.0.10rc1.
> Compiled on Sep 26 2005 for kernel 2.6.13.2-jnc2.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
>



--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org/ - The Linux Audio Users guide
Http://www.djcj.org/gigs - Gigs Guide Korea
========================================

Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Clemens Ladisch]

Eric Shattow wrote:
> I have a Hercules PC DJ Console (Windows Edition) that I would like to
> work with ALSA. The device outputs some sound at 48kHz after asoundrc
> configuration,

It should just work without an .asoundrc.  What did you put in there?

> MIDI is not functional.

Please try the patch below (against the current CVS).
How many ports does it have? -- Eight is probably too much ... :-)


HTH
Clemens


--- alsa-kernel/usb/usbquirks.h	26 Sep 2005 07:55:01 -0000	1.54
+++ alsa-kernel/usb/usbquirks.h	28 Sep 2005 11:58:56 -0000
@@ -1066,6 +1066,21 @@
 	/* TODO: add Edirol UM-3 support */
 	/* TODO: add Edirol MD-P1 support */

+/* Guillemot devices */
+{
+	USB_DEVICE_VENDOR_SPEC(0x06f8, 0xb000),
+	.driver_info = (unsigned long) & (const snd_usb_audio_quirk_t) {
+		.vendor_name = "Hercules",
+		.product_name = "DJ Console",
+		.ifnum = 4,
+		.type = QUIRK_MIDI_FIXED_ENDPOINT,
+		.data = & (const snd_usb_midi_endpoint_info_t) {
+			.out_cables = 0x00ff,
+			.in_cables  = 0x00ff
+		}
+	}
+},
+
 /* Midiman/M-Audio devices */
 {
 	USB_DEVICE_VENDOR_SPEC(0x0763, 0x1002),



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

On 9/28/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> Eric Shattow wrote:
> > I have a Hercules PC DJ Console (Windows Edition) that I would like to
> > work with ALSA. The device outputs some sound at 48kHz after asoundrc
> > configuration,
>
> It should just work without an .asoundrc.  What did you put in there?
>
> > MIDI is not functional.
>
> Please try the patch below (against the current CVS).
> How many ports does it have? -- Eight is probably too much ... :-)
>
>
> HTH
> Clemens
>
>
> --- alsa-kernel/usb/usbquirks.h 26 Sep 2005 07:55:01 -0000      1.54
> +++ alsa-kernel/usb/usbquirks.h 28 Sep 2005 11:58:56 -0000
> @@ -1066,6 +1066,21 @@
>         /* TODO: add Edirol UM-3 support */
>         /* TODO: add Edirol MD-P1 support */
>
> +/* Guillemot devices */
> +{
> +       USB_DEVICE_VENDOR_SPEC(0x06f8, 0xb000),
> +       .driver_info = (unsigned long) & (const snd_usb_audio_quirk_t) {
> +               .vendor_name = "Hercules",
> +               .product_name = "DJ Console",
> +               .ifnum = 4,
> +               .type = QUIRK_MIDI_FIXED_ENDPOINT,
> +               .data = & (const snd_usb_midi_endpoint_info_t) {
> +                       .out_cables = 0x00ff,
> +                       .in_cables  = 0x00ff
> +               }
> +       }
> +},
> +
>  /* Midiman/M-Audio devices */
>  {
>         USB_DEVICE_VENDOR_SPEC(0x0763, 0x1002),
>
>

I tried the above patch, and applied it to debian alsa-source package
1.0.9b4, and now the DJ Console is recognized. I've changed some of
the hardware around since my last post.

baker:/usr/src# amidi -l
Device    Name
hw:0,0    M Audio Delta 1010 MIDI
hw:2,0,0  DJ Console MIDI 1
hw:2,0,1  DJ Console MIDI 2
hw:2,0,2  DJ Console MIDI 3
hw:2,0,3  DJ Console MIDI 4
hw:2,0,4  DJ Console MIDI 5
hw:2,0,5  DJ Console MIDI 6
hw:2,0,6  DJ Console MIDI 7
hw:2,0,7  DJ Console MIDI 8

However, using amidi -d -p hw:2,0,n  does not yield any output when
moving the controls. I also tried 'amidi -p virtual -d' and to connect
all the outputs that show up in the alsa sequencer from the DJ Console
to this virtual device, and no output.

Isn't that strange? Maybe this is due to me not using cvs code, I will
have to make some time soon and try it. Anyways, thanks for the patch.
It is giving me some hope this device will eventually work :)


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Clemens Ladisch]

Eric Shattow wrote:
> I tried the above patch, and applied it to debian alsa-source package
> 1.0.9b4, and now the DJ Console is recognized.
>
> However, using amidi -d -p hw:2,0,n  does not yield any output when
> moving the controls.

Probably the devices user a different protocol than I was assuming.
Please uncomment the DUMP_PACKETS line near the top of usbmidi.c and
show any "received packet" lines that end up in the system log.


Regards,
Clemens



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

On 9/29/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> Eric Shattow wrote:
> > I tried the above patch, and applied it to debian alsa-source package
> > 1.0.9b4, and now the DJ Console is recognized.
> >
> > However, using amidi -d -p hw:2,0,n  does not yield any output when
> > moving the controls.
>
> Probably the devices user a different protocol than I was assuming.
> Please uncomment the DUMP_PACKETS line near the top of usbmidi.c and
> show any "received packet" lines that end up in the system log.
>
>
> Regards,
> Clemens
>
>

I tried your suggestion for DUMP_PACKETS and there was no output with
1.0.9b4+patches. I will now try CVS with the above usbquirk.h patch
and #define DUMP_PACKETS to see what happens:

Sep 29 13:54:18 [kernel] input: USB HID v1.10 Joystick [Hercules
Hercules DJ Console] on usb-0000:00:02.1-3
Sep 29 13:54:18 [kernel] input: USB HID v1.10 Mouse [Hercules Hercules
DJ Console] on usb-0000:00:02.1-3
Sep 29 13:54:18 [kernel] input: USB HID v1.10 Keyboard [Hercules
Hercules DJ Console] on usb-0000:00:02.1-3
Sep 29 13:54:18 [kernel] snd-usb-audio: probe of 2-3:1.5 failed with error -5
Sep 29 13:54:18 [kernel] ALSA
/tmp/alsa-cvs20050929/alsa-driver/usb/usbmixer.c:669: 2:6: cannot get
min/max values for control 8 (id 2)

I think I've seen error -5 mentioned on the list archives, how to fix this?


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

On 9/29/05, Eric Shattow <lucent@gmail.com> wrote:
> On 9/29/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> > Eric Shattow wrote:
> > > I tried the above patch, and applied it to debian alsa-source package
> > > 1.0.9b4, and now the DJ Console is recognized.
> > >
> > > However, using amidi -d -p hw:2,0,n  does not yield any output when
> > > moving the controls.
> >
> > Probably the devices user a different protocol than I was assuming.
> > Please uncomment the DUMP_PACKETS line near the top of usbmidi.c and
> > show any "received packet" lines that end up in the system log.
> >
> >
> > Regards,
> > Clemens
> >
> >
>
> I tried your suggestion for DUMP_PACKETS and there was no output with
> 1.0.9b4+patches. I will now try CVS with the above usbquirk.h patch
> and #define DUMP_PACKETS to see what happens:
>
> Sep 29 13:54:18 [kernel] input: USB HID v1.10 Joystick [Hercules
> Hercules DJ Console] on usb-0000:00:02.1-3
> Sep 29 13:54:18 [kernel] input: USB HID v1.10 Mouse [Hercules Hercules
> DJ Console] on usb-0000:00:02.1-3
> Sep 29 13:54:18 [kernel] input: USB HID v1.10 Keyboard [Hercules
> Hercules DJ Console] on usb-0000:00:02.1-3
> Sep 29 13:54:18 [kernel] snd-usb-audio: probe of 2-3:1.5 failed with error -5
> Sep 29 13:54:18 [kernel] ALSA
> /tmp/alsa-cvs20050929/alsa-driver/usb/usbmixer.c:669: 2:6: cannot get
> min/max values for control 8 (id 2)
>
> I think I've seen error -5 mentioned on the list archives, how to fix this?
>

It's not getting far enough to dump any packets.  What should I do next?


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Clemens Ladisch]

Eric Shattow wrote:
> It's not getting far enough to dump any packets.

This means that no packets are sent by the device.

It's possible that the controller data is reported by the HID
interfaces.  Did you test those?


Regards,
Clemens



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

On 10/4/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> Eric Shattow wrote:
> > It's not getting far enough to dump any packets.
>
> This means that no packets are sent by the device.
>
> It's possible that the controller data is reported by the HID
> interfaces.  Did you test those?
>
>
> Regards,
> Clemens
>
>

How would I make it so that usbhid module does not interfere?

 Eric


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Clemens Ladisch]

Eric Shattow wrote:
> On 10/4/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> > Eric Shattow wrote:
> > > It's not getting far enough to dump any packets.
> >
> > This means that no packets are sent by the device.
> >
> > It's possible that the controller data is reported by the HID
> > interfaces.  Did you test those?
>
> How would I make it so that usbhid module does not interfere?

You wouldn't.  The 'proper' way would be to write a utility that reads
input events from the three HID interfaces and converts them to MIDI.
Otherwise, somebody would have to write a new driver for this device,
and change the usbhid driver accordingly.


Regards,
Clemens



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

On 10/4/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> Eric Shattow wrote:
> > On 10/4/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> > > Eric Shattow wrote:
> > > > It's not getting far enough to dump any packets.
> > >
> > > This means that no packets are sent by the device.
> > >
> > > It's possible that the controller data is reported by the HID
> > > interfaces.  Did you test those?
> >
> > How would I make it so that usbhid module does not interfere?
>
> You wouldn't.  The 'proper' way would be to write a utility that reads
> input events from the three HID interfaces and converts them to MIDI.
> Otherwise, somebody would have to write a new driver for this device,
> and change the usbhid driver accordingly.
>
>
> Regards,
> Clemens
>
>

This HPCDJ Console is a USB MIDI device and from all indications I can
see, should be made to function as such. The device has an MIDI IN
port and an MIDI OUT port, as many USB-MIDI interfaces do. Event
device (evdev) support is irrelevent to function in ALSA, no? If
output from /dev/eventX for the HPCDJ would be helpful please let me
know and I can make some captures.

The Macintosh edition of HPCDJ Console works as an ALSA sound and midi
device, and so I must question where you and fellow ALSA developers
feel support for these DJ Console devices is most appropriate.

Should the HPCDJ Console (Mac, and Windows editions) be supported in
ALSA as sound devices only, ignoring the midi portion, or be supported
in ALSA as sound and MIDI devices?

Is it appropriate to continue supporting all midi and sound usb
devices with a single kernel module?

My target application is to use the HPCDJ Console with Mixxx software,
and Mixxx is requiring an OSS-style /dev/midi device to read data
from. Ideally I expect to debug and see function of the HPCDJ Console
Windows Edition approach that of the Mac edition, same device. It is
then a simple matter to have ALSA OSS provide the needed /dev/midiX
device.

Besides the USB ID, are the Mac and Windows editions of HPCDJ Console differing?

I'm eager to see this hardware work and have some fun. I'm not very
good at writing code. Help in answering my questions and offering
suggestions is most appreciated :)


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

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

On 10/4/05, Eric Shattow <lucent@gmail.com> wrote:
> On 10/4/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> > Eric Shattow wrote:
> > > On 10/4/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> > > > Eric Shattow wrote:
> > > > > It's not getting far enough to dump any packets.
> > > >
> > > > This means that no packets are sent by the device.
> > > >
> > > > It's possible that the controller data is reported by the HID
> > > > interfaces.  Did you test those?
> > >
> > > How would I make it so that usbhid module does not interfere?
> >
> > You wouldn't.  The 'proper' way would be to write a utility that reads
> > input events from the three HID interfaces and converts them to MIDI.
> > Otherwise, somebody would have to write a new driver for this device,
> > and change the usbhid driver accordingly.
> >
> >
> > Regards,
> > Clemens
> >
> >
>
> This HPCDJ Console is a USB MIDI device and from all indications I can
> see, should be made to function as such. The device has an MIDI IN
> port and an MIDI OUT port, as many USB-MIDI interfaces do. Event
> device (evdev) support is irrelevent to function in ALSA, no? If
> output from /dev/eventX for the HPCDJ would be helpful please let me
> know and I can make some captures.
>
> The Macintosh edition of HPCDJ Console works as an ALSA sound and midi
> device, and so I must question where you and fellow ALSA developers
> feel support for these DJ Console devices is most appropriate.
>
> Should the HPCDJ Console (Mac, and Windows editions) be supported in
> ALSA as sound devices only, ignoring the midi portion, or be supported
> in ALSA as sound and MIDI devices?
>
> Is it appropriate to continue supporting all midi and sound usb
> devices with a single kernel module?
>
> My target application is to use the HPCDJ Console with Mixxx software,
> and Mixxx is requiring an OSS-style /dev/midi device to read data
> from. Ideally I expect to debug and see function of the HPCDJ Console
> Windows Edition approach that of the Mac edition, same device. It is
> then a simple matter to have ALSA OSS provide the needed /dev/midiX
> device.
>
> Besides the USB ID, are the Mac and Windows editions of HPCDJ Console differing?
>
> I'm eager to see this hardware work and have some fun. I'm not very
> good at writing code. Help in answering my questions and offering
> suggestions is most appreciated :)
>

I have hacked up some Ruby code that reports most of the HPCDJ Console
control surfaces. No midi function yet, though. See attached files for
the curious.

 Eric

[-- Attachment #2: DJConsole-mod.rb --]
[-- Type: application/x-ruby, Size: 8382 bytes --]

[-- Attachment #3: Linux_evdev.rb --]
[-- Type: application/x-ruby, Size: 8439 bytes --]

[-- Attachment #4: PowerMate.rb --]
[-- Type: application/x-ruby, Size: 15065 bytes --]

[-- Attachment #5: mapping-hpcdj_win.txt --]
[-- Type: text/plain, Size: 893 bytes --]

[center]
	Fader:
	Xfade	0x28

[left side]

	Knobs:
	Treble	0x05
	Volume	0x2b
	Medium	0x04
	Bass	0x03
	
	Fader:
	Pitch	0x29

	Wheels:
	Jog		0x2d

	Buttons:
	Fx3		0x12c
	Fx2		0x12d
	Fx1		0x12e
	FxArrow	0x126
	Tempo	0x135
	AutoBeat	0x129
	Headphones	0x134
	PitchDec	0x133
	PitchInc	0x132
	TrackDec	0x12a
	TrackInc	0x12b
	Cue		0x128
	Play	0x127

	Led Indicators:
	Headphones	0x
	Fx		0x
	Cue		0x
	Loop	0x
	Tempo	0x

	Lighted Buttons:
	Cue		0x
	Play	0x
	AutoBeat	0x

[right side]
	
	Knobs:
	Treble	0x06
	Volume	0x2c
	Medium	0x01
	Bass	0x00

	Fader:
	Pitch	0x2a

	Wheels:
	Jog		0x2e

	Buttons:
	Fx3		0x131
	Fx2		0x130
	Fx1		0x12f
	FxArrow	0x120
	Tempo	0x139
	AutoBeat	0x123
	Headphones	0x138
	PitchDec	0x137
	PitchInc	0x136
	TrackDec	0x124
	TrackInc	0x125
	Cue		0x122
	Play	0x121

	Led Indicators:
	Headphones	0x
	Fx		0x
	Cue		0x
	Loop	0x
	Tempo	0x

	Lighted Buttons:
	Cue		0x
	Play	0x
	AutoBeat	0x

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

On 10/11/05, Eric Shattow <lucent@gmail.com> wrote:
> On 10/4/05, Eric Shattow <lucent@gmail.com> wrote:
> > On 10/4/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> > > Eric Shattow wrote:
> > > > On 10/4/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> > > > > Eric Shattow wrote:
> > > > > > It's not getting far enough to dump any packets.
> > > > >
> > > > > This means that no packets are sent by the device.
> > > > >
> > > > > It's possible that the controller data is reported by the HID
> > > > > interfaces.  Did you test those?
> > > >
> > > > How would I make it so that usbhid module does not interfere?
> > >
> > > You wouldn't.  The 'proper' way would be to write a utility that reads
> > > input events from the three HID interfaces and converts them to MIDI.
> > > Otherwise, somebody would have to write a new driver for this device,
> > > and change the usbhid driver accordingly.
> > >
> > >
> > > Regards,
> > > Clemens
> > >
> > >
> >
> > This HPCDJ Console is a USB MIDI device and from all indications I can
> > see, should be made to function as such. The device has an MIDI IN
> > port and an MIDI OUT port, as many USB-MIDI interfaces do. Event
> > device (evdev) support is irrelevent to function in ALSA, no? If
> > output from /dev/eventX for the HPCDJ would be helpful please let me
> > know and I can make some captures.
> >
> > The Macintosh edition of HPCDJ Console works as an ALSA sound and midi
> > device, and so I must question where you and fellow ALSA developers
> > feel support for these DJ Console devices is most appropriate.
> >
> > Should the HPCDJ Console (Mac, and Windows editions) be supported in
> > ALSA as sound devices only, ignoring the midi portion, or be supported
> > in ALSA as sound and MIDI devices?
> >
> > Is it appropriate to continue supporting all midi and sound usb
> > devices with a single kernel module?
> >
> > My target application is to use the HPCDJ Console with Mixxx software,
> > and Mixxx is requiring an OSS-style /dev/midi device to read data
> > from. Ideally I expect to debug and see function of the HPCDJ Console
> > Windows Edition approach that of the Mac edition, same device. It is
> > then a simple matter to have ALSA OSS provide the needed /dev/midiX
> > device.
> >
> > Besides the USB ID, are the Mac and Windows editions of HPCDJ Console differing?
> >
> > I'm eager to see this hardware work and have some fun. I'm not very
> > good at writing code. Help in answering my questions and offering
> > suggestions is most appreciated :)
> >
>
> I have hacked up some Ruby code that reports most of the HPCDJ Console
> control surfaces. No midi function yet, though. See attached files for
> the curious.
>
>  Eric
>
>
>

More news, I have cracked open the PC DJ Console (Windows edition) and
am looking at the ICs on the board...

DJ-CONSOLE REAR
020110-92
(c)2003

* Texas Instruments TUSB3200AC chip, with info from vendor site:
http://focus.ti.com/docs/prod/folders/print/tusb3200a.html
* AKM AK4529VQ, with data sheet from vendor site:
http://www.akm.com/datasheets/ek4529.pdf
* Fairchild Semiconductor 6N136 optocoupler, with data sheet from
vendor site: http://www.fairchildsemi.com/ds/6N/6N136.pdf
* Texas Instruments SN75179B, vendor datasheet:
http://www-s.ti.com/sc/ds/sn75179b.pdf
* Texas Instruments "SNxxF00" Quad 2-input positive-NAND gate
* Texas Instruments "SNxxHC04" Hex Inverter
* Texas Instruments "74HC/HCT14" Hex inverting Schmitt trigger
* Microchip 24LC64 (cmos serial EEPROM), datasheet:
http://www.kollar.com/observatory/dome/parts/24lc64.pdf
* Texas Instruments SN74ALVC126, vendor site info:
http://focus.ti.com/docs/prod/folders/print/sn74alvc126.html
* Cirrus Logic CS8427-CZ (96kHz Digital Audio Interface Transceiver),
vendor datasheet:
http://www.cirrus.com/en/pubs/proDatasheet/CS8427_F3.pdf

There's also three unknown chips labelled "33078 / 2203", physically
near the 6 output connectors.

I'll omit the other two boards, there's nothing too interesting on
them. Also I'd like to note that many screws were not securely
fastened, and some were in at an angle. Unksilled labor at time of
manufacture, perhaps?

 Eric


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

On 10/17/05, Eric Shattow <lucent@gmail.com> wrote:
> On 10/11/05, Eric Shattow <lucent@gmail.com> wrote:
> > On 10/4/05, Eric Shattow <lucent@gmail.com> wrote:
> > > On 10/4/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> > > > Eric Shattow wrote:
> > > > > On 10/4/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> > > > > > Eric Shattow wrote:
> > > > > > > It's not getting far enough to dump any packets.
> > > > > >
> > > > > > This means that no packets are sent by the device.
> > > > > >
> > > > > > It's possible that the controller data is reported by the HID
> > > > > > interfaces.  Did you test those?
> > > > >
> > > > > How would I make it so that usbhid module does not interfere?
> > > >
> > > > You wouldn't.  The 'proper' way would be to write a utility that reads
> > > > input events from the three HID interfaces and converts them to MIDI.
> > > > Otherwise, somebody would have to write a new driver for this device,
> > > > and change the usbhid driver accordingly.
> > > >
> > > >
> > > > Regards,
> > > > Clemens
> > > >
> > > >
> > >
> > > This HPCDJ Console is a USB MIDI device and from all indications I can
> > > see, should be made to function as such. The device has an MIDI IN
> > > port and an MIDI OUT port, as many USB-MIDI interfaces do. Event
> > > device (evdev) support is irrelevent to function in ALSA, no? If
> > > output from /dev/eventX for the HPCDJ would be helpful please let me
> > > know and I can make some captures.
> > >
> > > The Macintosh edition of HPCDJ Console works as an ALSA sound and midi
> > > device, and so I must question where you and fellow ALSA developers
> > > feel support for these DJ Console devices is most appropriate.
> > >
> > > Should the HPCDJ Console (Mac, and Windows editions) be supported in
> > > ALSA as sound devices only, ignoring the midi portion, or be supported
> > > in ALSA as sound and MIDI devices?
> > >
> > > Is it appropriate to continue supporting all midi and sound usb
> > > devices with a single kernel module?
> > >
> > > My target application is to use the HPCDJ Console with Mixxx software,
> > > and Mixxx is requiring an OSS-style /dev/midi device to read data
> > > from. Ideally I expect to debug and see function of the HPCDJ Console
> > > Windows Edition approach that of the Mac edition, same device. It is
> > > then a simple matter to have ALSA OSS provide the needed /dev/midiX
> > > device.
> > >
> > > Besides the USB ID, are the Mac and Windows editions of HPCDJ Console differing?
> > >
> > > I'm eager to see this hardware work and have some fun. I'm not very
> > > good at writing code. Help in answering my questions and offering
> > > suggestions is most appreciated :)
> > >
> >
> > I have hacked up some Ruby code that reports most of the HPCDJ Console
> > control surfaces. No midi function yet, though. See attached files for
> > the curious.
> >
> >  Eric
> >
> >
> >
>
> More news, I have cracked open the PC DJ Console (Windows edition) and
> am looking at the ICs on the board...
>
> DJ-CONSOLE REAR
> 020110-92
> (c)2003
>
> * Texas Instruments TUSB3200AC chip, with info from vendor site:
> http://focus.ti.com/docs/prod/folders/print/tusb3200a.html
> * AKM AK4529VQ, with data sheet from vendor site:
> http://www.akm.com/datasheets/ek4529.pdf
> * Fairchild Semiconductor 6N136 optocoupler, with data sheet from
> vendor site: http://www.fairchildsemi.com/ds/6N/6N136.pdf
> * Texas Instruments SN75179B, vendor datasheet:
> http://www-s.ti.com/sc/ds/sn75179b.pdf
> * Texas Instruments "SNxxF00" Quad 2-input positive-NAND gate
> * Texas Instruments "SNxxHC04" Hex Inverter
> * Texas Instruments "74HC/HCT14" Hex inverting Schmitt trigger
> * Microchip 24LC64 (cmos serial EEPROM), datasheet:
> http://www.kollar.com/observatory/dome/parts/24lc64.pdf
> * Texas Instruments SN74ALVC126, vendor site info:
> http://focus.ti.com/docs/prod/folders/print/sn74alvc126.html
> * Cirrus Logic CS8427-CZ (96kHz Digital Audio Interface Transceiver),
> vendor datasheet:
> http://www.cirrus.com/en/pubs/proDatasheet/CS8427_F3.pdf
>
> There's also three unknown chips labelled "33078 / 2203", physically
> near the 6 output connectors.
>
> I'll omit the other two boards, there's nothing too interesting on
> them. Also I'd like to note that many screws were not securely
> fastened, and some were in at an angle. Unksilled labor at time of
> manufacture, perhaps?
>
>  Eric
>

I have been able to make capture logs of the USB transactions as the
device is plugged in and initialized by the Hercules Windows (tm)
driver.  Would anyone be interested?

 Eric


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Clemens Ladisch]

Eric Shattow wrote:
> I have been able to make capture logs of the USB transactions as the
> device is plugged in and initialized by the Hercules Windows (tm)
> driver.  Would anyone be interested?

Yes.  Are there any vendor-specific commands, i.e., is there anything
that snd-usb-audio wouldn't be able to do?


Regards,
Clemens



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

On 10/18/05, Clemens Ladisch <clemens@ladisch.de> wrote:
> Eric Shattow wrote:
> > I have been able to make capture logs of the USB transactions as the
> > device is plugged in and initialized by the Hercules Windows (tm)
> > driver.  Would anyone be interested?
>
> Yes.  Are there any vendor-specific commands, i.e., is there anything
> that snd-usb-audio wouldn't be able to do?
>
>
> Regards,
> Clemens
>
>

I believe there are vendor specific commands, to handle the "push to
talk" potentiometer with built in momentary push switch. My basis for
this is I enabled the feature using Hercules software mixer control
program, and there is output in the capture program log. Then I push
the aforementioned button on the HPCDJ Console hardware, and there is
(what must be) a vendor specific command in the event viewer.

Some functions which I think may apply:  selecting which output the
headphone preamp is routed from, 44.1k / 48k function, MIDI button or
MIDI port (pick one), LED lamps and lights (not currently working for
me)

There may be other functions.  I have capture logs which are formatted
in HTML/Unicode/ASCII and quite large (about 30mb uncompressed). I
tried to keep the logs small, however they invariably contained data
of that annoyingly zen-like calming sound which Windows XP plays when
you plug in a new USB device. I activated and de-activated Hercules
software mixer features on the device. Omitted from the capture logs
are the device being used with user deejay software, as this resulted
in the device outputting many megabytes of ISO asynchronous data.

For a short while I will make these "giveitago.*" captures available,
at the following directory URL:

http://www.cuodan.net/~jnc/djconsolehacker/

I would like to note that the Macintosh edition of the DJ Console is
"hardwired" to be in MIDI button mode. The Windows edition (producing
"giveitago.*" output) is runtime selectable between a DirectInput+MIDI
USB device and a MIDI Button+Disabled MIDI USB i/o device. There are
reported hardware improvements in the sound chips of the Macintosh
edition versus the Windows edition.

Also of note is that upon using my DJ Console (windows edition)
hardware on a Windows XP system and Hercules drivers, the Hercules
software prompted a firmware upgrade. I allowed it, and the device
does not seem to behave any differently when used with ALSA sound
drivers. I am unsure which firmware was previously on the device. Also
unfortunate is I did not chance a capture of the firmware upgrade
process. Oh, well. The list of parts I gave should be enough to write
a firmware flasher, right?

Some of this may not apply to the scope of ALSA. Sorry about the
overlap, I know we have access to the DirectSound / DirectInput
specifications but it is covered by an NDA. I suck at coding. Anyone
else feel lucky?

 E

P.S. Apologies to Clemens for the duplicate mail. Gmail interface is
kind of clumsy for me.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Lee Revell]

On Wed, 2005-10-19 at 01:03 -0500, Eric Shattow wrote:
> I would like to note that the Macintosh edition of the DJ Console is
> "hardwired" to be in MIDI button mode. The Windows edition (producing
> "giveitago.*" output) is runtime selectable between a DirectInput+MIDI
> USB device and a MIDI Button+Disabled MIDI USB i/o device. There are
> reported hardware improvements in the sound chips of the Macintosh
> edition versus the Windows edition. 

They make a DIFFERENT DEVICE with a DIFFERENT CHIPSET for Mac and
Windows?!?  WTF?

Lee



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

On 10/19/05, Lee Revell <rlrevell@joe-job.com> wrote:
>
> They make a DIFFERENT DEVICE with a DIFFERENT CHIPSET for Mac and
> Windows?!?  WTF?
>
> Lee
>

Alexander Schussler owns both the Windows and Mac editions of the DJ
Console hardware. According to his correspondence with
Hercules/Guillemot representatives, the hardware is identical except
for improved audio function on the Mac edition. My guess is that the
Windows edition is first revision, and Mac edition is second revision.
The firmware is of course completely different between the two
editions.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Lee Revell]

On Wed, 2005-10-19 at 16:10 -0500, Eric Shattow wrote:
> On 10/19/05, Lee Revell <rlrevell@joe-job.com> wrote:
> >
> > They make a DIFFERENT DEVICE with a DIFFERENT CHIPSET for Mac and
> > Windows?!?  WTF?
> >
> > Lee
> >
> 
> Alexander Schussler owns both the Windows and Mac editions of the DJ
> Console hardware. According to his correspondence with
> Hercules/Guillemot representatives, the hardware is identical except
> for improved audio function on the Mac edition. My guess is that the
> Windows edition is first revision, and Mac edition is second revision.
> The firmware is of course completely different between the two
> editions.
> 

Christ, that's the stupidest thing I've heard this week.

I remember when software was designed around the hardware.  Now people
are working around Windows bugs in hardware.  Depressing.

Lee



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

On 10/19/05, Eric Shattow <lucent@gmail.com> wrote:
> On 10/19/05, Lee Revell <rlrevell@joe-job.com> wrote:
> >
> > They make a DIFFERENT DEVICE with a DIFFERENT CHIPSET for Mac and
> > Windows?!?  WTF?
> >
> > Lee
> >
>
> Alexander Schussler owns both the Windows and Mac editions of the DJ
> Console hardware. According to his correspondence with
> Hercules/Guillemot representatives, the hardware is identical except
> for improved audio function on the Mac edition. My guess is that the
> Windows edition is first revision, and Mac edition is second revision.
> The firmware is of course completely different between the two
> editions.
>

Anyways, update for everyone.  The ALSA 1.0.10 release doesn't appear
to work with Hercules PC DJ Console (Windows Edition) device. I have
not been able to make it output or record sound.

jnc@baker:~$ arecord -D hw:3 -f S16_LE -c 2 -r 48000 /tmp/test.wav
Recording WAVE '/tmp/test.wav' : Signed 16 bit Little Endian, Rate
48000 Hz, Stereo
arecord: xrun:1077: read/write error, state = PREPARED

Something like that.  Suggestions, anyone?

 Eric


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click

Re: Hercules PC DJ Console (Windows Edition) information

[Lee Revell]

On Wed, 2006-01-11 at 01:30 -0600, Eric Shattow wrote:
> On 10/19/05, Eric Shattow <lucent@gmail.com> wrote:
> > On 10/19/05, Lee Revell <rlrevell@joe-job.com> wrote:
> > >
> > > They make a DIFFERENT DEVICE with a DIFFERENT CHIPSET for Mac and
> > > Windows?!?  WTF?
> > >
> > > Lee
> > >
> >
> > Alexander Schussler owns both the Windows and Mac editions of the DJ
> > Console hardware. According to his correspondence with
> > Hercules/Guillemot representatives, the hardware is identical except
> > for improved audio function on the Mac edition. My guess is that the
> > Windows edition is first revision, and Mac edition is second revision.
> > The firmware is of course completely different between the two
> > editions.
> >
> 
> Anyways, update for everyone.  The ALSA 1.0.10 release doesn't appear
> to work with Hercules PC DJ Console (Windows Edition) device. I have
> not been able to make it output or record sound.
> 
> jnc@baker:~$ arecord -D hw:3 -f S16_LE -c 2 -r 48000 /tmp/test.wav
> Recording WAVE '/tmp/test.wav' : Signed 16 bit Little Endian, Rate
> 48000 Hz, Stereo
> arecord: xrun:1077: read/write error, state = PREPARED
> 
> Something like that.  Suggestions, anyone?

Assuming this worked with previous versions, the problem may be that USB
audio has been broken since kernel 2.6.14 (ALSA 1.0.10rcsomething).

Try the patch attached to this bug report.

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1585

Lee



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Re: Hercules PC DJ Console (Windows Edition) information

[Clemens Ladisch]

Lee Revell wrote:
> On Wed, 2006-01-11 at 01:30 -0600, Eric Shattow wrote:
> > arecord: xrun:1077: read/write error, state = PREPARED

There may be a message in the system log.

> Assuming this worked with previous versions, the problem may be that USB
> audio has been broken since kernel 2.6.14 (ALSA 1.0.10rcsomething).
>
> Try the patch attached to this bug report.
>
> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1585

Now fixed in CVS.

I've added another patch to the above bug report, or wait for the next ALSA
release.


HTH
Clemens


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

On 1/12/06, Clemens Ladisch <clemens@ladisch.de> wrote:
> Lee Revell wrote:
> > On Wed, 2006-01-11 at 01:30 -0600, Eric Shattow wrote:
> > > arecord: xrun:1077: read/write error, state = PREPARED
>
> There may be a message in the system log.
>
> > Assuming this worked with previous versions, the problem may be that USB
> > audio has been broken since kernel 2.6.14 (ALSA 1.0.10rcsomething).
> >
> > Try the patch attached to this bug report.
> >
> > https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1585
>
> Now fixed in CVS.
>
> I've added another patch to the above bug report, or wait for the next ALSA
> release.
>
>
> HTH
> Clemens
>

I applied the patch, and behavior is still broken for my device.

dmesg shows the following output after plugging in the HPCDJ Console:
+usb 3-1.6: new full speed USB device using ehci_hcd and address 5
+snd-usb-audio: probe of 3-1.6:1.0 failed with error -5
+input: Hercules Hercules DJ Console as /class/input/input4
+input: USB HID v1.10 Joystick [Hercules Hercules DJ Console] on
usb-0000:00:02.2-1.6
+input: Hercules Hercules DJ Console as /class/input/input5
+input: USB HID v1.10 Mouse [Hercules Hercules DJ Console] on
usb-0000:00:02.2-1.6
+input: Hercules Hercules DJ Console as /class/input/input6
+input: USB HID v1.10 Keyboard [Hercules Hercules DJ Console] on
usb-0000:00:02.2-1.6
+snd-usb-audio: probe of 3-1.6:1.5 failed with error -5
+usbcore: registered new driver yealink
+drivers/usb/input/yealink.c: Yealink phone driver:yld-20050816

...and trying to play a sound with alsaplayer to the device:

+ALSA /usr/src/modules/alsa-driver/usb/usbaudio.c:835: cannot submit
datapipe for urb 0, err = -38
+ALSA /usr/src/modules/alsa-driver/usb/usbaudio.c:835: cannot submit
datapipe for urb 0, err = -38
+ALSA /usr/src/modules/alsa-driver/usb/usbaudio.c:835: cannot submit
datapipe for urb 0, err = -38
+ALSA /usr/src/modules/alsa-driver/usb/usbaudio.c:835: cannot submit
datapipe for urb 0, err = -38

help?

 Eric


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642

Re: Hercules PC DJ Console (Windows Edition) information

[Clemens Ladisch]

Eric Shattow wrote:
> +usb 3-1.6: new full speed USB device using ehci_hcd and address 5
> +ALSA /usr/src/modules/alsa-driver/usb/usbaudio.c:835: cannot submit
> datapipe for urb 0, err = -38

Enable EHCI full speed support in the kernel configuration, or connect it
to the computer without using a USB 2.0 hub.


HTH
Clemens


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

Re: Hercules PC DJ Console (Windows Edition) information

[Eric Shattow]

On 1/17/06, Clemens Ladisch <clemens@ladisch.de> wrote:
> Eric Shattow wrote:
> > +usb 3-1.6: new full speed USB device using ehci_hcd and address 5
> > +ALSA /usr/src/modules/alsa-driver/usb/usbaudio.c:835: cannot submit
> > datapipe for urb 0, err = -38
>
> Enable EHCI full speed support in the kernel configuration, or connect it
> to the computer without using a USB 2.0 hub.
>
>
> HTH
> Clemens
>
>

>From my kernel .config for 2.6.15:

...
#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_EHCI_SPLIT_ISO is not set
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_ISP116X_HCD=m
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_SL811_HCD=m
CONFIG_USB_SL811_CS=m
...

Which option are you referring to?

 Eric


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642