Here's a problem I ran into last night.
I was fooling around with the Operator demo, just to check it out. I wrote a killer hook that I just had to keep, and so - sigh - I decided to shell out the dough to buy and register Operator so that I could keep my work.
Naturally, Ableton's marketing strategy worked on me.
Anyways, I purchased it online and unlocked it right then and there, so that I could save my Live set and preserve my work.
HOWEVER:
Once a Live set is considered to be in "demo mode" you can't save it no matter what. I bought, unlocked and registered operator with my Live set open, and when I went to save, no love man. I had to get a pencil, write down each and every operator parameter, write down all the effects and what their parameters were (and where they were inserted) and copy / paste my midi clips into a new live set. I was not happy about this man - it took the whole night to recreate what I had before, and it's still not 100% what it was originally.
Just a warning for others who may be using either the Live 4 Demo, or a Live set with the Operator demo - Paying for it, unlocking it, and even registering it won't save your precious work of genius once your live ste is tagged as demo mode.
That said, I am pretty happy with Operator as a synth - go figure. My only other FM synth is the FM-7, which has a crapola interface.
Live Sets in Demo Mode: still can't save even if you buy it.
-
- Posts: 995
- Joined: Thu Mar 04, 2004 11:38 pm
- Location: Montreal Canada
Live Sets in Demo Mode: still can't save even if you buy it.
I have changed my username; Now posting as:
M. Bréqs
-
- Posts: 995
- Joined: Thu Mar 04, 2004 11:38 pm
- Location: Montreal Canada
Thanks for the response Alex.Alex wrote:Hi montrealbreaks,
what you wrote is true for Live 4.1 and we are sorry for the work you may have lost. But since version 4.1.1 this is changed so when you now unlock the Operator you can save your documents immediately.
regards,
Alex
Although it's too late to help me out, this is a welcome addition to Live 4.1.1. There's probably a lot of folks who could have ran into this problem.
That said, I appreciate it that yourself and the others at Ableton (1) read your forum and respond so fast, and (2) think about your customers and solve problems like this quickly - I want you guys to know it's genuinely apprecaited.
I have changed my username; Now posting as:
M. Bréqs