Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

7516 discussions

by Kjetil S. Matheussen

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. > I don't agree about taking away the "L". Ladspa is not linux-specific, but it has certainly originated from linux, and has the best support in linux software. If linux dissapears before the ladspa format, we can at least still remember linux through the name of ladspa... Regarding your argumentation about the prononounciation, I think its a bit anglocentric language-vice. In most other countries (scandinavian, german, spanish, belgian, dutch, slavic (I might be wrong about some of these though)), where the "a" is actually pronounced like the round "ah" (and very short in this case), and you don't have to move the mouth that much as in english (and especially in american english), "ladspa" sounds really cool and is not very difficult to say. A good solution to this problem would be if the english speakers started to allways say the more common rounder "ah" instead of "a", not only for ladspa, but for all acronyms. I think the argument about S is valid enough though, but not a good enough argument to change a name we all have learned and love(?). As an alternative, we can change the meaning of s into something else, like Super, Second, Sophisticated, System, Steve, Sourcecode, Syntax, Structure, Success, Superb, Superior. To name a few, well, I'm sure there are better alternatives. > ---- > > 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. > I think its too short. Its not cool, and its hard to remember from the pronounciation.

19 years, 6 months

[linux-audio-dev] [ANN] libgig 3.0.0

by Christian Schoenebeck

Hi! Usually I don't announce new versions of libgig here anymore, but this release might be of interest for some: Beside a bunch of bug fixes it now also allows to modify existing and create new Gigasampler files. If anybody's interested in writing a .gig editor, have a look at the "gigwritedemo.cpp" example application: http://stud.hs-heilbronn.de/~cschoene/projects/libgig/#examples libgig is released under (pure) GPL and as always available on its original site: http://stud.hs-heilbronn.de/~cschoene/projects/libgig/ as well as on the LS server: http://www.linuxsampler.org/downloads.html http://download.linuxsampler.org/packages/ CU Christian P.S. I just restored the old libgig source packages on the LS server, all other packages will be restored after LAC (that is next week) - I know the downloads section on LS.org was dead for too long now, sorry!

19 years, 6 months

[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

19 years, 6 months

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

by Kjetil S. Matheussen

I vote for "LADSPA" as well.

19 years, 6 months

[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

19 years, 6 months

[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

19 years, 6 months

[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

19 years, 6 months

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

19 years, 6 months

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

19 years, 6 months

[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

19 years, 6 months

Jump to page:

2025

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