Ableton Forum

Anyone else had some of these problems,i'm getting pissed off
with these bugs that were not in 1.5


1) Long start time.Taking nearly a minute to start up.Live 1.5 was almost instant.
2) CPU meter jumping from 46% to 80% whilst in loop mode in arrange page (as it loops back to the start left marker)
Tried the same song in 1.5 no problem.
3) What happened to the extra filter modes?
4) Crashes with "orange vocoder" in VST directory.
5) Had a few different crash errors "Type2","Type3", "Text encoding could not be found"

6) Another fault in 2 that i've found is:- when the loop switch is on in the
arrange view
(set to say 2 bars) but im in the session page playing clips, after it has looped around
say 10 times some of the clips start to click (this click seems to increase slightly in volume
every time it loops around) in time as it loops back to the start of the left marker??

7) The problem with reason were the first part of the sound is missing (say a kick of redrum) as it loops round
is still there,this problem was in 1.5.??

I think i'm going
back to Live1.5, some of the things in 2 are cool but the bugs are driving me nuts.
I think ableton released this version a bit too quick without ironing out some really basic
problems which i've highlighted.It's also cost me
money to get something that isn't as good as the version before it.

I run a 667 titanium with os 9.2

Agreed

Lets hope for a bug killer

Hi phil,

to the points you mentioned..

1. Long startup time:
please see this thread http://www.ableton.com/forum/viewtopic.php?t=2475

2. CPU meter jumping from 46% to 80%
Are you using Live standalone, as ReWire master or as ReWire slave?
If I understand you right you have special 1.5 song, where the CPU usage display jumps from 56% to 80% when it has to jump from end loop to start loop point? But the same song in Live 1.5.2 keeps the 46%?
When it jumps from 46% to 80% when is it jumping back to 46%?

3. AutoFilter modes
Please see this thread http://www.ableton.com/forum/viewtopic.php?t=1972

4. Orange vocoder
Bugfix for that will be contained in an upcoming bugfix update.

5. Had a few different crash errors "Type2","Type3", "Text encoding could not be found"
Please let me know after which action you did which crash and with which error message. It's really important to get all these problems. Please always have in mind, that we cannot fix a big we don't know or we cannot reproduce.

6. click when loop is on
We had a some bug reports about this problem but could never reproduce it until a friendly person from Cycling74 sended a seflcontained song to use where we could reproduce this behaviour. So we working on that and hope to fix it.

7. Rendering ReWire
We also know about this problem. Until now we find out that it seems to depend on the instruments used in Reason. So we will invest more time toget a solution for this. Meanwhile you should record ReWire sources instead to use render.


Please also try to create different thread for different problems. It's much more difficult to handle all information in on thread and the risk that I forget someting by overreading is much higher.


regards,
Alex,

Alex,

Would it be possible to get a posting somewhere (preferably not the forums) of the current bug status? I've been able to reproduce quite a few different bugs, but I agree that they get lost in the boards here.

I understand the possible outcomes of posting a comprehensive bug list, but at times I feel that there's not a very clear line of communication between your organization, and us, the consumer.

- Mike