Dear Linux Audio Developers,
Bernard Bel and I are very happy to announce to you that a powerful tool for
computer-aided composition using Csound or Midi -- the Bol Processor -- is
being reborn as open source software! While the software only runs on
Macintosh computers at this time, we are hoping that some savvy Linux
developers with porting experience will be interested in joining the
project.
Thanks! (And please email me directly if you want to see the source code in
a more Linux-friendly format :)
Details are below ...
----------
From: Bernard Bel <bel(a)lpl.univ-aix.fr>
Reply-To: bp2-list(a)yahoogroups.com
Date: Mon, 8 May 2006 12:48:54 +0200
To: bp2-list(a)yahoogroups.com
Subject: [bp2] Bol Processor going Open Source!
[Please circulate]
Bol Processor is a program for music composition and improvisation with
real-time MIDI, MIDI file, and Csound output. It produces music from a set
of rules (a compositional grammar) or from text scores typed or captured
from a MIDI instrument. Bol Processor 2 was a shareware application
developed by Bernard Bel with the help of Jim Kippen and Srikumar Karaikudi
Subramanian. BP2 won the Bourges 1997 international award (ex aequo with
Cecilia) in the category of computer-aided composition and realization
software. More information about the capabilities of BP2 is available at
<http://www.lpl.univ-aix.fr/~belbernard/music/>.
Bol Processor is now being released as free software (open source) under a
BSD-style license. BP development is hosted by Sourceforge at
<http://bolprocessor.sourceforge.net/>. We are looking for several
developers to join the project to help with porting and to decide the future
directions that the software will take. If you are interested in helping,
please email Anthony Kozar for more information.
BP2 currently runs on the Classic MacOS. (However, its OMS MIDI driver,
including QuickTime music, only runs on machines booting MacOS 9.) One of
the goals of the open-source project will be to port it to other platforms.
We are hoping that Bol Processor 3 will at least run on MacOS X, and ports
to Windows and Linux are also possible depending on the desires and
expertise of the group of developers that can be assembled.
Two files are now available in the release section of the Bol Processor
Sourceforge site. There is a MacOS disk image with the BP 2.9.5 beta
application and another disk image with copies of all of the source files to
build it. The source code has also been added to the BP CVS repository.
This release is a snapshot of the current state of the project and
interested developers are encouraged to download the files and start looking
them over. Users will probably want to stick with version 2.9.3 for now but
are welcome to try out 2.9.5 beta as well. Note that we have not yet
removed the shareware registration notices, so please disregard them.
There is a mailing list for discussion of BP2 at <bp2-list(a)yahoogroups.com>
and there should soon be a developer mailing list hosted by the Sourceforge
project. Please join and help us determine the future of Bol Processor !!
Bernard Bel <bel(a)lpl.univ-aix.fr>
Anthony Kozar <anthonykozar(a)sbcglobal.net>
BP2 Yahoo! Groups Links
<*> To visit the BP2 group on the web, go to:
http://groups.yahoo.com/group/bp2-list/
<*> To subscribe from this group, send an email to:
bp2-list-subscribe(a)yahoogroups.com
Hi!
Requirements in order of importance, highest first:
- not likely to get us into legal trouble
- no too obvious negative interpretations/associations
("too obvious" because it's too hard, internationaly, otherwise)
- no conflict with established open source projects
- easy to search for
Pretty much every 3 letter combo is in use by some company or
institute. Few are pronounceable. It's similar with 4 letters.
Suggestions with few (and not relevant looking) or no Google hits:
splugs - stream processing plugins
sppib - stream processing plugins in bundles
laspib - linux audio ...
buspp - bundled stream processing plugins
streamins - streaming/stream-processing plugins
sprocins - stream processing plugins
[Streaming because there are continuous i/o streams of data
as far as I understand, while there's no limitation to
audio/float anymore. Corect me if I'm wrong.]
Cheers,
Thorsten Wilms
http://plugin.org.uk/ladspa2/
Changed name of the port shortname property to "symbol", which hopefully
implies more the right thing.
Added Rate before Control and Audio port names to hopefully make thier
menaing clearer for people who may not come from a LADSPA background.
This is just fiddling really, so I think it's starting to settle down.
- Steve
I've had this request on a non-Linux list:
Can you provide more feedback (about) ... multimedia players capable of
decoding Dolby AC3, DTS, DVD-Audio, etc. on a Linux machine?
What about software players running on a CAR-PC and surround-capable?
I know very little about the whole field of multimedia players
for proprietary formats on Linux. Can someone fill in the gaps ?
- which apps are available ?
- are they open-source ?
- what interfaces (ALSA, JACK, OSS, ...) do they have ?
- do they require Windoze emulation ?
- what is their maintenance state ?
- etc.
Many thanks,
--
FA
Follie! Follie! Delirio vano e' questo!
Hi,
I saw this thread earlier on this list about the Edirol UA-101 external
audio interface: http://lalists.stanford.edu/lad/2005/09/index.html#162
I'm trying to use the same device, but strangeley enough, it doesn't
even get recognized. Looking at both the kernel sources and at the
alsa-driver sources, I see the following comment:
./sound/usb/usbquirks.h: /* TODO: add Edirol UA-101 support */
how did you guys make it work?
Akos
http://plugin.org.uk/ladspa2/
Removed the :logarithmic hint, I agree with Paul, its not
fit-for-purpose as specified.
I'm now using the DOAP schema (http://usefulinc.com/doap) instead of Dublin
Core for software information, much more appropriate.
Fixed a load of typos in the schema and examples.
Dave R. doxygen-ised the .h and added some text about choosing URIs.
I removed the references to run_adding() (I think I got them all).
- Steve
To close this thread for now.
Thank you all for your kind and useful responces.
However, it turned out that the main showstopper is visa.
We can't get it for such a long time (a month), as it would be our first one.
Things get even more complicated, since my girlfriend right now is not
a student and does not have a job. They say we should build our
"Shengen history" and after one-two (more - better) short and regular
tours we can hope to get month-long visa anywhere we want.
Taking this into account, we have to postpone our Trip to the next
year and try to make two tours to shengen this year.
It's a pity, since tours via travel agencies are about twice as
expensive, but they are our only legal gates to europe.
Moveover, the choice of the first place to visit is also restricted.
We wanted to make London-Paris tour, but GB has very strict rules and
rules us out. Possibly, it will be France and/or Italy as the most
permissive ones.
Will try to match our DreamTrip with the next LAC.
Kind regards,
Dmitry.
Quoting Esben Stien <b0ef(a)esben-stien.name>:
> Steve Harris <S.W.Harris(a)ecs.soton.ac.uk> writes:
>
> > LV2
>
> What happened to the funny recursive acronyms?;). That they don't show
> up in a google search don't hold water; f.ex a search for JACK get
> you.. our beloved, sacred one.
>
> How about a girlie name to accompany JACK, then?;)
How about both recursive and a girlie name?
BELLA = BELLA Effects Layer for Linux Audio
(B could also be Bitchin')
Sampo
Richard's preferred name of "PEA" (AKA anything that's not LADSPA2) got me
to thinking. What about abstracting it up one level and calling the
directory + .so files + manifest thing a POD (Plugin Object and
Description). Theres nothing particularly audio specific about the high
level construct, its "just" that we don't have a concrete ABI for dealing
with sills, video etc.
This means that what we think of as a "LADSPA2" plugin would be a
"LADSPA POD". The directory would have a .pod extension.
POD seems like a nice word to me, plenty of scope for puns, short and "pod
plugin" on google doesn't come up with anything much. The only audio
related things for "pod" I could see are: a guitar effects processor called
a PODxt (there was a POD historically), an audio I/O device called a
Firepod, and the documentation for the LADSPA Perl module. Perl docs
are the only non-coincidental hits for "LADSPA POD".
I could juggle the description stuff around the seperate pod-ness from
ladspa-ness, it's not hard, but also not neccesary.
There is a small name clash with Perl, which uses .pod for it's
documentation format, but I dont think that's really an issue, our .pods
will be found in POD_PATH (eg. /usr/lib/pod/, ~/.pod/) and be will be
directories.
Thoughts?
- Steve