Diagonal "danger stripes" lines in nested and regular clips in edited sequence after upgrading the project to 13.01

[Schiemer]

Adobe and Premier Community,

I have a project that was ongoing for over a year with dozens of separate sequence videos in it for this website client.  In each sequence we have numerous nested clips because we change the speed on the clips and then sometimes apply Warped Stabilizer, thus the clips need to be nested to do this.  None of the footage or editing has changed since completing this project back in April (It was 100% perfect in this last version of Premier), but now the client wants to edit a few of the videos with new building stats.  No problem right, WRONG!  Much to my dismay, I now have the "danger stripes" blue diagonal line issue with dozens of clips and nested clips throughout my project sequences that I have to go through and manually fix to what was once a finished video.  WHY??? This project was perfectly edited to their request and all videos were exported to H264 for Vimeo upload. I thankfully have them all to use for re-editing each mistake that Premier caused!

Since the project was finished in April, Premier has been updated 1-2 times and thus the project needed to be updated to the latest version when I opened it in the new version on my system. I have never had an issue upgrading this project or any in the past.  This update caused this diagonal line issue throughout my already finished project on EVERY timeline in numerous spots. This is going to cost me days of non-billable time.  AHHHH!!!   This appears to mainly happen on all the nested clips, but it also happened on a few regular clips too.  Some nested sequences are fully black, yet still show the clip it's linked to properly in light blue.  Yet some show the footage for half the clip and diagonal lines through the other half, thus turning black for that half.  The reason for half and half is the linking of the nested clip is there, but the clip linked is only showing what was marked in to out.  It does not show the entire master clip it was originally pulled from.  Or, in some cases, it shows the wrong in to out location from when it was edited.

Why would updating my project cause this issue and change 50-60% of my nested clips and 20% of the regular clips to the wrong in-out and thus give me diagonal lines on the clip?  ALL of the clips with the glitch are shot on GoPro Hero 5, have the Gopro Lens correction filter applied and some also have Warp Stabilizer applied if that matters at all to the discussion. I am still scanning through each timeline, but it appears that all drone footage and graphics are 100% correct.

Here is a Dropbox folder full of images showing the issue across numerous sequences.

https://www.dropbox.com/sh/ogg7nn5xkufllka/AAB3O1X3xM2Ed0pveWQVJ5asa?dl=0

Again, this should have been a clean upgrade of a finished project, but instead, the upgrade has just caused me a nightmare to fix over a dozen 1 minute videos that were 100% complete.

Also, FYI, I do still have the original Project file and all the video source footage linked 100% correctly when the project rebuilt itself.
Nothing is missing from the original project. Just for reference, here are all the finished video linked on their site that I now have to fix unless there is a way to upgrade this again without the issue:

http://thomas-mack.com/virtual-tours/

Can I install the previous version to hopefully not have to fix all these videos and wait until Premier 13 is fixed and allows past Projects to be upgraded without issue???  I am so frustrated right now.  PLEASE HELP ADOBE!  FIX THIS!

[Schiemer · Accepted solution]

UPDATE:

I figured out how to install the previous version of Premier 2018 (Version 12.1.2) and the exact same project is now back to it's original 100% complete with none of the same issues that are caused in the upgrade of the project to Premier 2019 (version 13.01). 

Please Adobe, fix the issue with Premier 13.01 when it upgrades past projects. 

This is a serious issue to any editor looking to upgrade a finished or ongoing project file!!

[Schiemer]

No response from Adobe at all on this?  Per usual, Adobe does not care about their users and their projects. They increased their cost and decreased their reliability (I have issues with Premier, Photoshop and now even lost Muse).  This is such a sad realization that Adobe is just not the same company any longer.

[R Neil Haugen]

I have no clue what response you expected. This is designed as a primarily user to user forum for questions/answers with oversight by product support staff. Although in the last year, the program manager has made engineering staff available on here for certain things.

One of the better features of the whole CC model has been the ability to keep several major versions installed at the same time. You cannot do this say with Resolve.

Each major build series *will* change underlying code in order to move forward. This is why being able to keep previous versions installed and work projects in their version is SO useful.

Currently I have 2015.3, 2017, 2018, and 2019 installed.

Also a better practice if you do want to test a copy of a previous version project in the new version is to create a new project in the new version; copy that project file into the new version's projects folder you made, then from the Media Browser in PrPro navigate to and import the previous project file contents.

This is normally a more stable way to move a project forward. Also, if there are issues, you can immediately get back to the project in the older version.

Neil

[Daniel Hoover]

Schiemer​ Kevin-Monahan I wonder if your issue is related to these threads, namely the timecode being interpreted so far off that there isn't even media there to show, hence the diagonal lines.

Mismatched media timecode in and out points Premiere 13.0

Premiere Media Start timecode issue MXF

[Daniel Hoover]

Some people on UserVoice are reporting that this MXF timecode bug has been fixed in Premiere 13.0.2 - has anyone else tried the new update?

Bug: timecode is not accurate upon import – Adobe video & audio apps

[R Neil Haugen]

No one has posted back, but ... that's probably an indicator that things are better. If they weren't, there'd certainly be posts about it.

Neil

[Paulo Ovalle]

YEEESSSS !!! i've been with the same problem for tha past week and today i updated my PP and when i loaded my project tha had numerous danger stripes, i was all clear and g2g !

thanks guys you're the best ! hope this problem/bug won't appear anymore

[connor_d]

Has anyone figured out how to fix it without reverting to a previous version? I only have 5 or so clips in a large timeline with the problem so if I can just fix those few shots it would be back to normal. Plus I didn't notice them at first and I have kept editing in the 2019 version project file and I'd rather not lose the new work. Thanks.

[Daniel Hoover]

Have you upgraded to Premiere 13.0.2?  What version are you using?

Try changing the starting time code for each “danger striped” clip.  In the Project Panel, right click on the clip(s) and select Modify > Timecode.  Play around with different options, see if setting it to 0;00;00;00 or Original Timecode fixes it.  Or it may need some custom offset.  To figure that out, you may have to do some Match Frame commands on the ”danger striped” footage in the timeline to see what timecode it’s trying to use.  For example, you may have a 60 second clip, and you’re using a segment from 0:10-0:15 on the timecode.  But when you do a Match Frame command, it might show its trying to use a timecode like 10:10-10:15, well outside the clip’s actual duration.  So to fix, either use the Slip Tool to slip it back 10 minutes, or Modify the timecode to start at 10 minutes.  Something like that might work until this is fixed.

[rojgreen]

I had this as well, on a project - just happened one day, was running fine  and then diagonal lines throughout one section of my edited sequence. Sometimes they started halfway through a clip.

My solution was I had to slip each individual clip by a set amount of frames) in my case (59 sec16 frames to the left) All of the clips were out of sync, the ones with Diagonal lines were referencing timecode that were before the start of the clip. I ended up making a macro to slip each clip with Keyboard Maestro. What a drag. Fixed now though. (Thank goodness I had a separate audio recorder so I could work out the offset as that didn't slip, just the prores footage)

Funny thing was Just one part of the footage was corrupt - the rest of the project was fine.

I wish I could slip multiple clips at once, that would have been a lot quicker.

[Novel_MP]

I don't think it's accurate to say that this post has been "answered". Reverting back to a previous version is NOT an answer. It's a workaround.

However, I found another workaround that worked for me. Instead of trying to open your old project in the new version of Premiere. Start a new project file and import the old one once you're up and running. That seemed to work for now.

This syncing issue is a BIG deal! I needed to make an update to an old project today, and I opened it up and the start points of the footage is all messed up, which leaves all my edits in the wrong places.

And it's not feasible to tell us to work on the old version. I have on-going projects that are sometimes months long that I need to open the old project file months after I started it. And I have new projects that I'm starting all the time. So what happens with those new projects while I'm still using the old versions? That means for all my new projects that I start in the meantime, that are still on the old version, which means I have to wait to upgrade until those new projects are closed...sheesh! This is a mess.

I hope Adobe has moved this syncing issue to the top of the list of bugs. This is a MAJOR problem. It renders projects unusable. Adobe, please get this fixed ASAP.

[R Neil Haugen]

This forum is primarily user to user.

PLEASE post this over on the new bug/features page, linked on the top of the Overview page of this forum. Their UserVoice system is wired directly to both the engineers and the upper managers who make budget decisions.

I'm on my phone or I'd include the link.

And better, after posting there, come back here and post a link. We can then go upvote it.

Neil