this is very bad news
what the f@#!!
what the f@#!!
in live 6 i can't make any larsen by self feeding the returns tracks anymore!!!!
this is very bad news
this is very bad news
-
Robert Henke
- Posts: 1193
- Joined: Fri Jun 04, 2004 10:38 am
- Location: Berlin
technical background:
disabling sends in return tracks reduces the amount of internal feedback connections. this has two good effects:
a) it reduces CPU load
b) it makes latency compensation easier. under certain conditions the crossfeedback introduces a significant und inevitable increase in overall latency.
This is why we turned them off by default in Live 6.
( if you want them all on per default just create a template set )
Robert
disabling sends in return tracks reduces the amount of internal feedback connections. this has two good effects:
a) it reduces CPU load
b) it makes latency compensation easier. under certain conditions the crossfeedback introduces a significant und inevitable increase in overall latency.
This is why we turned them off by default in Live 6.
( if you want them all on per default just create a template set )
Robert
-
Johnisfaster
- Posts: 7251
- Joined: Thu Sep 29, 2005 8:34 am
- Contact:
so robert, does this cpu reduction apply even when compared to a send that is set to negative inf? as in, disabling a send is more cpu efficient than turning it all the way down?Robert Henke wrote:technical background:
disabling sends in return tracks reduces the amount of internal feedback connections. this has two good effects:
a) it reduces CPU load
b) it makes latency compensation easier. under certain conditions the crossfeedback introduces a significant und inevitable increase in overall latency.
This is why we turned them off by default in Live 6.
( if you want them all on per default just create a template set )
Robert
It was as if someone shook up a 6 foot can of blood soda and suddenly popped the top.
-
Johnisfaster
- Posts: 7251
- Joined: Thu Sep 29, 2005 8:34 am
- Contact:
I would have, but I am kinda assuming that the cpu increase is so minimal that I may not even be able to see it on the cpu meter, I was thinking that if it was an increase in cpu it would be a more behind the scenes increase
It was as if someone shook up a 6 foot can of blood soda and suddenly popped the top.
-
Johnisfaster
- Posts: 7251
- Joined: Thu Sep 29, 2005 8:34 am
- Contact:
just tried it with a whole bunch of sends containing reverbs and a breakbeat, though all of the sends were set to inf. disabling and enabling made absolutely no change to cpu that I could detect. so I was hoping robert could clarify.
It was as if someone shook up a 6 foot can of blood soda and suddenly popped the top.
-
Robert Henke
- Posts: 1193
- Joined: Fri Jun 04, 2004 10:38 am
- Location: Berlin
-
Pitch Black
- Posts: 6722
- Joined: Sat Dec 21, 2002 2:18 am
- Location: New Zealand
- Contact:
Robert Henke wrote: disabling sends in return tracks reduces the amount of internal feedback connections. this has two good effects:
a) it reduces CPU load
b) it makes latency compensation easier. under certain conditions the crossfeedback introduces a significant und inevitable increase in overall latency.
Robert
This is a new revelation for me, as I've been using live sets of 110 tracks, bussing through six subgroups that I originally put in there to speed up hardware output assinging. I'm going to investigate if routing all tracks direct to the hardware outs gives a significant performance boost...
I'm guessing that it should? I never alter anything on the busses themselves, so I don't actually need them.
*dashes off, pulling on lab coat*
MBP M1Max | Sonoma 14.7 | Live 12.1 | Babyface Pro FS | Push 3T | clump of controllers
Soundcloud
Ableton Certified Trainer
Soundcloud
Ableton Certified Trainer