Rui Nuno Capela

thanks, after all I believe it's actually qjackctl to blame in coping with qtractor higher MIDI resolution (ppqn) since v0.9.29... only the qjackctl BBT display is affected, in some circumstances.

I was wrong: it's actually qtractor jack-timebase BBT info to blame here; please check whether qtractor >= 0.9.31.32git.[1d5253](https://github.com/rncbc/qtractor/commit/1d52532a) behaves any better in this regard.

positioning the playhead with left-clicking is always achieved with the Shift or Ctrl modifiers; there is no option to change that otherwise. maybe you're referring to "Reverse *middle-button* modifier role...

is it the only one vst3 over yabridge that shows that way? what about the native ones (not on wine)?

meant if only that plugin in particular (not yabridge in general) please test with other plugins if you can

it seems to show up like that only on first time, while that plugin is boat-loading its huge sample-pack ... what happens if you close the GUI and open it...

fwiw. it shows up here in full on ubuntu 22.04 lts; yabridge 5.0.4; sometimes not, thus the call to just open the editor a 2nd time later. you may try...

yes, it probably uses the first it encounters in given m_lv2_features, as qtractor does have its own LV2_STATE__mapPath hook; it doesn't use any of the other though. do you have...

yeah you're certainly right; it all actually depends on how the lilv::add_features(() works, whether to append or prepend the lilv local map_features etc. it even might have changed across lilv...

my take for the fix in lilv side: ```diff diff --git a/src/state.c b/src/state.c index c8e8f14..9c284fb 100644 --- a/src/state.c +++ b/src/state.c @@ -378,6 +378,12 @@ add_features(const LV2_Feature* const* features, { size_t...