Marc Wielage wrote:MP4 is dicey for timecode support, and I've seen problems like this before in other kinds of software. One trick with workflow is that you have to do a thorough test before committing to a proxy format, because otherwise you can drive right off a cliff with issues like this.
My suggestion would be not to use MP4 but instead use something like DNxHD36 or ProRes LT, both of which are decent intraframe codecs that support accurate jogging and better frame-by-frame playback with embedded timecode. They're also proven to work pretty well on most Windows and Mac editing software packages. I don't use any Long-GOP format like MP4 or H.264 for anything except as a quick & dirty online viewing tool for dailies or something like that.
There are exceptions like HEVC, which is a very high-quality H.265 format used by Sony and some others, but that's at a much different level.
Marc, I did test it and it was working in earlier versions. Intraframe codecs are better for editing - but there is too much blockiness at 36 Mbps. H264 at 8Mbps is far superior. So that was the priority together with smaller file size for a proxy archive with hundreds of hours.
So this comes as a bad surprise, there is no way to reencode our proxy archive, I just hope BM can get around to look at the issue and fix it. Its good to know that it works with others MP4 types. It would just be a matter of looking at the metadata to see where Adobe puts starting timecode.