*** Yruama_Lairba has joined #lv2 | 00:11 | |
*** NickSB has quit IRC | 00:21 | |
*** NickSB has joined #lv2 | 00:35 | |
*** Yruama_Lairba has quit IRC | 02:57 | |
*** artfwo has joined #lv2 | 03:05 | |
*** Guest88863 has joined #lv2 | 03:27 | |
*** Guest88863 has quit IRC | 03:31 | |
*** jmagnusj has joined #lv2 | 04:12 | |
jmagnusj | I'm so close to getting the file selector parameter working | 04:12 |
---|---|---|
jmagnusj | One thing confuses me -- after i select a file, I get a patch_Get message, not a patch_Set message | 04:13 |
jmagnusj | hmm, I get it once. | 04:16 |
* jmagnusj debugs some more | 04:17 | |
jmagnusj | It works! | 04:21 |
*** edogawa has joined #lv2 | 07:15 | |
*** edogawa has quit IRC | 08:27 | |
*** sigma6 has joined #lv2 | 08:33 | |
*** edogawa has joined #lv2 | 08:39 | |
*** yann-kaelig has joined #lv2 | 09:13 | |
falktx | if a plugin has output atom port and supports patch messages... does that mean it can send a patch:Set to its input parameter to the host? | 09:54 |
falktx | ie, modify an input parameter value | 09:54 |
*** oofus has quit IRC | 10:13 | |
*** ftonello has joined #lv2 | 10:49 | |
rgareus | falktx: in principle, yes | 11:20 |
rgareus | falktx: I've outlined some semantics for that about a year ago. for a plugin to automate itself. (send message to host to change some input at a given time) | 11:22 |
falktx | not sure if I like that idea too much | 11:24 |
rgareus | but I don't think Patch:Set cannot modify properties of the patch itself | 11:24 |
rgareus | the host calls Patch:Get to query a property | 11:24 |
rgareus | well lv2:Parameter are read/write by the host and plugin via patch Set/Get | 11:27 |
*** dsheeler has joined #lv2 | 11:49 | |
ventosus | patch:Set from host to plugin is to set a parameter on the plugin | 13:13 |
ventosus | patch:Set from plugin to host is to notify host about parameter state/change | 13:14 |
ventosus | if a plugin wants to change one of its parameters, it just changes them and notifies the host with patch:Set | 13:14 |
ventosus | no need for a feedback, is there? | 13:14 |
rgareus | ventosus: falktx asked about modifing input parameters | 13:15 |
* rgareus understood that to mean [float] control ports | 13:15 | |
ventosus | ah, I see, mixed it up with lv2:Parameter | 13:15 |
falktx | I know we can't change control input ports, by design | 13:16 |
rgareus | falktx: can you clarify? you said "odify an input parameter value" | 13:16 |
falktx | but using lv2:parameters, it seems like it's possible | 13:16 |
falktx | self-automation | 13:16 |
*** Yruama_Lairba has joined #lv2 | 13:16 | |
ventosus | out of curiosity, what would I use for the URI as patch:property for an input control port? | 13:16 |
rgareus | ventosus: I don't think there's a spec for that | 13:16 |
rgareus | at least not an official one | 13:17 |
*** trebmuh has quit IRC | 13:26 | |
*** artfwo has quit IRC | 13:30 | |
*** artfwo has joined #lv2 | 13:36 | |
*** trebmuh has joined #lv2 | 13:39 | |
*** JaVelDa has left #lv2 | 14:30 | |
*** tytel has joined #lv2 | 14:31 | |
*** JaVelDa has joined #lv2 | 14:38 | |
*** tytel has quit IRC | 16:03 | |
*** sigma6 has quit IRC | 17:08 | |
drobilla | Technically you could give the port a designation and support that via messages, I guess, buuuuuuuuuuuuuuuut | 18:26 |
drobilla | Well, yeah, don't :) | 18:27 |
drobilla | Though on a vaguely related note I feel like Turtle pretty printing has misled us to a poor design since ports have strong symbols anyway so they really should just have URIs | 18:27 |
*** rncbc has joined #lv2 | 18:39 | |
*** yann-kaelig has quit IRC | 18:53 | |
*** NickSB has quit IRC | 19:13 | |
*** NickSB has joined #lv2 | 19:28 | |
*** yann-kaelig has joined #lv2 | 20:14 | |
*** yann-kaelig has quit IRC | 20:17 | |
*** edogawa has quit IRC | 20:43 | |
*** oofus has joined #lv2 | 21:36 |
Generated by irclog2html.py 2.13.0 by Marius Gedminas - find it at mg.pov.lt!