Frank wrote:

> So could you try something like "aplay -D default some.wav" and then

Ah, thanks very much Frank; that worked, even without the '-D default':

        dione$ aplay -l
        card 0: ENSONIQ [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC]
          Subdevices: 0/1
          Subdevice #0: subdevice #0
        card 0: ENSONIQ [Ensoniq AudioPCI], device 1: ES1371/2 [ES1371 DAC1]
          Subdevices: 1/1
          Subdevice #0: subdevice #0
        dione$ 
        
        dione$ arecord -l
        card 0: ENSONIQ [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC]
          Subdevices: 1/1
          Subdevice #0: subdevice #0
        dione$ 
        
        dione$ aplay /pub/multimedia/audio/radio/ragtime/dicky.au       <--- produces 
sound :-)
        dione$ 

So, now that I trust alsa really is working, I went back to trying to
timidity.

Bill wrote:

> You'll need TiMidity++-2.12.0-pre1 built with alsa server enabled for
> this to work.

Ok, Debian only has 2.10 available, so I tried that first:

        dione$ timidity -iA -B2,8 -Os -EFreverb=0
        /dev/snd/pcm00: Sound protocol is not compatible
        Couldn't open ALSA pcm device (`s')

Frank wrote:

> Your /proc/asound/dev file looks ok. I don't have pcmC0D0 neither, 
> that's fine.

Ok, so I guess the above error is because of using 2.10 instead of 2.12?
After a bit og fiddling with 'configure' options:

        dione$ ./configure --enable-alsaseq --enable-audio=alsa 
--prefix=/usr/server/opt/timidity LDFLAGS=-lasound
        dione$ make
        dione# make install

Then I symlinked the installed 2.10 config file and GUS patches to where
the new 2.12 could find them.

I then tried just:

        dione:~# /usr/server/opt/timidity/bin/timidity -B2,8 -Os -EFreverb=0 
<midi-file>

and that produced sound!

Bill wrote:

> timidity -iA -B2,8 -Os -EFreverb=0&

Ok, *before* I do that, I'll do the 'aconnect -lo' and '-li' so I see
the 'before' and 'after' results:

        dione:~# aconnect -li
        client 0: 'System' [type=kernel]
            0 'Timer           '
            1 'Announce        '
        client 64: 'External MIDI 0' [type=kernel]
            0 'MIDI 0-0        '                                <-- so this is the 
MIDI keyboard port, right?
        dione:~# 
        
        dione:~# aconnect -lo
        client 64: 'External MIDI 0' [type=kernel]
            0 'MIDI 0-0        '                                <-- will see timidity 
here in a moment?
        dione:~# 

> If you use aconnect type aconnect -li to see the available inputs. The
> External MIDI port will be something like 64:0. aconnect -lo will show you
> the output ports and your timidity ports should be 128:0 and 129:0. 

Ok, here goes :-) ....

        dione:~# /usr/server/opt/timidity/bin/timidity  -iA -B2,8 -Os -EFreverb=0
        Requested buffer size 2048, fragment size 1024
        ALSA pcm 'default' set buffer size 2048, period size 1024 bytes
        TiMidity starting in ALSA server mode
        set SCHED_FIFO
        Opening sequencer port: 128:0 128:1

And now the 'aconnect -lo' again:

        dione$ aconnect -lo
        client 64: 'External MIDI 0' [type=kernel]
            0 'MIDI 0-0        '
        client 128: 'Client-128' [type=user]
            0 'TiMidity port 0 '                                <-- yeah!!!
            1 'TiMidity port 1 '                                <-- yeah!!!
        dione$ 

Yeah! So, ok, now ...

> To connect them use aconnect 64:0 128:0.

        dione:~# aconnect 64:0 128:0
        Requested buffer size 2048, fragment size 1024
        ALSA pcm 'default' set buffer size 2048, period size 1024 bytes
        dione:~#

According to the 'aconnect' man page, it should be possible to list
the active connections (now I have one right?) using 'aconnect -l',
but this was a usage error :-( Anyway ...

So, shouldn't keypresses produce piano now? They don't.

I tried Muse, and got this:

        dione$ muse
        load plugin dir </usr/lib/muse/plugins>
        searching for software synthesizer in </usr/lib/muse/synthi>
        5 soft synth found
        found soft synth <Stk> <stk soft synth>
        found soft synth <iiwu> <iiwu soft synth>
        found soft synth <vam> <vam soft synth>
        found soft synth <organ> <Organ>
        found soft synth <S1> <S1 demo soft synth>
        NO Config File </home/alexis/.MusE>
        ALSA lib pcm_hw.c:597:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p failed: Device 
or resource busy

By using 'fuser', I see that /dev/snd/pcmC0D0p is busy because of the
timidity server running. Ok, well, perhaps that is right?

Ok, well, Muse looks pretty much like Cubase, but I still couldn't
configure it to get any sound :-) Is there anyway that - like 
Cubase I can press a key and see a s/w LED blink, so I know that
keypresses are being received? I'll search for a "How to get sound
when you press a key with Muse with the smallest amount of work",
but can anybody offer any pointers?

And one final thing, I take it that people here are pretty familiar
with Muse and Cubase: is there any way to convert '.ALL' files into
something Muse/Rosegarden/something-else can play?

Many thanks for your valuable assistance!

Regards

Alexis Huxley

_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to