Precisions about audio engine ON/OFF ?

[Vincent]

Hi all,

Since can drive Usine to it's limits regardless to the system ones, I'm facing some strange questions:
- What exactly means Audio engine OFF (ex. the Master section is still ON when Audio is OFF)? Are there two audio engines(!)? Or is it still ON but disconnect from the Tracks in/out? Or is there some kind of patch-bay between tracks in and tracls out? I don't understand! Audio Off manly looks like some "freezing" feature.
- What is OFF when audio is OFF, and what stays ON (can be usefull to know! eg. inserts, etc...)
- Other questions soon if I can't answer by myself!

Thanks.

[senso]

OFF mean all tracks are totally disabled; but the master section is still active.
Why this strange choice?
Because the master section can be used for a stage monitoring system so always active.

[Vincent]

Not such a strange choice, I understand.
I was just getting confused with the words "Audio Engine Off". In fact, Usine is never Off and you can't turn it off. Tracks are just totally disabled.
Master section can also be used to patch heavy VST or VSTi that are always used, whatever wkp you load, making loading quicker.
But this could need a lot of busses and additional audio in/out. It also may look like a non-logical concept. Having a VSTi placed side by side with master processing could seem weird. It would have be more ergonomic to have a specific bay/area for this (in the audio On/Off perimeter or not, I don't really know).
Besides, loading a wkp needs so many ressources that the master section generally cannot be used at the same time for sound processing.
That raises other questions:
It appears to me that busses sometimes don't work exactly like simple connections (eg. when you use 2 SendToMidi toward the same GetFromMidi). They are not only 'non visible' wires, right?
- Are busses greedy compared to simple wire conections?
- What exactly makes them different?
- Since I don't know how to follow invisible wires, I sometimes loose my busses. It would be nice to have a listing function that crates a *.txt file, or better, some kind of "Busses-tracing panel" on which you could click to find the bus.

Thanks.
V

[senso]

the main difference between buses and wire is that a bus can introduce a small latency, depending on the track order:

1) send on track1 and receive on track 2 -->>> no latency
2) receive on track1 and send on track 2 -->>> small latency (one bloc)

since the "master input" is calculated first, if you put a send on it and a receive on a track --> no latency
at contrary, the "master output" is calculated at the end.

[Vincent]

Okay, thanks Olivier.
One cycle latency won't kill me.

But since this works fine:


this does not:

So I think that the busses sometimes don't work exactly like wires and I would like to know in which ways.
(sorry to be OT 'audio engine off')