hi *!
the linux audio conference 2006, which takes place at the zkm in
karlsruhe/germany from april 27 to april 30, will be streamed live for
your convenience, inspiration and enjoyment.
all presentations (which are listed on
http://lac.zkm.de/2006/program.shtml) are covered as ogg vorbis audio
streams in two bitrates (one for modem users and one for
slightly-more-broadband users) and ogg theora/vorbis a/v streams (for
broadband users only). to watch and/or listen, you can use a recent
version of mplayer, vlc or curl | theora123, if you prefer.
the stream urls are listed at
http://lac.zkm.de/2006/streaming.shtml. we will start test streams
tomorrow by 12:00 utc+2. as always, there will be chat channels to go
with the streams, where you can report problems, discuss the
presentations and also ask questions which will be relayed to the live
audience by the local chat operators here at zkm.
these channels are #lac2006 for general issues and chitchat, and
#lac2006-track1 and #lac2006-track2 for questions and remarks about the
current presentation, all on irc.freenode.net.
you will be able to download the presentation slides in advance to read
along as you listen and watch. the quality of the video streams will not
be sufficient to read the projections, but you should easily be able to
make out which slide is currently up.
on behalf of eric rzewnicki (who did most of the streaming work this
year) and the rest of the lac organizational team i wish you lots of fun
with the streams. kudos again to the icecast team, especially to karl
heyes, all the folks at xiph.org who brought us all those great free
multimedia codecs, and the crew here at zkm for their great support and
cooperation!
best,
jörn
I have SCONS installed and when i type scons, it gives me this:
Checking for libsigc++-1.2...
Package sigc++-1.2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `sigc++-1.2.pc'
to the PKG_CONFIG_PATH environment variable
No package 'sigc++-1.2' found
I've been trying to build this for hours and I can't find sigc++1.2.pc
anywhere.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Hi all,
as it is LAC time, it's also release time :) .
Simple Sysexxer is a GUI sysex tool comparable to Sysexxer, but it's
based on Qt4 (no KDE dependency) and ALSA only (no OSS dependency).
Theoretically it should also build and run on Mac OS X, but I didn't try
it yet.
Feedback and bugreports are always welcome.
Information and source code:
http://www.christeck.de
Best regards
ce
maybe someone here can help?
<paniq> i need a decoder library that works on win32/linux, can decode
wav/ogg/mp3, can seek with sample precision and supports rendering of
userdefined frame sizes
<larsl> I'd say libsndfile, but it doesn't do MP3.
<paniq> which isnt that bad tho. i hate mp3.
<larsl> http://www.mega-nerd.com/libsndfile/
<paniq> no ogg support
<paniq> only support for wav files
<paniq> i'm not fond of adding separate libs with different apis to
access different audio codecs
--
-- leonard "paniq" ritter
-- http://www.mjoo.org
-- http://www.paniq.org
I'm in a cruft killing mood.
Has anyone ever used ImplementationData? I know I haven't, and I goggled
for it, but all I found was the ladspa.h file, which has a comment to the
affect of: we're not sure why you'd need this, but, just incase here's a
void *.
If anoyone has used it, or has a potential use for it, it should stay, but
otherwise it should go IMHO.
- Steve
I've added the port shortnames (ladspa:shortname). This is still tentative
in my mind, but as long as it doesn't cause any serious objections it will
stay.
Following a suggestion from Richard Furze I've removed the LADSPA_Data
type and replaced it with void. The ports are datatyped in the data, but
currently only ladspa:float is supported. I have misgivings about this,
but it seems like a good way to open up to more datatypes in the future.
I'd hate to see a future where there are plugins for translating between
different kinds of boring PCM data, that would suck, but this could allow
for some exciting developments. The first person to make a LADSPA plugin
that speaks 16bit int PCM audio data gets the LART treatment ;)
Thoughts?
- Steve
I like the bundle idea. What are the reasons to not use it? Reasons to use it include ease of distribution (especially on other platforms like osx).
I think bundles are a great idea that should be adopted by other unixen.
Or, can we make it so that bundles are a possible method of distribution and either it or the typical installation into various directories could be used?
Taybin
We haven't heard from a number of key people yet, but I think the overall
impression is positive so far. There are a number of decisions that need
to be made if it's going to go ahead. Either things that I didn't
consider, or where I made arbitrary choices:
A) Dropping runAdding: personally I dont think runAdding is worthwhile. How
many hosts take advantage of it? Its something LADSPA 1.1 can do and 2.0
wouldn't be able to though.
B) RDF syntax: RDF/Turtle seems a lot more popular in these parts than
RDF/XML. We could mandate Turtle for all LADSPA metadata.
C) Port scales: these weren't really in LADSPA 1.x, but they were in lrdf, so
adding them is a bit arguable. I think they're clearly beneficial though,
and they are getting close to critcal mass recently.
D) Port shortnames: for OSC, Pd etc. access. I dont have a strong feeling on
that. It /is/ an extension, but retrofitting it will mean OSC servers etc.
will have to support both accessor methods.
E) Bundles: no-one screamed when I suggested it, but its a bit different to
LADSPA 1's /lib directory. Hosts would be required to allow the plugin
link to libraries in the bundle if they need to (this is why OPENSTEP did
it, I guess its done by setting LD_LIBRARY_PATH, but I dont know), which
is a bit more work, but makes moving plugins between machines easier. Oh,
and the plugins needs to have the path of its bundle passed to it when its
instantiated, which isn't in the API right now.
F) Host OS specific macros in ladspa-2.h that Jack O'Q suggested. It seems
like a reasonable idea to me. No need to punish users of inferiour OSs
more than they are allready ;)
- Steve
http://plugin.org.uk/ladspa2/
First of all, I realised I was being cheeky by adding a feature I wanted
(units), while refusing to consider anyone elses! So, I removed the units
property from the Amp plugin. I'm happy to consider it a testcase and I
will make a schema for it and start using it when/if LADSPA2 gets OKd by
the community.
I made 2 actual ABI changes:
The path of the directory/bundle is passed to instantiate(). This is
neccessary to make it actually useful. It could have been passed to other
methods, but that seemed most appropriate.
For some potential features, like Fons' polyphonic control ports, it's hard
for the plugin to detect wether the host is using the feature or not. I
added an array of URIs to instantiate() that lets the host tell the plugin
what hints etc. it supports. The plugin can then refuse to instantiate or
fall back if it doesn't like the featureset.
I also added some (silly) scale points to the Amp plugin, just to show how
it's done, and I added translations to some of the strings, to show how
that's done.
- Steve