There is a bug in the new version of Premiere Pro version 14.8.0 (build 39).

I have mpeg files on my D:/ drive that worked fine in a Premiere project 3 weeks ago. Now when I open the project I get a bunch of errors...

Frame substitution recursion attempt aborting after multiple attempts on file D:\myfile.mpeg

I have hundreds of files that have this problem in the project. However, if I copy the file from the D: drive to the C: drive, there are no problems.

This is a big problem for me though because my C: drive does not have enough room for the hundreds of files on my D: drive.

NOTE: These files open and play just fine on either drive using Windows Media player or any other software to play the videos. It's only Premiere that has a problem when the files are on the D: drive. I have run all kinds of tests on my D drive with SeaTools and there are no drive problems reported. It's a Seagate ST8000DM0004-1ZC11G (8TB) drive.

Also note that my project had no problems whatsoever opening and displaying these files 3 weeks ago when I last worked on them. The only thing that changed was Adobe Premiere got updated.

Recently, at our company we've been producing virtual corporate events with multiple layered assets - one layer for a powerpoint slideshow, one layer for a camera shot, and one layer for a motion background. While working on these videos via Adobe team projects in Premiere Pro, we happened across a consistent bug that would black out our motion background. Here's the process that caused the issue:

• We would begin with footage that was recorded in 720p 59.94, ProRes422 LT. One camera shot, and one recording of the powerpoint slides using the same style of recorder capturing the camera. We'd create a sequence set to 1080p 59.94, and drop the camera and powerpoint clips into the timeline, then we'd toggle the "Scale to Frame Size" feature for both clips.


• The client wanted to see the camera shot and powerpoint on screen simultaniously with the camera being a smaller Picture-in-picture over the slides. So we'd scale the powerpoint recording to 90% with a position of 864,486. Then the camera shot we'd scale down to 35% with a position of 1584,891. The camera shot would be on video track 3, the slides on track 2, then we'd drop a motion graphic background on track 1. The motion graphic is created at 1080p 60 ProRes422.


• After that, we would add cuts to the powerpoint clip where the slides change. Then we would take 4000x2250px PNGs of each slide rendered out directly from Powerpoint and Alt-drag them over the cut clips of the Powerpoint recording to replace the old 720p recording with the higher resolution image. Because the clip was already toggled for "Scale to Frame Size" no further scaling was needed.

Now, this is the point where the bug shows up. If we close out of the team project or quit Premiere, when we re-open the team project and return to the point in the timeline where the three clips are layered together the motion graphic background will be blacked out. We were able to bring the background back by either toggling the "scale to frame size" of the (now PNG) powerpoint slide clip on and off, deleting the PNG and edit>undoing the delete, or altering the transform options of the PNG - either scaling it up and back down 1% or adjusting the position 1px in a direction and back again. We would need to do this for each powerpoint slide PNG individually, if we tried to batch them in some way the workaround would not work. The issue always seemed tied to the PNG clip, because altering anything in track 1 where the motion background was would not yield any change.

After executing the workaround in the affected sequences, everything was fine again up until we closed the team project and reopened it. At which point we'd need to go back through and execute the workaround once again, the tediousness of which really made the bug stand out for us.

Hopefully this is enough to go off of, I will be very interested if any changes for this come through, as it is a workflow we are beginning to implement for many of our virtual events moving forward. Thanks for reading! I'll keep an eye on this thread in case more information is needed regarding the issue.

Something always baffles me.
Why is it I can render something (e.g. Render in to out) and my timeline indicates green. And the payback is fine. And the export is great (and fast). But the next day after I power-up and open the project my timeline is once again dappled with red & yellow sections?

Why does PP lose track of the renders?
In an Avid MC system once I render it, it’s done forever - unless I change a parameter or delete the media myself.
So I find the unprovoked disappearance of rendered files not annoy annoying but terrifying.
Sometimes I may want to screen something the next day and I’d like to assume all is well and ready to go for tomorrow.
Now I find myself showing up early just to re-render everything again.

(Before you ask, my cache is not set to delete in X days)

><({(º>

It would be very helpful if Premiere Pro would have a feature to easily move an item or several selected items to a specific targeted bin. I appreciate the drag-and-drop feature to move items inside or outside of bins but it would be a life saver if just by right-clicking on an item would bring up an option to Move Item to Bin and have a submenu come up to allow selecting from a list of bins already created by the user as shown in attached mock-up image I created. This would be tremendously helpful especially when working with a large project with hundreds of items in a project. Premiere already makes use of a similar feature to change a bin item's label color: Right-click on item>Label>Select Label Group>Label Color Name. So, I don't think it would be difficult to add a similar feature to move a selected bin item to a specific (already created) bin. It's menu path would be something like: Right-click on item>Move Item to Bin>Select Target Bin>Target Bin Name

When an external monitor is attached (either as the primary or secondary display) Premiere will hang during project open (never displaying the UI), either during application launch or Mac wake from sleep, if and when the Lumetri Scopes window is/will be 'active' ie open in the GUI monitoring an active sequence.

Workaround 1: Close Scopes window (or close all sequences) before closing the project / quitting the app and/or allowing the Mac to sleep.

Workaround 2: force quit and reopen Premiere using (creating if necessary) an empty project... once the application is fully launched and the empty project is open (the UI is drawn) then the original project can be opened without issue.

Workaround 3: disconnect external display

Sometimes Warp Stabilizer gives really weird wobbly results, and that's because it sees a face in the frame and it's trying to stabilize to the face. Occasionally I want that, but in my view what we normally want is for it to stabilize the whole shot (in other words make the camera less shaky relative to the environment it's in). Surely there could be a simple option (applied by default) that ignores faces? Also the faces are normally somewhere in the centre of the frame, you could make a warp stabilizer mode that favours near the edges of the frame that could give alternative results that might be closer to what you're looking for.

Premiere and Audition refuse to work well together with his subclips. I clean up his edit as I would with any other project, bounce it to Audition using the standard workflow and settings (r-click on sequence > Edit in Audition > Sequence

Entire Sequence

None

9.0sec handles

Transfer Settings

Transfer Settings

☑ Pan & Volume

☑ Open in Audition

The project opens up in Audition, the audio files conform, and everything looks fine. Except that every sinlge subclip is using the wrong portion of the audio. I'm sure there's a rhyme or reason to it on the backend, like Audition is reading the duration TC from the subclip and applying it to the master clip or something, but the end result is an unsuable mess in Audition -- instead of a clip playing the proper sound bite from the edit itself, Audition plays back a seemingly random piece of audio from the master clip.
I've spent hours playing around with the various "edit in Audition" settings with no luck. I've tried opening the Pr. project directly in Audition instead of trying to bounce it to Audition from within Pr. Same thing happens. I've tried to project manage the sequences (consolidate and transcode with handles), but the operation fails due to some unspecified error where Premiere refuses to transcode the audio clips (I assume for whatever the same reason is that Audition 'effs everything up).

I've done a Render and Replace with the audio on the timeline before bouncing to Audition. This works --everything opens up properly in Audition --- but there doesn't seem to be any way to R&R audio with handles, so I'm stuck with zero leeway to edit clips on the Audition multitrack timeline. Frankly, I'm not about to spend hours manually rearranging all of the clips on the Pr timeline, adding handles on either side of every piece of audio, because Adobe can't figure out how to make their programs actually work properly.

I keep having this exact same problem with every project this guy sends me; I've never had this happen with any other client (and I've been doing this for a LONG time). In the past, I've ended up just doing a rough audio edit for each different interview subject/VO recording/nats audio track, exporting an individual mixdown for each, stacking all of the various track mixdowns in a multitrack session, doing a fine mix, exporting separate voice/nats/music mixdowns back into Premiere for any final timing adjustments. I'm not going to mince words here: that process 'effing SUCKSSSSSSSSSS.

Anyone have any suggestions for fixes or workarounds? I'm completely out of ideas...

Win10 Pro

Pr 14.8.0 / Au 13.0.13.46

Though this same problem has been happening to me with every version of Pr since at least Pr 13.1.5 / Au 12.1.5.3 (the versions I was running when this guy first started bringing stuff to me).

All footage stored on internal SSD drives - no NAS drives or DAS drives in play. No proxies, working with the raw footage (well, subclips created from the raw footage, anyway :facewithrolling_eyes:). Clips were captured using a ton of different cameras, in varying framerates, framesizes, codecs; all clips have this issue, regardless of their specs or point of origin.

I've spent dozens of hours trying to make this work. As best I can tell, there are three"solutions" to this bug:

1) Don't use subclips -- they're janky and super broken.

2) If for some reason you absolutely HAVE to use subclips (or have a client who insists on using them cough), don't use Audition -- the subclips will not translate to Audition properly.

3) If you find yourself forced to use subclips and want to use Adobe's audio editing software to, y'know, edit audio, you'll have to go through each and every subclip in the project one at a time at the bin level and convert them to Master Clips. Once they're Master Clips instead of subclips, they'll bounce to Audition properly.

Go to the bin where your subclips are located

Right-click on the subclip

Choose Edit Subclip

Click the Convert to Master Clip checkbox

Click OK