189,693 users have contributed to 42,668 threads and 256,812 posts.
In the past 24 hours, we have 1 new thread(s), 4 new post(s) and 48 new user(s).
Dear VSL team, please make this a top priority! I'm considering buying a Mac Pro as a VSL slave, but I'll wait until this is sorted out. I think the whole point in using a server is that you can switch projects or restart the sequencer without reloading samples...
Cheers
Pitt
@PierreFunck said:
Dear VSL team, please make this a top priority! I'm considering buying a Mac Pro as a VSL slave, but I'll wait until this is sorted out. I think the whole point in using a server is that you can switch projects or restart the sequencer without reloading samples...
Cheers
Pitt
If I were you I would also wait until 64bit is possible on OSX, or be prepared to run XP64 or Vista64 via Bootcamp.
DG
And as I said earlier, I can load projects with 7.5GB in my template in around 30 seconds.@benbartlett said:
With all due respect, I think the last poster doesn't quite see the point. It's irrelevant how much (Ram) we can load. It's the fact that it must RELOAD each time we switch projects. In the meantime, multiple instances of VE works well on a mac while we wait.
DG
I agree this should be made a priority for VE3. Reloading each time partly defeats the point of having a slave computer with an orchestra template ready for use in any project / cue. Hope a new version is in the pipeline! Best,
David
Oliver, please try my trick whilst you are waiting for an update to VE3, even if it is going to be possible. At least re-loading will only take 30", if it works with VE3 as well as it does with FXT.
I don't know why people aren't willing to try things that are suggested. The time taken to test would probably be less than re-loading one cue! [;)]
DG
@rpmusic said:
Ok...I think I found it....not really sure what a 'chainer' is though(?). Being a Mac user, I'm not sure if I'm a viable candidate for this work around. Any insight would be appreciated! Thanks
Chainer is just a simple VST host. If you have something similar it would be worth testing out. Bidule maybe?
DG
@benbartlett said:
Regarding Bidule: It's simpler than is at first apparent to set it up. However, it drops midi when it's fully loaded. And delay compensation (in Cubase at least) is not covered properly under re-wire (if you use Bidule that way). As a standalone, Bidule offers no real benefit now that VE can support 64 outputs - allowing you to pretty much address any chunk of your hardware you want.
No, you don't understand. Nothing passes through Bidule. No MIDI; no audio. It is only a way of getting the samples loaded into plugin memory. The advantage being that you can load cues much faster, as VE just checks which samples are already loaded into VE plugin memory. It also means that the sample settings are saved with the project, rather than having to save lots of standalone versions. Obviously I haven't checked that this works with VE, as I was just offering a suggestion to cut loading times between cues from 15 minutes (in my case) to 30 seconds.
DG
@herb said:
The next version of VE3 is in developement, and will offer this feature of samples stay loaded if you switch projects in your sequenzer.
It's a major developement step and will need some time. We expect to have it ready in late summer/early fall.
best
Herb
Herb, will it also be able to save the project as a whole, or will one have to save individual Presets, much as I used to do with GVI and FXT?
DG