With Prelude gone, it's now very difficult to quickly copy, verify and rename clips on ingest. I'd love this to be streamlined in the new media importer or perhaps added to Media Encoder. I really don't think it should be that we have to create a preset for each ingest in order to achieve these simple tasks which Prelude was perfect for, especially as you have to select a destination in order to create the preset.

Prelude allowed for quick, logical progression through the ingest settings allowing you to customize each ingest as needed.
Working in an education environment we produce several batches of video clips through the day, sometime within the hour and being able to efficiently name the clips is a crucial part of our workflow to ensure no clip overwrites another and so that we can easily find a students work when needed.

I hope you consider this for future updates.

I am editing a project for a client and I am stuck, and there is a deadline looming. My source material is XAVC Intra. When I attempt to bring in to Premiere either through the Media Browser or through File>Import, the result is an audio-only clip, no video. I also tried to bring the footage into Media Encoder and After Effects, with same results. After reading about other issues with XAVC format in Premiere, I downloaded Premiere Beta, but had simiular results. Thinking that perhaps Black Magic Desktop Video was somehow interfering, I uninstalled it but still had the same issue. I took the media to an edit facility also running Premeire 15.4.1, and had the same result. I can open the file just fine in QuickTime Player v10.5 and in Final Cut Pro 10.5.4, but not in Premiere 15.4.1. If I don't get this resolved today (10/5/21), tomorrow morning I will be forced to transcode all of the footage in QuickTime to H.264 (removing timecode, lowering resolution and minimizing color imformation) and eye-match the edits to the rough cut. I appreciate any help in this issue.

MacOS Big Sur 11.5.2
Premiere 15.4.1 (Build 6)
iMac (Retina 5K, 27-inch, 2017)
Processor: 4.2 GHz Quad-Core Intel Core i7
Memory: 64 GB 2400 MHz DDR4
Graphics: Radeon Pro 580 8 GB

I am editing a project for a client and I am stuck, and there is a deadline looming. My source material is XAVC Intra. When I attempt to bring in to Premiere either through the Media Browser or through File>Import, the result is an audio-only clip, no video. I also tried to bring the footage into Media Encoder and After Effects, with same results. After reading about other issues with XAVC format in Premiere, I downloaded Premiere Beta, but had simiular results. Thinking that perhaps Black Magic Desktop Video was somehow interfering, I uninstalled it but still had the same issue. I took the media to an edit facility also running Premeire 15.4.1, and had the same result. I can open the file just fine in QuickTime Player v10.5 and in Final Cut Pro 10.5.4, but not in Premiere 15.4.1. If I don't get this resolved today (10/5/21), tomorrow morning I will be forced to transcode all of the footage in QuickTime to H.264 (removing timecode, lowering resolution and minimizing color imformation) and eye-match the edits to the rough cut. I appreciate any help in this issue.

MacOS Big Sur 11.5.2
Premiere 15.4.1 (Build 6)
iMac (Retina 5K, 27-inch, 2017)
Processor: 4.2 GHz Quad-Core Intel Core i7
Memory: 64 GB 2400 MHz DDR4
Graphics: Radeon Pro 580 8 GB

I was doing a deeper dive to troubleshoot the XML export issues outlined in a previous bug report (https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/43998075-bug-audio-exported-from-premiere-pro-2021-via-fin) and discovered another bug.

Theoretically you can use a workaround to fix the export bug, if you have a 23.976033fps file you can replace footage with a 24fps file of the same content, make a new sequence off the 24fps file, and then copy your edits over to it. This allows you to export an xml that works when you import it back into adobe... mostly.

I say mostly because there's another bug that pops up, I believe due to the way different versions of Premiere Pro round the framerates. Based on the math of the ppro ticks it looks like 2019 is rounding framerates to 3 digits after the decimal, and 2021 uses 6 digits. This results in different ppro tick values for the exact same cut in different versions of Adobe.

This in itself isn't an issue, but the way it's interpreted causes a bug in xml imports. Premiere doesn't really respect the -1 in start/end xml tags which indicate a transition is attached to one end of a clip.

simple example:
Clip 1
In: 0
Out: 100
Start:0
End:100

Clip 2
In: 100
Out: 200
Start:100
End:200

Apply a 1 second Constant Power transition (24fps) and these values become
Clip 1
In: 0
Out: 112
Start:0
End:-1

Clip 2
In: 88
Out: 200
Start:-1
End:200

When a transition is applied to a clip, the in/out values change by (for example) half the length of the Constant Power transition.

So if you have an audio transition that's fully shifted to the left, the pproticks being just slightly off between versions can cause it to ONLY apply the transition to the left of the two clips. Because the clip lengths have been changed in expectation of a transition being applied to them, you end up with audio that's desynced from the video. For example if the transition was only applied to the left clip, then the audio in the right clip would start roughly 12 frames too early, because it was expecting the additional 12 frames of audio to be used/encapsulated by the transition.

There should be more protection/bug checking around the -1 start/end values so that transitions that are a few pproticks off from where they should be still generate their transition correctly rather than being detached from one of the two clips. In the previously outlined export bug for instance, you could have erroneous transition values that put transitions in the middle of clips, 30 seconds away from any cuts that might have needed a transition. Premiere pro should detect and warn the user of transitions it can't fix, rather than happily placing broken transitions on the timeline.

The Project Panel in the Assembly Workspace always defaults to the wrong pane! I don't understand why the default Assembly Workspace wants the Project Panel in the top right pane and the Audio Levels in the great big left pane that takes up half of the screen. I mean why do Audio Levels even matter in Assembly mode?
What I wish it would do is have the Project Panel in the great big left pane and the Media Browser should be in the upper Right Pane and that should be defaulted to open at the location of the Project File because all of my project assets are in the same root folder to keep them organized together.
I'm getting tired of having to rearrange the Assembly Workspace every time I open it.