9 Aug
2004
9 Aug
'04
11:33 a.m.
I'm relatively new to the audio on Linux scene, and
admittedly don't have near the best equipment to do
anything serious, but I'd at least like to hear some
sounds of out of the synth and/or MIDI sequencing
software on my Agnula distro. I don't have an
external keyboard, so I'm limited to writing the score
with rosegarden or lilypond. I'd like to edit the
MIDI sequences I produce with something like muse, but
I can't figure out how to hear what changes I make
*from within muse*. I don't have an on-board
sequencer (/dev/sequencer is never recognized or
accessible, which is no surprise, really) on my card.
I thought I'd try using timidity with the -iA option,
and when I do that, then try to play a midi file from
within muse, muse crashes.
I just wanna' figure out how to do two things:
1) tweak my midi sequences for timing, rubato,
expression, using somethink like muse or rosegarden,
and be able to hear what I've done by clicking the
play button(s) provided
2) create my own timbres using some of the
cool-looking synth software, that I can't figure out
how to hear whether I've made any changes or created
any new patches.
The subject line says it all, really. ;-)
Thanks for any help you can give the clueless...
Mark
=====
--
Seek professional help! Ask a librarian.
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
9 Aug
9 Aug
12:24 p.m.
Hi Mark,
Your days as a moron are over!! ;-P
On Monday 09 August 2004 17.17, Mark Wilson wrote:
I'm relatively new to the audio on Linux scene,
and
admittedly don't have near the best equipment to do
anything serious, but I'd at least like to hear some
sounds of out of the synth and/or MIDI sequencing
software on my Agnula distro. I don't have an
external keyboard, so I'm limited to writing the score
with rosegarden or lilypond. I'd like to edit the
MIDI sequences I produce with something like muse, but
I can't figure out how to hear what changes I make
*from within muse*. I don't have an on-board
sequencer (/dev/sequencer is never recognized or
accessible, which is no surprise, really) on my card.
Ok, this might require some explaining.
/dev/sequencer is the sequencer interface for OSS. MusE and Rosegarden do not
support this interface. If AGNULA has ALSA you should instead have the alsa
sequencer interface. I think this should have been loaded even if your
soundcard does not have any midi features (I could be wrong about this
though).
Since you don't have any external keyboard and do not plan on using any
outboard gear at the moment the features of your soundcard should not matter.
Whether the alsa-sequencer really exists is easiest to check by doing 'lsmod'
as root and checking if the module snd-seq has been loaded. (I think there is
a device somewhere also but I forget..)
I guess AGNULA has MusE 0.6.3 ? With the config you are suggesting this should
work fine, stability wise 0.7 would be better but it requires jack at the
moment which is another obstacle to overcome.
The real question here is whether MusE outputs any errors?
If not you should be able to get some of the internal synths to output enough
beeps to make you happy for a few seconds atleast ;)
Under the config menu select the "Midi ports / Softsynth" and instantiate the
organ synth and connect it to a midi port in the "Midi connections" view.
After this you can connect it to the midi track you've done by clicking in the
O-port column in the arranger.
After you get this to work it should be no problem stepping to more advanced
grounds, other synths etc.
I thought I'd try using timidity with the -iA option,
and when I do that, then try to play a midi file from
within muse, muse crashes.
If this persists after you tested the above I need to know some more, like if
there are any printed errors in the terminal?
I just wanna' figure out how to do two things:
1) tweak my midi sequences for timing, rubato,
expression, using somethink like muse or rosegarden,
and be able to hear what I've done by clicking the
play button(s) provided
Should be no problem with either.
2) create my own timbres using some of the
cool-looking synth software, that I can't figure out
how to hear whether I've made any changes or created
any new patches.
The subject line says it all, really. ;-)
Thanks for any help you can give the clueless...
Mark
=====
--
Seek professional help! Ask a librarian.
/Robert
--
http://spamatica.se/music/
7:07 p.m.
On Monday 09 August 2004 12:04 pm, Robert Jonsson wrote:
Pretty sure the fine folks at Agnula have the mixer volumes up by default,
but you may want to check on that if you haven't.
Synth software is outputting PCM streams either to /dev/dsp or to jack
ports, for the latter case you may have to connect the ports "by hand"
Hi Mark,
Your days as a moron are over!! ;-P
On Monday 09 August 2004 17.17, Mark Wilson wrote:
I gave agnula a spin a couple days ago. It's pretty much "point and shoot"
once it's installed. it has ALSA and it includes MusE 6.3.
If I understand how agGNUla works 0.7 MusE will filter down from Debian
testing. 0.7 hasn't hit Debian unstable yet.
I'm relatively new to the audio on Linux
scene, and
admittedly don't have near the best equipment to do
anything serious, but I'd at least like to hear some
sounds of out of the synth and/or MIDI sequencing
software on my Agnula distro. I don't have an
external keyboard, so I'm limited to writing the score
with rosegarden or lilypond. I'd like to edit the
MIDI sequences I produce with something like muse, but
I can't figure out how to hear what changes I make
*from within muse*. I don't have an on-board
sequencer (/dev/sequencer is never recognized or
accessible, which is no surprise, really) on my card.
Ok, this might require some explaining.
/dev/sequencer is the sequencer interface for OSS. MusE and Rosegarden do
not support this interface. If AGNULA has ALSA you should instead have the
alsa sequencer interface. I think this should have been loaded even if your
soundcard does not have any midi features (I could be wrong about this
though).
Since you don't have any external keyboard and do not plan on using any
outboard gear at the moment the features of your soundcard should not
matter. Whether the alsa-sequencer really exists is easiest to check by
doing 'lsmod' as root and checking if the module snd-seq has been loaded.
(I think there is a device somewhere also but I forget..)
I guess AGNULA has MusE 0.6.3 ? With the config you are suggesting this
should work fine, stability wise 0.7 would be better but it requires jack
at the moment which is another obstacle to overcome.
The real question here is whether MusE outputs any
errors?
If not you should be able to get some of the internal synths to output
enough beeps to make you happy for a few seconds atleast ;)
Under the config menu select the "Midi ports / Softsynth" and instantiate
the organ synth and connect it to a midi port in the "Midi connections"
view. After this you can connect it to the midi track you've done by
clicking in the O-port column in the arranger.
He didn't say what kind of soundcard, so the organ softsynth is a good
recommendation.
If he has a supported wavetable on his card or wants to use fluidsynth,
of course patches will need to be loaded.
After you get this to work it should be no problem stepping to more
advanced grounds, other synths etc.
There is no facility for "groove templates" or swing, if thats what you're
after.
Weak quantize and hand editing will do the job.
MusE has available excellent tick per quarter-note resolution
I thought I'd try using timidity with the -iA
option,
and when I do that, then try to play a midi file from
within muse, muse crashes.
If this persists after you tested the above I need to know some more, like
if there are any printed errors in the terminal?
> I just wanna' figure out how to do two things:
> 1) tweak my midi sequences for timing, rubato, expression,
using somethink like muse or rosegarden,
and be able to hear what I've done by clicking the
play button(s) provided
Should be no problem with either.
> 2) create my own timbres using some of the
> cool-looking synth software, that I can't figure out
> how to hear whether I've made any changes or created
> any new patches.
> The subject
line says it all, really. ;-)
Thanks for any help you can give the clueless...
Mark
=====
--
Seek professional help! Ask a librarian.
/Robert 
10 Aug
10 Aug
4:36 a.m.
On Monday 09 Aug 2004 11:50 pm, John Check wrote:
On Monday 09 August 2004 12:04 pm, Robert Jonsson
wrote:
Rosegarden does swing quantize, and tempo mapping from a beat track.
No groove templates for quantization though.
Chris
On Monday 09 August 2004 17.17, Mark Wilson
wrote:
> I just wanna' figure out how to do two things:
> 1) tweak my midi sequences for timing, rubato,
There is no facility for "groove templates" or swing, if thats what
you're after.
11 Aug
11 Aug
1:59 a.m.
On Tuesday 10 August 2004 04:23 am, Chris Cannam wrote:
On Monday 09 Aug 2004 11:50 pm, John Check wrote:
I've been looking at it, it's very nice. Will it be able to chase timecode in
the foreseable future?
On Monday 09 August 2004 12:04 pm, Robert Jonsson
wrote:
Rosegarden does swing quantize, and tempo mapping from a beat track.
No groove templates for quantization though.
On Monday 09 August 2004 17.17, Mark Wilson
wrote:
> I just wanna' figure out how to do two things:
> 1) tweak my midi sequences for timing, rubato,
There is no facility for "groove templates" or swing, if thats what
you're after.
Chris
10 Aug
10 Aug
9:36 a.m.
Last Monday 09 August 2004 23:50, John Check was like:
MusE-0.7 will be included in the distro as soon as that, yes. I have had some
problems with the 0.6.x releases of MusE under AGNULA, so Mark's problems may
not all be due to lack of understanding.
On Monday 09 August 2004 12:04 pm, Robert Jonsson
wrote:
> On Monday 09 August 2004 17.17, Mark Wilson wrote:
> > I don't have an on-board
> > sequencer (/dev/sequencer is never recognized or
> > accessible, which is no surprise, really) on my card.
What soundcard do you have?
> If AGNULA has ALSA you should instead have
> the alsa sequencer interface. I think this should have been loaded even
> if your soundcard does not have any midi features (I could be wrong about
> this though).
I'm fairly sure that you are correct.
I guess AGNULA
has MusE 0.6.3 ? With the config you are suggesting this
should work fine, stability wise 0.7 would be better but it requires jack
at the moment which is another obstacle to overcome.
I gave agnula a spin a couple days ago. It's pretty much "point and shoot"
once it's installed. it has ALSA and it includes MusE 6.3.
If I understand how agGNUla works 0.7 MusE will filter down from Debian
testing. 0.7 hasn't hit Debian unstable yet. Pretty sure the fine folks at Agnula have the mixer
volumes up by default,
but you may want to check on that if you haven't.
Synth software is outputting PCM streams either to /dev/dsp or to jack
ports, for the latter case you may have to connect the ports "by hand"
Volumes are up by default only in the latest release candidates of
A/DeMuDi-1.2.0. This is actually an FAQ and most of the answers can be found
here:
http://wiki.agnula.org
http://www.debian.org/doc/manuals/reference/reference.en.html
http://www.agnula.org/download/demudi/1.2.0-FAQ
http://www.agnula.org/documentation/FAQ/
http://d-i.alioth.debian.org/manual/en.i386/index.html
http://www.alsa-project.org/alsa-doc/
http://kreiger.linuxgods.com/kiki/?linux+sound-permissions
http://www.togaware.com/linux/survivor/index.shtml
check that /dev/dsp* /dev/mixer* belong to the right (audio) group, they don't
by default - also check that _you_ do, the latter is set by default. I've
been considering starting an AGNULA config wiki page, but have not done so
yet because it represents a considerable duplication of info, however,
repeated questions like this make me think that there _is_ a need.
Mark, please let me know what remains unclear. The best place for this
conversation would really be users(a)lists.agnula.org or even directly through
http://wiki.agnula.org - I shall start a config page there in the next few
days.
cheers
tim hall
11 Aug
11 Aug
2 a.m.
On Tuesday 10 August 2004 09:20 am, tim hall wrote:
I'm sure I'll get flamed, but wikis leave a lot to be desired as primary
documentation. There are ways to address this, but they're obvious.
At least to me.
Last Monday 09 August 2004 23:50, John Check was
like:
MusE-0.7 will be included in the distro as soon as that, yes. I have had
some problems with the 0.6.x releases of MusE under AGNULA, so Mark's
problems may not all be due to lack of understanding.
The 0.6.2/3 releases were... uh.. suboptimal.
On Monday 09 August 2004 12:04 pm, Robert Jonsson
wrote:
> On Monday 09 August 2004 17.17, Mark Wilson wrote:
> > I don't have an on-board
> > sequencer (/dev/sequencer is never recognized or
> > accessible, which is no surprise, really) on my card.
What soundcard do you have?
> If AGNULA has ALSA you should instead have
> the alsa sequencer interface. I think this should have been loaded even
> if your soundcard does not have any midi features (I could be wrong
> about this though).
I'm fairly sure that you are correct.
I guess
AGNULA has MusE 0.6.3 ? With the config you are suggesting this
should work fine, stability wise 0.7 would be better but it requires
jack at the moment which is another obstacle to overcome.
I gave agnula a spin a couple days ago. It's pretty much "point and
shoot" once it's installed. it has ALSA and it includes MusE 6.3.
If I understand how agGNUla works 0.7 MusE will filter down from Debian
testing. 0.7 hasn't hit Debian unstable yet. Pretty sure
the fine folks at Agnula have the mixer volumes up by
default, but you may want to check on that if you haven't.
Synth software is outputting PCM streams either to /dev/dsp or to jack
ports, for the latter case you may have to connect the ports "by hand"
Volumes are up by default only in the latest release candidates of
A/DeMuDi-1.2.0. This is actually an FAQ and most of the answers can be
found here:
http://wiki.agnula.org
http://www.debian.org/doc/manuals/reference/reference.en.html
http://www.agnula.org/download/demudi/1.2.0-FAQ
http://www.agnula.org/documentation/FAQ/
http://d-i.alioth.debian.org/manual/en.i386/index.html
http://www.alsa-project.org/alsa-doc/
http://kreiger.linuxgods.com/kiki/?linux+sound-permissions
http://www.togaware.com/linux/survivor/index.shtml
check that /dev/dsp* /dev/mixer* belong to the right (audio) group, they
don't by default - also check that _you_ do, the latter is set by default.
I've been considering starting an AGNULA config wiki page, but have not
done so yet because it represents a considerable duplication of info,
however, repeated questions like this make me think that there _is_ a need.
Mark, please let me know what remains unclear. The
best place for this
conversation would really be users(a)lists.agnula.org or even directly
through http://wiki.agnula.org - I shall start a config page there in the
next few days.
cheers
tim hall
6:32 a.m.
Last Wednesday 11 August 2004 06:44, John Check was like:
I'm sure I'll get flamed, but wikis leave a
lot to be desired as primary
documentation. There are ways to address this, but they're obvious.
At least to me.
It's not primary documentation, The links are ;-)
This is due to the fact that I'm not a primary documenter for AGNULA, I'm just
using the WIKIs as a talking shop and a place to gather together information
so I can post shorter links. Contributions are welcome ;-)
cheers
tim hall
8:28 p.m.
On Wednesday 11 August 2004 06:16 am, tim hall wrote:
Last Wednesday 11 August 2004 06:44, John Check was
like:
I meant in general, not specific to Agnula.
I'm sure I'll get flamed, but wikis leave
a lot to be desired as primary
documentation. There are ways to address this, but they're obvious.
At least to me.
It's not primary documentation, The links are ;-)
This is due to the fact that I'm not a primary documenter for AGNULA, I'm
just using the WIKIs as a talking shop and a place to gather together
information so I can post shorter links. Contributions are welcome ;-)
As long as you didn't ask ;) How does the stuff from the wiki find it's way
into the primary doco?
cheers
tim hall
12 Aug
12 Aug
6:47 a.m.
Last Thursday 12 August 2004 01:12, John Check was like:
On Wednesday 11 August 2004 06:16 am, tim hall wrote:
Probably by me converting it to HTML (?)
John, I'm not understanding your point here.
If this is more than a personal dislike of WIKI I really would appreciate a
bigger clue :-] [if really OT: Offlist is OK]
cheers
tim hall
Last Wednesday 11 August 2004 06:44, John Check
was like:
I meant in general, not specific to Agnula.
I'm sure I'll get flamed, but wikis leave
a lot to be desired as
primary documentation. There are ways to address this, but they're
obvious. At least to me.
It's not primary documentation, The links are ;-) This is due to the fact that I'm not a
primary documenter for AGNULA, I'm
just using the WIKIs as a talking shop and a place to gather together
information so I can post shorter links. Contributions are welcome ;-)
As long as you didn't ask ;) How does the stuff from the wiki find it's way
into the primary doco?
12:55 p.m.
On Thursday 12 August 2004 06:31 am, tim hall wrote:
Last Thursday 12 August 2004 01:12, John Check was
like:
That's not too far off the mark. I don't dislike them, per se. Wiki's are a
great concept, but the way they're used in practice makes an already bad
situation worse. There is already an overwhelming amount of doco, and it's
disorganized. This is of course, not something particular to linux audio.
As your reply indicates, wikis can be culled for good information which can be
brought into the primary doco, but it's not sexy, so whether it gets done or
not is a crapshoot for any given project.
I was being vague because the concept is still being tuned, and I'm busy with
some archival work just now, but I mentioned off list to Dave Phillips about
doing something along the lines of linux-sound.org, but adding MIDI
implementation charts and an API support matrix with a reporting system to
make it easy for projects to keep they stuff up to date, then linking to
projects Wikis and main doco from there. IOW if I want a sequencer with foo &
bar, a search returns appropriate hits ranked by development status with
direct links. Of course the weak spot there is getting people to use it;
That's the same problem Wiki's have, but they're conceptually too general.
As it stands now, it just takes too much time to evaluate what's out there for
linux music/audio to get any serious traction.
Don't get me wrong, I don't mean to denigrate anybody's hard work, but I see a
lot of things that make the current situation untenable from a business
context. It's potentially good for me, but bad for everybody else that's
interested in linux audio as a tool and not interested in the geekery
aspects.
On Wednesday 11 August 2004 06:16 am, tim hall
wrote:
Probably by me converting it to HTML (?)
John, I'm not understanding your point here.
If this is more than a personal dislike of WIKI I really would appreciate a
bigger clue :-] [if really OT: Offlist is OK]
Last Wednesday 11 August 2004 06:44, John Check
was like:
I meant in general, not specific to Agnula.
I'm sure I'll get flamed, but wikis leave
a lot to be desired as
primary documentation. There are ways to address this, but they're
obvious. At least to me.
It's not primary documentation, The links are ;-) This is due to the fact that I'm not a
primary documenter for AGNULA,
I'm just using the WIKIs as a talking shop and a place to gather
together information so I can post shorter links. Contributions are
welcome ;-)
As long as you didn't ask ;) How does the stuff from the wiki find it's
way into the primary doco? cheers
tim hall
8:23 p.m.
Last Thursday 12 August 2004 17:39, John Check was like:
On Thursday 12 August 2004 06:31 am, tim hall wrote:
I can see your point.
Last Thursday 12 August 2004 01:12, John Check
was like:
That's not too far off the mark. I don't dislike them, per se. Wiki's are a
great concept, but the way they're used in practice makes an already bad
situation worse. There is already an overwhelming amount of doco, and it's
disorganized. This is of course, not something particular to linux audio.
As your reply indicates, wikis can be culled for good information which can
be brought into the primary doco, but it's not sexy, so whether it gets
done or not is a crapshoot for any given project. On Wednesday 11 August 2004 06:16 am, tim hall
wrote:
Probably by me converting it to HTML (?)
John, I'm not understanding your point here.
If this is more than a personal dislike of WIKI I really would appreciate
a bigger clue :-] [if really OT: Offlist is OK] Last Wednesday 11 August 2004 06:44, John Check
was like:
> I'm sure I'll get flamed, but wikis leave a lot to be desired as
> primary documentation. There are ways to address this, but they're
> obvious. At least to me.
It's not primary documentation, The links are ;-)
I meant in general, not specific to Agnula.
This is due to the fact that I'm not a
primary documenter for AGNULA,
I'm just using the WIKIs as a talking shop and a place to gather
together information so I can post shorter links. Contributions are
welcome ;-)
As long as you didn't ask ;) How does the stuff from the wiki find it's
way into the primary doco? I was being vague because the concept is still being
tuned, and I'm busy
with some archival work just now, but I mentioned off list to Dave Phillips
about doing something along the lines of linux-sound.org, but adding MIDI
implementation charts and an API support matrix with a reporting system to
make it easy for projects to keep they stuff up to date, then linking to
projects Wikis and main doco from there. IOW if I want a sequencer with foo
& bar, a search returns appropriate hits ranked by development status with
direct links. Of course the weak spot there is getting people to use it;
That's the same problem Wiki's have, but they're conceptually too general.
As it stands now, it just takes too much time to evaluate what's out there
for linux music/audio to get any serious traction.
Don't get me wrong, I don't mean to denigrate anybody's hard work, but I
see a lot of things that make the current situation untenable from a
business context. It's potentially good for me, but bad for everybody else
that's interested in linux audio as a tool and not interested in the
geekery aspects.
Thanks. Currently I'm playing with WIKI, it's easy to use and fun. What you're
talking about is somewhat beyond my ken, but I would be happy to use some
better system if it meant better documentation. The randomness factor is part
of what makes the documentation hard to get through. A system which easily
highlighted what documentation was either missing or duplicated would be a
valuable resource for potential authors too. I shan't waste my time getting
too much into WIKI if it's really not the way to go. I'm not attached to the
means.
cheers
tim hall
13 Aug
13 Aug
4:43 p.m.
On Thursday 12 August 2004 08:07 pm, tim hall wrote:
Last Thursday 12 August 2004 17:39, John Check was
like:
Actually, I have the resources to pull it off and host it, I just have to make
the time to do it. That you'd be happy to use it makes me smile, because
the system has to make life easier for it's end users.
I'll start a thread for feedback on monday.
On Thursday 12 August 2004 06:31 am, tim hall
wrote:
I can see your point.
Last Thursday 12 August 2004 01:12, John Check
was like:
That's not too far off the mark. I don't dislike them, per se. Wiki's are
a great concept, but the way they're used in practice makes an already
bad situation worse. There is already an overwhelming amount of doco, and
it's disorganized. This is of course, not something particular to linux
audio. As your reply indicates, wikis can be culled for good information
which can be brought into the primary doco, but it's not sexy, so whether
it gets done or not is a crapshoot for any given project. On Wednesday 11 August 2004 06:16 am, tim hall
wrote:
> Last Wednesday 11 August 2004 06:44, John Check was like:
> > I'm sure I'll get flamed, but wikis leave a lot to be desired as
> > primary documentation. There are ways to address this, but
> > they're obvious. At least to me.
>
> It's not primary documentation, The links are ;-)
I meant in general, not specific to Agnula.
> This is due to the fact that I'm not a primary documenter for
> AGNULA, I'm just using the WIKIs as a talking shop and a place to
> gather together information so I can post shorter links.
> Contributions are welcome ;-)
As long as you didn't ask ;) How does the stuff from the wiki find
it's way into the primary doco?
Probably by me converting it to HTML (?)
John, I'm not understanding your point here.
If this is more than a personal dislike of WIKI I really would
appreciate a bigger clue :-] [if really OT: Offlist is OK] I was being vague because the concept is still
being tuned, and I'm busy
with some archival work just now, but I mentioned off list to Dave
Phillips about doing something along the lines of linux-sound.org, but
adding MIDI implementation charts and an API support matrix with a
reporting system to make it easy for projects to keep they stuff up to
date, then linking to projects Wikis and main doco from there. IOW if I
want a sequencer with foo & bar, a search returns appropriate hits ranked
by development status with direct links. Of course the weak spot there is
getting people to use it; That's the same problem Wiki's have, but
they're conceptually too general. As it stands now, it just takes too
much time to evaluate what's out there for linux music/audio to get any
serious traction.
Don't get me wrong, I don't mean to denigrate anybody's hard work, but I
see a lot of things that make the current situation untenable from a
business context. It's potentially good for me, but bad for everybody
else that's interested in linux audio as a tool and not interested in the
geekery aspects.
Thanks. Currently I'm playing with WIKI, it's easy to use and fun. What
you're talking about is somewhat beyond my ken, but I would be happy to use
some better system if it meant better documentation. The randomness factor is part of what makes the documentation hard to get
through. A system which
easily highlighted what documentation was either missing or duplicated
would be a valuable resource for potential authors too. I shan't waste my
time getting too much into WIKI if it's really not the way to go. I'm not
attached to the means.
WIKI is another tool in the chain, so by all means take advantage of what we
have now. I've got some ideas for automating extraction of data from wikis
and list archives.
cheers
tim hall
14 Aug
14 Aug
9:43 a.m.
Last Friday 13 August 2004 21:27, John Check was like:
Excellent, I look forward to developments.
cheers
tim hall
Thanks.
Currently I'm playing with WIKI, it's easy to use and fun. What
you're talking about is somewhat beyond my ken, but I would be happy to
use some better system if it meant better documentation. The randomness
factor
Actually, I have the resources to pull it off and host it, I just have to
make the time to do it. That you'd be happy to use it makes me smile,
because the system has to make life easier for it's end users.
I'll start a thread for feedback on monday.
is part of what makes the documentation hard to
get through. A system
which easily highlighted what documentation was either missing or
duplicated would be a valuable resource for potential authors too. I
shan't waste my time getting too much into WIKI if it's really not the
way to go. I'm not attached to the means.
WIKI is another tool in the chain, so by all means take advantage of what
we have now. I've got some ideas for automating extraction of data from
wikis and list archives.
10 Aug
10 Aug
1:49 p.m.
--- Robert Jonsson <rj(a)spamatica.se> wrote:
Hi Mark,
Your days as a moron are over!! ;-P
On Monday 09 August 2004 17.17, Mark Wilson wrote:
I forgot to specify that my soundcard is a
SoundBlaster 16 PCI. According to the ALSA website,
the modules for the Ensoniq 1371 are the best match.
There is no on-board wave-table, if I read the
documentation correctly.
I'm relatively new to the audio on Linux
scene,
and
admittedly don't have near the best equipment
to
do
anything serious, but I'd at least like to
hear
some
sounds of out of the synth and/or MIDI
sequencing
software on my Agnula distro. I don't have an
external keyboard, so I'm limited to writing the
score
with rosegarden or lilypond. I'd like to
edit the
MIDI sequences I produce with something like muse,
but
I can't figure out how to hear what changes I
make
*from within muse*. I don't have an on-board
sequencer (/dev/sequencer is never recognized or
accessible, which is no surprise, really) on my
card.
Ok, this might require some explaining.
/dev/sequencer is the sequencer interface for OSS.
MusE and Rosegarden do not
support this interface. If AGNULA has ALSA you
should instead have the alsa
sequencer interface. I think this should have been
loaded even if your
soundcard does not have any midi features (I could
be wrong about this
though). Since you don't have any external keyboard and do
not plan on using any
outboard gear at the moment the features of your
soundcard should not matter.
Whether the alsa-sequencer really exists is easiest
to check by doing 'lsmod'
as root and checking if the module snd-seq has been
loaded. (I think there is
a device somewhere also but I forget..)
I guess AGNULA has MusE 0.6.3 ? With the config you
are suggesting this should
work fine, stability wise 0.7 would be better but it
requires jack at the
moment which is another obstacle to overcome.
The real question here is whether MusE outputs any
errors?
If not you should be able to get some of the
internal synths to output enough
beeps to make you happy for a few seconds atleast ;)
Under the config menu select the "Midi ports /
Softsynth" and instantiate the
organ synth and connect it to a midi port in the
"Midi connections" view.
After this you can connect it to the midi track
you've done by clicking in the
O-port column in the arranger.
After you get this to work it should be no problem
stepping to more advanced
grounds, other synths etc.
I'm heartened that I seem to have figured correctly
that having timidity started with the -iA option is a
possible correct thing to do. I also tried
$pmidi -p 128:0 foo.mid
after starting timidity with the ALSA option, and I
could see that the CPU is significantly taxed, but I
still hear nothing. Also tried other ports like
129:0, 130:1 -- even 64:0. Just wild guessing. Still
no joy.
BTW, just playing individual midi files from CLI works
fine--I've even messed around with different patches.
Agnula 1.2.0 BETA comes with a pkg. called freepat,
which has most (all?) of the same patches that
timidity-patches*.deb contains, but they're located
elsewhere so I have to specify the full path, which is
kind of a pain.
Thanks!
Mark
=====
--
Seek professional help! Ask a librarian.
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
I thought I'd try using timidity with the -iA
option,
and when I do that, then try to play a midi file
from
within muse, muse crashes.
If this persists after you tested the above I need
to know some more, like if
there are any printed errors in the terminal?
11 Aug
11 Aug
2:08 a.m.
On Tuesday 10 August 2004 01:33 pm, Mark Wilson wrote:
--- Robert Jonsson <rj(a)spamatica.se> wrote:
You are correct, Sir. Your best option with that card and MusE are the
softsynths.
Unfortunately, that chipset is really not good for duplex operation, or even
overdubbing.
The problem is (at least on any one I've had any truck with) the sample rate
is off by 1 on the capture side. Playback is 44.1kHz. The net effect is your
program length will be off by about 2 seconds for every hour.
Hi Mark,
Your days as a moron are over!! ;-P
On Monday 09 August 2004 17.17, Mark Wilson wrote:
I forgot to specify that my soundcard is a
SoundBlaster 16 PCI. According to the ALSA website,
the modules for the Ensoniq 1371 are the best match.
There is no on-board wave-table, if I read the
documentation correctly.
I'm relatively new to the audio on Linux
scene,
and
admittedly don't have near the best equipment
to
do
anything serious, but I'd at least like to
hear
some
sounds of out of the synth and/or MIDI
sequencing
software on my Agnula distro. I don't have an
external keyboard, so I'm limited to writing the
score
with rosegarden or lilypond. I'd like to
edit the
MIDI sequences I produce with something like muse,
but
I can't figure out how to hear what changes I
make
*from within muse*. I don't have an on-board
sequencer (/dev/sequencer is never recognized or
accessible, which is no surprise, really) on my
card.
Ok, this might require some explaining.
/dev/sequencer is the sequencer interface for OSS.
MusE and Rosegarden do not
support this interface. If AGNULA has ALSA you
should instead have the alsa
sequencer interface. I think this should have been
loaded even if your
soundcard does not have any midi features (I could
be wrong about this
though).
7485
days inactive
7490
days old
linux-audio-user@lists.linuxaudio.org
15 comments
5 participants
participants (5)
-
Chris Cannam -
John Check -
Mark Wilson -
Robert Jonsson -
tim hall