CPU obsession (a new frenchie-soporific movie)

[Vincent]

Hi Olivier, hi usiners.

I'm working now with the sequencer view. It's really very very powerful.
You can have all the automation you've ever dreamed of, and much more!
Absolutely vertiginousse (breathtaking).

I have five questions:
_
1
In track 1 I have a patch where I put a Synchro. I've also put there a Preset with a User Curve connect to it.
That way, I can store eg. tempo changes in presets and change presets with my curve.
Of course, if I forget to store it while Synchro is ON, the sequencer just stop when recalling that preset!
It may be useful... I think I just have to be careful, this is not a bug, right?
OK.
_
2
I can also put there a Mixer Track Output. I imagine that I'll be able, just like before, to put any other track OFF (and be careful not to self-put-off the track 1...)
Well, no! The only control that I cannot change is the ON/OFF switch!
Not useful... I think this not a bug, right?
OK.
_
3
About RAM and CPU, my obsession. And the obsession of my computer too.
Let's say that I need patch 1 mn at the beginning and 1 mn at the end of my piece of 6 mn.
I suppose it's better to have it short at the beginning and again one more time short at the end, right?
Is it the same instance or is it loaded twice?
And what about CPU when cursor is between these two patches? What means exactly activate/deactivate? I guess it's not similar (CPU speaking) to activate or deactivate a track.
_
4
About Presets, maybe a bug, I don't know:
I have the same problem with Conductor, many interface controls seem not to be stored, thou, sometimes their values are good, sometimes no. I've tried many times with different manners. I never have the full Preset right like the one I stored ...well, OK, just almost never.
But it's to much hazardous for me!
_
5
About the current bloc size.

Important: You must verify that this parameter is always set to 64, 80, 96 or 128 for best performances.

Nothing directly to do with patching in Usine night and days, but what does it mean exactly? Which is better, 64 or 128, and why (I can change easily if necessary)?

Thanks!

[senso]

hello

04:04:58

really crazy man!

A quick morning response.

1) not a bug: the synchro on/off is a normal stored param. Very usefull to create breaks.

2) not a bug, more a choice. In the next version, there is a new module call "activate 'on/off)" that can switch the current patch off. (the patch can disable itself...)

3) take a look on the concept of 'cloned patches'. Put a patch at the begining and a cloned version at the end. (loaded once in memory)

4) I'm working hard on presets and conductor. Will work much more efficiently in the next version.

5) some optimized intern functions are enabled only if the bloc size is a multiple of 16 (SSE instructions). It's a mistake on the manual, 128 is a perfect value.

thanks for feedbacks

[Vincent]

Thanks, Olivier.

I forgot to use Cloned patches. Must be hreat solution.

04:04:58

really crazy man!

Don't you mix up "craziness" and "freedom"?