Is Ableton Live suitable for any kind of real work?
Re: Is Ableton Live suitable for any kind of real work?
The OP's work in this thread is done.
Re: Is Ableton Live suitable for any kind of real work?
Haha no wayyur2die4 wrote:I've made phone calls with Ableton Live by generating dial tones from Operator. No joke.
I wanted to mess with the person picking up with a busy signal but the GUI froze on me and I had to hard-quit Live to get that godawful noise to stop.
Re: Is Ableton Live suitable for any kind of real work?
I had a good laugh at this thread
-
- Posts: 7033
- Joined: Wed Jun 25, 2014 11:34 am
Re: Is Ableton Live suitable for any kind of real work?
Without getting into boring details I think you're truly misrepresenting "object-oriented programming" (OOP) here. There's certainly no reason whatsoever to run code that isn't needed with object-oriented code unless you're misusing existing code libraries.Machinesworking wrote:Mostly the problem is that object oriented style programming runs each 'object' with a ton of code out side of what it does
On the contrary you can write very concise code where one object only does one thing very well and executes very efficiently. What you're describing is simply bad object design.
The vast amount of code written today is object-oriented, more or less, and exists in a landscape of multi-paradigm programming languages, like C++ for instance.
Make some music!
-
- Posts: 11421
- Joined: Wed Jun 23, 2004 9:30 pm
- Location: Seattle
Re: Is Ableton Live suitable for any kind of real work?
Go back a little, you're going into the strictest sense of object oriented code, that's not at all what I'm talking about.Stromkraft wrote:Without getting into boring details I think you're truly misrepresenting "object-oriented programming" (OOP) here. There's certainly no reason whatsoever to run code that isn't needed with object-oriented code unless you're misusing existing code libraries.Machinesworking wrote:Mostly the problem is that object oriented style programming runs each 'object' with a ton of code out side of what it does
On the contrary you can write very concise code where one object only does one thing very well and executes very efficiently. What you're describing is simply bad object design.
The vast amount of code written today is object-oriented, more or less, and exists in a landscape of multi-paradigm programming languages, like C++ for instance.
Max/MSP and Reaktor use 'object oriented programming' in the most GUI accessible way, an object on the screen contains code to make an oscillator etc. I'm not talking about how OS9 used it, or higher level programming languages use it, but as a way to explain the graphic modular "programming" environment that Max/MSP and Reaktor give you. These programs use way more code to give you an oscillator than any commercial VST instrument does really. Like I mentioned to recreate Massive in Reaktor it would take way more CPU than Massive takes simply based on the fact that each part of a Reaktor instrument is like a modular synthesizer really, compare the amount of electricity use a modular has to the Waldorf Blofield for instance. Graphic modular programing environments like Max and Reaktor cost more CPU and are harder to debug compared to simply making a delay or synth etc. in C++, no way around that.Machinesworking wrote: Reaktor is also an object oriented programming environment, I suppose not in the strictest sense of the term, but both Max/MSP and Reaktor allow a user to use objects to connect together larger programs, and you can if you wish use code to modify things.
Re: Is Ableton Live suitable for any kind of real work?
thats pretty awesome. hahayur2die4 wrote:I've made phone calls with Ableton Live by generating dial tones from Operator. No joke.
I wanted to mess with the person picking up with a busy signal but the GUI froze on me and I had to hard-quit Live to get that godawful noise to stop.