Posted
Hi.
There seems to be a one-measure discrepancy re: the recorded location of incoming MIDI.
This is in Synfire v2.5.4 b5.
I've made a video to demonstrate:
Possibly there is something I don't understand correctly here, as I'm not very experienced with the Record operation, but it looks like a bug to me.
Please advise. Thanks.
Thu, 2025-01-02 - 18:19 Permalink
Thanks for the video.
There has been an issue with shifted takes in sub containers that was fixed some time ago. I just tested again to be sure the current build is fine. Also tested with a pre-roll of 1m for the arrangement (i.e. first measure of song starts at 1m rather than 0m).
Could it be you have a latency in your input chain, plus an additional latency in the monitoring? What happens if you record along a metronome?
Any mastering or limiter FX on the output? That adds considerable latency.
Also make sure you use the Audio Engine for MIDI input (Option for Take parameter). That adds proper time-stamps to all incoming messages like a DAW.
Thu, 2025-01-02 - 19:38 Permalink
As the video shows, I'm recording into a container, at a non-zero location.
Did you test that?
Re; latency, I'm not noticing any latency in the sounding of what I play as I record, fwiw. The issue is that the data is landing a full measure out of position
There were no mastering or limiter FX on the output.
Also make sure you use the Audio Engine for MIDI input (Option for Take parameter).
I did not have that option checked, so perhaps that is relevant. I will retest.