Skip navigation

Premiere Pro

rklem

Currently Being Moderated

After Premiere Pro 6.02 update: Media offline

Sep 6, 2012 8:31 AM

Tags: #6.02 #media_offline

I just upgraded Premiere Pro from 6.01 to 6.02, opened my current projects, and all Canon 5D MK II clips (and an imported m4v clip), which were there in PPro 6.01, are now offline! :-( (HVX200 files, Screen recordings and audio only files are still there). That's bad, because I have to finish that project asap. In case there's no easy fix: can I downgrade to 6.01?

2398 Views 23 Replies Latest reply: Jack KDS, Sep 7, 2012 11:48 AM

Replies

Currently Being Moderated

1. ECBowen,

Sep 6, 2012 8:36 AM in reply to rklem

Report

The Codec decode import Data has likely changed with the update. Try Creating a new project and then import 1 sequence at a time into the new project. See if it will relink the media.

Eric
ADK

|
Mark as:
Currently Being Moderated

2. rklem,

Sep 6, 2012 9:06 AM in reply to ECBowen

Report

Thanks Eric,

I created a new project and tried to import one of these "missing" clips, and PPro 6.02 does not recognize it as video anymore. It imports it as audio only.

A second project I'm working on (files from the same cameras) is fine. Just opened it in 6.02: no problems.

So the core of the problem seems to be, that 6.02 does not recognize some of my movie files as movie files anymore. But in OS X Finder, QuickTime etc. these files are fine, read/write permissions are the same as the files which are recognized...

|
Mark as:
Currently Being Moderated

3. ECBowen,

Sep 6, 2012 9:18 AM in reply to rklem

Report

What happens if you import a 5D clip that has not been imported to a project yet? Also go ahead and deactivate Adobe and then reactivate to make sure all of the codecs are active.

Eric
ADK

|
Mark as:
Currently Being Moderated

4. rklem,

Sep 6, 2012 9:33 AM in reply to ECBowen

Report

As said: I even can import the 5D clips of my second project, so some 5D clips work, some don't – but all of these clips worked in Premiere Pro 6.01. I tried some 5D files, which I did not import into PPro before: these work too.

What do you mean be "deactivate Adobe"? I repaired permission, started the Mac again...

|
Mark as:
Currently Being Moderated

5. ECBowen,

Sep 6, 2012 9:52 AM in reply to rklem

Report

If it is recognizing standard MOV files then all the codecs are active. There is no need to Deactivate Adobe and Reactivate.

Launch the Project in Question. Go to Project Settings and see if you have the MPE egnine set to Hardware. If so switch it to Software MPE mode and Delete the Previews when it prompts you. Save the Project and close it. Launch a new Project and Leave the MPE engine as software. Right lick in the Project bin area select Import. Hit the drop down where it shows all supported media and select Adobe Premiere Pro Projects. Go to the location where that project file is and select that project file. When it prompts you for entire project or selected sequences, choose selected sequences and just pick one of the sequences. See if the Media will relink.

Eric
ADK

|
Mark as:
Currently Being Moderated

6. rklem,

Sep 6, 2012 10:08 AM in reply to ECBowen

Report

Hi Erik,

thanks, did everything you suggested, but it didn't help.

|
Mark as:
Currently Being Moderated

7. ECBowen,

Sep 6, 2012 10:19 AM in reply to rklem

Report

Create a new Project directory preferably on a different mounted drive. Copy that project and media into that new directory. Launch that project file from the new location. When it prompts you for the location with the media select where the media files are now. See if it will relink the media then.

Eric
ADK

|
Mark as:
Currently Being Moderated

8. bobgundu,

Sep 6, 2012 10:25 AM in reply to ECBowen

Report

Same problem here. None of my RED footage is linking. Even if I start a new project the thumbnails finally show up and then Media pending warning.

|
Mark as:
Currently Being Moderated

9. rklem,

Sep 6, 2012 10:42 AM in reply to ECBowen

Report

@Eric, after copying the files to another drive they are recognized as movies again, so I can relink the media. So now I have to relink everything. Seems like a serious bug, but thanks for the workaround.

|
Mark as:
Currently Being Moderated

10. Jim Simon,

Sep 6, 2012 10:45 AM in reply to rklem

Report

FAQ: Why are some codecs and sequence presets missing from my installation of Premiere Pro?

|
Mark as:
Currently Being Moderated

11. ECBowen,

Sep 6, 2012 10:46 AM in reply to rklem

Report

That means the meta data attached to the Files is either corrupting or is no longer recognized by Adobe's Media Bowser. Do you have the original Drive Formatted as HFS+ Journaled or Non Journaled?

Eric
ADK

|
Mark as:
Currently Being Moderated

12. ECBowen,

Sep 6, 2012 10:48 AM in reply to bobgundu

Report

Bob, Do the same thing. Create a new directory on another drive preferably and then copy that project with the media into that directory. Open the project from that location and then Relink the files.

Eric
ADK

|
Mark as:
Currently Being Moderated

13. rklem,

Sep 6, 2012 11:00 AM in reply to ECBowen

Report

Both drives are formatted as Mac OS Extended (Journaled). The 5D files, wich worked after the update, and the 5D files, which did not work after the update, were on the same drive. Whatever happened here: I'm pretty sure that it was caused by the update to 6.02: The project worked in 6.01, I closed it, updated to 6.02 (which took two minutes), re-opened the project, and it didn't work anymore.

|
Mark as:
Currently Being Moderated

14. ECBowen,

Sep 6, 2012 11:27 AM in reply to rklem

Report

HFS+ Journaled has absolutely no positive effect on individual volumes. It helps data recovery with raid volumes and the OS drive with Time Machine. HFS+ Journaled however does cause allot of issues due to the Meta Data applied to the file system and adds significant performance degrading to drive requests in general. People who use HFS+ Journaled are simply creating far more failure points that will effect their editing experience and time frames. Honestly I see allot of Meta Data based issues on the Mac side in this forum and I would be willing to bet most would go away if the Drives would be formatted to HFS+ Non Journaled and then create a new master directory to copy the data back into to break the Meta Data ties in the volume table. Whether clients follow that advice is up to them. However people cannot hold Adobe at fault for issues caused by partition tables and OS specific functions when there are clear ways those are avoided. If clients are passing Storage media to others that use PC then they definitely want those media formatted HFS+ Non Journaled because right now Mac Drive has allot of issues with that. This is a clear message, to avoid failure follow recommended configuration policies.

Eric
ADK

|
Mark as:
Currently Being Moderated

15. rklem,

Sep 6, 2012 11:42 AM in reply to ECBowen

Report

Eric, I'll gladly follow your advice and reformat my media drives to non Journaled (I did not know that Journaled is a bad choice for media drives), but if you're telling me that this issue was only caused by a journaled drive, then you're simply ignoring the fact that this issue occured right after the update to 6.02. Anyway, thanks a lot for the workaround.

|
Mark as:
Currently Being Moderated

16. bobgundu,

Sep 6, 2012 11:42 AM in reply to ECBowen

Report

Looks like I hasd to re-install the RED importer. Now the performance issue... it appears 6.02 is not happt when using my RED Rockert card. I get better performance by turning it off. Is this a bug???

|
Mark as:
Currently Being Moderated

17. ExactImage,

Sep 6, 2012 11:46 AM in reply to ECBowen

Report

ECBowen wrote:

If clients are passing Storage media to others that use PC then they definitely want those media formatted HFS+ Non Journaled because right now Mac Drive has allot of issues with that. This is a clear message, to avoid failure follow recommended configuration policies.

Eric
ADK
Do you recommend that over using ExFat drives that both Windows and Mac can read/write? We've typically been using ExFat and not had any problems so far.

|
Mark as:
Currently Being Moderated

18. ECBowen,

Sep 6, 2012 11:46 AM in reply to rklem

Report

I am not ignoring this happened after 6.0.2. What I am stating is Adobe does not necessarily have all of the updates Apple includes with OSX that adjust meta data for Journaling. If they dont have those SDK Kits or changes then how can they know what changes they make to their media browser or file taging/scanning will have when they update it. If this issue was caused by the Journaling then had the drives not been formatted journaled, you would not even know an issue existed. Hence my point about configuration practices.

Eric
ADK

|
Mark as:
$terri\'s fav$

Currently Being Moderated

19. terri\'s fav,

Sep 6, 2012 11:47 AM in reply to bobgundu

Report

6.02 is way slower than 6.01 in my experience.

|
Mark as:
Currently Being Moderated

20. ECBowen,

Sep 6, 2012 11:50 AM in reply to ExactImage

Report

The only problem I have seen with ExFat has been with Windows users trying to work directly off an Exfat drive. If you copy the media off that drive then you should be ok. However I have seen the Quicktime Mpeg2 corruption issue out of FCP so you may want to try HFS+ Non journaled if you start seeing that with Pro Res Files on import on the Windows systems.

Eric
ADK

|
Mark as:
Currently Being Moderated

21. ECBowen,

Sep 6, 2012 12:05 PM in reply to terri\'s fav

Report

I am currently setting up a test system to start looking at the performance with test projects I have. It would help if I know what you are running into and when along with what media/codecs your using. If your using red then please let me know if it's Red One material or Epic/Scarlet since I dont have any samples of those right now. please also state Mac or PC. I currently have limited testing options on Mac.

Eric
ADK

|
Mark as:
Currently Being Moderated

22. ECBowen,

Sep 6, 2012 2:06 PM in reply to terri\'s fav

Report

I listed the Performance Fix for Windows under the 6.0.2 update Thread created by Todd.
http://forums.adobe.com/thread/1061522?tstart=0

Eric

|
Mark as:
Currently Being Moderated

23. Jack KDS,

Sep 7, 2012 11:48 AM in reply to rklem

Report

I had the same problem (on Mac os 10.6.8) with media showing Offline after update from 6.0.1 to 6.0.2... I tried deteling media cache files and re-activating my subscription account, but nothing worked. My solution was to un-install Premiere, reboot then re-install it again (v6.0.0) from the Trial installer I still had. Now I can open my project andget back to work.

|
Mark as: