Bug fix update Live 5.0.2 is available!
-
timothyallan
- Posts: 5788
- Joined: Wed Nov 24, 2004 11:05 pm
- Location: Melbourne Australia
- Contact:
Thanks for the update! A nice and speedy follow up.
This being said I am begging you to bring back the 5.01 way of editing the start marker in the clip view. I have liked it from day one and now the feature has been removed?! I know that people freaked out all over this forum with posts like "freaking orange dot!" and all the rest of it but it makes moving around in clips way better for me. The way it is now again in 5.02 totaly messes up the way i use live to arange my tracks in a live setting. I for one think that there is a need for both ways of working with the start marker in the clip. I truly hope this can be brought back in as I will miss it.
This being said I am begging you to bring back the 5.01 way of editing the start marker in the clip view. I have liked it from day one and now the feature has been removed?! I know that people freaked out all over this forum with posts like "freaking orange dot!" and all the rest of it but it makes moving around in clips way better for me. The way it is now again in 5.02 totaly messes up the way i use live to arange my tracks in a live setting. I for one think that there is a need for both ways of working with the start marker in the clip. I truly hope this can be brought back in as I will miss it.
ABIT NF7+AMDXP@2500, RME Multiface, TC Powercore Element+Virus, UAD-1, Nord Lead2, Reason2.5, impOSCar, Microtonic, Reaktor5 and some other stuff...
Something else odd I noticed in the new version...
With Live 4 and 5.0.1 I have left the Ambience reverb on an aux send. I like the plug, but it does use a lot of CPU. In the previous versions this did not register on the CPU meter until I started to send a signal through it from one of the channels.
In Live 5.0.2 however the full Ambience CPU hit registers even when I don't have anything going through it.
The reason I don't much like that is that I have two or three different reverbs on different return strips in my template, and choose between them when mixing. THis makes that impossible.
Could anyone comment/explain?
With Live 4 and 5.0.1 I have left the Ambience reverb on an aux send. I like the plug, but it does use a lot of CPU. In the previous versions this did not register on the CPU meter until I started to send a signal through it from one of the channels.
In Live 5.0.2 however the full Ambience CPU hit registers even when I don't have anything going through it.
The reason I don't much like that is that I have two or three different reverbs on different return strips in my template, and choose between them when mixing. THis makes that impossible.
Could anyone comment/explain?
iMac Retina 4K 3.3Ghz i7, 16Gb RAM
Live Suite 9.7.1 + Reason 9.1 + Pianoteq 5 + Sibelius 8.5
Listen on Soundcloud
Live Suite 9.7.1 + Reason 9.1 + Pianoteq 5 + Sibelius 8.5
Listen on Soundcloud
Alex,
About the bugfix/improved latency reporting...
I'm getting
5.01 is 11ms + 11ms.
5.02 is 12.3ms + 12.3ms.
Both with a 512 buffer size. Guess this is due to better accuracy as formerly posted.
More importantly, My question about the third adjustable latency box:
Followed your advice about double checking the latency setting with 5.02. So I checked my HW latency using the "settting latency" example lesson. In 5.01 I got 4ms. In 5.02 I got only 1.3ms. Even double checked myself after entering the setting...seems OK. But I'm confused though. Why would the soundcard latency improve from one version to the next using the same soundcard?
About the bugfix/improved latency reporting...
I'm getting
5.01 is 11ms + 11ms.
5.02 is 12.3ms + 12.3ms.
Both with a 512 buffer size. Guess this is due to better accuracy as formerly posted.
More importantly, My question about the third adjustable latency box:
Followed your advice about double checking the latency setting with 5.02. So I checked my HW latency using the "settting latency" example lesson. In 5.01 I got 4ms. In 5.02 I got only 1.3ms. Even double checked myself after entering the setting...seems OK. But I'm confused though. Why would the soundcard latency improve from one version to the next using the same soundcard?
Re: Bug fix update Live 5.0.2 is available!
Has it been taken off? Because I couldn't find it at all. Only the update for 414.Alex wrote:Hi folks,
we just released the bugfix update Live 5.0.2.
Just check the download section on our website or use the 'Check for Updates...' entry from Live's help menu.
cheers
iMaci7, Logic Pro & Live 9 Focal CMS65 &Softube Console 1 Mkii
Re: Bug fix update Live 5.0.2 is available!
http://www.ableton.com/index.php?main=downloadsshotsi673 wrote:Has it been taken off? Because I couldn't find it at all. Only the update for 414.Alex wrote:Hi folks,
we just released the bugfix update Live 5.0.2.
Just check the download section on our website or use the 'Check for Updates...' entry from Live's help menu.
cheers
Re: Bug fix update Live 5.0.2 is available!
And you have to enter your Live5 serial there, not your Live4 serial, otherwise you'll get the option to download Live4 update....hoffman2k wrote:http://www.ableton.com/index.php?main=downloadsshotsi673 wrote:Has it been taken off? Because I couldn't find it at all. Only the update for 414.Alex wrote:Hi folks,
we just released the bugfix update Live 5.0.2.
Just check the download section on our website or use the 'Check for Updates...' entry from Live's help menu.
cheers
Cheers,
amo
Live 5.0.3 - IBM Thinkpad R51 1.5ghz Centrino - 1,5 Go RAM - 7200 RPM 2nd HDD intern - RME Multiface - Windows XP Pro SP2
Hi icedsushi,
So in Live 5.0.1 the reported latency was truncated from Live so you got 11.0ms and 11.0ms. In Live 5.0.2 you get 12.3ms and 12.3ms.
So the the difference is 1.3ms for input and 1.3ms for output too.
That means Live 5.0.1 reported 1.3ms + 1.3ms = 2.6ms to less
But because the real latency of your soundcard has not changed of course you had also to compensate this 2.6ms difference.
So in Live 5.0.1 you have a compensate value of 4.0ms but in Live 5.0.2 only 1.3ms. Just check the difference, 4.0ms - 1.3ms = 2.7ms which is about the 2.6ms difference from above.
regards,
Alex
It does not. In Live 5.0.1 the overall compensation value is only a value to manual compensate the difference between the reported latency from the audio interface and the "real" latency you experience when you play or record something.Why would the soundcard latency improve from one version to the next using the same soundcard?
So in Live 5.0.1 the reported latency was truncated from Live so you got 11.0ms and 11.0ms. In Live 5.0.2 you get 12.3ms and 12.3ms.
So the the difference is 1.3ms for input and 1.3ms for output too.
That means Live 5.0.1 reported 1.3ms + 1.3ms = 2.6ms to less
But because the real latency of your soundcard has not changed of course you had also to compensate this 2.6ms difference.
So in Live 5.0.1 you have a compensate value of 4.0ms but in Live 5.0.2 only 1.3ms. Just check the difference, 4.0ms - 1.3ms = 2.7ms which is about the 2.6ms difference from above.
regards,
Alex
Wow !Alex wrote:Hi icedsushi,
It does not. In Live 5.0.1 the overall compensation value is only a value to manual compensate the difference between the reported latency from the audio interface and the "real" latency you experience when you play or record something.Why would the soundcard latency improve from one version to the next using the same soundcard?
So in Live 5.0.1 the reported latency was truncated from Live so you got 11.0ms and 11.0ms. In Live 5.0.2 you get 12.3ms and 12.3ms.
So the the difference is 1.3ms for input and 1.3ms for output too.
That means Live 5.0.1 reported 1.3ms + 1.3ms = 2.6ms to less
But because the real latency of your soundcard has not changed of course you had also to compensate this 2.6ms difference.
So in Live 5.0.1 you have a compensate value of 4.0ms but in Live 5.0.2 only 1.3ms. Just check the difference, 4.0ms - 1.3ms = 2.7ms which is about the 2.6ms difference from above.
regards,
Alex
(I didn't understand nothing...)
Thanks Alex,Alex wrote:the overall compensation value is only a value to manual compensate the difference between the reported latency from the audio interface and the "real" latency you experience when you play or record something.
I read that like 15 times and I think I finally understand it about half. So 5.01 was "rounding" the numbers and since 5.02 is more accurate to the decimal, there is now a difference in the adjustment equal to the increased accuracy.
I'm still thinking about what the user changeable compensation value represents (in my case the 1.3ms). I thought this was the soundcard's in/out latency but after your statement above I'm so sure now what it represents.