Wednesday, 2017-03-08

*** Yruama_Lairba has joined #lv200:11
*** NickSB has quit IRC00:21
*** NickSB has joined #lv200:35
*** Yruama_Lairba has quit IRC02:57
*** artfwo has joined #lv203:05
*** Guest88863 has joined #lv203:27
*** Guest88863 has quit IRC03:31
*** jmagnusj has joined #lv204:12
jmagnusjI'm so close to getting the file selector parameter working04:12
jmagnusjOne thing confuses me -- after i select a file, I get a patch_Get message, not a patch_Set message04:13
jmagnusjhmm, I get it once.04:16
* jmagnusj debugs some more04:17
jmagnusjIt works!04:21
*** edogawa has joined #lv207:15
*** edogawa has quit IRC08:27
*** sigma6 has joined #lv208:33
*** edogawa has joined #lv208:39
*** yann-kaelig has joined #lv209:13
falktxif 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
falktxie, modify an input parameter value09:54
*** oofus has quit IRC10:13
*** ftonello has joined #lv210:49
rgareusfalktx: in principle, yes11:20
rgareusfalktx: 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
falktxnot sure if I like that idea too much11:24
rgareusbut I don't think Patch:Set cannot modify properties of the patch itself11:24
rgareusthe host calls Patch:Get  to query a property11:24
rgareuswell  lv2:Parameter  are read/write by the host and plugin via patch Set/Get11:27
*** dsheeler has joined #lv211:49
ventosuspatch:Set from host to plugin is to set a parameter on the plugin13:13
ventosuspatch:Set from plugin to host is to notify host about parameter state/change13:14
ventosusif a plugin wants to change one of its parameters, it just changes them and notifies the host with patch:Set13:14
ventosusno need for a feedback, is there?13:14
rgareusventosus: falktx asked about modifing input parameters13:15
* rgareus understood that to mean [float] control ports13:15
ventosusah, I see, mixed it up with lv2:Parameter13:15
falktxI know we can't change control input ports, by design13:16
rgareusfalktx: can you clarify?   you said  "odify an input parameter value"13:16
falktxbut using lv2:parameters, it seems like it's possible13:16
falktxself-automation13:16
*** Yruama_Lairba has joined #lv213:16
ventosusout of curiosity, what would I use for the URI as patch:property for an input control port?13:16
rgareusventosus: I don't think there's a spec for that13:16
rgareusat least not an official one13:17
*** trebmuh has quit IRC13:26
*** artfwo has quit IRC13:30
*** artfwo has joined #lv213:36
*** trebmuh has joined #lv213:39
*** JaVelDa has left #lv214:30
*** tytel has joined #lv214:31
*** JaVelDa has joined #lv214:38
*** tytel has quit IRC16:03
*** sigma6 has quit IRC17:08
drobillaTechnically you could give the port a designation and support that via messages, I guess, buuuuuuuuuuuuuuuut18:26
drobillaWell, yeah, don't :)18:27
drobillaThough 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 URIs18:27
*** rncbc has joined #lv218:39
*** yann-kaelig has quit IRC18:53
*** NickSB has quit IRC19:13
*** NickSB has joined #lv219:28
*** yann-kaelig has joined #lv220:14
*** yann-kaelig has quit IRC20:17
*** edogawa has quit IRC20:43
*** oofus has joined #lv221:36

Generated by irclog2html.py 2.13.0 by Marius Gedminas - find it at mg.pov.lt!