Re: [Linuxsampler-devel] Win32-Integration-Proposal

[Mattias H. <ma...@mu...>]

<be...@ga...> wrote:
>
> About FXT, ok but the problem is we want a free windows client.
> I doubt he will make a (even closed source) client for us.
> Or perhaps he will open the protocol and we will use a FXT-compatible
protocol.
> So that LS works with both our free client and with FXT ?
> Or alternatively we develop our own network protocol and since the specs
> are open the FXT guy can add support to FXT so that you can use an LS
machine
> and a FXT client.
> There are many possibilities, but I guess that he will try to keep
> his protocol closed in order to avoid cannibalizing his sales.
Ok, it seems he's actually been planning a Linux version of the FXT server.
No planned timetable though so far and without no doubt the Mac version (OS
X btw so it's not too different) has precedence right now... Anyway, LS
would need to support Jack or LADSPA in order to work with the FXT server
when it finally shows up. I'm very new here but didn't I at least read
something about Jack support the other day? If that is the case both
solutions (FXT and the "native" LS solution) could be used.

> Anyway network streaming is not as hard as one might think,
> Some tunable client buffering and it works.
> Writing a VSTi is not hard either, the APIs are really straightforward.
Agreed, this is at least something I can confirm. I've touched network
streaming in a few projects and I've messed a bit with the VST SDK too
lately and it's very straight-forward.

> Since LS usues a TCP socket for the GUI controls and since we plan
> to use the Qt library (which allows for crossplatform GUI code) so
> we can embed the GUI controls directly into the VSTi without problem.
> This would be userfriendly since you have an all-in-one solution.
Very cool solution.

/Mattias