Linux-audio-dev April 2006

linux-audio-dev@lists.linuxaudio.org

99 participants
74 discussions

[linux-audio-dev] LADSPA2 name early consensus

by Steve Harris

OK, it seems like the consensus is clear to me. So far, most people want to use/keep LADSPA2. I ran it through a condorcet program, just to make sure, but it't not in doubt. FWIW, by my count the pure "acceptable" numbers came out as: 17 ladspa2 7 xap 6 peep 5 apa 4 sax 4 plux 3 rap 2 peeper 2 eep 1 wasap 1 sap 1 pea 1 openplux 1 lapa 1 fap 1 clap 1 chap And the condorcet pattern was: 9 ladspa2 1 ladspa2>apa>sax 1 ladspa2>plux 1 ladspa2>sap>xap>peep>peeper>sax>fap>eep>clap>chap>apa>rap>pea>wasap>rap 1 ladspa2>lapa>plux>xap 1 openplux>plux>ladspa2 1 peep 1 peeper>peep>apa 1 plux>apa>ladspa2 1 sax>eep>xap 1 xap>apa>ladspa2 1 xap>peep 1 xap>rap>peep 1 xap>sax>peep>ladspa2 Only 23% of those voters would find LADSPA2 unacceptable, next best is XAP which 68% would find unacceptable. I wasn't especially rigourous, so I may have missed, or misinterpreted someones vote. Someone could poll the LAU list if they felt inclined. I think that we should give the people who's names appear on the original .h file a veto, as were doing some radical changes to the design - though hopefully still in the spirit of the original. It doesn't look like we'd ever reach consensus on any other name though. *sigh* I guess I should invest in an anti-RSI keyboard. - Steve

18 years

[linux-audio-dev] Re: "LADSPA2" name

by Kjetil S. Matheussen

I vote for "LADSPA" as well.

18 years

[linux-audio-dev] "LADSPA2" name early consensus?

by Steve Harris

Discusson seems to have slowwed down a bit, so I went through the list archive and pulled out all the names: apa chap clap eep fap ladspa2 pea peep peeper rap sax wasap xap ---- I vetoed ape and meep as the name clashes are too close. To see if theres early consensus lets run a condorcet vote on the options. If everyone posts thier preference in order seperated by >, eg. foo>bar>baz means "I'd like foo, but if I cant have that I'l have bar, and if I cant have that I'l have baz, everything else is unacceptable". Then we can run it thorugh an online voting system. - Steve

18 years

[linux-audio-dev] Re: [linux-audio-user] LAC 2006 Live Streams

by Joern Nettingsmeier

Hans Fugal wrote: > That sounds great! Will these also be available for download afterwards? > yes, if all goes well. we will not have time to edit them, but if someone volunteers, we can upload the raw dumps immediately after they are done, in 30min chunks. any takers? jörn

18 years

[linux-audio-dev] "LADSPA 2" name

by Steve Harris

Several people have suggested that LADSPA is not a great name for what we are calling LADSPA 2. Reasons for this include: The L, it's not really linux specific, and though /we/ know that its the L of LAD, its not obvious to people outside. The S, it ain't really going to be simple. For someone like me, who is neck deep in triples on a daily basis, 2.0 seems like the paragon of simplicity, but I can imagine 2.9 being quite a beast. LADSPA, (pron. ladspuh?) is a bit of a mouthful, and not exactly catchy. 2.0, it's not going to be obvious to all users that 2.0 and 1.0 are binary incompatible. I'm not sure everyone thinks in major and minor revisions. So, with some trepidation I suggest that we think about naming, with the proviso that if we haven't reached consensus by May 10th we default to LADSPA 2.0, and live with the pain. ---- My suggestion is that we ressurect the XAP name (http://www.google.com/search?q=lad+xap) It stood for Xap Audio Plugin IIRC. Pros: it's short*, relatively unused** and pronouncable*** Cons: xap.{com,org,net} will have gone long ago (too short), theres a small ammount of baggage. - Steve * I've typed LADSPA_ a lot ** There is a home automaption protocol, called xAP that takes plugin modules. Though I think we started using the name around the same time, they seem like nice people and we should OK it with them. *** "zap"@en-gb

18 years

Re: [linux-audio-dev] Trouble compiling cheesetracker in Slackware 10.2

by Jonathan Woithe

Blaze Monger wrote: > 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. Slackware 10.2 doesn't come with sigc++. You will have to get the source, compile and install it before attempting to compile anything that uses it, such as cheesetracker. It's not hard though - sigc++ compiles and installs cleanly under Slackware 10.2 (for me at least) using the normal ./configure make make install process. Regards jonathan

18 years

Re: [linux-audio-dev] "LADSPA 2" name

by Sampo Savolainen

Quoting Steve Harris <S.W.Harris(a)ecs.soton.ac.uk>: > My suggestion is that we ressurect the XAP name > (http://www.google.com/search?q=lad+xap) > It stood for Xap Audio Plugin IIRC. > > Pros: it's short*, relatively unused** and pronouncable*** More pros: we would have a VST -alike logo already! (looking at http://xap-plugins.org/artwork.html). And it's not too VST -alike, as XAP doesn't share a single letter with VST. > Cons: xap.{com,org,net} will have gone long ago (too short), theres a > small ammount of baggage. I think we would select a short name anyway. Most of them are gone already, so we have the same problem whichever [a-z][a-z][a-z] we select :) Sampo

18 years

[linux-audio-dev] Todays "LADSPA2" update

by Steve Harris

I've written a first cut at an ontology/schema for the plugin RDF: http://plugin.org.uk/ladspa2/ladspa-2.ttl The term schema is a bit misleading, as it doesn't really enforce anything, it really just gives you some hints about what to write. The bulk of it is english text to explain the meaning of the bits that are no longer in the .h I tried to write it as clearly as possible, but the machine readable parts might still be a bit cryptic and there could be errors. Shout if there's any bits that don't make sense. - Steve

18 years

[linux-audio-dev] LAC 2006 Live Streams

by Joern Nettingsmeier

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

18 years

[linux-audio-dev] Om-synth CVS compile problem

by Dave Phillips

Greetings: Has anyone else encountered this problem when compiling recent CVS Om-synth : if g++ -DHAVE_CONFIG_H -I. -I. -I../../.. -DGTK_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -I../../../src/common -I../../../src/clients -DPKGDATADIR=\"/usr/local/share/om\" -DXTHREADS -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/include/atkmm-1.6 -I/usr/include/gtk-2.0 -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/X11R6/include -I/usr/include/atk-1.0 -DXTHREADS -I/usr/include/libglademm-2.4 -I/usr/lib/libglademm-2.4/include -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/libglade-2.0 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/include/atkmm-1.6 -I/usr/include/gtk-2.0 -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/X11R6/include -I/usr/include/atk-1.0 -I/usr/include/libxml2 -DXTHREADS -I/usr/include/libgnomecanvasmm-2.6 -I/usr/lib/libgnomecanvasmm-2.6/include -I/usr/include/gtkmm-2.4 -I/usr/lib/gtkmm-2.4/include -I/usr/include/libgnomecanvas-2.0 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/gdkmm-2.4 -I/usr/lib/gdkmm-2.4/include -I/usr/include/pangomm-1.4 -I/usr/include/atkmm-1.6 -I/usr/include/gtk-2.0 -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/lib/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/X11R6/include -I/usr/include/atk-1.0 -I/usr/include/libart-2.0 -I/usr/include/freetype2 -I/usr/local/include/lash-1.0 -I/usr/include/alsa -I/usr/local/include -g -O2 -DNDEBUG -DNDEBUG -pipe -fmessage-length=139 -fdiagnostics-show-location=every-line -MT PortController.o -MD -MP -MF ".deps/PortController.Tpo" -c -o PortController.o PortController.cpp; \ then mv -f ".deps/PortController.Tpo" ".deps/PortController.Po"; else rm -f ".deps/PortController.Tpo"; exit 1; fi PortController.cpp: In member function 'virtual void OmGtk::PortController::set_path(const Om::Path&)': PortController.cpp:120: error: 'class OmGtk::OmPort' has no member named 'set_name' make[4]: *** [PortController.o] Error 1 make[4]: Leaving directory `/home/dlphilp/om-synth/src/clients/gtk' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/dlphilp/om-synth/src/clients' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/dlphilp/om-synth/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/dlphilp/om-synth' make: *** [all] Error 2 The set_name function is commented out in OmPort.h. I've posted to the om-synth list and to the author, no responses yet. I'd like to review Om for my next LJ column, I have an older version workjingn but would like to profile the latest & greatest if possible. Best, dp

18 years

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-dev April 2006