Multimedia :: Sequencer



plop your icon image into /home/dsl/.xtdesktop and then start up the icon tool (desktop menu: Desktop->Icontool).
Click the "add" button
Select your icon file
Fill in the blanks ("full path" is the path to the muse executable)
Click "ok"
Thanks Mikshaw....

Well after much ado I've got Muse installed and running and Fluidsynth. I've looked in the Muse properties and it's playing through Alsa. However it is not playing through my USB midi! I've a Soundblaster and it's sending the midi through that. When I try to select a different midi interface ( ie my Edirol UM-1EX) it's not an option.  But Muse is definitely using Alsa.
Does anyone know how to tell Alsa how to get it to start taking input/output from my Edirol UM-1EX? I've a feeling I got in a muddle last time and assumed the Edirol was ok in Alsa but maybe it's not.....

Here's what fluidsynth looks like running in alsa, and below I did a modprobe snd-usb-audio and lsmod as you might see what's wrong - thanks again all!
BTW everyone I am using DSL 3.3 now - I was just in for more headaches using 2.4 and everything seems to be working in 3.3
Here's what my lsmod


fluidsynth: warning: The sample rate is set to 44100, the synthesizer may be out of tune
fluidsynth: warning: Requested a period size of 64, got 65 instead
fluidsynth: ALSA driver: Using format s16, rw, interleaved

fluidsynth version 1.0.5
Copyright © 2000-2002 Peter Hanappe and others.
FLUID Synth comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; see the COPYING file for details.
SoundFont® is a registered trademark of E-mu Systems, Inc.

[/home/dsl]# modprobe snd-usb-audio
[/home/dsl]# lsmod
Module                  Size  Used by    Not tainted
snd-usb-audio          38720   0
snd-seq-midi            3296   0  (autoclean)
snd-seq-midi-event      3184   0  (autoclean) [snd-seq-midi]
snd-seq                39536   0  (autoclean) [snd-seq-midi snd-seq-midi-event]
mousedev                3832   0  (unused)
hid                    22372   0  (unused)
input                   3168   0  [mousedev hid]
snd-mixer-oss          11280   0  (autoclean)
snd-ens1371            11456   0  (autoclean)
gameport                1388   0  (autoclean) [snd-ens1371]
snd-pcm                57504   0  (autoclean) [snd-usb-audio snd-ens1371]
snd-timer              15044   0  (autoclean) [snd-seq snd-pcm]
snd-page-alloc          5584   0  (autoclean) [snd-pcm]
snd-rawmidi            12512   0  (autoclean) [snd-usb-audio snd-seq-midi snd-en                                                                                     s1371]
snd-seq-device          3716   0  (autoclean) [snd-seq-midi snd-seq snd-rawmidi]
snd-ac97-codec         40012   0  (autoclean) [snd-ens1371]
snd                    29988   0  (autoclean) [snd-usb-audio snd-seq-midi snd-se                                                                                     q-midi-event snd-seq snd-mixer-oss snd-ens1371 snd-pcm snd-timer snd-rawmidi snd                                                                                     -seq-device snd-ac97-codec]
unionfs                68800   7
af_packet              13544   0  (autoclean)
nls_cp437               4348   0  (autoclean)
ext3                   64452   0  (autoclean)
jbd                    46516   0  (autoclean) [ext3]
nls_iso8859-1           2844   1  (autoclean)
ntfs                   50944   0  (autoclean)
msdos                   4684   0  (autoclean)
agpgart                42660   0  (unused)
8139too                13736   1
mii                     2240   0  [8139too]
crc32                   2816   0  [8139too]
cfi_cmdset_0001        24760   1  (autoclean)
jedec_probe             9072   0  (autoclean)
gen_probe               1792   0  (autoclean) [jedec_probe]
ich2rom                 1876   0  (unused)
mtdcore                 2404   1  [ich2rom]
chipreg                  860   0  [jedec_probe ich2rom]
hw_random               2700   0  (unused)
serial                 52100   0  (autoclean)
usb-midi               16700   0  (unused)
soundcore               3428   3  [snd usb-midi]
pcmcia_core            39840   0
thermal                 6564   0  (unused)
processor               8976   0  [thermal]
fan                     1568   0  (unused)
button                  2508   0  (unused)
battery                 5888   0  (unused)
ac                      1824   0  (unused)
rtc                     7036   0  (autoclean)
cloop                  39204   2
ieee1394              183076   0
usb-storage            61696   0
usb-uhci               21644   0  (unused)
ehci-hcd               16392   0  (unused)
usbcore                57600   1  [snd-usb-audio hid usb-midi usb-storage usb-uh                                                                                     ci ehci-hcd]
ataraid                 6180   0
ide-cd                 28512   0
ide-scsi                8816   1
[/home/dsl]#
My guess would be that alsa has correctly identified both your soundblaster card and your midi device but you need to tell it which one to use.

I am not in front of a DSL machine at the moment but I seem to remember that if you look somewhere like /proc/asound/cards, you will see which devices alsa has identified. Once you see what alsa has called your devices, you can use that to identify them or you can try something like "aplay hw:0,0 filename" or "aplay hw:1,0 filename" to figure out which is which and enter that as the inerface for fluidsynth to use.
Thanks for your quick response Juanito. When I look at /proc/asound I have a number of entries:

Audio PCI/
UM1/ 5 bytes
card0/ 5 bytes
card1/ (0 bytes) - all the rest are 0 bytes
oss/
seq/
cards
devices
modules
pcm
timers
version

how can I tell which is hw:0 or hw:1?
In emelFM, highlight the items (eg cards) and then choose "view" from the right-click menu or enter (for example) "cat /proc/asound/cards" from a terminal window.
Next Page...
original here.