Christian Schoenebeck wrote: > Am Dienstag, 22. Januar 2008 18:53:11 schrieb Chris Cherrett: > >> The problem is as follows: >> >> - It eats 2 GB of RAM. I only have 2GB of RAM. >> > > I don't know what your exact setup requirements are. But the first thing you > can tweak of course is the amount of sample points to be precached in RAM by > the sampler, because that's what usually takes the most. Unfortunately this > yet a compile time option: > > ./configure --enable-preload-samples=VALUE > > but as the amount of max voices and disk streams, this is highly on our TODO > list to become a runtime parameter. > If you could advise on this it would be appreciated!
> >> - I cannot separate the channels like channel 1, channel 2. I have to >> run all instruments on channel 1 and route the audio ins. Ardour will >> only see channel 1. >> > > Uh? Why shouldn't you be able to do that? You're using JACK right? So you can > route it as you like. You can create as many audio output channels as you > want with LS. Each channel strip can then be assigned to one of those audio > outputs of LS. You can even create multiple JACK clients for the same LS > instance (e.g. handy in conjunction with jackdmp for load balancing on SMP > and/or multi-HD systems) and you can even create as many effect sends for > each channel strip individually and route it as you like. Maybe I don't > understand what you mean. > > Might be just my understanding level. I will keep playing with it. Thanks! :) >> Is there anything that you guys could help me with that will make this >> process more efficient? If I have to get more RAM will 4GB total do? I >> can compile options if need be, would that help? >> > > That really depends on your exact setup and especially what kind of > instruments you're going to keep in memory (precached) at the same time. > > Would be a nice new feature for JS/QS/gigedit to see the amount resources to > be consumed by an instrument in advance, but unfortuntealy it doesn't exist > yet. But if you really need it for deciding whether to buy hardware > extension, you could calculate it (roughly) e.g. by opening the instrumen(s) > in gigedit and then by multiplying the amount of samples with your > (previously mentioned) preload-samples compile time setting. > > CU > Christian > > I bought another 2GB or RAM and have a fresh 500GB SATA 2 hard drive to run my samples and projects on so that should make a difference. I still would like to the the most out of what I have. Thanks Again! Chris > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ^^ lol! We owe Microsoft a big thank you for sponsoring our email! :) > _______________________________________________ > Linuxsampler-devel mailing list > Linuxsampler-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Linuxsampler-devel mailing list Linuxsampler-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxsampler-devel
