|
From: Matthias W. <mat...@in...> - 2002-11-12 20:16:40
|
On Mon, Nov 11, 2002 at 11:53:02PM +0000, Steve Harris wrote: > On Mon, Nov 11, 2002 at 10:20:06 +0100, Matthias Weiss wrote: > > 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? > > I would say that you only send graphical inforamtion to the GUI, and it > sneds instructions back to the engine, which executes them. That's what I called "sample view data". > The ammount of data in a visible lump of waveform is acutally pretty low > if you think about it, you cant see more than a couple of thousand samples > at once. I agree, but it seems to me that the effort to create a remote GUI is considerable. Running it remote via network might also have an impact on the latency side because of the interrupts generated by the NIC, of course when running it locally, this wouldn't be a problem. Further, as I outlined in my previous mail, it propably won't be possible to integrate an existing wave file editor in the sampler app which I'd consider a true drawback. matthias |