> > I've got a MIDI keyboard and an SB PCI64 that I really miss using
> > now I've ditched MS from my disk. I'd like to keep MS off my disk,
> > but after several *months* of frustrating and searching the web and
> > posting to NGs I still don't have it working. So here I am, with
> > rather a long post; hopefully it has all the info some kind souls out
> > there need to assist me ...
> 
> Alexis, you shouldn't need virmidi to do this. All you need to do is run 
> timidity in alsa sequencer server mode, then connect your midi in port to 
> the timidity port. You can use aconnect to do this, but I've found that 
> Bob Ham's alsa-patch-bay makes this much easier for me.
> 
> You need to run timidity in server mode, I use:
>  
> timidity -iA -B2,8 -Os -EFreverb=0&

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

Ok, I checked for /dev/snd/pcm00 and it does not exist! /dev/snd does
not exist. Ok, so something must have gone wrong during OS installation
I guess.

I ran snddevices from the lastest ALSA from their web page, and it
created /dev/snd -> /proc/asound/dev, but /proc/asound/dev/pcm00
doesn't exist either:

        dione:/dev# ls -l /proc/asound/dev
        total 0
        crw-rw----    1 root     audio    116,   0 Jun 14 16:50 controlC0
        crw-rw----    1 root     audio    116,   8 Jun 14 16:50 midiC0D0
        crw-rw----    1 root     audio    116,  24 Jun 14 16:50 pcmC0D0c
        crw-rw----    1 root     audio    116,  16 Jun 14 16:50 pcmC0D0p
        crw-rw----    1 root     audio    116,  17 Jun 14 16:50 pcmC0D1p
        crw-rw----    1 root     audio    116,   1 Jun 14 16:50 seq
        crw-rw----    1 root     audio    116,  33 Jun 14 16:50 timer

(I also tried searching www.debian.org to determine which packages
'snddevices' and /dev/snd belong to, but they say none, which is
maybe which they were missing from my installation.)

I tried now running Timidity without '-Os'; presumably it'll route
audio to the OSS devices, but the source MIDI events will still come
via ALSA?  That produced the following:

        dione:/dev# timidity -iA -B2,8 -EFreverb=0 
        TiMidity starting in ALSA server mode
        set SCHED_FIFO
        error in snd_seq_create_simple_port
        Opening sequencer port:                  <-- [sic]

> Then launch alsa-patch-bay. You'll see on the left External MIDI 0::MIDI 
> You'll need TiMidity++-2.12.0-pre1 built with alsa server enabled for this 
> to work.

Ok, I'll give that a go - mine is 2.10. But can you confirm that the
differences between 2.10 and 2.12 would cause the error above? It'd
be nice to upgrade and not get the same error :-)

> 0-0. On the right side you should see 2 timidity ports. Connect the 
> External MIDI port on the left to one of the timidity ports. You should 
> then be able to play piano.

If 'aconnect' should work, then I'll try that first, since it's
already on the machine, whereas alsa-patch-bay isn't.

> If you use aconnect type aconnect -li to see the available inputs. The
> External MIDI port will be something like 64:0. 

Ok, that looks good:

        dione:~# aconnect -li
        client 0: 'System' [type=kernel]
            0 'Timer           '
            1 'Announce        '
                Connecting To: 63:0
        client 64: 'External MIDI 0' [type=kernel]
            0 'MIDI 0-0        '

> aconnect -lo will show you
> the output ports and your timidity ports should be 128:0 and 129:0. To
> connect them use aconnect 64:0 128:0.

Ok, as explained above Timidity crashes immediately; so those are
not listed:

        dione:~# aconnect -lo
        client 64: 'External MIDI 0' [type=kernel]
            0 'MIDI 0-0        '

> To change programs, I have a utility that Frank Barknecht wrote, but it 
> requires PD to be installed. Or, you can install muse and change programs 
> through it (as well as have a nice midi sequencer).

I think I don't understand what you mean by 'program' in this context
:-)

>>         dione$ alsaplayer 
>>         snd_pcm_open: No such file or directory (default)
>>         /usr/lib/alsaplayer/output/libalsa.so failed to load
>>         I could not find a suitable output module on your
>>                system. Make sure they're in "/usr/lib/alsaplayer/output/".
>>                Use the -o parameter to select one.
>>         failed to load output add-on. exitting...
>>         dione$ 

Going back to alsaplayer again: having created the /dev/snd symlink
with snddevices, alsaplayer now does something a bit different:

        dione$ alsaplayer 
        ...done playing
        dione$ 

and with a real file as parameter the same:

        dione$ alsaplayer /pub/multimedia/audio/radio/ragtime/zuza.au 
        ...done playing
        dione$ 

But still no sound; volume *is* turned up (xmms works). If I tell
alsaplayer to use a specific device under /proc/asound then I'm back
to a variation on the old error:

        dione$ alsaplayer -d /proc/asound/dev/pcmC0D0p
        /pub/multimedia/audio/radio/ragtime/zuza.au 
        ALSA lib pcm.c:1599:(snd_pcm_open_noupdate) Unknown PCM
        /proc/asound/dev/pcmC0D0p
        snd_pcm_open: No such file or directory (/proc/asound/dev/pcmC0D0p)
        /usr/lib/alsaplayer/output/libalsa.so failed to load
        I could not find a suitable output module on your
               system. Make sure they're in "/usr/lib/alsaplayer/output/".
               Use the -o parameter to select one.
        failed to load output add-on. exitting...
        dione$ 
        
And the same if I use the 'p' pcm device instead of the 'c' one.

Any more ideas? Thanks for the advice so far; some progress!

Alexis

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - 
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink

_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to