Usually I just use flex machines for everything, and try to keep my projects small. But the other day I found myself running out of memory, so I used a static machine to hold 2 fairly large wave files.
Heres the issue..
I have scene B setup with the slice parameter to play different slices than scene A.
So that by moving the slider, I can have almost infinte variation options just on one pattern.
When I had these tracks on the flex machines, using the fader to play different slices/pieces was instantaneous and accurate in where the slices played from. So I could use muscle memory to play certain phrases, based on where I was on the slider.
However, after moving these two tracks to static machines....that trick of using muscle memory dissappears, because theres noticeably less accuracy in what slices play where, and even if they will play at all. Theres also very noticeable latency in me sliding the slider, and hearing the slices playing different slices. Like quickly sliding from left to right and back again on a flex, would play a neat little pattern, but now doing that, does nothing, since the slide seems to be too fast to even register??
Anyone else experience this? Its unfortunate, because most of the time, I need this feature, with larger "songs" sliced into bits. And static machines are perfect for such tracks. But this glitch removes any reliability in a live setting.
Any ideas on what can be done?
I guess just try to downsample and compress the tracks further?? So that I can use them on flex machines without taking all the memory.
Or do I just have a faulty machine?? It would be nice if someone could try with theirs and give me some feedback. Slice a large static track into 64 slices, and lock scene B to different slices. Then play with the fader. Then do the same with the exact same track on a flex and compare the results.