Re: LIVE 9.2b1 Discuss....
Posted: Wed Mar 04, 2015 7:58 pm
I see 9.2b3 is up already! Go for it Ableton great to see the renewed activity.
Yes there are a few problems with "complex" / elastique3.Grill Pheiss wrote:
Ok SO it seems to be related to the new Complex and Complex pro algorythms more than the PDC stuff per say.
what i'm observing when playing back a problem free, "track heavy" BUT "plugin light" 9.1 project in 9.2 :
1) at first playback is pretty chaotic, almost like if 9.2 needed to finish loading some data in order for everything to play right. After a couple of start stop start stop, the audio seems to settle.
2) REGARDLESS OF THE PRECEDING, the tracks that are using COMPLEX AND COMPLEX PRO (migration by default towards the new algorythms in 9.2) are completelly off time, mostly playing back early by enough ms to completelly throw the feel and groove of the whole song off.
This is systematic
Yeah, lots of extra pops and wierd stuff w the complex pro algo in 9.2. i had to stop using it because of this as I do alot of repitching and formant shifting w complex pro and w 9.2 it just sounded really bad. I'm assuming it will be fixed at some point?Grill Pheiss wrote:
Ok SO it seems to be related to the new Complex and Complex pro algorythms more than the PDC stuff per say.
what i'm observing when playing back a problem free, "track heavy" BUT "plugin light" 9.1 project in 9.2 :
1) at first playback is pretty chaotic, almost like if 9.2 needed to finish loading some data in order for everything to play right. After a couple of start stop start stop, the audio seems to settle.
2) REGARDLESS OF THE PRECEDING, the tracks that are using COMPLEX AND COMPLEX PRO (migration by default towards the new algorythms in 9.2) are completelly off time, mostly playing back early by enough ms to completelly throw the feel and groove of the whole song off.
This is systematic
Great!The Phat Conductor wrote:OMFG the plugin delay compensation is SO AMAZING!!!
FINALLY!!!
I am A:Bing between two versions of Ableton on the new track I'm working on and it is just CRAZY!
What's the delay amount? There will always be *some* delay, especially with M4L devices, considering how many of the public ones available are not the most efficient.roomkillahprods wrote:Still seeing a delay in sequencer data sent from a max for live device. Bummer.
The delay is microscopic but enough to throw certain functions off.
What's odd is that most VST based sequencers are spot on for timing.
Unless there is something I'm missing. Wouldn't be the first time.
It seems now in 9.2b7, that at least some tempo-synced devices are delay compensated as is the graphic playback position (Also verified in third party Melda MMultiAnalyzer) no matter what high latency is being used (tested with 2048 samples). Could some of you please try and verify this? I tried quickly with auto-pan. Will try more later.vinz89 wrote:What i find really strange with the way ableton deals with PDC is that the soft doesn't seem to have clock sync delay compensation.
Unlike other DAW with full PDC, Live doesn't compensate it's internal clock when dealing with lantency inducing plug-ins, therefore, when yo press play, the playhead starts immediately, even if the audio is delay compensated, leading to a complete GUI mess...
Do you think that's why tempo synced devices are not delay compensated?
Cheers
Vinz
I have actually no issues at all. Push updated. Everything currently works as expected and more including Max devices.ambientidm wrote:complete horrid buggy mess
Just tried autopan and autofilter with ozon 5 and invisible limiter in 9.2b7, still not compensated.Stromkraft wrote: It seems now in 9.2b7, that at least some tempo-synced devices are delay compensated as is the graphic playback position (Also verified in third party Melda MMultiAnalyzer) no matter what high latency is being used (tested with 2048 samples). Could some of you please try and verify this? I tried quickly with auto-pan. Will try more later.
If this is indeed coming in the release, this is huge.
Thanks, I made a too quick test and added too little latency to make this noticeable. Redid the test with more than 10ms plug-in latency and it failed.Rold wrote:
Just tried autopan and autofilter with ozon 5 and invisible limiter in 9.2b7, still not compensated.