On Tuesday, May 16, 2017 11:17:07 Andrew C wrote:
> Not sure if I should post this here or to LAU, but here goes.
Don't worry, there is not much traffic around here.
> Finally I've decided to step into the modern age of plugins running in
> hosts as opposed to having everything standalone and hoo
Rosegarden does not support LV2, sadly. I think it is on the developers'
'to do' list Soon(tm).
>The usual work flow with any plugin standard I know of, is usually one
>(instrument) plugin instance per DAW track.
Yes, I seem to be barking up the wrong tree at the wrong people.
AFAICS, LinuxSample
On Wednesday, May 17, 2017 19:53:03 Andrew C wrote:
> Rosegarden does not support LV2, sadly. I think it is on the developers'
> 'to do' list Soon(tm).
>
> >The usual work flow with any plugin standard I know of, is usually one
> >(instrument) plugin instance per DAW track.
>
> Yes, I seem to be
On Wednesday, May 17, 2017 21:28:09 Christian Schoenebeck wrote:
> For the small minority of users [ you ;-) ] who want a different plugin
> behavior: Like I said, simply launch your plugin instances, then open
> QSampler and modify the sampler internal MIDI routing as desired. So you
> can also ho
Thank you so much for the indepth response, Christian! I was a bit slow on
the uptake of the design workflow here with plugins...
Did some more RTFMing and googling to make sense of it.
>What I must add here, and maybe that's the missing brick for you to solve
that
>issue: Even when using the plug
On Wednesday, May 17, 2017 21:30:09 Andrew C wrote:
> So if I have one midi input port for the linuxsampler instance, I can,
> using qsampler, simply add extra channel strips and create 'layered' sounds
> for that particular port.
>
> Midi Port 0: Violins, Cellos, Violas, Basses sustain patches lo
