I have all of my source footage and audio sorted into about 12 folders. Some of the folders have multiple files, others have just one.

If I import all of these folders into Premiere, any folders that have more than one file get a BIN created automatically. Any folders with just one file don't get a BIN.

I don't see the point or benefit of not creating a bin for folders with just one file. If I'm importing folders, I think it's safe to assume I want to use that structure. I plan to add files to these bins later and having to manually create them again in the Premiere interface is a waste of time!

This is related to:
https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/41902426-maintain-folder-structures-on-import?page=1&per_page=20#:~:text=Maintain%20folder%20structures%20on%20import

Not only has the above request been ignored for far too long, Adobe have compounded the issue with the new Import page.

The new import page is useless for anyone who is organized. And that means just about any professional video editor. Why?

When importing source material it is very likely the source material will have already been sorted into folders outside of Premiere, or be in a predefined folder structure which should be maintained.

Can I do that in the new Import dialog? No. Premiere decides that any imported folder structure is not required and dumps everything into the project panel.

If I have an exisiting folder structure that I import, I expect Premiere to maintain it.

Let me spell this out:
If the folder has multiple files in it - maintain it.
If the folder has ONE file in it - maintain it.
If the folder has NO files within it - maintain it.

NO LUT ON IMPORT !!!
Common. Nobody had that stupid idea for last 15 years!!!

Every time I open Premiere I have to "Interprate footage as REC709. Every folder. Fcuk. I have a lot of seperate folders. All my friends are saying like me "Fcuk" and make it the same.

We never had to do it for last 15 years. Why we have to now??? Did we do sth wrong to somebody???

Simply: I import materials SLOG3 from my Sony Cameras and everything on the timeline looks like ****. Too yellow, overexposed. Is this my material? Do I have to work with it like that????? No I have to go back change all the materials "interprete fotage as REC709" in all the folders separetly. Then push them again on the timeline and I can start to work.

Every time is the same. Siht!

NO LUT ON IMPORT!!! WHy somebody break Premiere PRO...pro.

Give me a button "NO LUT ON IMPORT"

Premiere is not recognizing the audio on my C100 footage when I import it. When I look at the audio in the source monitor, there is no wave form there is no audio on playback. When I try to sync by audio Premiere gives me an error that it can't beacause there is no audio. The audio is there when I play it back in VLC media player. Sometimes when I replace the footage, or make it offline and then relink it premiere will pick up the audio. But not always. This is happening on 3 different Intel based PC's running Windows 10. All are running Premiere v22.0.

I'm starting a new thread for an issue that originally started here:

https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/45186289-aaf-imported-sequences-not-playing-on-apple-silico

The original post (the title of which I can no longer edit, hence my opening this new thread) outlined an issue that I thought was a general Apple Silicon AAF import problem. But as I dig deeper with troubleshooting the issue, I figured out that the actual problem is that only ProRes .MOV files don't work when imported into Premiere via AAF on Apple Silicon machines. ProRes MXF files, however, import fine via AAF.

Again, this is a showstopping bug. We simply can't use Premiere on our Apple Silicon machines because of this, as we have to conform Video AAFs from Avid editors in Premiere for finishing and delivery.

I am using Premiere Pro 22.4.0 on a MacBook Pro (16-inch, 2021)

Using the new import / create a project in the updated Premiere I copy my video files from an SD card to an external hard drive. I do this by selecting copy media on the right panel and selecting my external hard drive as the location. This usually uses Adobe Ingest and opens up Media Encoder which will automatically copy the files to the new location.

But I get an error in the Events: 'Invailed Copy Path' which means the files are not copied over.

If I change the location to be my local drive then I have no issues and the files are copied over.

My general workflow is to work on external hard drives as I like to keep the local drive clear. The drive I am using is a Samsung 2TB SSD T5 connected by USB C.

Is anyone else experiencing similar problems or have I overlooked something?

It seems whenever I am navigating this new super-clunky interface for importing that every visible file and folder is just automatically selected with no quick way to deselect. And often deselecting takes around 5 seconds per file, which is great when it selects hundreds of files automatically. This being the only way to get into a new sequence means it sometimes takes me 5-10 minutes just to get into my project. This is the absolute worst. The audacity for any software designer to force you to use their file navigator vs the system's dialogue is absolutely ridiculous. Please just completely get rid of this import screen or else I'm just going to learn Final Cut.

This has been requested repeatedly, trying to convey the urgency a bit clearer:
With todays increasing mix of different device classes in production for all kinds of media, the lack of this feature has reached a breaking point.
The time and work required to synch up footage manually and/or use a work-around with Resolve/outsidePremierePro pushes you to use other NLEs to work efficiently and cost effective. Converting LTC inside premiere pro should be a given, footage ingest is at beginning, at the base of all projects!
And I do say this as someone who really likes premiere Pro.
Thank you, development team!

Hi,

For my projects, I still use a rigorous approach in copying all assets to a designated project folder before they are imported into a PPro project. This way, I prevent any assets from getting lost in the process, because they originated from temporary drives, download folders or other drives on your system beyond the project drive.

However, things would get a lot easier if PPro offered the possibility that anything that gets added to the project bin via drag & drop or the import feature, actually get copied over to the folder, perhaps as a background process. Meanwhile copying takes place PPro accesses the original source and when copying is done it replaces the instances with the copied file in the project folder on the hard drive.

This way, at the end of the project, you only need to copy the entire project folder on one or two archive drives to complete the archiving stage of the project.