Skip to main content
oceanet40021756
Participating Frequently
November 2, 2016
Répondu

Media offline after cc 2017 update plus audio issue

After the premiere pro cc 2017 update I have some issues with clip sequences and audio.

When starting a premiere pro file of the previous version the system says:

"This project has been created with a previous version of Premiere Pro and has to be converted..."

After clicking "OK", all the video sequences are missing. By trying to insert them manually, the audio files of the clips are missing.

I tried to start a new project with different video-clips and the same problems occur again. No audio files are in the project just the video file.

I tried to sign out and sign in to premiere pro following a troubleshooting instruction but it didnt work.

Anyone can help me? Thank you very much in advance.

Ce sujet a été fermé aux réponses.
Meilleure réponse par Vidya Sagar

Hi,

Apologies for the Inconvenience.

As stated by Howardj, Please clear the Media Cache & check the audio in the timeline.

Instructions are in the following link. FAQ: How to clean media cache files

If you want to install the Previous version of Premiere Pro, please check the instructions in this link

FAQ: How do I reinstall Premiere Pro CC 2015.2 (9.2)?

Thanks,

Vidya Sagar.

44 commentaires

rexomus
Known Participant
November 16, 2016

I was having the same problem. I went to the media cache folder (C:\Users\YourName\AppData\Roaming\Adobe\Common) and opend the Media Cache Files folder and deleted everything in it.

After that I open my project and right clicked on the files missing audio and clicked "replace footage" and navigated to the files I needed and it worked correctly after that.

Thank you for starting this thread.

Participating Frequently
November 19, 2016

I did that as well but it's not importing files that were already in the project and working.  It says they are now damaged or unsupported format

richm33506555
Participant
November 16, 2016

Look at this...

info: Need help now? Find answers in the Premiere Pro, After Effects, Encore, and Audition forums. Join the conversation with Adobe staff and community experts.

You can also chat with Adobe experts live on Twitch. See our schedule for Ask the Experts LIVE, and get "How To" video live streams, ask questions, and learn new skills! 

info: All our representatives are currently busy assisting other customers. Your wait time is approximately '2' minutes. Thank you for your patience.

info: You are now chatting with Sarthak .
Please don’t close the chat window or browser tab since it will end our chat session. 

Sarthak : Hello! Welcome to Adobe support.

Sarthak : Please allow me 1-2 minute(s) to review your account details.

Sarthak : https://helpx.adobe.com/creative-cloud/help/download-install-app.html#topic-3

Sarthak : Please follow the above steps to install Premiere Pro 2015.3

Sarthak : This problem is occurring on certain old projects.

Sarthak : You can finish your project in the old version and then start afresh in Premiere 2017.

rich murphy: I've done that. that verrsion will not open the file because it was saved with the new version (2017)

Sarthak : You will have to open the old copy of the project, not the latest copy.

rich murphy: we have been using 2017 on this file for days. one machine can open them and the rest cannot.

Sarthak : Yes, I got that from the previous case.

Sarthak : Try this on the other computers.

rich murphy: so you're telling me that the current file is lost???

Sarthak : Make a new project in Premiere Pro 2017. Window-> Workspace-> Uncheck 'Import workspace from projects'. Then import that old project into the new one.

Sarthak :

rich murphy: The old project doesn't help me. We have 20+ hours of editing and client changes in multiple versions past the old file.

info: Your chat transcript will be sent to RICH@OBATA.COM at the end of your chat.

Sarthak : By old project, I mean the project file that does open on one computer.

rich murphy: ok tried that and I get the same error.

Sarthak : Then this project file won't open on other computers.

Sarthak : You can try any auto-save copies however, I don't think it might help much.

rich murphy: yes it will. we just did and saved with a new filename.

Sarthak : ok, great!

rich murphy: But I can't open on this machine.

Sarthak : On the new machine, right?

rich murphy: we have three editors. one can open this file and the others can't.

rich murphy: I'm worried that the one that can will eventually not be able to and then we will be in real trouble.

Sarthak : Like I said, it can happen with the old project files and the only work around is to finish the project in Premiere Pro 2015.

Sarthak : You can keep on saving backup copies of the project.

rich murphy: But that is impossible since the file is already in 2017. Is Adobe working on a fix for this mess?

Sarthak : Yes, we are working on a fix.

rich murphy: Timing?

rich murphy: still there?

Sarthak : Yes, I am here.

rich murphy: when is this fix expected?

Sarthak : It should be addressed in the next update; we don't have concrete information.

rich murphy: You have to be kidding me. We have more than a dozen projects mid-stream. This is unacceptable.

Sarthak : Then please install Premiere Pro 2015 and finish the projects in that version.

Sarthak : It is anyway not recommended to update or upgrade applications in the middle of a project.

rich murphy: That is nonsene. What about opening projects in the future???

rich murphy: nonsense

rich murphy: Are you telling me that Adobe does not guarantee the ability to pick up on projects in the future and make edits?

Sarthak : It does guarantee however, sometimes the problem can happen on certain projects.

rich murphy: Your installer for 2017 disables 2015

rich murphy: BTW

Sarthak : If the problem occurs in future, you get the option to download a previous version.

Adam92
Participating Frequently
November 16, 2016

It doesn't look like Sarthak did a great job.  But from what I can glean from your transcript, he seems to think that part of the issue is coming from PPro failing while trying to initialize a particular Workspace?  I had similar issues when I was starting to mess around with writing extensions in the new CEP architecture and certain buggy panels would completely crash PPro when it tried to launch, which was extra crappy when that buggy panel was part of a saved Workspace.

My workaround, and I'm on a Windows machine, was to hop into

C:\Users\[yourUserAccountName]\Documents\Adobe\Premiere Pro\10.0\Profile-[yourUserAccountName]\Layouts

and delete any recent workspaces. 

That fixed the crash at launch issue for me.  I believe that you can even blow away the entire contents of that Layouts folder completely and the next time you launch PPro, it'll default back to the vanilla workspaces that ship with the program.

If that gets you back into the project, then you can try testing panel by panel until you figure out which one was causing your issue.

I hope this helps!

Participant
November 15, 2016

really? I've also audio issue with my .aep file.. dynamic link to Premiere Pro CC 2017, and no backgound music but just the voices of persons.. is there any solution ?

Roman Kosenko
Participant
November 15, 2016

Sorry. I don't know any solution for linked aep-files. Try my method. Maybe it works

Roman Kosenko
Participant
November 14, 2016

This is not only Premiere Pro 2017 problem. I seeing it before. Deleting cache not working. Just move all your files to another folder, or rename original.

Smurfs
Known Participant
November 9, 2016

im getting this horrible audio dsync issue with premiere cc 2017, now im using only 2015 because everything runs fine there...if anyone could lend me a hand to fix this issue i would be really glad

kulpreet singh
Inspiring
November 10, 2016

Hi Smurfs,

What is the source and format of that video?

We need a lot more information to begin with.

Thanks,

Kulpreet

Smurfs
Known Participant
November 10, 2016

awesome, im using .mov videos that im taking with my camera, 1280X720, 4k bit rate, 24fps, my audio is like this, 44khz, 1400 kbps, 2 channels, i dont know what to do to make it work on premiere cc 2017 anymore...i was like "well...gonna keep my 2015 that was fine"

is there anymore information that im missing ?

Participant
November 9, 2016

I followed these instruction and lost a whole weekend responding to the issues that most contributors have outlined already in the forum, so I won't reiterate. But, I desperately need to be able to export a decent file ASAP.

I as I stated , I have spent time scouring the forums and with support and followed all the instructions and advice given.  I've adjusted my RAM, I've cleaned caches (often), etc etc.

I still cannot get an export with both a video and audio file of any kind of quality. I have tried a number of combinations of codecs. Nothing works.

This is a 15 minute documentary with virtually no special effects (except for transitions and some minor color correction). All imported media has been thoroughly checked for issues.

Have there been any fixes or developments that anyone can share with this export issue? I see I am not the first person to post such an issue....

Participant
November 8, 2016

Hi everyone, here is what I did to solve the issue, something that I have to do every time Adobe issue an upgrade: create new folders where ever your project is stored, copy all the video files from the old folder to the new, open Premiere, replace old files in the project with files the same files from the new folder, this solved the problem for me

Known Participant
November 7, 2016

I managed to get audio back and clips to reappear following the instructions above on rename common to common1... that worked... premiere will then rebuild files and things got more back to working. However my audio keep dropping out now on playback, ever few seconds. Ho hum.

Kostas Arvanitidis
Inspiring
November 7, 2016

My experience on this issue. On the sequence the audio (mp3) played back normally. Exporting via Media encoder all audio was ok except the mp3 track (absent audio).

Exported via "export" all was ok.

What I found out is that despite my setting on where media cache files should be (a separate drive) Media encoder insisted to create media files on the prproj project folder. Deleted those cache files also and the problem was solved. (but still getting cache files on wrong folder... obviously a bug... please fix it.)

Participant
November 4, 2016

The issue was that Adobe could not link to the old commons folder.