Hi there folks..it’s been a month…I’ve emailed the techs..and no reply. Simply put..can you tell me at what Midi Tick resolution EZPlayer pro is running at? That will help me determine how to get the midi tracks I import into my DAW to sync up with the actual DAW tempo. 120 bpm on EZ Player and 120 BPM on my DAW are NOT the same.

I have played with the Tick resolution. 960 is the limit of SAWStudio..and it is almost there…but not quite. I have spoken to the developer of SAWStudio, Bob Lentini, and he took the time to analyze the EZPlayer Pro midi files that I was generating. It would seem that EZPlayer does indeed track at a much higher tick resolution than 960. From reading the various posts on this forum it would appear that SAWStudio is not the only DAW with this issue. Bob did explain to me the reasons why producing Midi files with unneccesarily high Tick resolution counts. He also detailed the negative consequences of doing so in terms of how the internal engines cope with it. The default resolution in SAWStudio is 480 which , apparently is fine enough to not be able to hear.
For example…a Midi Tick resolution of 480 means that each quarter note (or one beat)…has 480 divisions of time in which to accurately place a Midi event. 960 resolution is 960 time divisions per quarter note. Can you Hear 1/480th of a difference in a quarter note? I can’t. I doubt I could even feel it. Some of the Software developers are producing programs that output Tick resolutions in the Thousands per quarter note. When they do this…and your DAW will only go up to 960…the result is a Midi track that progressively goes out of sync with the audio track.

So…at 120 BPM…, each beat is half a second long (60 seconds /120bpm=0.5 sec. or 500ms) . Take that 500ms per Beat and divide it by the 480 Tick resolution/ divisions of time. You get a time difference of 1.04 milliseconds between Midi Ticks. That’s too fine to hear in my books.