Re: [LAD] LV2: Communicate from the DSP to the UI

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Aurélien Leblond <blablack@...>
Cc: <devel@...>, Linux Audio Developers <linux-audio-dev@...>
Date: Monday, October 28, 2013 - 8:30 pm

--047d7b86f3066896dc04e9d2f7b7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 28, 2013 at 11:58 AM, Michael Fisher wrote=
:

> On Mon, Oct 28, 2013 at 10:24 AM, Aur=E9lien Leblond =
wrote:

o
First things first. Your plugin, after modifying ttl files, works fine in
Jalv. For ingen support, your best bet might be to add a Trac ticket on
drobilla.net.

Ok, so I figured out the problem... the GUI ttl file should look
something like this (with a portNotification setting)

a guiext:GtkUI ;

guiext:binary ;

guiext:portNotification [

guiext:plugin =
;

lv2:symbol "notify" ;

guiext:notifyType atom:Float

] .

the Port definition in the plugin's turtle :

... [

a lv2:OutputPort, atom:AtomPort ;

atom:bufferType atom:Sequence ;

atom:supports atom:Float ; # <<<<<< NEED THIS (i think)

lv2:index 1 ;

lv2:symbol "notify" ;

lv2:name "Notify" ;

] .

I also added more debug output to the GUI... all relevant changes
were committed in a git mirror on Github (its just easier for me to do
that) The only files I modified were scope*.* files

You'll want to look at the GUI code, because I also show you how to
'un-package' the atom in the port_event method.

https://github.com/axetota/avwlv2/tree/devel

--047d7b86f3066896dc04e9d2f7b7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 28, 2013 at 11:58 AM, Michael Fisher <mfish=
er31@gmail.com
> wrote:
On Mon, Oct 28, 20=
13 at 10:24 AM, Aur=E9lien Leblond <blablack@gmail.com> wro=
te:

> The map object is 'just there' for when you n=
eed it, like creating new

> forges ;) =A0I've always wondered if it made more sense =A0to prov=
ide a accessor

hing like
ll
get the size
notify);
.size);
br>
to the
n't recall the
straight

Thanks for checking, I really have the feeling I'm missing something
small here :)Yep, missing =
something small seems to happen to me frequently. =A0I'm jumping over t=
o my Linux machine and will give it a go.=A0

The SVN is here:
svn checkout svn://svn.code.sf.net/p/avwlv2/code/trunk avw.lv2

(Ingen is the host I use to test them)

First things =
first. =A0Your plugin, after modifying ttl files, works fine in Jalv. =A0 F=
or ingen support, your best bet might be to add a Trac ticket on =A0drobilla.net.
Ok, so I figured out the problem... =A0 the GUI ttl file should look somet=
hing like this (with a portNotification setting)

<http://avwlv2.sourceforge.net/plug=
ins/avw/scope/gui
>
a =
guiext:GtkUI ;
guiext:binary <scope_gui.so> ;

guiext:portNotification [
guiext:plugin <http://avwlv2.sourceforge.net/plugins/avw/scope> ;

lv2:symbol "notify" ;

guiext:notifyType atom:Float
] =
.
the Port definiti=
on in the plugin's turtle : ... [
a=
lv2:OutputPort, atom:=
AtomPort ;
atom:bufferType=
atom:Sequence ;=

atom:supports=
atom:Float ; # <<<<<< NEED THIS (i th=
ink)
lv2:index 1 ;
lv2:symbol "notify" ;=
lv2:name "Notify" ;
] .
I also added more debug output to the GUI... all relevant changes were com=
mitted in a git mirror on Github (its just easier for me to do that) The o=
nly files I modified were scope*.* files
You'll want t=
o look at the GUI code, because I also show you how to 'un-package'=
the atom in the port_event method.
https://github.com/axetota/avwlv2/t=
ree/devel
=

--047d7b86f3066896dc04e9d2f7b7--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAD] LV2: Communicate from the DSP to the UI, Aurélien Leblond, (Mon Oct 28, 2:00 pm)
Re: [LAD] LV2: Communicate from the DSP to the UI, Michael Fisher, (Mon Oct 28, 2:52 pm)
Re: [LAD] LV2: Communicate from the DSP to the UI, Aurélien Leblond, (Mon Oct 28, 3:24 pm)
Re: [LAD] LV2: Communicate from the DSP to the UI, Michael Fisher, (Mon Oct 28, 4:58 pm)
Re: [LAD] LV2: Communicate from the DSP to the UI, Michael Fisher, (Mon Oct 28, 8:30 pm)
Re: [LAD] LV2: Communicate from the DSP to the UI, Aurélien Leblond, (Mon Nov 4, 12:52 pm)
Re: [LAD] LV2: Communicate from the DSP to the UI, Michael Fisher, (Tue Nov 5, 5:48 am)
Re: [LAD] [LV2] LV2: Communicate from the DSP to the UI, David Robillard, (Wed Nov 6, 4:45 am)
Re: [LAD] LV2: Communicate from the DSP to the UI, Robin Gareus, (Wed Nov 6, 3:33 am)
Re: [LAD] LV2: Communicate from the DSP to the UI, David Robillard, (Wed Nov 6, 4:41 am)
Re: [LAD] LV2: Communicate from the DSP to the UI, Aurélien Leblond, (Wed Nov 6, 3:21 pm)
Re: [LAD] LV2: Communicate from the DSP to the UI, David Robillard, (Sat Nov 9, 7:09 pm)
Re: [LAD] LV2: Communicate from the DSP to the UI, Robin Gareus, (Wed Nov 6, 11:49 pm)
Re: [LAD] LV2: Communicate from the DSP to the UI, David Robillard, (Sat Nov 9, 7:10 pm)
Re: [LAD] [LV2] LV2: Communicate from the DSP to the UI, David Robillard, (Sun Nov 10, 6:58 pm)
Re: [LAD] [LV2] LV2: Communicate from the DSP to the UI, Aurélien Leblond, (Sun Nov 10, 8:05 am)