Ableton Forum

BtW, The "old "Z3ta+ bug is still present in 5.02 and 5.03....
I explain :
Load an Instance of RGC Z3ta+ in LIVE, play with it, no problems.....
Now just make ctrl+N to start working on a new track...Bang!!You can't scroll in the browser anymore with your mouse, and all keyboards shortcuts have no more effects......100% reproducible...
You have to restart Live completely to solve the problems...

Well... I managed to get a glitchfree 5 hour performance with beta 7

Still got that bug with recording unwanted CC MIDI snaphots when recorded MIDI clips should be blank though Alex

lola wrote:

Pilgrim wrote:

Doc Jones wrote:Hello all, just curious. I just purchased Live and installed it. I am now installing the public beta and the beta installs to a different directory than the full Live installation - is this so that when the full 5.03 version is released, it will install to the default full version directory and then I will just need to uninstall the public beta installation?

thanks.

Doc,
Any installation of LIVE will go in a folder named "LIVE "version number"
LIVE 5.03 will make a new folder named "LIVE 5.0.3"
Unused versions can be removed using "add-remove software" item in Control Panel

Pilgrim

Hi, mebe stupid, but i can't seem to remove abe from my pc.
I still get these iritating messages when trying to uninstall.
"can't find install.log" ...and thats strange because the install.log is in the dir of ableton.
A reg fix does not help also.
Any pc guru who can help me out with this?

create a text file in the directory containing the 'unwise.exe' (or whatever the uninstall program is called - i'm at work so can't confirm the name) & the install.log.
In the text file simply write 'unwise.exe install.log ' (no quotes) & save it as a .bat file, e.g. uninstall.bat & doubleclick it to run - it should start the uninstaller for you.

lola wrote: Hi, mebe stupid, but i can't seem to remove abe from my pc.
I still get these iritating messages when trying to uninstall.
"can't find install.log" ...and thats strange because the install.log is in the dir of ableton.
A reg fix does not help also.
Any pc guru who can help me out with this?

Same thing here... I have a bunch of expired betas that don't want to uninstall.... Weird.

diverdee wrote: create a text file in the directory containing the 'unwise.exe' (or whatever the uninstall program is called - i'm at work so can't confirm the name) & the install.log.
In the text file simply write 'unwise.exe install.log ' (no quotes) & save it as a .bat file, e.g. uninstall.bat & doubleclick it to run - it should start the uninstaller for you.

Thanx for the tip, I had some trouble too to deinstall the last betas too, but i thought my system was corrupted in some manner.
With this .bat file it works now, but there is a bug then in the Live installer then.

Thanx a lot

Greetings

diverdee wrote:

lola wrote:

Pilgrim wrote: Doc,
Any installation of LIVE will go in a folder named "LIVE "version number"
LIVE 5.03 will make a new folder named "LIVE 5.0.3"
Unused versions can be removed using "add-remove software" item in Control Panel

Pilgrim

Hi, mebe stupid, but i can't seem to remove abe from my pc.
I still get these iritating messages when trying to uninstall.
"can't find install.log" ...and thats strange because the install.log is in the dir of ableton.
A reg fix does not help also.
Any pc guru who can help me out with this?

create a text file in the directory containing the 'unwise.exe' (or whatever the uninstall program is called - i'm at work so can't confirm the name) & the install.log.
In the text file simply write 'unwise.exe install.log ' (no quotes) & save it as a .bat file, e.g. uninstall.bat & doubleclick it to run - it should start the uninstaller for you.

Thank u very very much, it helped

Pilgrim wrote: Doc,
Any installation of LIVE will go in a folder named "LIVE "version number"
LIVE 5.03 will make a new folder named "LIVE 5.0.3"
Unused versions can be removed using "add-remove software" item in Control Panel

Pilgrim

thanks for the info pilgrim.

Yep the .bat file did the trick, thanks!

I love when people post bugs that still haven't been fixed in these beta threads. they do read the forums and they know the existing bugs. and if the fix list doesn't include a fix for it then it's not going to be fixed in that particular beta version so they know it still exists. I'm not trying to have an attidude about it really but it's just common sense. they tell you what is fixed in that beta. everything else not in the fix list is still there.

Alex wrote: -----------------------------------------------------------------
[04] Bug: Clip length of recorded clips
-----------------------------------------------------------------
Platform: All

When recording quantized audio session clips with a tempo of 130, the resulting sample can sometimes be one frame too short (because of jitter). In such a case we used to make the resulting loop brace one frame shorter, which is bad, because it results in clips that run out of sync if you play them long enough.
Instead, we leave the loop brace as it is now, so that it extends one frame beyond the end of the sample.
Furthermore, the clip length display of such clips would be incorrect in the Track Status Display and in the Clip Detail view.

Status: Fixed

This is probably the one that was making Reason 3.0 clips that i was recording
go horribly out of sync after so many bars.. THANKS FOR FIXING THAT! YAY!

Johnisfaster wrote:I love when people post bugs that still haven't been fixed in these beta threads. they do read the forums and they know the existing bugs. and if the fix list doesn't include a fix for it then it's not going to be fixed in that particular beta version so they know it still exists. I'm not trying to have an attidude about it really but it's just common sense. they tell you what is fixed in that beta. everything else not in the fix list is still there.

We're all jus' trying to help

-----------------------------------------------------------------
[04] Bug: Clip length of recorded clips
-----------------------------------------------------------------
Platform: All

When recording quantized audio session clips with a tempo of 130, the resulting sample can sometimes be one frame too short (because of jitter). In such a case we used to make the resulting loop brace one frame shorter, which is bad, because it results in clips that run out of sync if you play them long enough.
Instead, we leave the loop brace as it is now, so that it extends one frame beyond the end of the sample.
Furthermore, the clip length display of such clips would be incorrect in the Track Status Display and in the Clip Detail view.

Status: Fixed



I just tested this, and it seems to be working. however, I noticed something strange; I accidentally recorded a 3 bar loop instead of 4 and wanted to add an extra bar of space to keep things in line. when I entered 4 in the length section, it changed from 3 to 2.3.3.

also, I had an even 4 bar loop that I changed to 2 bars and when attempting to bring it back to 4, it came out 3.3.3

It would be cool if we could extend the loop brace by simply entering a larger loop length.

happy holidays!

-M