Hmm, thats a real shame that this is the company policy.Robert Henke wrote:@ Angstrom:
feedbacks in digital audio are pandoras box. At some point we might introduce block wise audio calculation for all our effects, and from that day on you'll have all kinds of wierd behaviour with such kinds of feedback. your loop will be *almost* eight bars long and it will change as a function of many factors we cannot determine now.
now imagine what users would tell us if this would happen....
so, we do not officially allow. better remind us to do spend more focus on you looper guys !
Robert
This loopback is created by doing something very unusual, it would be next to impossible to do this by accident - IE: route two compressors to each other and have them both on 'monitor sidechain'.
To remove that hacking ability is to have a corporate culture of ' user safety' , instead of 'user creativity'. User safety is dull dull dull.
If some user feeds two sidechains back on each other and manages to set up a loopback correctly - this is certainly a hack. Anyone doing that and then complaining to Ableton about it sounding 'wrong' is a fool, plain and simple. This process is used to make things sound wrong! That's what it is for, "sound abuse".
I make VST loopers and they are terribly made, really bad, with awful programming. But despite the obvious flaws I still use them and so do many other people. Version 1 of my basic looper was downloaded about 5,000 times before someone noticed that it went out of time after 30 minutes. It was so useful, even with that error, that people tolerated it. It is the same case here.
I think giving us the possibility to play is much more important than making sure everything is 'safe' . Remember that guitar amp distortion was considered a flaw by the amp designers until artists put it to use. Should a guitar amp be incapable of distortion in case some one distorts by mistake? Should my guitar come covered in protective foam in case I hit myself on the head with it?
I would prefer that Ableton give the more experienced and intrepid users something to play with, rather than focusing on making everything safe and secure and locked down just in case some idiot stumbles across the dynamite.
---
as a final note :
what of sending return channels back to themselves?
This is an equivalent process, it is an audio feedback loop. This is my standard way of using delays, and has been ever since I was about 16 (The 'dub' style delay)
It was the second main reason that I chose Ableton as my DAW, where other applications would not allow this.
Is the ability to send a return back to itself going to be removed too?
if this is the case I really will not be able to use the program any more.
I just had to check beta 6, with my heart in my mouth, thankfully 'dub' delays still work.
