Joe Rusnak

My feedback

  1. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Premiere Pro » Import  ·  Flag idea as inappropriate…  ·  Admin →

    I have an AVCHD camera, that follows that naming convention; agreed, tedious.

    Renaming source media files on import can cause problems with lots of formats, and is a behavior PPro avoids, whenever possible.

    PPro can differentiate between files with identical names, based on their paths. But you’re right, this isn’t very obvious in the project panel (unless you’ve already set up the project panel to show paths).

    Would your suggestion be to append the date/time to the project item name, associated with 00001.MTS files?

    An error occurred while saving the comment
    Joe Rusnak commented  · 

    One factor that just dawned on me that I think may be the reason why Premiere Pro has difficulties with the file management. I was using a portable hard drive for my project and would work on the project on a Mac...edit...then mirror the file changes using a filesync program to the portable hard drive. Then I would go edit in the other location on a PC...file sync to the PC...edit...save...filesync the hard drive. I never changed the file structures. I was only really saving the project files and possibly some proxy files that may have changed as a result of whatever preview Premiere had made. I made sure to keep entire folder intact. I think this file saving between operating systems is the culprit. Windows 10 and OSX 10.15.7 Catalina.

    An error occurred while saving the comment
    Joe Rusnak commented  · 

    My suggestion would be to first ask the programmers why this behaviour is happening. I was told by the online live chat tech to bring in the files via the Premiere file browser. I don't think this is a fix. To be clear...I first drag the entire file folder from the capture card to the hard drive. Then I drag that folder into the Premiere Project window. It automatically creates a folder with a list of numbered .MTS files. in the "Projects Window". When an offending clip is on the timeline I can right click on the file and "Reveal in Finder" and Adobe somehow managed to display the file chain inside the AVCHD "folder". I then right click and "Reveal in Project" which points me to the proper .MTS file. I double click on that file and that clip pops up in a Source Monitor window and plays back properly. But then I go back to the main sequence timeline that has it's own unique sequence name and it still plays back audio from another file. There may be a problem between the way Adobe sees files and how MAC OSX handles the AVCHD file package. It's impossible to use the OSX Finder and double click on the AVCHD to drill down into the folder structure. I have tried to view the AVCHD file in several different view modes (list view, column view, icon view, ect) and when you double click the AVCHD all you get is Quicktime opening up a file browser window with generic clip names (Clip#1, Clip#2, Clip#3, ect) Regardless...Adobe is confused about something and all roads lead to the naming convention of .MTS files when imported. Again...the programmers need to be asked what or how Premiere sees the files. And how could it possibly only confuse the audio layer of a file? You would think that it would confuse both layers and play the audio and video at the same time...but it is only the audio that plays incorrectly.

    Joe Rusnak shared this idea  · 

Feedback and Knowledge Base