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
-
Yesss! I agree! Dear Vienna Team: PLEASE make it a priority! Otherwise it´s a pain, a mistake in design. Even with 64bit-PCs: it makes no sense to reload 16GB for a little cue again and again. Just imagine 32GB!!!... Many of us are film composers, so: Is there hope soon???? Best Oliver
-
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! ThanksChainer is just a simple VST host. If you have something similar it would be worth testing out. Bidule maybe?
DG
-
30 seconds for 7.5 GB is WAAAY too slow. We need snap snap bang - loaded. If you translate that to 16GB that would be a whole minute. Plus, each load and re-load can slightly fragment memory, eventually leading to unnecessary memory consumption. At present, a slave hardwired is really the only method right now, if you are working on multiple cues or projects at the same time. We already have the discipline to make sure our templates "fit". Thanks.
-
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.
-
Thanx a lot Herb for a clear statement.!!! Best Oliver (Does it have to be that long?))))))))
-
@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
-
@herb said:
At the moment you save the whole sequenzer project including the VE3 network instances on your slaves.
Do you mean with "project" VE3 exclusively?
best
Herb
I was thinking that if there was the opportunity to disconnect whilst loading a new Cubase project file, then how would that affect all the samples that are currently saved whilst using a project? With GVI one could either save the samples,. which resulted in the being dumped from memory when opening a new project file, or the other option was to disconnect from Giga, which meant saving a Preset for each cue. Maybe this is all a little OT, so feel free to email me if you'd like to continue this discussion.
DG
-
Bidule: I think it would be worth checking that it did work with VE. I can see your point, and that it would work with Vienna INSTRUMENTS. However, on the Mac at least, a VE instantiation occupies it's own memory space, and so would ignore (I believe) the presence of other VE instances. My Bidule point (missing yours, I admit) was a parallel one.... B