25 Jan
2005
25 Jan
'05
6:42 p.m.
Just wondering if anyone has gotten solfege to work with either external
midi ports, virmidi, or a soft synth using alsa and not oss. I have been
struggling with getting it to play to my midi port or to virmidi, and
have no clue how to select the device properly. There is little
explanation as to what the options in the set up area mean. I'm on gentoo.
Thanks
iain
26 Jan
26 Jan
1:05 p.m.
Iain Duncan wrote:
Just wondering if anyone has gotten solfege to work
with either
external midi ports, virmidi, or a soft synth using alsa and not oss.
I have been struggling with getting it to play to my midi port or to
virmidi, and have no clue how to select the device properly. There is
little explanation as to what the options in the set up area mean. I'm
on gentoo.
Hi Iain:
I just took a look at the audio preferences for 2.0.2, there's no
provision for anything ALSA. :(
The other options offered were /dev/sequencer, /dev/sequencer2,
/dev/music, and none. Selecting /dev/sequencer2 and /dev/music gave me
error messages, /dev/sequencer was selected without error but I got no
sound from the test. No MIDI activity appeared on my patchbay.
The Solfege Web site includes instructions for wedding timidity to
/dev/music. Didn't work for me though, I still received the error for
/dev/music.
Best,
dp
1:23 p.m.
On Wed, 26 Jan 2005 12:18:14 -0500
Dave Phillips <dlphilp(a)bright.net> wrote:
I just took a look at the audio preferences for
2.0.2, there's no
provision for anything ALSA. :(
The other options offered were /dev/sequencer, /dev/sequencer2,
/dev/music, and none. Selecting /dev/sequencer2 and /dev/music gave me
error messages, /dev/sequencer was selected without error but I got no
sound from the test. No MIDI activity appeared on my patchbay.
The Solfege Web site includes instructions for wedding timidity to
/dev/music. Didn't work for me though, I still received the error for
/dev/music.
Hi,
easy workaround:
Check "use external midiplayer" and enter:
aplaymidi -p 129:0 %s
Change the 129:0 to the corresponding port, of course [i use fluidsynth
and it happens to open port 129:0 if it's the only midi app on my system
:)] I suppose it would be possible to automate this: If you know you
always use fluidsynth, it is possible to replace aplaymidi with a script
that parses the output of
aconnect -io | grep -i fluid
and calls aplaymidi with the right -p parameter.. my own shell skillz
are to n00b though..
Flo
--
Palimm Palimm!
http://affenbande.org/~tapas/
4:51 p.m.
Awesome Florian, I got that to work with pmidi. I will add your
instructions to the Solfege wiki, where it really does not explain that
technique very well for newbies!
Thanks you soooo much,
iain
Florian Schmidt wrote:
On Wed, 26 Jan 2005 12:18:14 -0500
Dave Phillips <dlphilp(a)bright.net> wrote:
I just took a look at the audio preferences for
2.0.2, there's no
provision for anything ALSA. :(
The other options offered were /dev/sequencer, /dev/sequencer2,
/dev/music, and none. Selecting /dev/sequencer2 and /dev/music gave me
error messages, /dev/sequencer was selected without error but I got no
sound from the test. No MIDI activity appeared on my patchbay.
The Solfege Web site includes instructions for wedding timidity to
/dev/music. Didn't work for me though, I still received the error for
/dev/music.
Hi,
easy workaround:
Check "use external midiplayer" and enter:
aplaymidi -p 129:0 %s
Change the 129:0 to the corresponding port, of course [i use fluidsynth
and it happens to open port 129:0 if it's the only midi app on my system
:)] I suppose it would be possible to automate this: If you know you
always use fluidsynth, it is possible to replace aplaymidi with a script
that parses the output of
aconnect -io | grep -i fluid
and calls aplaymidi with the right -p parameter.. my own shell skillz
are to n00b though..
Flo
27 Jan
27 Jan
4:08 a.m.
Florian Schmidt wrote:
aplaymidi -p 129:0 %s
Change the 129:0 to the corresponding port, of course [i use fluidsynth
and it happens to open port 129:0 if it's the only midi app on my system
:)] I suppose it would be possible to automate this: If you know you
always use fluidsynth, it is possible to replace aplaymidi with a script
that parses the output of
aconnect -io | grep -i fluid
and calls aplaymidi with the right -p parameter..
You can simple give the ALSA client name to aplaymidi (see the man
page).
HTH
Clemens
6:47 a.m.
On Thu, 27 Jan 2005 09:08:06 +0100 (MET)
Clemens Ladisch <clemens(a)ladisch.de> wrote:
Florian Schmidt wrote:
Oh doh!.. Well, at least i learned something by not reading the manpage:
echo `aconnect -io |grep -i fluid |cut -d ' ' -f 2`0
:)
flo
--
Palimm Palimm!
http://affenbande.org/~tapas/
aplaymidi -p 129:0 %s
Change the 129:0 to the corresponding port, of course [i use fluidsynth
and it happens to open port 129:0 if it's the only midi app on my system
:)] I suppose it would be possible to automate this: If you know you
always use fluidsynth, it is possible to replace aplaymidi with a script
that parses the output of
aconnect -io | grep -i fluid
and calls aplaymidi with the right -p parameter..
You can simple give the ALSA client name to aplaymidi (see the man
page).
26 Jan
26 Jan
4:44 p.m.
I just took a look at the audio preferences for
2.0.2, there's no
provision for anything ALSA. :(
The other options offered were /dev/sequencer, /dev/sequencer2,
/dev/music, and none. Selecting /dev/sequencer2 and /dev/music gave me
error messages, /dev/sequencer was selected without error but I got no
sound from the test. No MIDI activity appeared on my patchbay.
The Solfege Web site includes instructions for wedding timidity to
/dev/music. Didn't work for me though, I still received the error for
/dev/music.
That about sums up my experience, seems kinda tragic. I'll try a little
longer before resorting to using the Csound5 api to make my own python
ear training program, which kinda seems like gross overkill ...
Thanks Dave
iain
5:05 p.m.
Iain Duncan wrote:
Well, Florian came up with a workaround solution, proving once again
that there's always some way to do it in Linux... ;)
But you would think that the ALSA sequencer interface would be supported
by now...
Best,
dp
I just took a
look at the audio preferences for 2.0.2, there's no
provision for anything ALSA. :(
The other options offered were /dev/sequencer, /dev/sequencer2,
/dev/music, and none. Selecting /dev/sequencer2 and /dev/music gave
me error messages, /dev/sequencer was selected without error but I
got no sound from the test. No MIDI activity appeared on my patchbay.
The Solfege Web site includes instructions for wedding timidity to
/dev/music. Didn't work for me though, I still received the error for
/dev/music.
That about sums up my experience, seems kinda tragic. I'll try a
little longer before resorting to using the Csound5 api to make my own
python ear training program, which kinda seems like gross overkill ...
7051
days inactive
7053
days old
linux-audio-user@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
Clemens Ladisch -
Dave Phillips -
Florian Schmidt -
Iain Duncan