Beta of upcoming bug fix update is online: Live 8.0.4b1

[Alex]

Hi folks,

We just released the first beta version of the upcoming 8.0.4 bugfix update.
Every Live 8 owner can use this beta version.

As it is a beta, please remember to backup critical data before you use it.


Version info:

Current version: Live 8.0.4b1
Expiration date: 2009/06/05
Required serial: Live 8 full version




Kind Regards
/Alex





Changes from Live 8.0.3 to 8.0.4b1:


Bugfixes:

Unquantized scrubbing would not work properly in MIDI clips.

On Mac OS X, the DUY Tape AU plug-in would crash on instantiation. [5429]

When the Looper is set to a fixed length recording and the song is running, the recording length of the Looper might be miscalculated.

Under certain conditions, moving a MIDI clip in arrangement could crash Live.[5543]

[timothyallan]

Under certain conditions, moving a MIDI clip in arrangement could crash Live.[5543]

Is this the sticky clip copy bug?

[3dot...]

Under certain conditions, moving a MIDI clip in arrangement could crash Live.[5543]

Is this the sticky clip copy bug?

I've had crashes when resizing an audio clip in arrange...

[selthym]

Can you look into the userconfig.txt issues that crept in with 8.02. I posted the issue in detail in that beta's forum. I know you were looking at it for 8.03 but still not fixed

[koranek]

I hope there is progress on the space bar/start-stop bug for plugins (on Mac platforms as far as I know). Not a deal breaker, but really annoying. Works much better in Live 7.

[weedywhizz]

Already informed Ableton about a bug with Faderfox-Controllers in combination of VST Plugins....no reply since a week...

[Angstrom]

Already informed Ableton about a bug with Faderfox-Controllers in combination of VST Plugins....no reply since a week...

they don't reply unless they need more info, they just put it on the bugfix list and then fix it.

[Coupe70]

Already informed Ableton about a bug with Faderfox-Controllers in combination of VST Plugins....no reply since a week...

they don't reply unless they need more info, they just put it on the bugfix list and then fix it.

Would be nice if they would at least answer with "Filed as a bug.".
So you knew they heard you and you were right...

[weedywhizz]

Already informed Ableton about a bug with Faderfox-Controllers in combination of VST Plugins....no reply since a week...

they don't reply unless they need more info, they just put it on the bugfix list and then fix it.

Would be nice if they would at least answer with "Filed as a bug.".
So you knew they heard you and you were right...

That's exactly the point. If I buy a software for lot of $$ and playing a betatester after official release I would at least know that my bugreport has been filed. That's the minimum Ableton can do!

[ark]

Every time I have sent email to [email protected] I have received a reply.

If you didn't get one, it could be that the reply is languishing in an overly aggressive spam filter somewhere.

[Angstrom]

if you are mailing to 'support@' you tend to get a reply because it is a support problem on the released product, and you get a response from a person trained in not losing their cool in the face of adversity.

if you send a mail to beta@ then you are sending a mail to a cave dwelling code-elf, who speaks only binary and eats babies

and that's the reason

[weedywhizz]

LOL ...

wait I'll try to explain my problems in binary:

00010100010100111011010000110000101010110000011000010101010101010000101010110001

I'm done.


The mails I wrote were all sent to "support@". 2 mails - no reply. I'll try it again via 5 different mail accounts.
Hopefully 1 of them will get a reply.

I am wondering myself why the mails don't "reach" Ableton. Everytime I wrote before for various reasons I have always got answers with my standard mail-adress.