[Lmuse-developer] Fwd: lv2 host support status

[Robert J. <spa...@gm...>]

Was goint to send it to the list


---------- Forwarded message ----------
From: Robert Jonsson <spa...@gm...>
Date: 2014-10-19 14:27 GMT+02:00
Subject: Re: [Lmuse-developer] lv2 host support status
To: Andrew Deryabin <and...@gm...>


Hi Andrew,

2014-10-19 3:20 GMT+02:00 Andrew Deryabin <and...@gm...>:
> Hi, Robert!
>>
>> Hi Andrew,
>>
>> 2014-10-18 20:49 GMT+02:00 Andrew Deryabin <and...@gm...>:
>>>
>>> Hi, All!
>>>
>>>       Now lv2 host supports  state save/restore for lv2 rack plugins.
>>>
>>> At this time all major lv2 plugin features are supported. Any testers
>>> are welcome :).
>>>
>>> P.S. Is anybody here?
>>>
>> Yep, checking in. And it's wayy to late to start any testing but I will
>> soon.
>>
>> I did a bit of testing yesterday, or rather two days ago.
>> Had no trouble with what I tried, apart from drumkv1 which didn't
>> store it's settings, but I wanted to reserve judgement until I tried a
>> more recent version of it but couldn't manage to compile it.
>> I see it's possible to choose which GUI to open for the plugins, neat!
>> An enhancement, to limit the number of clicks needed to open, would be
>> to add it as a submenu to the first menu, or maybe a preference
>> setting which guis to prefer.
>
> I've spent some time to figure out why the latest version on drumkv1 leads
> MusE to crash while opening gui. By default it uses qt5 if it's installed
> and all options to force use qt4 are not working while compiling. I had to
> rename my /usr/lib/qt5 to /usr/lib/qt5__ and rename /usr/lib/qt4 to
> /usr/lib/qt to make it compile against qt4. Then it loaded without a
> problem. May be in your system drumkv1 has the same problem...
> Checked now - settings are saved and restored, tempo sync working (for delay
> effect). I'am using version 0.5.1 compiled from source now.

No the problem for me was to get it to compile at all, somekind of
conflict between qt4 and qt5, includes point to qt4 but somehow it
fails on some qt5 stuff.

In the end I found that debian had a 0.5.1 package that I was able to
install. It doesn't work that well though, a shame as it seems to have
great potential.
I did get it to recall the loaded settings, but it didn't playback the
samples until I clicked on them in the file selector.
I suppose I should try it in another host to see if it behaves similarily.

>
> And what about gui select popup - I'll try to implement submenus - thanks
> for idea :).
>
>>
>> One thing I've been thinking about, now that I'm writing. It's not
>> specifically about lv2 but more a general question, if we should allow
>> effects to be added as tracks, like synths are added. MusE is mostly
>> built for stereo, not the least the plugin racks, but there are
>> enhancements for routing between track-types. I'm not 100% as I
>> haven't tried but I think it would allow us to use sidechain effects
>> in a pretty usable way.
>
> Sidechain works that way, but only for audio now, not for midi. But for midi
> - may be more correctly is to implement rack plugins for midi tracks and
> filter only plugins (dssi/vst/lv2) that have at least 1 midi input and 1
> midi output? That's the subject to think of...
>
About audio I'm not sure what you mean. I believe only plugins
registered as synths are displayed in Add Synth menu the arranger.
There are for instance some plugins Calf* Sidechain which aren't
visible there. They aren't synths so that's fine. But, since the
effect rack can only connect mono and stereo plugins it's not possible
to connect the sidechain there.
I'm arguing that it would be useful with an Add effect menu item also,
for plugins that benefit from connecting more inputs/outputs.

For midi, sure it would be cool to add a plugin rack to midi tracks. I
suppose we are quite a bit away from realising that though.

>>
>> More, better, testing coming up.
>> I want to try doing some music with these things but keep bumping into
>> annoying small bugs, unrelated to LV2 ;)
>
>
> Thanks! Waiting for results :).

I tested some more, Vex synth, DrumSynth, Tal-filter2, dRowAudio:
Reverb. drumkv1.
I had some random krash closing the gui in drumkv1 plus the issues I
mentioned above. otherwise it worked pretty good.
I routed the Vex synth through the tal filter2 and further into the
dRowAudio reverb accompanied by a simple rythm in DrumSynth. Sounded
very spooky ;)
A was a bit sad though that it wasn't possible to automate the filter
in tal-filter2. It sounded very cool sweeping the filter by hand. I
suppose that's a limitation of the plugin though.

All for now. Really great work!

Regards,
Robert


>
> Regards,
> Andrew
>
>> Regards,
>> Robert
>
>