Menu

2 alsa devices

Help
2008-02-22
2013-06-13
  • Luc Tanguay

    Luc Tanguay - 2008-02-22

    Hi.
    First thanks for the driver. I've downloaded line6usb 0.7.3. Compiled and installed like a charm. I'm running Fedora 8 with PlanetCCCRMA kernel (2.6.23.12-1.rt14.2.fc8.ccrmart).

    Just bought a PODxt Live. I would like to control it from a MIDI sequencer.  With the line6usb module loaded, I plugged the PODxt in the USB port and then I see 2 ALSA devices (output from aconnect -i):
    client 0: 'System' [type=kernel]
        0 'Timer           '
        1 'Announce        '
    client 14: 'Midi Through' [type=kernel]
        0 'Midi Through Port-0'
    client 20: 'USB Oxygen 49' [type=kernel]
        0 'USB Oxygen 49 MIDI 1'
    client 24: 'Line6-USB' [type=kernel]
        0 'PODxt Live      '
    client 28: 'Line6-USB' [type=kernel]
        0 'PODxt Live      '

    The 24:0 seems to be the real MIDI device. I do "aseqdump -p 24:0" then I press a button on the POD and the MIDI messages are dumped on the screen.  With "aseqdump -p 28:0", nothing.

    My question is: why there is 2 ALSA devices?  Is it because I have 2 audio cards (but one is broken so no snd module is loaded for this one)?

    This may help:
    [root]# lsmod |grep line
    line6usb               68388  3
    snd_pcm                63620  7 line6usb,snd_usb_audio,snd_ice1712,snd_ac97_codec,snd_pcm_oss
    snd_rawmidi            21120  4 line6usb,snd_seq_midi,snd_usb_lib,snd_mpu401_uart
    snd                    44036  26 line6usb,snd_usb_audio,snd_hwdep,snd_ice1712,snd_ak4xxx_adda,snd_cs8427,snd_ac97_codec,snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_i2c,snd_mpu401_uart,snd_rawmidi,snd_seq_device

    Thanks
    lucus

     
    • Luc Tanguay

      Luc Tanguay - 2008-02-22

      Sorry for the long lines.
      Didn't know it was not wrapped automatically.
      lucus

       
    • Markus Grabner

      Markus Grabner - 2008-02-22

      The PODxt Live has two separate interfaces:
      *) the POD interface (i.e., amp modeler),
      *) the Variax interface (i.e., a built-in Variax workbench)
      Both show up with "aconnect -i". It would indeed be nice if this distinction would be clear from the output of this command. I will consider this for a future version.

      Kind regards,
      Markus

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.