Automation gets out of sync if a track's latency is more than 58368 samples (FIXED)

[amagalma]

Problem: Automation gets latency-compensated up to some value (58368 samples in my tests), if it is more than that then it is out of sync.

To check:

here is a test project

Project contains two tracks with automation of ReaEQ. They are identical but the second track has ReaFir instances loaded. Track 1 has 0 latency and Track 2 has latency of 58368 samples. Track 1 is phase reversed so they cancel each other out.

Now, enable the last ReaFir instance of Track 2, which will raise the latency to 59392 samples. At the moment of the automation they cancel out no more because the automation of Track 2 gets compensated up to 58368 samples and now it is out of sync by 1024 samples.

Reaper v5.70 x86, Windows 7 x64

[edwood75]

Originally Posted by amagalma

Problem: Automation gets latency-compensated up to some value (58368 samples in my tests), if it is more than that then it is out of sync.

To check:

here is a test project

Project contains two tracks with automation of ReaEQ. They are identical but the second track has ReaFir instances loaded. Track 1 has 0 latency and Track 2 has latency of 58368 samples. Track 1 is phase reversed so they cancel each other out.

Now, enable the last ReaFir instance of Track 2, which will raise the latency to 59392 samples. At the moment of the automation they cancel out no more because the automation of Track 2 gets compensated up to 58368 samples and now it is out of sync by 1024 samples.

Reaper v5.70 x86, Windows 7 x64

Ainda mais estranho é não cancelar sempre (quando em loop), mesmo sem a ultima instância do ReaFir inserida.

[amagalma]

Really? That's an additional bug then.. I 'll try it on loop here to see if it cancels every time or not

[edwood75]

Originally Posted by amagalma

Really? That's an additional bug then.. I 'll try it on loop here to see if it cancels every time or not

Yes. Sorry for the portuguese.
The odd thing is that the behavior is not totally random. Its quasi cyclic! Looping the pattern:

a) does not cancel (amp varies slightly)
b) amp decrease
c) further decrease or total cancelation
d) amp increases

[heda]

tested the project and I don't have the problem.
they cancel with or without the reafir enabled.
5.70x64

[edwood75]

I can upload a video here. Its a pretty consistent behaviour.

[edwood75]

Originally Posted by heda

tested the project and I don't have the problem.
they cancel with or without the reafir enabled.
5.70x64

Actually there are some developments concerning to this in another topic. I noticed there that if i increase time selection duration further from the loop, it cancels with or without ReaFir

[amagalma]

Automation plays out of sync for some of us in some cases.. This is something that should be looked at ASAP!

[edwood75]

Originally Posted by amagalma

Automation plays out of sync for some of us in some cases.. This is something that should be looked at ASAP!

@Amalgama. I guess that you saw the video. It replicates the issue but it adds another case = it is time selection dependent. Any ideia on this? Did you try time selection lenght variations?

[amagalma]

Yes, I get erratic behaviour depending on time selection length here too.

P.S. I uploaded your video in the Stash so that there is no need to download and unzip to see. Here it is:

[edwood75]

[QUOTE=amagalma;1930633]Yes, I get erratic behaviour depending on time selection length here too.


Thanks for that...i was always dealing with video size issues here and didnt look for a solution other than zipping it. Pure laziness. Now i know.

[heda]

interesting! I can confirm the issue happens, when a time selection and loop playback is on. Changing time selection doesn't create the issue if loop playback is off.

[edwood75]

Originally Posted by heda

interesting! I can confirm the issue happens, when a time selection and loop playback is on. Changing time selection doesn't create the issue if loop playback is off.

And even if loop playback is on, but only if the time selection length is bigger than the item.

[Justin]

Thanks -- the 58368 samples is a red herring, it's actually related to the loop point (automation is not properly timed when within <latency amount> of the loop point, which in this case is the end of the items). This only affects looped playback. Looking at a fix now.

[amagalma]

Thanks! Looking forward to it!

[Bri1]

This only affects looped playback. Looking at a fix now.

^Smart-- if your hovering on loop point fixes for a while__ would it be practical or workable at this time to include a crossfading option for timeline playbacks.??
This would be beautiful right now--pretty pleasingz.
Nice musical addition- because loop selections can be slipped for exellent realtime reasults!!
Right now, loops always click/clip if not zero crossed.
Cheers for eyes n ears.