Dear fellow Linux enthusiasts and consortium members,
Please allow me to bring to your attention the upcoming L2Ork debut:
On December 4th Virginia Tech DISIS (<http://disis.music.vt.edu>) Linux
Laptop Orchestra (L2Ork, <http://l2ork.music.vt.edu>) will hold its first
sneak preview debut performance on Virginia Tech (VT) campus, Squires Studio
Theatre, starting at 7pm. Admission is free.
At noon on the same day, L2Orkists will also host a demo booth outside the
Commonwealth Ballroom in Squires Student Center (VT campus) demoing how
L2Ork works.
For additional info on L2Ork and a video preview of L2Ork in rehearsal:
<http://l2ork.music.vt.edu>
Facebook Event Page:
<http://www.facebook.com/home.php#/event.php?eid=180832548428&ref=mf>
Sincerely,
Ivica Ico Bukvic, D.M.A.
Composition, Music Technology
Director, DISIS Interactive Sound & Intermedia Studio
Assistant Co-Director, CCTAD
CHCI, CS, and Art (by courtesy)
Virginia Tech
Dept. of Music - 0240
Blacksburg, VA 24061
(540) 231-6139
(540) 231-5034 (fax)
ico(a)vt.edu
http://www.music.vt.edu/faculty/bukvic/
Dear reader,
as has been announced here 2 days ago by Marc Groenewegen, the next Linux
Audio Conference (LAC#8) will take place at the HKM in Utrecht, Netherlands,
from May 1st - 4th, 2010 (see http://lac.linuxaudio.org/2010).
We have now opened the Website that accepts paper submissions. Please direct your
browser to http://lac.linuxaudio.org/2010/openconf
For those who have been following the LAC activities in the past years: It's
the same used&tested "OpenConf" web-based system that allows us to easily collect
paper submissions, review them and create a programme from accepted papers.
The available categories for paper submission looks like this:
* Ambisonics
* Education
* Live performance
* Audio Hardware Support
* Signal Processing
* Music Composition
* Audio Languages
* Sound Synthesis
* Audio Plugins
* MIDI
* Music Production
* Linux Kernel
* Physical Computing
* Interface Design
* Linux Distributions
* Networked Audio
* Video
* Games
* Media Art
* Licensing
Note that "Video" is also in the list. Yes, that's not strictly Audio :-), but
we feel that the two disciplines are close enough to one another to allow
opening up the conference scope a bit here. After all, we have already had
several very nice audio/video gigs in the past (some might remember the YUE
concert in Karlsruhe 2006 with a remote VJ live from Italy, which was pretty
groundbreaking at that time).
Also, we very much welcome practical papers resp. software demos ("how I use
Linux Audio applications to create my music/media art").
The web page also holds the paper templates that have to be used for submissions.
Pick one of the two provided templates (LaTeX or OpenOffice), author your paper
and convert it to PDF, then upload that PDF. Make sure you are using A4 as
paper size.
Some constraints:
- The conference is held in English, so the paper has to be in English too.
- Length of a paper is 4-8 pages. Papers have to include an abstract (50-100
words). Also, papers should include up to 5 keywords.
- The copyright of the paper remains with you (of course), but we reserve the
right to create printed proceedings from all submitted (and accepted) papers.
- We have fixed the following dates:
- Deadline for paper submissions: February 14th, 2010
- Notification of paper acceptance: March 14th, 2010
- Deadline for final version of paper: April 4th, 2010
Please note that the OpenConf system is only to be used for paper submissions;
for concert pieces ("Call for Music") or sound installation proposals, please
contact us directly by email ("lac -at- linuxaudio -dot- org ").
We are looking forward to many interesting submissions for the 8th
Linux Audio Conference and we hope to see you in Utrecht in 2010!
Please feel free to forward this e-mail to anybody who might be
interested - mailing lists, blogs, Linux portals, magazines, you name them.
Public relation work for this conference is something we need, and where
everybody can easily help.
Thanks for reading.
On behalf of the LAC2010 organisation team,
Frank Neumann
Hi everyone,
Jackbeat, the minimal-but-nevertheless-useful multi-platform step sequencer, has
just reached version 0.7.3 !
This is mainly a bugfix release, that you can grab from:
http://jackbeat.samalyse.org
It's easy to build and easy to try.
News
~~~~
- Tracks can now be reordered
- A buffer overflow and a bug preventing to load some jab files have been fixed
ChangeLog
~~~~~~~~~
jackbeat (0.7.3)
* #40: allow to reorder tracks (move up/down)
* #43: fix buffer overflow in core messaging routine
* fix bogus track name conflict when loading jab, thanks Florent
Enjoy
--
Olivier
Tarball containing D-Bus patched jack 0.118.0 is available here:
http://nedko.arnaudov.name/soft/jack/dbus/http://nedko.arnaudov.name/soft/jack/dbus/jack-audio-connection-kit-dbus-0.…http://nedko.arnaudov.name/soft/jack/dbus/jack-audio-connection-kit-dbus-0.…
D-Bus modifications add optional autodetected support for the D-Bus
based server control system.
D-Bus is object model that provides IPC mechanism. D-Bus supports
autoactivation of objects, thus making it simple and reliable to code a
"single instance" application or daemon, and to launch applications and
daemons on demand when their services are needed.
* Simplified single thread model for control and monitor
applications. Various D-Bus language bindings make it trivial to
write control and monitor applications using scripting languages like
Python, Ruby, Perl, etc..
* JACK has log file (~/.log/jack/jackdbus.log) that is available for
inspection even when autoactivation happens because of first JACK
application is launched.
* There is real configuration file used to persist settings that can be
manipulated through configuration interface of JACK D-Bus object.
* Improved graph inspection and control mechanism. JACK graph is
versioned. Connections, ports and clients have unique (monotonically
increasing) numeric IDs.
* High level abstraction of JACK settings. Allows applications that can
configure JACK to expose parameters that were not known at compile
(or tarball release) time.
Currently there are some minor differences between jack1 jackdbus and
jack2 jackdbus:
* There is no parameter constraints support (no enums and no ranges)
* No get client pid function (probably affects lash)
* Settings file (in ~/.config/jack/) is conf-jack1.xml instead of
conf.xml, because jack1 and jack2 settings and not really compatible.
When configured with D-Bus support, jack_control is
installed. jack_control is simple commandline interface for jackdbus.
Other tools that can communicate with JACK through D-Bus:
* LADItools (tray icon, configuration, etc.)
* Patchage (and lpatchage too)
* LASH 0.6.x
* ladish
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Tarball containing D-Bus patched jack 0.117.0 is available here:
http://nedko.arnaudov.name/soft/jack/dbus/http://nedko.arnaudov.name/soft/jack/dbus/jack-audio-connection-kit-dbus-0.…http://nedko.arnaudov.name/soft/jack/dbus/jack-audio-connection-kit-dbus-0.…
D-Bus modifications add optional autodetected support for the D-Bus
based server control system.
D-Bus is object model that provides IPC mechanism. D-Bus supports
autoactivation of objects, thus making it simple and reliable to code a
"single instance" application or daemon, and to launch applications and
daemons on demand when their services are needed.
* Simplified single thread model for control and monitor
applications. Various D-Bus language bindings make it trivial to
write control and monitor applications using scripting languages like
Python, Ruby, Perl, etc..
* JACK has log file (~/.log/jack/jackdbus.log) that is available for
inspection even when autoactivation happens because of first JACK
application is launched.
* There is real configuration file used to persist settings that can be
manipulated through configuration interface of JACK D-Bus object.
* Improved graph inspection and control mechanism. JACK graph is
versioned. Connections, ports and clients have unique (monotonically
increasing) numeric IDs.
* High level abstraction of JACK settings. Allows applications that can
configure JACK to expose parameters that were not known at compile
(or tarball release) time.
Currently there are some minor differences between jack1 jackdbus and
jack2 jackdbus:
* There is no parameter constraints support (no enums and no ranges)
* No get client pid function (probably affects lash)
* Settings file (in ~/.config/jack/) is conf-jack1.xml instead of
conf.xml, because jack1 and jack2 settings and not really compatible.
When configured with D-Bus support, jack_control is
installed. jack_control is simple commandline interface for jackdbus.
Other tools that can communicate with JACK through D-Bus:
* LADItools (tray icon, configuration, etc.)
* Patchage (and lpatchage too)
* LASH 0.6.x (may not work properly with jack1 jackdbus implementation)
--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
I have started a new project called Composite, which is planned to be a
sequencer for live-performance sequencing, sampling, and looping. One might
say that it will be like Ableton Live. It will be an LV2 host for synths and
effects, and will have a built-in sampler (which will probably be an LV2
plugin).
At this time, the project is in the planning stages.[1] Anyone who is
interested is invited to join the mailing list and share your thoughts and
opinions -- especially as it relates to UI and workflow.[2]
Links......
Project: http://gabe.is-a-geek.org/composite/
Mailing List: http://groups.google.com/group/composite-dev
Code: http://gitorious.org/composite
Specs (WIP): http://gabe.is-a-geek.org/composite/specification.html
FAQ: http://gabe.is-a-geek.org/composite/faq.html
Thanks especially to Patrick Shirkey for stirring things up.
Peace,
Gabriel
CC: LAU, LAD, LAA, Composite-Dev
[1] Strategy: Create a published spec. of what we want to
accomplish, and then get after it. There is currently
no code, but we plan to steal as much as we can.
[2] However, these will probably *not* change:
+ Will be monolithic. Let's not start a monolithic
vs. modular debate.
+ Will use Qt and C++.
I have started a new project called Composite, which is planned to be a
sequencer for live-performance sequencing, sampling, and looping. One
might say that it will be like Ableton Live. It will be an LV2 host for
synths and effects, and will have a built-in sampler (which will probably
be an LV2 plugin).
At this time, the project is in the planning stages.[1] Anyone who is
interested is invited to join the mailing list and share your thoughts and
opinions -- especially as it relates to UI and workflow.[2]
Links......
Project: http://gabe.is-a-geek.org/composite/
Mailing List: http://groups.google.com/group/composite-dev
Code: http://gitorious.org/composite
Specs (WIP): http://gabe.is-a-geek.org/composite/specification.html
FAQ: http://gabe.is-a-geek.org/composite/faq.html
Thanks especially to Patrick Shirkey for stirring things up.
Peace,
Gabriel
CC: LAU, LAD, LAA, Composite-Dev
[1] Strategy: Create a published spec. of what we want to
accomplish, and then get after it. There is currently
no code, but we plan to steal as much as we can.
[2] However, these will probably *not* change:
+ Will be monolithic. Let's not start a monolithic
vs. modular debate.
+ Will use Qt and C++.
BigBand is a program to compose real music for real musicians.
If you are interested then please visit:
members.chello.nl/w.boeke/bigband/index.html
BigBand should be easily portable to different Linux versions as
it is built using only the SDL libraries for graphics and sound.
Kind regards,
Wouter Boeke
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bonjour,
We've just added a new service to linuxaudio.org:
http://planet.linuxaudio.org/
..to make it easy to keep up on what people are up to in general and you
can browse the planet to see who you'd like to follow..
If you want your blog to be included in planet.linuxaudio.org, visit:
http://wiki.linuxaudio.org/wiki/planet
Kudos to Dave Robillard and Erik de Castro Lopo for suggesting and
pushing this idea.
Cheers!
robin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkr0IeMACgkQeVUk8U+VK0I+cACgrbxIg1I5wLzgoiGzWUrTnwWz
Qg4AoKr9xOfCO/ArCPN8x9nB3wxN7eKl
=zulW
-----END PGP SIGNATURE-----