hi there,
i can't get Linuxsampler lv2 version to keep it state after save/close in qtractor.
i tested qtractor last version and svn : same error
Linuxsampler's dev said LS is using the lv2-saverestore extension.
Is it because Qtractor does not support this extension, i can't save/restore LS state in Qtractor ?
Re: lv2-saverestore
You're correct, Qtractor doesn't support the saverestore extension, yet.
I'll have a look at it soon.
Byee
cool :D
im glad to hear this.
thx man ;)
Re: lv2-saverestore (DONE)
Today's SVN trunk already has it for the grabs (qtractor-0.4.5.1529+).
Don't be shy and please tell whether it works for you, specially re. LinuxSampler LV2 plug-in. It does seem to work for me ;)
Enjoy
lv2-saverestore : working here too !!
hi Rui,
i gave the last svn version a try, and linuxsmpler lv2 is working fine here.
man that's really cool. qtractor is becoming something really interesting, thx to you.
Brother, lv2-saverestore mission for qtractor is a success !!!
see ya ;)
Re: linuxsampler (lv2)
Awesome!
May you disclose a little bit about the ways you're using the linuxsampler lv2 plugin? Do you use it on a MIDI track (single channel) or bus (multi-channel/timbral)? How many plug-in instances and/or sampler channels are you using effectively? Does the lv2-saverestore extension work without clashing on all scenarios? Which linuxsampler front-end do you use for setting up sampler channels? Qsampler, Jsampler (or is it raw lscp via telnet/netcat like real men do:) ?
Seeya
lv2-saverestore testings
hi Rui
Do you use it on a MIDI track ?
- Yes, everything is working just fine
or bus (multi-channel/timbral)?
- Yes i tried this configuration too, no problems to report, i just have to figure out how to route the plugin audio and to add FX on each instruments. Maybe the simplest way would be to use one sampler instance for one track...
How many plug-in instances and/or sampler channels are you using effectively?
- not that much : 5 or 6
Which linuxsampler front-end do you use for setting up sampler channels?
- Jsampler, sometimes Qsampler
if you have other question just go ahead and ask :)
thx man
how to use it?
From which version of Linuxsampler is this supported?
You add linuxsampler as plugin, but how do you add an sample? Or do you start linuxsampler outside qtractor first?
Re: how to use it?
LinuxSampler 1.0.0 comes ready in both LV2 and DSSI plugin forms. Just add one instance to a MIDI track or bus and linuxsampler server will get automatically started behind the scenes. Then you can use your preferred LS front-end, either Qsampler or Jsampler to add and manage sampler channels, as usual.
nb. each LS plugin is seen as one device instance of the PLUGIN device type which gets in use by each sampler channel (this is all LSCP parlance:). You don't get the usual/integrated GUI for each plugin instance. You use a regular LS front-end instead to manage all sampler channel instances, including the ones which might not be inserted as plugins at all, ie. the regular stand-alone LS use cases on device types JACK, ALSA, etc. Yep, kitchen-sink approach :))
Just try :)
Cheers
benefit?
"linuxsampler server will get automatically started behind the scenes."
> Is it also possible to start it with an lscp file like:
cat /home/user/linuxsampler/piano.lscp | nc localhost 8888 &
?
> What is the benefit of using it as plugin instead of standalone app?
thanks,
Re: benefit?
Is it also possible to start it with an lscp file ?
- yes, of course
What is the benefit of using it as plugin instead of standalone app?
- the host (eg. qtractor) will take care of saving and restoring session state seamlessly; after all that is the whole purpose of the OP ;)
Cheers
Post new comment