|
From: Matthias W. <mat...@in...> - 2002-11-11 21:23:43
|
Hi all! I'd like to know your opinion about some thoughts regarding the GUI. As mentioned by Benno and Steve, when linuxsampler will run as a plugin of jackd, it'll be necessary to use some sort of communication mechanism between the plugin and the GUI. While the stability plus and the code cleanness due to the forced separation of engine code/GUI code are very attractive, there are also some difficulties connected with it. I think linuxsampler should also have the ability to create a sample instrument/set. Therefore it will be necessary to edit wave files, set loop points etc. Now the first problem that occures to me: how do I generate the waveview of the sample data when the samples are on one machine and the GUI on the other? Should I pregenerate the sample view data on the plugin machine and send it to the GUI machine? And if I edit the sample, should the edit commands be send over the net to the plugin machine, the plugin calculates the result, obtains the new sample view datas and sends them back? This seems to get really complicated. It also makes an idea of me impossible to imbed an existing wave editor as a component (e.g. as a bonobo component) into linuxsampler. In that case we would not have to reinvent the weel and write the XXX's wave editor but use an existing one (e.g. snd). But AFAIK the existing ones have no capabilities of remote control. matthias |