With ongoing preparation to "Integrate End User and Developer Resources
at linuxaudio.org" (workshop @ LAC2007) we are proud to announce a first
version of Dave's linux-sound application index as public-wiki:
http://apps.linuxaudio.org/
this is by far no cute end-user resource portal yet, but a first
step in merging data and setting up a prototype back-end!
We are looking for interested people to contribute at various levels and
suggest to use the mailing list for general discussion while keeping
dokuwiki and style related requests at
http://apps.linuxaudio.org/wiki:open_discussion
Further [major] back-end development on http://apps.linuxaudio.org/ will
probably not happen until LAC2007, but we are interested to tweak the
look and feel, fix bugs, and collect feedback.
We're also looking for qualified LAU's and LAD's to verify and maintain
the current content with editor privileges, responsibilities and deeds.
next up: docs.linuxaudio.org:
- static documentation (docbook, LateX, [x]html)
- slides and presentations (PDF, ps, png jpg,..??)
- music (collaborate with or outsource to freesound et al.)
- include (external?) video presentations, movies, etc
- source code (coding examples: wiki-page; svn-mirror/server ??)
for each hosted documentation there will be an option for user
annotation(s). eg. wiki-discussion page, blog-comments,
email-notify[-mailing-list]? - some of it will be merged with
apps.linuxaudio.org which will provide automatic indexing; details
remain to be discussed.
some of the intended supported formats imply moderation / maintained
upload or installation of static documentation. - the ring of
maintainers could evolve with key-signatures, and parts of the system
may become completely open. - suggestions:
http://apps-devel.linuxaudio.org/wiki:suggest_doc
ico & robin
Dear list members,
On the 1st of march at 0h00 GMT, the three LA* lists will be moved to
linuxaudio.org. What will it change for you ? not much :
¤ The new address you send your posts to will be :
linux-audio-announce(a)linuxaudio.org for LAA
linux-audio-dev(a)linuxaudio.org for LAD
linux-audio-user(a)linuxaudio.org for LAU
¤ All the user currently subscribed will be migrated automatically,
you do NOT need to create a new account
¤ Your password will be reset in the process, so will your parameters.
Sorry we cannot do better than this... To get a password reminder (the
first one should be automatically generated), you will find the lists
home page at http://lists.linuxaudio.org/
¤ The former addresses will still be valid, but when you will post to
them, you will receive a reminder asking you to post on the new list.
To avoid having duplicates when merging archives, the posts on the
former addresses _will not be received_ by the list members.
¤ We will have a bigger and faster server, a spamassasin setup and
interfacing with mailman is also in progress so administration will be
easier _and_ moderation will be less pain (thus faster to do).
I hope everything will go smoothly. If any of you run into trouble I
will be on #LAD(a)freenode.net during the migration and available at
"mobarre at linuxaudio dot org" which will be the new list admin
address to help you with anything you'd need.
Cheers,
__________________
Marc-Olivier Barre,
Markinoko.
Dear all,
thanks to many submissions from yourselves, we have been able to create an
extensive program for the Linux Audio Conference in Berlin in March,
featuring many paper presentations, tutorials, workshops and demos, and not
to forget concerts on each night of the conference.
(btw, if you still have some linux-made songs you would like to send in for
the Radio music, feel free to do so; there are no restrictions on genre
there, and we especially created that category to give a place for linux-made
recordings).
Below is the press release.
Hope to see you all in Berlin!
------------
The 5th Linux Audio Conference is taking place in Berlin (Germany) in 2007.
The TU-Berlin is hosting the conference in cooperation with people of the
Humboldt University Berlin, the Berliner Künstlerprogramm of the DAAD, the
festival MaerzMusik, the Instituto Cervantes Berlin and the Tesla Berlin.
The conference shows once per year important developments in the subject Â
making music with Linux and open source tools. Invited is everyone who is
interested in the possibilities of this platform.
The LAC is offering a wide range of workshops, tutorials and hands on demos.
There will be presentations on the subjects Computer Music, Music Production,
Drivers and Sound Architectures and Audio Distributions.
The LAC aims at bringing together developers and users of Linux and
open source audio software with the goal of information sharing, project
discussion and music.
Each day of the conference there is a concert which features music composed
and created with open source software. One of the highlights of the conference
is the demonstration of a auditorium of the TU-Berlin, that has been equipped
with a new spatialisation system (Wave Field Synthesis), driven by a
Linux-Cluster.
The program of the conference is now online and (free) registration is
possible.
Free admission to all events except to the concerts at the Tesla and the
MaerzMusik
LAC2007 22.3. to 25.3.2007, TU-Berlin, www.lac.tu-berlin.de
Hi all,
As discussed previously on this list, we are getting ready for a
migration of the three LA* lists to linuxaudio.org.
Many things are done to make our list better. One of them concerns
archives. As you may have noted, LA* archives found on
music.columbia.edu date back to 2002. Ico told me that there used to
be an LA list hosted somewhere else way before that (1998).
Having to do this migration, we will also migrate our archives. If
possible it would be cool to be able to merge also the older archives
in the whole.
The question is, do some of you have any idea where I could find these
archives, if they still exit...
Cheers,
__________________
Marc-Olivier Barre,
Markinoko.
"Carlo Trimarchi":
>
> My intention was to build an end-user application.
> One plays notes on the keyboard and it memorizes and shows them on a
> staff. There you can modify the duration of a note and other things
> and then playback.
>
> I wanted to implement some other functions: for example, one before
> choose the notes on the staff, the program plays it but with no sound
> and you have to follow the note and it tells you the errors in playing
> them. For example, wrong notes, bad timing...
>
> And well, I don't know yet what else. I have to think.
>
>> ad 1) see the other answers
>> ad 2) use pd (pure data), supercollider or something similar
>
Another alternative, in case you like lisp (who knows), is to use snd with
the realtime extension:
http://www.notam02.no/arkiv/doc/snd-rt/
I used it to make the san dysth softsynth:
http://www.notam02.no/~kjetism/sandysth/
Its performance is pretty good, but not perfect. So if that is
important, you can at least you can use snd to make a draft of your
program before you do some hardcore c or assembler programming.
(well, you can define your own functions in c though)
Hi, I need to build an application that can process sound from an
external instrument (a midi keyboard, for example). I also need to
create a graphic interface and I'd like to know which language maybe
best to do this.
Any suggestion?
Thanks, bye.
Hi!
I'm sorry to ask that here, but it seems I can't get an anser anywhere else.
Does the libstdc++ support UTF-8 strings? Or is there some simple example
code snippet somewhere to derive/modify something which would fullfill this
need?
Kindest regards and thanks!
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
> > > > you can think all you want. unless there a plugin->host callback that
> > > > allows the plugin to determine its operating environment in huge detail,
> > > > this kind of idea is pretty impossible to make use of.
> > >
> > > What?
> > > Once again: misunderstood! These optimizations involve that the
> > > "wrapper" (I should stop calling it this way) knows about the network
> > > of processing objects (read: plugins) and that these last ones contain
> > > "generic" information on their functionality (ex. STFT for LTI proc.
> > > objects).
> > > Then the wrapper takes care of optimizing the net.
> >
> > find me a host author who would want to use such a thing... managing
> > plugins is a central task of a host, and handing that over to some
> > "wrapper" that hides information from the host doesn't make the host's
> > life easier, it makes it more complex.
>
> In fact you wouldn't have to.
> You could just use it as a plugin wrapper, network representation and
> optimizazion would be of some use only for some (experimental?
> advanced? strange?) hosts.
> Personally, I would use such thing for my project.
> Then, who said that it has to hide such informations to the host?...
> It is definitively not a plugin arch wrapper, but a kind of
> "inter-application jack-like connectivity tool for processing objects
> with already existing plugin archs wrapping and network optimization
> capabilities".
> As it goes when you build a GTK app, you don't have to use each
> library function, and so it would become just a plugin wrapper.
> Maybe the two things can be split, but maybe optimization could hardly
> depend on each processing object interface (aka plugin format).
Well, I thought about it last night, and maybe the whole thing could
be split in three parts:
1. A modular processing object format wrapper (one module for each format)
2. A GUI generation and handling (and maybe embedding? XEMBED?)
wrapper with format-specific modules and toolkit-specific modules
3. A library with network representation, optimizing and processing
capabilities.
What do you think about it?
Stefano
I've been using jack and qjackctl with audacity under Linux (FC6). It
seems to be working OK with 1 approx 1 msec xrun in a half hour
recording session, when unfortunately my backup system kicked in.
However there's something I don't understand about jack, even after
reading a lot of the documentation. At the bottom of the qjackctl
window is a set of arrows, like on an audio control device. When I
click on the arrow pointing right, the green "Stopped" in the main
window changes to "Rolling". What does this mean? What are the other
arrows for? No useful info on the web.
The above recording session was done while jack was "Stopped". Would
jack work better if it were "Rolling"?
Please excuse these elementary questions.
Thanks - jon