We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
Hi there. In premiere pro CC, I'm trying to link media that has been changed or moved to a project. The media I'm looking for is on a network drive. When I click on "locate media" I am unable to browse to the netwok drive as there are simply no drives showing up under the "network drives" dropdown. Any ideas on how to make Permiere see my network to locate these files? Thanks in advance. BB.
Honestly, outside of using Adobe Anywhere, the better option is usually to keep everything local. Use network drives only for backup.
Some/all? versions of Premiere do not work properly, if at all, over a network
-see messages #1 and #3 in http://forums.adobe.com/thread/771151
-you MUST give all users administrator accounts to use Premiere
-and especially Encore dual layer http://forums.adobe.com/thread/969395
-#5 Server 2008 is UNsupported http://forums.adobe.com/thread/851602
-a work around, of sorts http://forums.adobe.com/thread/957523
-and not on a "domain" http://forums.adobe.com/thread/858977
Copy link to clipboard
I just had the same problem. The workaround was to create a shortcut to the folder holding the media on my desktop. Then in the Premiere Locate File I was able to dive into the server to access and link the files that way. Although this solution has a big shortcoming, because it relies on the shortcut being there. If you remove the shortcut the files can no longer be located.
Sidenote: In this day and age, that Premiere doesn't handle accessing media on servers well, is very surprising to me.
Copy link to clipboard
Just switch off 'Use Media Browser' in the Link Media dialog box, Premiere then uses Explorer (WIN) or Finder (macOS) and you can find your network drives (and your locally attached drives) in the normal way.
Unticking "Use Media Browser to locate files" in the "Link Media" dialog and using the OS file browser is quick and painless.
This is what worked for me. Thank you for the tip!
(Media browser wasn't even able to find an alias on my desktop).
This worked here as well. We have this contious problem on/off when Premiere working on the server. Usually derived when a project is created on Mac OS and then later on opened on a Windows machine.
This worked.. thanks so much. Lost precious time fighuring out this. Why Adobe changes things that worked for users, for somethinmg else more complicated...
OK, this is a GREAT tip but you missed a critical step. It is not possible to launch the dialog if you go to File > Link Media.
It requires the following:
1) In your project window, select-and-highlight any missing asset.
2a) Go to File > Link Media
2b) Right-click and select Link Media
3) De-select the 'Use Media Browser to locate files' as shown in the screen capture.
4) Using your system file browser (with access to the newtwork!) now select and replace the missing asset. This must be completed.
This setting will now remain as the new defailt, even after you close and re-open the file.
This totally works this solution, use this people, thanks Julienprod
Can not believe I've never noticed that option before!!!! Thank you!!!
The solution is to map the network drive to your computer and then Premiere Pro CC will detect it under network drive at the Media Browser panel.
I've created short blog post with step by step instructions and screenshots for this problem. Do check it out! SOLUTION: Link or Import Media on Network drive in Premiere Pro CC 2015
Thanks. You saved my day.
Handy workaround, but workaround all the same. Have Adobe acknowledged that isse?
The technician I talked to just blamed my network config (I am on Windows 7 pro), but I just checked with Bridge CC and if I go to Desktop/Networks, then all my network drives appear.
So it is definitely an Adobe Issue
thanks, the shortcut is the solution!
I just found this problem myself today and the solution by RichardB99-bbh2ia worked and I'm back to business.
The question is why ADOBE ignores those things and don't correct them. This is going on since 2014. How many updates came after that and why this wasn't handled?
Does Adobe have an answer for that or will keep ignoring their problems?