RTC timer questions

RTC timer questions

[Maarten de Boer]

Hello,

I sent the following to the list, but did not get any answer, so I
repost, and will elaborate a bit on it.

> Hello, I noticed that the alsa rtctimer is not compiled when you have
> the RTC in your kernel as a module. The problem is in
> alsa-kernel/core/Makefile, where CONFIG_RTC is tested for y
> and not for m. 

> Where can I find up-to-date documentation about how to use the rtc timer?

The latest I find is a mail by Takashi, that is a year old, which says:

Installation:
Add the following lines in /etc/modules.conf:
options snd-timer snd_timer_limit=2
alias snd-timer-1 snd-rtctimer
For using RTC timer in sequencer as default:
options snd-seq snd_seq_default_timer=1

This is not working anymore, because parameters changed.

Starting sound driver: snd-emu10k1 done
/lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o: invalid parameter parm_snd_seq_default_timer
/lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o: insmod /lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o failed
/lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o: invalid parameter parm_snd_seq_default_timer
/lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o: insmod /lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o failed
/lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o: insmod snd-seq-midi failed

Also, is there any way (apart from 'listining') to know whether the rtctimer
is used by the sequencer or not?

Maarten

ALSA instrument API

[Richard Bown]

Hi,

Thanks to Maarten I've got involved in implementing ALSA support for Rosegarden 4.
I've been browsing the ALSA API and patching together a driver layer to give us a
general framework we can share between ALSA and aRts.  The ALSA Instrument API looks
promising but so far I can't find much on it on the mailing list archive or on
the web.  Any clues for an overview?

We've got the beginnings of quite a sophisticated Instrument/Studio concept in the
pipeline similar to Logic's Environment and of course I'd like to make the most
of the driver features as flexibly as we can right from the start.

Cheers,
Richard Bown
-- 
http://www.all-day-breakfast.com/rosegarden
http://www.bownie.com

Re: ALSA instrument API

[Paul Davis]

>Thanks to Maarten I've got involved in implementing ALSA support for
>Rosegarde n 4.  I've been browsing the ALSA API and patching together
>a driver layer to give u s a general framework we can share between
>ALSA and aRts.  The ALSA Instrument API looks promising but so far I
>can't find much on it on the mailing list archive or on the web.  Any
>clues for an overview?

AFAIK, it has never been fully developed (and certainly is not used by
more than a handful of test programs). You should be talking to Josh
Green and others on LAD who are interested in defining how this should
work more fully. There are a lot of tricky issues that arise from the
distinctions between external MIDI devices and software-implemented
MIDI devices, including those with hardware support (such the as the
synths on many current consumer audio interfaces). I don't think these
have ever really been worked out within ALSA - I could, as usual, be
wrong. 

--p

Re: ALSA instrument API

[Juan Linietsky]

On Thu, 04 Apr 2002 09:31:56 -0500
Paul Davis <pbd@op.net> wrote:

> >Thanks to Maarten I've got involved in implementing ALSA support for
> >Rosegarde n 4.  I've been browsing the ALSA API and patching together
> >a driver layer to give u s a general framework we can share between
> >ALSA and aRts.  The ALSA Instrument API looks promising but so far I
> >can't find much on it on the mailing list archive or on the web.  Any
> >clues for an overview?
> 
> AFAIK, it has never been fully developed (and certainly is not used by
> more than a handful of test programs). You should be talking to Josh
> Green and others on LAD who are interested in defining how this should
> work more fully. There are a lot of tricky issues that arise from the
> distinctions between external MIDI devices and software-implemented
> MIDI devices, including those with hardware support (such the as the
> synths on many current consumer audio interfaces). I don't think these
> have ever really been worked out within ALSA - I could, as usual, be
> wrong. 
> 
> --

I'm interested in extending the api only for retrieval of info about 
bank names/info, patch names/info and controller names. Info
would default to some midi standard defaults.
What do you have in mind for an instrument api?

Juan Linietsky




> 
> 
> 
> 
> 
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
> 

Re: ALSA instrument API

[Richard Bown]

Juan Linietsky wrote:

> I'm interested in extending the api only for retrieval of info about 
> bank names/info, patch names/info and controller names. Info would
> default to some midi standard defaults.  What do you have in mind for
> an instrument api?

I don't have anything in mind for the instrument API - I'm just curious really.
>From our app's perspective we want to be informed about possible instruments
sometimes and prescriptive the rest of the time.  I'm wondering actually how
much you really need at the driver level for this kind of thing?

Once you've worked out the device you're talking to its up to the user (or other
enthusiastic individuals) to create templates of device specific MIDI mappings
to allow the application's presentation of the features.  It would be nice to
have self describing MIDI devices but this isn't really part of the standard is
it?  And (again) how would you be consistent across external and soundcard
devices?  We already see this kind of distinction in OSS and ALSA and one thing
any instrument interface is going to want is consistency of approach.

Anyway, just some thoughts.  For the moment I'm going to implement our ALSA
layer such that it reports devices, synths, channels etc. and creates an
Instrument map for the application to use.  We'll see how we get on with that
approach.

R
-- 
http://www.all-day-breakfast.com/rosegarden
http://www.bownie.com

RTC timer questions, reposting

[Maarten de Boer]

Hello,

Sorry for being such a pain, but I really want this to work, and I
really think this is something that has general interest: using a
higher accurate midi event timing. So: HOW DO I USE THE RTC TIMER?
I can find no up-to-date documentation about this.

The latest I find is a mail by Takashi, that is a year old, which says:

Installation:
Add the following lines in /etc/modules.conf:
options snd-timer snd_timer_limit=2
alias snd-timer-1 snd-rtctimer
For using RTC timer in sequencer as default:
options snd-seq snd_seq_default_timer=1

This is not working anymore, because parameters changed.

Starting sound driver: snd-emu10k1 done
/lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o: invalid parameter parm_snd_seq_default_timer
/lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o: insmod /lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o failed
/lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o: invalid parameter parm_snd_seq_default_timer
/lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o: insmod /lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o failed
/lib/modules/2.4.18/kernel/sound/acore/seq/snd-seq.o: insmod snd-seq-midi failed

So, please tell me how it works. If I can get it to work, I would not mind 
writing some documentation about it, but please help me out!

Also, is there any way (apart from 'listening') to know whether the rtctimer
is used by the sequencer or not?

BTW, I noticed that the alsa rtctimer is not compiled when you have
the RTC in your kernel as a module. The problem is in 
alsa-kernel/core/Makefile, where CONFIG_RTC is tested for y and not for m. 

Maarten