Frame.IO (V4) keeps overwriting comments markers in Premiere Pro Pro

[Andrew C. Brinsmead]

How do I lock comments from Frame.IO to a sequence, so that they don’t revert to the previously saved version of a sequence on Frame.IO?

Frame.IO V4 is overwriting & deleting comments markers on my sequences in Premiere Pro, and I need it to stop making my comments markers revert to the previously saved version on Frame.IO

After I've imported marker comments about a sequence from Frame.IO, if I open a duplicate of that sequence again while having the Frame.IO comments window open, the comments in my timeline will revert to match the previous version of the edit on Frame.IO that had been uploaded to Frame.IO and had comments added., instead of moving the markers with the current edited version, this is after I've started working with a new version of the sequence.

In previous (v3 legacy) version of Frame.IO, once I’d imported markers, they were in the sequence in Premiere pro and would adjust to the edit as normal (ie - I could edit them, and they would move with my edit); but now I have my markers constantly reverting and referring to the older version of the sequence (that has had comments added on frame.IO). If I turn off the comments for the older version of the sequence, I lose the Frame.IO marker comments completely.

The only workaround that I’ve found is to completely close the Frame.IO comments window in Premiere Pro, which allows the comments on subsequent duplicates of the sequence to behave as expected.

[Stan Jones]

@Patrick Southern?

Stan

[Patrick Southern]

Hey @Andrew C. Brinsmead! I'm the Product Manager for the Frame.io panels in Premiere. Thanks for bringing this to our attention. What version of Premiere Pro are you using? Do you have a screen recording of the behavior you can share?

@Stan Jones, as always, thank you for tagging me.

[Andrew C. Brinsmead]

Hi @Patrick Southern  my replies don't seem to be posted by the forum (must be a glitch). also I can't post a video or a link to a video of a screen recording of this issue.

I've been editing on Premiere Pro 25.5.1, and having these issues.

[Patrick Southern]

@Andrew C. Brinsmead the forum is acting weird. We're replacing the V4 Comments panel with a complete rebuild of the Frame.io integration in Premiere 25.6 on November 12th. You can test it in Premiere (Beta) between now and then. I'd be curious to know if you run into similar behavior with the new panel.

[Andrew C. Brinsmead]

Hi @Patrick Southern I've actually (temporarily) moved up to editing this project on 26.0 Beta to see if that helps with the Frame.IO; there's a couple of weird things that I've noticed with the Frame.IO panel in v26.0 Beta: there's no indication in the panel when a file is actually exporting or uploading (I have to open the web browser version to at least see when a file is uploading); also, I'm working at 25fps, but the export settings appear to indicate that my exports are exporting at 29.97fps (although when I've checked the exports on the web browser, that's showing them as being at 25fps). However, using 26.0 Beta Frame.IO window, at least my markers aren't be deleted & replaced by the markers from previous versions that I had uploaded to Frame.IO!

[Andrew C. Brinsmead]

@Patrick Southern  here is a screen grab showing the purported change in frame rate between the sequence settings at 25fps & the export setting mysteriously changing to 29.97fps…

[julian_9486]

I have some issues on the 25.6 Version too.. The marker wont even place themselve in the timeline

[Patrick Southern]

@Andrew C. Brinsmead we've got an engineer working on that mismatch right now. We're showing the default framerate and resolution for presets that have a "Match Source" setting, rather than reading the sequence settings. The export will match your settings, but our summary is off. Hoping to have a fix for the mismatch in the summary within the next few weeks in Premiere (Beta).

[Patrick Southern]

@julian_9486 you're using an older version of Premiere. That panel is known to be broken. Can you update Premiere to 25.6 or later? If you're still running into issues in the latest version of Premiere, we can triage together from there.

[Errin Vasquez]

Hi @Patrick Southern. I'm unable to delete the markers in my sequence after I've addressed the note. I want to clear them out but when I delete or clear them they reappear. I am running Premiere 25.6.2. 

I'm also having issues uploading a new version of the cut. If, say the old cut is there V1, and I want to upload a V1.1, I can upload the V1.1 but it's still called V1. I didn't have this issue in the previous version. Maybe I have a setting wrong somewhere? 

[Andrew C. Brinsmead]

this problem of modified markers on my premiere pro timeline being overwritten by the last version saved on a sequence in Frame.IO has returned for me - although I'm working in Beta (I've just downloaded the latest Beta 26 build 46; but the problem has been returning for the last several beta versions).  I'm finding that my markers are reverting to the comments on the last saved version of an edit that were created on Frame.IO when I have the Frame.IO v4 panel open.  I'm losing any & all modifcations to these markers (such as changed comments / marker colours / timeline positions etc.)

[Andrew C. Brinsmead]

Hi @Patrick Southern , unfortunately now I'm getting markers randomly duplicating themselves and reverting to their last frame.IO version, despite having the frame.IO v4 panel closed. I delete these duplicates, but as soon as I click on one of the markers, multiple duplicates of the original version are appearing in my timeline. Although I've updated to the latest Beta version (build 46), this has been occuring for a few builds now.

I'm updating almost daily with every build update release - not sure if that's a good thing or not, but I'm presuming that being Beta, each build is a little bit more refined / improved than the last, hence my updateing.  I always rebuild my system preferences with each update (and a couple of other times each day)

[Suvo Sur]

Hello everyone — I’m the lead Quality Engineer for this effort and will be reviewing this starting today. Looping in our lead Designer, @Anna Lehman , as well.

[Andrew C. Brinsmead]

Thanks Suvo! For what it's worth, I've found that I'm getting multiple new copies of the same comments markers based on the last version of my sequences downloaded from Frame.IO v4 panel.  These erroneous iteratnions keep popping up at the same original timecode of each comment, even without the FrameIO.v4 panel being open (I've taken to closing it as soon as I've downloaded each round of comments).  

Each round of new iterations of the comments seems to be triggered by clicking on any of the downloaded comments markers (to read it).

[Andrew C. Brinsmead]

another oddity that I've noticed overnight is that when I'm exporting one particular sequence to Frame.IO v4 panel, the frame.IO v4 export panel mis-names that sequence, and now it's mis-named several previous exports as this wrong sequence name (as shown in the attached screen grab - these are all different sequences that have been giving the same export sequence name & thumbnail in the Frame.IO v4 window; the resultant exports all look to have uploaded correctly).  

BTW, I'm currently on Beta build 47, and I'm resetting my app preferences 3 - 6 times per day (and have been doing this due to constant crashing for a couple of weeks (I'm updating to the latest build almost every day, hoping that updating might introduce more stability))

[Stan Jones]

@Andrew C. Brinsmead,

Thanks for continuing to post specifics on the issues you are seeing in frame.io. This is very helpful for their troubleshooting. Since you're using the Beta, be sure to report the specific build you are using.

> I'm updating almost daily with every build update release - not sure if that's a good thing or not, but I'm presuming that being Beta, each build is a little bit more refined / improved than the last, hence my updateing. I always rebuild my system preferences with each update (and a couple of other times each day)

Just keep in mind that while the general expectation is improvement in each Beta build, the practical reality is that any given build may introduce a work-stopping bug - that may be fixed by tomorrow or not for several builds. And you can't rollback Beta builds using the cloud desktop.

I've posted a couple things recently on the Beta:

See my "Cautions" when using the Beta here:
https://community.adobe.com/t5/premiere-pro-beta-bugs/cannot-install-premiere-pro-beta/idc-p/1484839....

I have posted about how to minimize problems when updating the Beta:

https://community.adobe.com/t5/premiere-pro-beta-discussions/new-beta-uninstall-reset-or-just-update...

In this post, about the recent issues re the 25.6.0 update, see the section beginning "I would add the following..."

https://community.adobe.com/t5/premiere-pro-bugs/p-premiere-projects-saved-in-v25-6-0-cannot-be-open...

@Suvo Sur 

Does the PR Beta build provide you enough information? Do you ever need the frame.io build or date? I see it in the account drop down info.

Stan

[Andrew C. Brinsmead]

thanks Stan, I haven't used the Beta updates before (I'm only using them this time around because an Adobe support tech advised me to work in Beta because of issues that I was having with Frame.IO while using 25.5.2 (I know 25.6.2 has been released; but I'm working in a productions project, with multiple productions, and I can't revert this project to 25.6.2).

I had wondered what the best practice is for working with Beta, so thanks for your update (it's pretty much what I thought; including the accidental hiccups associated with using Beta). I'll be reading your Beta  guides this morning!

[Andrew C. Brinsmead]

Hi Stan, there's a problem with your first link:

See my "Cautions" when using the Beta here:
https://community.adobe.com/t5/premiere-pro-beta-bugs/cannot-install-premiere-pro-beta/idc-p/1484839....

the article seems to be missing

[Stan Jones]

Sorry posted an abbreviated link:

https://community.adobe.com/t5/premiere-pro-beta-bugs/cannot-install-premiere-pro-beta/idc-p/1484839...

Stan

[Suvo Sur]

@Stan Jones - Yeah, having the Beta build version definitely helps. Currently, I am attempting to repro this issue in our Production build (25.6.2), with the expectation to work into Beta from there as necessary.

[Andrew C. Brinsmead]

HI @stan, thanks for your notes.  

One question that I do have (which is likely impossible to answer), how should I know when to update a Beta Build? As I mentioned above, I've been updating pretty much daily as they come out (with similar expectations to yours that there might be new bugs being introduced & I can't roll back…). 

[Suvo Sur]

My understanding is that the Premiere Beta build updates nightly. On the V4 Panel side, we aim to publish nightly builds as well, though they may not be as frequent. You can check the panel version on the “Get Started” (login) page, where the build date is displayed.

[Patrick Southern]

@Andrew C. Brinsmead and chance we could set up a call with you and our team? Both the duplicate markers and mis-named sequence issues are very odd. We'd love to triage the underlying cause of both issues with you, if you're open to it.

[Andrew C. Brinsmead]

Thanks @Patrick Southern  I would love to do that! I'm in Sydney Australia, but I"m working from home on this project, so I can be up late or early to do a Teams session (we'll just have to work out the best time). I have two other persistent problems that may or may not be related: media relinking when opening projects and matchframing back to source multicam sequences (which I've been discussing with Matt Christensen.

Here's my posts about the two other issues:

Relinking:
https://community.adobe.com/t5/premiere-pro-beta-bugs/system-hanging-up-while-relinking-media-on-ope...
Matchframing to Multicam sequences

https://community.adobe.com/t5/premiere-pro-beta-bugs/matchframe-to-multicam-clip-links-to-edit-lock...

cheers & thanks!

Andrew 

[Andrew C. Brinsmead]

thanks @Suvo Sur! I've generally been updating my Beta version daily, while I'm aware that new versions might introduce new issues, what is the best practice to follow in terms of frequency of Beta updating? (how regularly should I be doing it, and how do I find out if an update has any issues (apart from the obvious way…)?)