Re: fst-1.8 triggers wine-preloader processes using a lot of ram

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Paul Davis:
On Thu, 2006-06-22 at 18:37 +0200, Benjamin Fabricius wrote:
Hi all,

ive made some more progress on the madi vst server.

now ive got following problem. i am planing on being
able to run a large amount of plugins as i route 64 channels
of audio i/o.

fst seems to start a dedicated wine-preloader process for every
plugin that is loaded. this causes my ram to decimate very
quickly and thats one thing i dont have a lot of. 512MB - Ramdisk
(running kind of an embedded system).
after starting 15 - 17 plug instances there is none
left obviously. is there a possibility of using only one shared wine
process or does anybody out there know a different work around to this
problem?

kjetil's vstserver design works this way.


Not really. I think vstserver V0.0.1 or something ran everything in one process. But I changed it quickly because if one plugin crashed, the whole server went down as well, I'm not sure how bugfree v0.0.1 is though. It
might still work...



[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux