Workarounds for RAM Save with Velocty xFade?

[cwillsher]

I only have the one G5 at present and generally make good use of the RAM Save feature to optimise my sample usage. But when using Velocity xFade on ensemble tracks, of course, the RAM Save feature doesn't log the samples used.

How are people getting around this - other than buying more computers and leaving everything loaded? Is the only other choice to bounce/freeze the tracks as audio and replace the patch/remove the instance?

Just wondering if I've missed something here...

Thanks

Colin

[david ender]

@cwillsher said:

But when using Velocity xFade on ensemble tracks, of course, the RAM Save feature doesn't log the samples used.

Hi Colin,

don't know if I'm misunderstanding you - but RAM Save does keep track of samples with velocity xFade on, too. Only it keeps all the layers of one note in memory, so you can still make corrections to xFade without having to optimise again.

Kind regards,
David
VSL manuals

[cwillsher]

Hmmm...Thanks David but this was a problem for me on my last project.

I optimised several VI instances in one pass and many of them stopped playing a large number of notes immediately afterwards. I assumed this was because Vel xFade had been in use on nearly all of them.

Any other reason why this might have happened after RAM Saving?

Do the VIs also take into account if Vel xFade has been switched on and off via a controller within the sequence?

C

[david ender]

Good question for I don't know the answer ... judging from your experience I'd say no, but I haven't tried it myself yet. Perhaps I'll find the time to run a test tomorrow.

Cheers,
d.