At Thu, 3 Jul 2003 18:05:08 +0200 (CEST),
Thomas Charbonnel wrote:
>
> > Hello all,
> >
> > here are my next goals for the ALSA library development (short
> > term). I invite all developers to comment these directions.
> >
>
> [...]
>
> > * initiate a development of a graphical tool which wi
At Thu, 3 Jul 2003 16:39:36 +0300 (EEST),
Kai Vehmanen wrote:
>
> Ok, this is a bit late, but hopefully not too late. :)
>
> On Tue, 24 Jun 2003, Joern Nettingsmeier wrote:
> >>> other people might propose XML. then it becomes to a question whether
> >> I think that XML is too overkill for our p
> Hello all,
>
> here are my next goals for the ALSA library development (short
> term). I invite all developers to comment these directions.
>
[...]
> * initiate a development of a graphical tool which will manage
> the alsa configuration files (~/.asoundrc)
> - we need a rapid develop
On Thu, 3 Jul 2003, Kai Vehmanen wrote:
> * making alsa-conf the primary tool for setting up ALSA user-space
Ugh, that should "primary tool for setting up ALSA (kernel) drivers".
Hmm, I guess we could have two tools, one for drivers (current alsa-conf)
and one for user-space (asoundrc editor).
-
On Sun, 22 Jun 2003, Jaroslav Kysela wrote:
> here are my next goals for the ALSA library development (short
> term). I invite all developers to comment these directions.
[...]
> * create ordinary pcm & mixer interfaces
These are very welcome additions, especially the mixer part! Although
Ok, this is a bit late, but hopefully not too late. :)
On Tue, 24 Jun 2003, Joern Nettingsmeier wrote:
>>> other people might propose XML. then it becomes to a question whether
>> I think that XML is too overkill for our purposes.
> otoh, the embedded guys will probably not like it, but then memo
At Tue, 24 Jun 2003 20:28:08 +0200 (CEST),
Jaroslav wrote:
>
> > i believe, if we change the configuration syntax, it would be better
> > to branch the development tree (or jump the version number).
> > the current system works well already in many fields, so it's nice to
> > keep the stable serie
On Tue, 24 Jun 2003, Takashi Iwai wrote:
> At Tue, 24 Jun 2003 08:16:18 -0400,
> Paul Davis wrote:
> >
> > >It is something similar like "HTML" and "Java script". The first one is
> > >good to describe the static part of web pages, but if you want something
> > >dynamic, you have to use another
At Tue, 24 Jun 2003 15:04:22 +0200 (CEST),
Jaroslav wrote:
>
> On Tue, 24 Jun 2003, Giuliano Pochini wrote:
>
> > Lisp should be fine, although it's not very user-friendly. But what the
> > interpreter is supposed to do ? Is it possible to create an ordinary
> > mixer control that the hw doesn't
At Tue, 24 Jun 2003 08:16:18 -0400,
Paul Davis wrote:
>
> >It is something similar like "HTML" and "Java script". The first one is
> >good to describe the static part of web pages, but if you want something
> >dynamic, you have to use another embeded language.
>
> or use a real language for the
On Tue, 24 Jun 2003, Giuliano Pochini wrote:
> Lisp should be fine, although it's not very user-friendly. But what the
> interpreter is supposed to do ? Is it possible to create an ordinary
> mixer control that the hw doesn't support ? For example: a card may not
> have an hw master volume contr
On 23-Jun-2003 Takashi Iwai wrote:
> At Sun, 22 Jun 2003 21:10:31 +0200 (CEST),
> Jaroslav wrote:
>>
>> Hello all,
>>
>> here are my next goals for the ALSA library development (short
>> term). I invite all developers to comment these directions.
>>
>> * create ordinary pcm & mixer interfa
>There are two differences between lisp and alsa configuration language.
>Lisp is standard dynamic language but the ALSA configuration is static
>(if you ommit the runtime evaluation hacks added to enhance functinality).
but the runtime evaluation hacks are precisely what give rise to the
problems
On Tue, 24 Jun 2003, Paul Davis wrote:
> this is just another version of the kind of embedded quoting nightmare
> that we all face when using shell scripts. the right form is:
>
> (defun cards
> (load-conf (concat (data-dir) "/cards/aliases.conf") 0)
> (defun load-conf-all (card)
>@hooks [
>{
>func load
>files [
>"/etc/asound.conf"
>"~/.asoundrc"
>]
>errors false
>}
>]
>
>New code:
>
># pre-load the configuration files
>
>@elisp "
>(load-co
Jaroslav Kysela ha scritto:
On Tue, 24 Jun 2003, Joern Nettingsmeier wrote:
# pre-load the configuration files
@elisp "
(load-conf \"/etc/asound.conf\" 0)
(load-conf \"~/.asoundrc\" 0)
"
I'd suggest a simpler alternative:
- introduce a new type SND_CONFIG_TYPE_SEXP
- change parse
On Tue, 24 Jun 2003, Joern Nettingsmeier wrote:
> Jaroslav Kysela wrote:
> >>
> >>other people might propose XML. then it becomes to a question whether
> >>alsa-lib should rely on other libs...
> >
> >
> > I think that XML is too overkill for our purposes.
>
> true if you only consider als
Joern Nettingsmeier wrote:
true if you only consider alsa. but on most systems, libxml2 is there
anyway. and imvho xml is less a matter of
taste than lisp. and xml is way easier to handle in other
contexts (i'm thinking of auto.configuration stuff etc.)
otoh, the embedded guys will probably n
Jaroslav Kysela wrote:
>>
>>other people might propose XML. then it becomes to a question whether
>>alsa-lib should rely on other libs...
>
>
> I think that XML is too overkill for our purposes.
>
>Jaroslav
>
true if you only consider alsa. but on most s
>btw, what was the biggest reason to change to XML in ardour?
>it used guile once upon a time.
i didn't like the fact that the entire main() call had to be
encapsulated within a guile invocation (given what ardour does with
memory, threads, scheduling, etc, etc). i also didn't like having to
requi
At Mon, 23 Jun 2003 09:41:32 -0400,
Paul Davis wrote:
>
> >my afraid is that the more control flows like conditionals may lead to
> >a difficulty for a parser utility. i.e. the parser itself would be
> >like an interprerter. but it's true that an extesion is needed
> >anyway...
>
> with a smile
>my afraid is that the more control flows like conditionals may lead to
>a difficulty for a parser utility. i.e. the parser itself would be
>like an interprerter. but it's true that an extesion is needed
>anyway...
with a smile, i seem to recall noting that we'd end up with
lisp. quasimodo had g
At Mon, 23 Jun 2003 14:01:08 +0200 (CEST),
Jaroslav wrote:
>
> > > * investigate a lisp integration to the current configuration syntax
> > > - we need to describe the relations between high level abstract
> > > layer (ordinary mixer) and current universal controls (very lowlevel);
> > >
On Mon, 23 Jun 2003, Takashi Iwai wrote:
> At Sun, 22 Jun 2003 21:10:31 +0200 (CEST),
> Jaroslav wrote:
> >
> > Hello all,
> >
> > here are my next goals for the ALSA library development (short
> > term). I invite all developers to comment these directions.
> >
> > * create ordinary pcm &
At Sun, 22 Jun 2003 21:10:31 +0200 (CEST),
Jaroslav wrote:
>
> Hello all,
>
> here are my next goals for the ALSA library development (short
> term). I invite all developers to comment these directions.
>
> * create ordinary pcm & mixer interfaces
> - proposed headers are in current CVS
25 matches
Mail list logo
