25 Apr
2006
25 Apr
'06
8:28 a.m.
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
25 Apr
25 Apr
8:48 a.m.
On Tue, 2006-04-25 at 11:28 +0100, Steve Harris wrote:
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.
That is interesting - it could be used to store frames of frequency
domain data, like the spectral variables in Csound, or timestamped
events of different types, like JACK MIDI. In the future.
--
Lars Luthman
PGP key: http://www.student.nada.kth.se/~d00-llu/pgp_key.php
Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E
11:29 a.m.
On Tue, 25 Apr 2006 at 11:28 +0100, Steve Harris wrote:
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
Hmm, well couldn't we have one libsndfile plugin that can convert
between whatever common boring PCM formats you like? I haven't looked
closely at the ladspa2 stuff yet - is it possible to change these port
types at runtime, if so the libsndfile plugin would only need an input
and an output...
--
Hans Fugal ; http://hans.fugal.net
There's nothing remarkable about it. All one has to do is hit the
right keys at the right time and the instrument plays itself.
-- Johann Sebastian Bach
12:11 p.m.
On Tue, Apr 25, 2006 at 07:29:31AM -0600, Hans Fugal wrote:
On Tue, 25 Apr 2006 at 11:28 +0100, Steve Harris
wrote:
Their constant.
But that's what I was trying to avoid, the current sitatuion is that all
LADSPA plugins speak only IEEE floats, and that's really nice.
You can end up burning a lot of memory bandwidth and cpu just doing
pointless PCM conversions.
- Steve
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
Hmm, well couldn't we have one libsndfile plugin that can convert
between whatever common boring PCM formats you like? I haven't looked
closely at the ladspa2 stuff yet - is it possible to change these port
types at runtime, if so the libsndfile plugin would only need an input
and an output... 
3:36 p.m.
On Tue, 2006-04-25 at 11:28 +0100, Steve Harris wrote:
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?
Votes += infinity
-DR-
7:34 p.m.
LADSPA is not a sexy name. please consider using something more erotic
this time.. acronyms are so 80s :)
i'm going to read the header file now.
On Tue, 2006-04-25 at 15:11 +0100, Steve Harris wrote:
On Tue, Apr 25, 2006 at 07:29:31AM -0600, Hans Fugal
wrote:
--
-- leonard "paniq" ritter
-- http://www.mjoo.org
-- http://www.paniq.org
On Tue, 25 Apr 2006 at 11:28 +0100, Steve Harris
wrote:
Their constant.
But that's what I was trying to avoid, the current sitatuion is that all
LADSPA plugins speak only IEEE floats, and that's really nice.
You can end up burning a lot of memory bandwidth and cpu just doing
pointless PCM conversions.
- Steve 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
Hmm, well couldn't we have one libsndfile plugin that can convert
between whatever common boring PCM formats you like? I haven't looked
closely at the ladspa2 stuff yet - is it possible to change these port
types at runtime, if so the libsndfile plugin would only need an input
and an output... 
8:27 p.m.
On Tue, Apr 25, 2006 at 11:41:41PM +0200, Leonard paniq Ritter wrote:
LADSPA is not a sexy name. please consider using
something more erotic
this time.. acronyms are so 80s :)
its retro, it ALL going back to the eighties.
i'm going to read the header file now.
On Tue, 2006-04-25 at 15:11 +0100, Steve Harris wrote:
--
torben Hohn
http://galan.sourceforge.net -- The graphical Audio language
On Tue, Apr 25, 2006 at 07:29:31AM -0600, Hans
Fugal wrote:
--
-- leonard "paniq" ritter
-- http://www.mjoo.org
-- http://www.paniq.org
On Tue, 25 Apr 2006 at 11:28 +0100, Steve Harris
wrote:
Their constant.
But that's what I was trying to avoid, the current sitatuion is that all
LADSPA plugins speak only IEEE floats, and that's really nice.
You can end up burning a lot of memory bandwidth and cpu just doing
pointless PCM conversions.
- Steve 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
Hmm, well couldn't we have one libsndfile plugin that can convert
between whatever common boring PCM formats you like? I haven't looked
closely at the ladspa2 stuff yet - is it possible to change these port
types at runtime, if so the libsndfile plugin would only need an input
and an output...
6597
days inactive
6597
days old
linux-audio-dev@lists.linuxaudio.org
6 comments
6 participants
participants (6)
-
Dave Robillard -
Hans Fugal -
Lars Luthman -
Leonard "paniq" Ritter -
Steve Harris -
torbenh＠gmx.de