LinuxSampler VSTi plugin
-
- Advanced User
- Posts: 147
- Joined: Fri Sep 26, 2008 9:04 am
LinuxSampler VSTi plugin
I have read on the homepage that experimental vst support was implemented.
Are there any plans for a official release?
I wanted to buy Tascams GVI for use with Repaer in a network (with ReaMote: network vst rendering) but I face a problem with the usb dongle when I install GVI on a seperate machine. To make it work GVI has to be installed on the main computer (for using the GUI, no sampel playback) and the network machine (for sample playback). I would need a second usb key and license...
I would really appreciate a vst-version of linuxsampler to solve this issue.
Martin
Are there any plans for a official release?
I wanted to buy Tascams GVI for use with Repaer in a network (with ReaMote: network vst rendering) but I face a problem with the usb dongle when I install GVI on a seperate machine. To make it work GVI has to be installed on the main computer (for using the GUI, no sampel playback) and the network machine (for sample playback). I would need a second usb key and license...
I would really appreciate a vst-version of linuxsampler to solve this issue.
Martin
Re: VSTi status
Maybe we finish a new release this year, but no guarantee.
-
- Advanced User
- Posts: 147
- Joined: Fri Sep 26, 2008 9:04 am
Re: VSTi status
This sounds great.cuse wrote:Maybe we finish a new release this year, but no guarantee.
I just started to convert all my gig files to Kontakt / EXS but it's a real pain.
I would love to stick with the original format.
Having an AUi or VSTi of linuxsampler would make things so much easier.
I hope we will also get a 64bit version of linuxsampler with AU/VSTi support, since GVI 4 will never be released.
Re: VSTi status
Are you planning to use the open VST headers which are used by dssi-vst or some of this "download the sdk and ... "stuff?
Re: VSTi status
Currently it is required to download the vst sdk from steinberg to be able to build linuxsampler as a VSTi.Steele wrote:Are you planning to use the open VST headers which are used by dssi-vst or some of this "download the sdk and ... "stuff?
Re: VSTi status
why don't you change to the open source headers?
Re: VSTi status
I'm not sure, but I think vestige is missing features that are used in the linuxsampler vsti, the get/set chunk functions.
Re: VSTi status
Hi, in principle LinuxSampler VSTi already works quite nicely (Andreas and me are testing it under various sequencers, I'm using reaper),
what currently still needs to be fixed is the ability to use FX sends in LinuxSampler VST since it will allow to provide midi controllable FXes
for GIG samples using the sequencer's FXes. (eg reverb,chorus etc).
As cuse said not sure if we can release it till the end of the year but the finish line is in sight
I hope that VST users will find LS VST useful as it provides perfect integration with familiar sequencer environments while retaining all
chracteristics, functionalities and performance of LS. LS VST has even the advantage that by opening multiple instances you can take advantage
of multicore CPUs and achieve a polyphony of several hundreds of voices (the bottleneck is usually the disk).
As for 64bit support, an unofficial mingw version (gcc for windows) already seems to support generating 64bit binaries on WIN64
http://sourceforge.net/projects/mingw-w64/
so we could try to compile LS VST in 64bit mode and see if it works.
BTW does reaper now support 64bit VSTis on WIN64 ? (probably no LS developer currently has a commercial 64bit capable (cubase,sonar) VST sequencer to test.
keeping you posted about the progress
what currently still needs to be fixed is the ability to use FX sends in LinuxSampler VST since it will allow to provide midi controllable FXes
for GIG samples using the sequencer's FXes. (eg reverb,chorus etc).
As cuse said not sure if we can release it till the end of the year but the finish line is in sight
I hope that VST users will find LS VST useful as it provides perfect integration with familiar sequencer environments while retaining all
chracteristics, functionalities and performance of LS. LS VST has even the advantage that by opening multiple instances you can take advantage
of multicore CPUs and achieve a polyphony of several hundreds of voices (the bottleneck is usually the disk).
As for 64bit support, an unofficial mingw version (gcc for windows) already seems to support generating 64bit binaries on WIN64
http://sourceforge.net/projects/mingw-w64/
so we could try to compile LS VST in 64bit mode and see if it works.
BTW does reaper now support 64bit VSTis on WIN64 ? (probably no LS developer currently has a commercial 64bit capable (cubase,sonar) VST sequencer to test.
keeping you posted about the progress
-
- Advanced User
- Posts: 147
- Joined: Fri Sep 26, 2008 9:04 am
Re: VSTi status
This is so good news!
Right now it supports only 64bit plugins. 32bit vstis don't show up.
There is also one nice thing: The x64 preview also includes a 64bit "remote" - the network vst streaming component of reaper.
One more question: Is it possible to compile also a Mac VSTi?
The OSX Version of linuxsampler needs JackOSX which crashes quite often. It woud be great if Jack could be avoided.
As far as I know it does. There is a x64 beta available: http://reaper.fm/files/2.x/reaper253_x64-install.exesbenno wrote: BTW does reaper now support 64bit VSTis on WIN64 ? (probably no LS developer currently has a commercial 64bit capable (cubase,sonar) VST sequencer to test.
keeping you posted about the progress
Right now it supports only 64bit plugins. 32bit vstis don't show up.
There is also one nice thing: The x64 preview also includes a 64bit "remote" - the network vst streaming component of reaper.
One more question: Is it possible to compile also a Mac VSTi?
The OSX Version of linuxsampler needs JackOSX which crashes quite often. It woud be great if Jack could be avoided.
Re: VSTi status
Did I get it right that the goal is to load wrapped win32 VST-instruments (vsti) in a Linuxsampler channel and save them (with their settings) as a linuxsampler project? so channel one is a .gig and channel two some VSTi-instrument?