========================================================================
L'Ircam organise dans le cadre de Résonances 2003 une journée pour faire
le point sur les logiciels libres dans le domaine musical et audio
professionnel, l'évolution de Linux vers plus de facilité d'utilisation,
les compatibilités avec les équipements audio, les drivers audio et
MIDI.
Date : Jeudi 23 octobre 2003, de 10h à 18h
Lieu : Ircam, Studio 5
Conditions d'accès : entrée gratuite sur inscription auprès de
Sylvie.Benoit(a)ircam.fr, en fonction des places disponibles
Les présentations sont disponibles en ligne et sont diffusées en
streaming audio, vous pouvez les suivre en direct et intervenir par le
canal IRC:
- programme et présentations:
http://freesoftware.ircam.fr/article.php3?id_article=64
- streaming : http://freesoftware.ircam.fr:8000/resonances.ogg
- IRC : site irc.linux.org, channel #ircam
Pour plus d'informations: http://freesoftware.ircam.fr,
http://resonances.ircam.fr
========================================================================
Ircam organizes during Résonances 2003 a one-day conference to have an
update on free musical and professional audio software, the evolution of
Linux towards an easier use, compatibility with audio equipment, audio
drivers and MIDI.
Date : Thursday, October 23rd, 2003, 10:00am to 06:00pm
Venue : Ircam, Studio 5
Access conditions : Free entrance upon registration :
Sylvie.Benoit(a)ircam.fr, depending upon available seats
Important : presentations are available on line and are streamed, you
can follow the talks and ask questions using the IRC:
- program and presentations :
http://freesoftware.ircam.fr/article.php3?id_article=65
- streaming : http://freesoftware.ircam.fr:8000/resonances.ogg
- IRC : site irc.linux.org, channel #ircam
For more informations: http://freesoftware.ircam.fr,
http://resonances.ircam.fr
========================================================================
Hi all,
LADCCA's now reached a state where I reckon it's worth releasing again.
It's pretty stable for me, and it now seems to do what it should without
any hiccups. I'm releasing alsa patch bay and jack rack along with it
as the only changes are support for the new ladcca version. ALSA Patch
Bay has had 1.0-ness for a while now so I'm taking the opportunity to
bump the version. There's only two other supported apps at the moment,
muse, which already has 0.4.0 support in cvs and fluidsynth, a patch for
which is included in the tarball.
From the ladcca NEWS file:
* low level tcp protocol has changed along with a lot of structure clean
ups on the client- and server-side.
* added low level protocol versioning
* well defined server interface protocol (that works! :) this has been
the bulk of the work that's added two more properties to cca_event_t,
client_id and project, bumped the major version of the high level
protocol and caused more changes to the low level protocol
* new high level normal client event, CCA_Server_Lost
* removed CCA_Use_Jack and CCA_Use_Alsa client flags; sending the server
the jack client name or alsa client id now suffices
* major amounts of cleanups and fixes
* server now saves project info in XML which means a new dependency on
libxml2
* socket stuff now uses protocol-agnostic system calls and the server
defaults to IPv6. an entry in /etc/services is required to support
this. make install will install an entry if there isn't one present.
this can be disabled with a configure option, --disable-serv-inst.
there's also a new option for ladccad, --no-ipv6 which, suprisingly,
stops the server using ipv6.
* the --with-default-dir configure option and -d ladccad option now set
the directory relative to $HOME, rather than being a system-wide
directory
* project directories now get cleaned up if they haven't been saved
* updated the manual
Patches
* fluidsynth cvs
http://pkl.net/~node/ladcca.htmlhttp://pkl.net/~node/alsa-patch-bay.htmlhttp://pkl.net/~node/jack-rack.html
Bob
--
Bob Ham <rah(a)bash.sh>
"At some point, keystroke recorders got installed on several machines at
Valve. Our speculation is that these were done via a buffer overflow in
Outlook's preview pane." -- Gabe Newell on the Half-Life 2 source leak
1)is API monolithous or there are sub-APIs
like GMPI-audio, GMPI-seq, GMPI-control
2) Explicit versioning for API?
3) Explicit versioning for plugins?
4) uniq IDs for plugins?
who is authority?
5) format for plugin state saving:
XML? (damn its ugly!)
I vote for more YAML-like language.
6) Should the GMPI discussion produce
reference plugin implementation
reference host implementation
reference tools implementation
7) Can there be off-line non real-time plugins?
8) Should the specification produce
any requirement for more documents?
For example:
A documant describing standard set of plugins
(like in General Midi) so one could expect
the first 64 plugins to be so and so.
horsh
Well it's just requirements?
Then what about :
1) jack-transport-like and
2) LADCCA-like functionality?
the requirement resolution could sound as:
"GMPI does not need such functionality",
but if it souns as "GMPI _does_ need..."
then it would be very welcome.
horsh
====================8<==========================
One of my tasks as part of GMPI is to provide a draft of the requirements
doc. I turn tp you all. If you have requirements that you think should be
in GMPI - please let me know. These have to be requirements. Not
handwaving though explosions, and not wishful dreaming. Things that are
required or desired that will make GMPI be the open music platform we need.
Feel free to email me privately or publicly. I'll be happy to condense
ideas and to extract requirements from whatever you have for me.
Trying to get the ball rolling again...
Tim
One of my tasks as part of GMPI is to provide a draft of the requirements
doc. I turn tp you all. If you have requirements that you think should be
in GMPI - please let me know. These have to be requirements. Not
handwaving though explosions, and not wishful dreaming. Things that are
required or desired that will make GMPI be the open music platform we need.
Feel free to email me privately or publicly. I'll be happy to condense
ideas and to extract requirements from whatever you have for me.
Trying to get the ball rolling again...
Tim
--
Notice that as computers are becoming easier and easier to use,
suddenly there's a big market for "Dummies" books. Cause and effect,
or merely an ironic juxtaposition of unrelated facts?
>It's called OProfiler.
>"OProfile can help you identify issues such as loop unrolling, poor cache
>utilization, inefficient type conversion and redundant operations, branch
>mispredictions, and so on."
There is an oprofile rpm supplied with RedHat 9
Hi,
This seems like an interesting article, describeing a new kernel
service/application in 2.6.
http://www-106.ibm.com/developerworks/library/l-oprof.html?ca=dnt-441
It's called OProfiler.
"OProfile can help you identify issues such as loop unrolling, poor cache
utilization, inefficient type conversion and redundant operations, branch
mispredictions, and so on."
Just thought I'd pass it on.
/Robert