Premiere confuses files of same name

Forum|Forum|8 years ago
December 14, 2017
11 replies
16452 views

I'm editing many VOB files from different DVDs in the same project. Files from one DVD have the same files name as files from other DVDs, but placed in separate directories. Not only does Premiere get completely confused when previewing the videos (playing video from a completely different sequence than the one selected with the play head), but it replaces the incorrect audio from wrong files when rendering... or drops the audio for certain VOB files entirely.

The only way to get Premiere to correctly reference the correct file placed on any sequence timeline is to pre-process all of my VOB files with Mpeg Streamclip, saving one large uniquely named VOB file per DVD, and importing that file into Premiere.

How is it possible that Premiere cannot handle files that have the same name? This is beyond amateur.... Professional grade? Really? I'm having a hard time showing people at work that Premiere can be used in a professional environment. I'm having to resort to using a decade old video converter (Mpeg StreamClip) to read and correct issues that Premiere completely chokes on.

Combined with the horrible extremely slow import bug that plagues large projects, and the decade old 'Unknown Error' encountered by many during export, Adobe is showing that their software is not professional grade and cannot be counted on in work environments. But what choice do I have? Sony Vegas became horribly buggy 5 years ago, pushing me to Adobe Premiere. Avid Media Composer? Software standards, with the advent of never-ending patches, have turned all customers into beta testers. This is not acceptable yet seems to be the industry norm now.

In 4 years of my CC membership, paying an average of $75 CAD/month, I've spent over $3500 to use Premiere. Adobe is repaying loyal customers with terribly buggy software that is only getting more and more buggy.

Show previous replies

S

SAFEHARBOR11

Participating Frequently

Importing using Media Browser rather than File > Import would likely fix the confusion within Premiere, however you may have to move or rename the current media folders, prior to re-importing media or the previous issue may follow along if working in the same project. NEW project should be okay just using Media Browser method.

Thanks

Jeff Pulera

Safe Harbor

V

vanlazarus2013Author

Known Participant

Sorry Jeff, but your suggestion is not relevant to my problem because I am using Media Browser to import these files. And this is also a new project not created with an earlier version of Premiere. I appreciate your suggestions but am tired of the black magic voodoo methods that many bring up to solve problems with Premiere. How is it that different methods of import in Premiere DO NOT USE THE EXACT SAME CODE TO IMPORT? And why is the mantra of avoiding project files created with earlier versions of Premiere so prevalent? If Premiere is not backward compatible with old project files, then don't allow it to load them. Period. Some form of half backward compatibility is completely misleading and a complete garbage policy by Adobe, which their marketing department seems oblivious to. Either the CC suite is backward compatible or it is not. Apparently, it is not.

Has someone flagged your response as the correct answer to make it appear that the problem I report is user error?.... as if using the 'incorrect' method of import is considered user error?