Radium

this would make mixing a lot easier. of course there should be an option to automatically make the new busses invisible in the sequencer

yeah, that's what i was thinking of!

one question (i can't test this myself rn): do you have to manually retrigger the sample whenever you change the starting point, or does it automatically retrigger when you set the value?

any way to chop up samples using track commands or automation, like in traditional trackers?

haven't found anything myself

ok for future reference, it's when you give two tracks the same instrument

now i figured it out

in this picture, you can see that track 3 and 4 are grouped together somehow:

how do i do that? i haven't been able to figure it out myself

okay so this is more addressed to anyone reading this thread rather than you, kjetil, but i was experimenting with the whitelist and i discovered that the hanging thing i mentioned earlier was because lv2vst was trying to load every lv2 on my system, since i didn't have a whitelist at the time so wh...

whelp, it works now! i had to make a whitelist and put it in the same dir as lv2vst.so and add some plugins to it by using the output of lv2ls. once i do that, my lv2 plugins show up in the plugin manager! of course, i'll have to check what crashes and what doesn't (i tested vitalium lv2 and it cras...

really? i have my LV2_PATH set to /usr/lib/lv2 and it still isn't working

also tried adding fluida (https://github.com/brummer10/Fluida.lv2) to the whitelist and that isn't working

by any chance, did you get something like this whenever you scanned for plugins?

whelp screw my sleep schedule lmao

i'll try using the whitelist (actually the readme has an example line for the x42 plugins). i'll test that

i would, but the host would also need to lack lv2 support to get a reliable result, and i don't know any linux vst hosts that don't also support lv2

of course, maybe i could try to find a setting to just turn off lv2 plugins and test it that way

i'll test this tommorow, i'm in bed atm