[LV2] Startup slloowwss dooooowwwwnn???
brummer- at web.de
Wed Oct 29 21:24:17 PDT 2014
Am 30.10.2014 01:32, schrieb David Robillard:
> On 2014-10-27 13:59, hermann meyer wrote:
>> Am 27.10.2014 14:56, schrieb Stefano D'Angelo:
>>> 2014-10-27 7:33 GMT+01:00 hermann meyer <brummer- at web.de>:
>>>> Am 27.10.2014 01:56, schrieb David Robillard:
>>>>> On Thu, 2014-10-02 at 17:19 +0200, hermann meyer wrote:
>>>>> I have been meaning to add a config file for lilv to be able to disable
>>>>> dyn-manifest (and thus naspro bridges) at run time. Hosts can
>>>>> do this, but there's no easy mechanism to do it globally.
>>>> Maybe a config switch were doubled plugs could be switched of generally,
>>>> instead print warnings about, would be good?
>>>> As far I remember right, the problem with naspro seems to be that it not
>>>> only add the ladspa plugs to the world, but scans again the existing lv2
>>>> plugs and double them up, which leads to a huge amount of error
>>>> messages in
>>>> the terminal. My terminal cache was overflowed by the amount.
>>> FYI, NASPRO bridges scan LADSPA_PATH and DSSI_PATH (or default paths
>>> if not set). They won't scan LV2_PATH and won't "double" LV2 plugins.
>>> What you probably see are LADSPA plugins being loaded where you also
>>> have LV2 versions (e.g. swh, invada). In these cases there is a
>>> mechanism to avoid the "duplication" using dc:replaces in ttl files (I
>>> don't know if Lilv supports that automagically?). The bridges also
>>> don't print anything on stdout/stderr.
>> As I said, this behavior I notice with a updated LV2 core and not
>> updated naspro-bridges.
>> With updated naspro-bridges, I receive just a single error message.
> Did you recompile lilv in the process?
> dyn-manifest support is a compile-time lilv option.
I'm using debian/sid, standard packages from the repro, selected updates.
More information about the Devel