Pyramix Bug: Metronome Unreliable?
Posted: Thu Mar 10, 2016 08:24
My team and I recently recorded an important drum session at an outside studio, to do so we printed separate stems for each instrument group as well as mixing down the click track from Pyramix.
Upon reviewing the session, we felt something off in the timing and with further examination found that the recorded click track appeared to fluctuate around the bars beats grid up to 15 ms ahead or behind the down beats
Mind you, not every click instance is offbeat, but this offset would occur at sporadic intervals.
We asked a colleague to see if he ever noticed this issue so he took a closer look himself on his primary and secondary (Pyramix Masscore 32-bit) systems. After comparing the audio/waveforms of his tests to our own, we found that our respective click tracks had IDENTICAL errors in timing, regardless of whether they were recorded in realtime or non-realtime
For now, we've adapted by recording in metronomes from other DAWs or even downloading a click track of the required length, but how could this type of bug even be possible with such a powerful system as Pyramix? We have already recorded several musical projects with this click track as our basis, and when recording personally, my team and I had felt something 'off' in the click, but attributed timing issues to our own human irregularity in rhythm. In case it is not clear, we are extremely concerned about this issue and the ramifications it may have had on our work.
For reference, we compared pmf files and noticed the same fluctuation with BWF, WAV, and AIFF. We have tried all manner of metronome settings and tempos.
Setup
Pyramix Masscore 64-bit (v9.1 Build 8.26786)
Windows 7, SP1
Horus
V-Cube.
I beseech my fellow Pyramix users to examine this issue themselves and make sure they are not experiencing such problems, and for the engineers at Merging to help identify and resolve this issue.
Thank you in advance for any and all input.
Upon reviewing the session, we felt something off in the timing and with further examination found that the recorded click track appeared to fluctuate around the bars beats grid up to 15 ms ahead or behind the down beats
Mind you, not every click instance is offbeat, but this offset would occur at sporadic intervals.
We asked a colleague to see if he ever noticed this issue so he took a closer look himself on his primary and secondary (Pyramix Masscore 32-bit) systems. After comparing the audio/waveforms of his tests to our own, we found that our respective click tracks had IDENTICAL errors in timing, regardless of whether they were recorded in realtime or non-realtime
For now, we've adapted by recording in metronomes from other DAWs or even downloading a click track of the required length, but how could this type of bug even be possible with such a powerful system as Pyramix? We have already recorded several musical projects with this click track as our basis, and when recording personally, my team and I had felt something 'off' in the click, but attributed timing issues to our own human irregularity in rhythm. In case it is not clear, we are extremely concerned about this issue and the ramifications it may have had on our work.
For reference, we compared pmf files and noticed the same fluctuation with BWF, WAV, and AIFF. We have tried all manner of metronome settings and tempos.
Setup
Pyramix Masscore 64-bit (v9.1 Build 8.26786)
Windows 7, SP1
Horus
V-Cube.
I beseech my fellow Pyramix users to examine this issue themselves and make sure they are not experiencing such problems, and for the engineers at Merging to help identify and resolve this issue.
Thank you in advance for any and all input.