22 Dec
2011
22 Dec
'11
3:56 p.m.
Hi everyone. I'm starting to write a simple filter and I want to expose it
as an lv2 plugin.
My development environment is very simple right now: vim editor, gcc
compiler, package the lv2 manually (will write a script for that in a day
or two) and then load the plugin in ardour to test it.
I've found this setup to be a bit unconfortable because once I load the
plugin in ardour I don't know how to get debug information from it (print
statements or breakpoints with gdb).
What does a lv2 development environment typically looks like? what are you
guys using?
Thanks!
--
Rafael Vega
email.rafa(a)gmail.com
22 Dec
22 Dec
4:46 p.m.
Hi Rafa,
I'm not a plugin developer so I can't comment on the best workflow. I can
say that I'd try use a more lightweight host than Ardour. Have you tried
running your plugin using the example jack host that comes with the
LV2-core source?
<shameless self-promotion>
In case your intrested: I've written a simple C++ host class, in case you
want to write a host specifically for testing purposes:
https://github.com/harryhaaren/Lv2Host
</self-promotion>
Are you documenting what your doing in a blog or so?
I'm hoping to get writing LV2 plugins, but I've never found a "newbie"
style tutorial..
Cheers, -Harry
4:55 p.m.
Hey Rafael,
I wrote lv2file (https://github.com/jeremysalwen/lv2file) specifically for
debugging lv2 plugins. Also look at lv2proc (
http://naspro.atheme.org/applications/lv2proc/).
A) If you just test with a single input file, you get a uniform debugging
environment.
B) You can set breakpoints and debug inside your LV2 plugin just like you
would any other C library code (so long as you compiled in debugging
information to the shared library).
Jeremy
On Thu, Dec 22, 2011 at 9:55 AM, email.rafa(a)gmail.com
<email.rafa(a)gmail.com>wrote;wrote:
Hi everyone. I'm starting to write a simple filter
and I want to expose it
as an lv2 plugin.
My development environment is very simple right now: vim editor, gcc
compiler, package the lv2 manually (will write a script for that in a day
or two) and then load the plugin in ardour to test it.
I've found this setup to be a bit unconfortable because once I load the
plugin in ardour I don't know how to get debug information from it (print
statements or breakpoints with gdb).
What does a lv2 development environment typically looks like? what are you
guys using?
Thanks!
--
Rafael Vega
email.rafa(a)gmail.com
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
5:31 p.m.
Thanks for the links, Jeremy.
I assume you use either lv2file or lv2proc within a script to generate
output files, is that correct? That sounds powerful to conduct
(semi)automated testing.
On Thu, Dec 22, 2011 at 10:55 AM, Jeremy Salwen <jeremysalwen(a)gmail.com>wrote;wrote:
Hey Rafael,
I wrote lv2file (https://github.com/jeremysalwen/lv2file) specifically
for debugging lv2 plugins. Also look at lv2proc (
http://naspro.atheme.org/applications/lv2proc/).
A) If you just test with a single input file, you get a uniform debugging
environment.
B) You can set breakpoints and debug inside your LV2 plugin just like you
would any other C library code (so long as you compiled in debugging
information to the shared library).
Jeremy
On Thu, Dec 22, 2011 at 9:55 AM, email.rafa(a)gmail.com <
email.rafa(a)gmail.com> wrote:
--
Rafael Vega
email.rafa(a)gmail.com
Hi everyone. I'm starting to write a simple
filter and I want to expose
it as an lv2 plugin.
My development environment is very simple right now: vim editor, gcc
compiler, package the lv2 manually (will write a script for that in a day
or two) and then load the plugin in ardour to test it.
I've found this setup to be a bit unconfortable because once I load the
plugin in ardour I don't know how to get debug information from it (print
statements or breakpoints with gdb).
What does a lv2 development environment typically looks like? what are
you guys using?
Thanks!
--
Rafael Vega
email.rafa(a)gmail.com
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
6:20 p.m.
On 12/22/2011 08:55 AM, email.rafa(a)gmail.com wrote:
My development environment is very simple right now:
vim editor, gcc
compiler, package the lv2 manually (will write a script for that in a
day or two) and then load the plugin in ardour to test it.
I've found this setup to be a bit unconfortable because once I load the
plugin in ardour I don't know how to get debug information from it
(print statements or breakpoints with gdb).
What does a lv2 development environment typically looks like? what are
you guys using?
I use Ingen and SLV2.
SLV2 also provides a simple CLI for loading your plugin (using its URL)
and attaching it to the jack server. It's probably packaged for your OS.
You have to build Ingen from source, but I recommend it highly. Use
Ingen. http://drobilla.net/software/ingen/
As for breakpoints, gdb usually loads your symbols as soon as your .so
file gets loaded. So you can set your breakpoint at the start and when
it says "set on future library load?" (or something like that) you say
"yes." After you inspect the backtraces when you stop on your functions
a few times... you'll get a feel for how the host application is working
(in case you want to set breaks in the host app).
-gabriel
8:57 p.m.
On Thu, 2011-12-22 at 11:20 -0600, Gabriel M. Beddingfield wrote:
On 12/22/2011 08:55 AM, email.rafa(a)gmail.com wrote:
The soon-to-be-released replacement for lv2_jack_host from (dead) SLV2
is Lilv, which can be found here:
http://svn.drobilla.net/lad/trunk/lilv/
Lilv is intended to be a somewhat minimal, but fully featured, LV2 Jack
host, particularly suitable for testing, but also a useful (non-toy)
tool for running LV2 plugins as Jack applications. It is much more
fully featured than lv2_jack_host, most notably supporting GUIs and
presets. Currently ongoing work to support host-shared preset saving.
-dr
My development environment is very simple right
now: vim editor, gcc
compiler, package the lv2 manually (will write a script for that in a
day or two) and then load the plugin in ardour to test it.
I've found this setup to be a bit unconfortable because once I load the
plugin in ardour I don't know how to get debug information from it
(print statements or breakpoints with gdb).
What does a lv2 development environment typically looks like? what are
you guys using?
I use Ingen and SLV2.
SLV2 also provides a simple CLI for loading your plugin (using its URL)
and attaching it to the jack server. It's probably packaged for your OS.
4748
days inactive
4748
days old
linux-audio-dev@lists.linuxaudio.org
5 comments
5 participants
participants (5)
-
David Robillard -
email.rafa＠gmail.com -
Gabriel M. Beddingfield -
Harry van Haaren -
Jeremy Salwen