1 Jan
2012
1 Jan
'12
3:55 p.m.
Hello everyone,
During this jolly holidays, I worked a bit on the AMS LV2 plugins.
The version 0.0.6 can be downloaded here:
http://sourceforge.net/projects/avwlv2/files/avw.lv2.0.0.6.tar.gz/download
This new version comes with:
* Basic GUI for Analog Driver, Envelop and Advanced Envelop
* Ported:
- CV Source
- Delay
- Dynamic Waves (4 Osc)
The basic GUIs are based on the ones from AMS itself.
In addition, the SVN is now fixed:
svn checkout svn://svn.code.sf.net/p/avwlv2/code/trunk avwlv2-code
Finally, plans for the future are to port more of the AMS plugins (I'm
sorry guys, but I'm only gonna port the ones I actually use and might
ignore some others).
I was thinking as well to:
- create a percussive envelop and 'Note Filter' (a plugin that let the
Velocity/Gate/Trigger of the Ingen Note Internal go through only when
a certain Frequency is hit). I have patches that simulate the TR 808
Kick/Snare/Etc, and I need these to be able to create a Drum Machine
in Ingen.
- create a beat slicer/repeater plugin (probably will base the code on
Tranches).
- a LFO synchcronized with Jack (I have always missed that one AMS!).
So here you go!
Have a happy new year 2012 guys!
Aurélien
11 Mar
11 Mar
3:39 a.m.
On Sun, 2012-01-01 at 14:55 +0000, Aurélien Leblond wrote:
Hello everyone,
During this jolly holidays, I worked a bit on the AMS LV2 plugins.
The version 0.0.6 can be downloaded here:
http://sourceforge.net/projects/avwlv2/files/avw.lv2.0.0.6.tar.gz/download
Ack! Why the heck do these plugins have URIs at http://lv2plug.in?!
Don't give things URIs at domains you don't control without at least
permission!
-dr
11:01 a.m.
Hello
everyone,
During this jolly holidays, I worked a bit on the AMS LV2 plugins.
The version 0.0.6 can be downloaded here:
http://sourceforge.net/projects/avwlv2/files/avw.lv2.0.0.6.tar.gz/download
Ack! Why the heck do these plugins have URIs at http://lv2plug.in?!
Don't give things URIs at domains you don't control without at least
permission!
-dr
8:34 p.m.
On Sun, 2012-03-11 at 10:01 +0000, Aurélien Leblond wrote:
Hi David,
Sorry about that, I simply started to work from other examples and
never changed the URIs as I didn't think it matter in any way!
Well, it doesn't really "matter" depending on how you look at it, but in
general it's inappropriate to claim big chunks of namespace in other
people's domains. I thought this was obvious but I suppose the examples
need to state it explicitly.
The main practical thing you lose is the convenience of people being
able to plug those URIs into a browser and actually getting to
information.
That said, we can perhaps establish chunks of namespace at lv2plug.in if
people want them, but you at least have to ask :P Maybe we should use
PURLs or set up a similar simple redirect service at lv2plug.in for
people who don't have a long-term stable namespace to use...
Hello everyone,
During this jolly holidays, I worked a bit on the AMS LV2 plugins.
The version 0.0.6 can be downloaded here:
http://sourceforge.net/projects/avwlv2/files/avw.lv2.0.0.6.tar.gz/download
Ack! Why the heck do these plugins have URIs at http://lv2plug.in?!
Don't give things URIs at domains you don't control without at least
permission!
-dr If I do bn't control any domains, what can I use
as URI?
You control http://avwlv2.sourceforge.net/, calf uses its sourceforge
URI.
-dr
8:58 p.m.
On Sun, 2012-03-11 at 10:01 +0000, Aurélien Leblond
wrote:
Hi David,
Sorry about that, I simply started to work from other examples and
never changed the URIs as I didn't think it matter in any way!
Well, it doesn't really "matter" depending on how you look at it, but in
general it's inappropriate to claim big chunks of namespace in other
people's domains. I thought this was obvious but I suppose the examples
need to state it explicitly.
The main practical thing you lose is the convenience of people being
able to plug those URIs into a browser and actually getting to
information.
That said, we can perhaps establish chunks of namespace at lv2plug.in if
people want them, but you at least have to ask :P Maybe we should use
PURLs or set up a similar simple redirect service at lv2plug.in for
people who don't have a long-term stable namespace to use...
Sounds like a useful service. You could even make some money out of it by
charging corporate users for the privilege...
Hello everyone,
During this jolly holidays, I worked a bit on the AMS LV2 plugins.
The version 0.0.6 can be downloaded here:
http://sourceforge.net/projects/avwlv2/files/avw.lv2.0.0.6.tar.gz/download
Ack! Why the heck do these plugins have URIs at http://lv2plug.in?!
Don't give things URIs at domains you don't control without at least
permission!
-dr If I do
bn't control any domains, what can I use as URI?
You control http://avwlv2.sourceforge.net/, calf uses its sourceforge
URI.
-dr
15 Mar
15 Mar
3:12 p.m.
Hi David,
Sorry about that, I simply started to work from other examples and
never changed the URIs as I didn't think it matter in any way!
Well, it doesn't really "matter" depending on how you look at it, but in
general it's inappropriate to claim big chunks of namespace in other
people's domains. I thought this was obvious but I suppose the examples
need to state it explicitly.
The main practical thing you lose is the convenience of people being
able to plug those URIs into a browser and actually getting to
information.
That said, we can perhaps establish chunks of namespace at lv2plug.in if
people want them, but you at least have to ask :P Maybe we should use
PURLs or set up a similar simple redirect service at lv2plug.in for
people who don't have a long-term stable namespace to use...
If I do bn't control any domains, what can I
use as URI?
You control http://avwlv2.sourceforge.net/, calf uses its sourceforge
URI.
11 Mar
11 Mar
8:53 p.m.
New subject: Plugin CV ports (WAS: AMS LV2 plugins: Version 0.0.6)
I implemented cv:CVPort[1] for these plugins (a CVPort is just an
AudioPort that works as a control). I've only done some very quick
preliminary testing.
However, I don't think this is the best way of doing CV for most
plugins, mainly because it is not backwards compatible with ControlPort.
For plugins only usable in a modular and/or plugins where there's no
computational benefit, it doesn't matter, but for some it certainly
does.
I was thinking we should solve this generically, since there's similar
situations (backwards compatible stereo ports, perhaps?). The
hypothetical "poly-port" (polymorphic port) extension would add a
function which lets the host say a port is connected to a buffer for a
particular port type. The optional port types would be listed by a
different property, so unless this function is called, they would appear
as normal ControlPorts to an oblivious host. Something like:
# Plugin data
_:someport a lv2:ControlPort ;
pp:supportedType cv:CVPort .
# Plugin code
void set_port_type(LV2_Handle instance,
uint32_t port_index,
uint32_t port_type_urid) { ... }
Thoughts on this welcome, I plan to use it for my blop port. Variants
suck!
Anyway, sorry this took so long, I've been spending so much time on LV2
infrastructure stuff there's not much left to work on my own programs :/
-dr
[1] http://lv2plug.in/ns/ext/cv-port#CVPort
14 Apr
14 Apr
4:42 a.m.
New subject: Plugin CV ports (WAS: AMS LV2 plugins: Version 0.0.6)
On Sun, 2012-03-11 at 15:53 -0400, David Robillard wrote:
I implemented cv:CVPort[1] for these plugins (a CVPort
is just an
AudioPort that works as a control)
[...]
Since the cv-port extension was literally just this one URI, the port
type doesn't really introduce anything new (same format as
lv2:AudioPort, used like an lv2:ControlPort), and abuse of audio ports
for this has been around since the early LADSPA days, I just moved this
to the core spec. So, lv2:CVPort is the type now.
Cheers,
-dr, attempting to minimize the shotgun-blast-of-extensions thing
4601
days inactive
4705
days old
linux-audio-dev@lists.linuxaudio.org
7 comments
3 participants
participants (3)
-
Aurélien Leblond -
David Robillard -
Patrick Shirkey