Frame.io comments shown as NaN:NaN:NaN:NaN and not with timecode in Premiere Pro

​@jamieclarke , unfortunately not fixed in 25.6.4 Build 5 on Win 11… The (forced) transition from a perfectly working Frame io V3 into V4 this month is a brutal experience. V4 is far from being ready for prime time, even though it’s been out for what, a year now? There are so many things that were working in v3 but are totally broken in v4, and hence, are serious regression bugs!

​@invisibleavatar , FWIW, I reported this issue earlier this month “live” in chat with a Frame io tech… The official answer after he circled back with “engineering” was that we were not to use our own codec presets - stick to Adobe’s defaults. The short answer is that this seems to work, but I wonder if the problem is in the difference of the framerate of the sequence vs the one of the encoding preset one is exporting with. IOW, I wonder if by setting a homemade preset and leaving the framerate take the one from the sequence if that does not fix the problem? Still have to test this theory...

Other issue: our comments are now plagued with an uber-long “user id” that is about 30 characters long with hyphens… Each. And. Everyone. Of. Them.

And to make matters worse, after installing Premiere 26 (but not using it), the Frame io V4 publishes from Premiere 25.6.4 will render, but will fail uploading if you have a mogrt in your sequence (that is the common thread for all the projects I’ve tried that have failed). They were working fine up to the day before Premiere 26 was installed.

Bad. Just bad.