You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
faust2jack mysynth does compile a nice gtk2 app: midi input works, sound output works.
Now if I want to use my synth as a lv2 instrument (here in Ardour)
faust2lv2 mysynth produces as expected
mysynth.so
mysynth.ttl
manifest.tll
Once installed (in my case, on debian 12.5, copied to /usr/lib/lv2)
the plugin is listed by lv2ls
the plugin is listed in ardour effects, but not as an instrument.
If I modify the lines in mysynth.ttl
<https://faustlv2.bitbucket.io/grosynth>
a lv2:Plugin ;
to
<https://faustlv2.bitbucket.io/grosynth>
a lv2:InstrumentPlugin ;
Now Ardour sees it as a LV2 instrument, but no sound is output (all other lv2 instruments work correctly in the same Ardour instance).
Reading the faust2lv2 script, I do not see any related command switch. I see some mentions of "(For instruments, the lv2:InstrumentPlugin type will be added automatically)" but it's obviously not the case.
Am I missing something, or is this a limitation or bug of the lv2 production in faust ?
Thanks !
version : faust-master (2024.05.05) compiled from git on debian 12.5
The text was updated successfully, but these errors were encountered:
faust2jack mysynth
does compile a nice gtk2 app: midi input works, sound output works.faust2lv2 mysynth
produces as expected/usr/lib/lv2
)lv2ls
mysynth.ttl
to
Now Ardour sees it as a LV2 instrument, but no sound is output (all other lv2 instruments work correctly in the same Ardour instance).
Reading the
faust2lv2
script, I do not see any related command switch. I see some mentions of "(For instruments, the lv2:InstrumentPlugin type will be added automatically)" but it's obviously not the case.Am I missing something, or is this a limitation or bug of the lv2 production in faust ?
Thanks !
version : faust-master (2024.05.05) compiled from git on debian 12.5
The text was updated successfully, but these errors were encountered: