3phase wrote:Khazul wrote: setting up a feedback route without realised it
so there are ways to set this up without realising it?
how? can you give some examples?
If you are working with bog standards, tracks -> master, sends -> master it isnt going to happen.
IF OTOH you routte all your returns to their own submix and forget tpo disable the sends on the fx submix, then you have a feedback loop - even if by default live will eventually throw away the feedback audio if the send levels are all -inf. You need to disable such sends unless you really want them for actual feedback.
Its not just direct feedback loops - you have to consider indirect as well, for eg, create a submix on sends to key a compressor, but forget to disable the send to the key submix from the track containing the keyed compressor.
Any feedback loops seems to cause a huge timing shift (because Live probably stores the feedback audio buffers for the buffer next calculation cycle). Im guessing it calculates buffers one at a time for simplicity on multicore load distribution and overall cpu efficiency rather than tying to calculate a sample from each which would have the immediate benefit of offsetting feedback loops by only a single sample rather than at least a whole plugin buffer which is either you audio interface buffer size, or I think 32 samples depending on set preferences. (Related here, you allways talk like there is one summing bus - there isnt - there are potentially loads of them running within live at the same time - every audio/fx/drum/instrument rack with mutiple chains, every group track, anywhere where mutiple tracks are routed to the same submix track etc etc - these are all sync points where live has to deal with multiple buffers simulateously each probably with their own offsets.)
How audiable these are depends on what yo are doing with the resulting delayed audio. It can be as little as no effect at all, just when you are working there seems to be an inexplicably high latecy all the time, to a track being subtley out of sync, or quite severe combing effects. The end result depends on alot of factors, but all easily resolved by ensuring unnessary sends are allways diabled.
You will notice when you disable a send that is the source of a possible feedback loop as there is a tiny delay in the UI while it re-organises plugin delay compensation and quite possibly reassignment of audio pathways between available CPU cores to deal with the change properly. In earlier versions there used to be another good reason to be careful of sends and that was because of how live appeared to partitioned audio pathcways between CPU cores, so levvaing sends on even though they were inert to audio processig, could have the effect of forcing Live to assign too many audio pathways to one CPU core, and too few to another. Im not sure if this still applies in Live 8 becuase I only tend to think about it if I inexplicably start maxing CPU use and I beleive itts an area that was significantly overhauled in Live 7->8.