Dear Ableton,
I just updated form Live v1.1 to v1.5 and come to the conlution that my songs are not 100% compatible.
I made songs in v1.1 with asigned relative controlers of the Doepfer Pocket Dial.
Live v1.1 recognized the controlers al relative (turned green).
Loading this songs into Live v1.5 i get absolute controlers back, it lost
the relative-controler-bit.
This is a HUGE problem, i assigned thousends of controlers, my template song contains only 942 controlers!!!
I don't have time to reasign (switch from absolute to relative) all knobs by
hand. My question is, is there a posibility to do this in batch??? or is there a hidden default switch in Live for this problem.
Or do i have to go back to Live v1.1???
Now all my songs became useless, please provide a solution.
Yours sincerely,
Frank Heijkamp
Lost controler assignement (relative is now absolute)
eh, hello?
Anyone at ableton?
Ableton PLEASE ANSWER THE QUESTION
Last week i've send an email to TechSupp, and posted here.
Reply from Ableton by email:
> Hello,
>
> Sorry for the late reply.
>
> This definately a bug, we´ll fix it in the next version.
>
> Best,
> CH. Kleine
>
Dear Ableton,
Please ANSWER THE QUESTION.
Yes ofcouse i know it's a BUG, you don't have to tell me that.
My question was: IS THERE A SOLUTION!!!
We'll fix it in the next version is no solution to me. Please listen to your customers...
I know you are able to provide THE SOLUTION in a couple lines of coding.
For a programmer it's a job of about TEN MINUTES.
If you are not providing a solution to this song incompatibility problem,
you are actually saying to akabaden, to me and to many other Live users, F*CK YOU ALL.
Because we all have to spend several weekends to put all assignements right in all songs created by now.
THANKS FOR THE CO-OPERATION
f
Reply from Ableton by email:
> Hello,
>
> Sorry for the late reply.
>
> This definately a bug, we´ll fix it in the next version.
>
> Best,
> CH. Kleine
>
Dear Ableton,
Please ANSWER THE QUESTION.
Yes ofcouse i know it's a BUG, you don't have to tell me that.
My question was: IS THERE A SOLUTION!!!
We'll fix it in the next version is no solution to me. Please listen to your customers...
I know you are able to provide THE SOLUTION in a couple lines of coding.
For a programmer it's a job of about TEN MINUTES.
If you are not providing a solution to this song incompatibility problem,
you are actually saying to akabaden, to me and to many other Live users, F*CK YOU ALL.
Because we all have to spend several weekends to put all assignements right in all songs created by now.
THANKS FOR THE CO-OPERATION
f
Gentlemen,
as Christian wrote, this is a bug. We've had very intensive testing for the 1.5, including three public beta versions. But as we have seen, there is no 100% safety. That's no excuse - bugs should not happen.
The bug will be fixed in the next version. I cannot tell you when we will put up the next version. You might not be aware that putting up an update is a huge effort - much more than changing a couple of lines of code. Why? Because while changing a couple of lines of code you might introduce a new bug, which might be worse than the one you fixed. Therefore, the developers must discuss code changes and test a lot.
For now, I cannot offer you anything but not to use version 1.5. Should you still have the 1.1 update available, use it instead of 1.5. If not, let us know and we'll make it accessible to you.
Sorry for the inconvenience! Be assured we will solve this problem, and try even harder to avoid such things in the future.
Gerhard
ableton
as Christian wrote, this is a bug. We've had very intensive testing for the 1.5, including three public beta versions. But as we have seen, there is no 100% safety. That's no excuse - bugs should not happen.
The bug will be fixed in the next version. I cannot tell you when we will put up the next version. You might not be aware that putting up an update is a huge effort - much more than changing a couple of lines of code. Why? Because while changing a couple of lines of code you might introduce a new bug, which might be worse than the one you fixed. Therefore, the developers must discuss code changes and test a lot.
For now, I cannot offer you anything but not to use version 1.5. Should you still have the 1.1 update available, use it instead of 1.5. If not, let us know and we'll make it accessible to you.
Sorry for the inconvenience! Be assured we will solve this problem, and try even harder to avoid such things in the future.
Gerhard
ableton
...
Okay, i understand, i'm sorry for sounding a bit rude sometimes.
I still got v1.1 so there is no real problem for old songs.
But i'm seriously thinking of re-assigning my default song with those 942 controlls, oh well i got the whole weekend
f
I still got v1.1 so there is no real problem for old songs.
But i'm seriously thinking of re-assigning my default song with those 942 controlls, oh well i got the whole weekend
f