{"id":524,"date":"2015-06-09T16:22:13","date_gmt":"2015-06-09T16:22:13","guid":{"rendered":"http:\/\/editspecialists.com\/pr\/?p=524"},"modified":"2016-08-26T22:52:49","modified_gmt":"2016-08-26T22:52:49","slug":"troubleshooting-101","status":"publish","type":"post","link":"https:\/\/editspecialists.com\/pr\/index.php\/troubleshooting-101\/","title":{"rendered":"Pr Troubleshooting CC 2015.4 Summer 2016"},"content":{"rendered":"

Before troubleshooting\u00a0anything,<\/strong> make sure your WIN or MAC is optimized\u00a0for video editing by following the Resolve 12\u00a0Configuration Guide.\u00a0<\/a><\/p>\n

Premiere crashes before opening.
\n<\/strong>Delete the the file: “Effect Presets and Custom Items.prfpset”, which is stored here:
\nWIN<\/strong> >C:\\Users\\<username>\\Documents\\Adobe\\Premiere Pro\\9.0\\Profile-<username>
\nMAC<\/strong>>\/Users\/<username>\/Documents\/Adobe\/Premiere Pro\/9.0\/Profile-<username><\/p>\n

Video file\u00a0errors:<\/strong>
\n“The selected file does not contain video media used by clip references in one or more sequences”<\/strong>
\nThis is a codec not installed or not recognized error.\u00a0Try opening the file in Quicktime or VLC. If it doesn’t open install the missing codec.
\nIf it opens>\u00a0Reset Premiere >see step 4\u00a0below. Also try trashing Quicktime preferences or un-install\/re-install Quicktime.<\/a>
\n“The File Has no Audio or Video Streams”<\/strong>
\nThis is another codec error >\u00a0Quicktime Animation codec is not supported anymore in Premiere 2015<\/a>
\nExport ProRes\u00a04444\u00a0(Mac only) or Cineform<\/a>\u00a0for Mac & PC compatibility.
\nQuickTime for Windows cannot export H.264<\/a>\u00a0on computers that have more than 16 CPU virtual cores due to a problem in the Apple H.264 compressor component. This means no .MOV from a Windows Machine for ProTools. See\u00a0Avid-qualified video codecs for Pro Tools 11 and 12<\/a><\/p>\n

Click here for more Adobe instructions on troubleshooting video files<\/a><\/p>\n

Adobe Premiere Pro CC has stopped working.
\n\"pr-stopped\"
\n<\/a><\/strong>-After the program\u00a0disappears
\n-Restart the CPU if you worked\u00a0more than 3hr.
\n-Start Premiere by clicking in Start-menu\/Dock, NOT<\/strong> the project you had open.
\n-When the message comes up that the previous project was recovered> save it with a different name in project location.
\n-Close the recovered project (it is\u00a0unstable\u00a0, DO NOT USE!)
\n-Open the last saved project, either from the Auto Save\u00a0location or the project folder. (whichever one was the latest)
\n-Using Media Browser, import the Sequence you where last working on from the recovered project.
\n-Save the project as, with a new version number>Never rename project files,<\/strong>\u00a0instead use File >Save as.
\n-Put the other projects in an\u00a0“old” folder.
\nTake care of your project files<\/a> especially when they get\u00a0complicated, contain multi-camera sequences, or a lot of media objects (clips, graphics, audio, other media).\u00a0Managing versions of project files is a\u00a0necessary part of your\u00a0job as a video editor. After all, it represents the sum total of all the hours, days, and weeks spent on the project.
\n
\nApply these tips in order to prevent time loss:
\n<\/strong>1.\u00a0Premiere doesn’t like to be connected to many files in multiple network locations!\u00a0Improve\u00a0performance 1000% by working local. Project, Media Caches and Media. That\u2019s what sound mixers and designers do;\u00a0work local,\u00a0move final files over network.
\nCopy the media from the server to a USB-3 SSD (1TB Crucial<\/a>=$300)
\nIt takes about 1\u00a0hour to copy 1TB from the server, easy to\u00a0relink back to the server.
\nAs a bonus have an\u00a0SSD as your Media Cache drive. Then you can\u00a0move around and not have to re-cache the waveform files.
\nPay attention to the drive letters. On our systems the first external drive always\u00a0comes up as (F:) Because the internal media drive is (D:)\u00a0The DVD\u00a0is\u00a0(E:) The second external drive comes up as (H:). So plug them in, in the right order, you can not change the drive letters because you are not administrator.
\n<\/strong>2. Restart Pr\u00a0or reboot machine. Adobe has\u00a0memory leaking out it’s ears.<\/a> (On PC restart every hour!)
\n3. If you just imported a file, or added an effect and crashing starts, try to undo or do it different.
\n4.\u00a0Trash preferences, to fix all kinds\u00a0of buggy behavior,\u00a0like playback stopping after few seconds, or no audio.
\nQuit Premiere, then re-start in Dock\/Start Menu\u00a0and:
\nFor the Mac, press <\/strong>Shift+Option<\/strong>
\nFor the PC, press Shift+Alt
\n<\/strong>Verify reset by noticing\u00a0>recent projects are gone from the splash screen. You’ll have to redo Preferences<\/a>, Keyboard settings<\/a> and other things you customized.
\n5. Only use one creative cloud app at the same time<\/a>!
\nLots of conflicts, stalls and crashes happen because\u00a0the\u00a0apps fight over the same GPU, CPU, RAM, output\u00a0card, media, metadata, preview files etc.
\n6. Keep the project size under 50MB<\/strong>, >absolute max=70MB<\/strong>\u00a0(each warp stabilize adds 1\u00a0MB to the project size!)
\n<\/a>You may want to work in a separate project,\u00a0render the result out and bring it back into your main project,<\/a>\u00a0to speed up project loading and saving. Reduce size by removing: duplicate sequences, warp stabilizes<\/a>, tracked objects and direct links<\/a>,\u00a0then do a save-as.
\n7. Disconnect any third party hardware, Mouse, Wacom Tablet<\/a>, external HD, USB-stick etc.
\n-Remove plug-ins
\nTemporarily disable everything that runs in background that isn’t absolutely necessary. For example:
\n-virus checkers
\n-instant messengers
\n-skinning software
\n-power\/temperature monitoring software
\n-automatic updates
\n-drive monitors\/auto-defragmenters.
\n8. Check that you have more than 20% of free disk space remaining on every hard drive.
\n9.\u00a0Stuttery playback:
\n\"render-system\"<\/a><\/strong>-Turn on the Render System Display> Ctrl\/CMD+SHIFT+F11\"wrench\"<\/a>
\n-Turn on the green dropped frame indicator in the program wrench.
\n<\/strong>-Try turning off GPU acceleration. (in project settings)\u00a0If that helps, it’s probably a driver issue. If so, try updating drivers.
\n–Choppy\u00a0multi cam\u00a0playback?<\/a>>\u00a0Don’t be in multi cam mode!<\/strong> (you can still live switch using keyboard Ctrl\/CMD + 1-0 number keys)
\n<\/span><\/span><\/span>-Click the timeline wrench, and deselect\u00a0composite preview on trim<\/strong>
\n–<\/em>Lower the resolution to 1\/2 or 1\/4 (The playback and pause resolutions are stored per sequence)
\n<\/em>-Put Media Cache Database and Media Cache files on a different drive than startup or media drives, ideally on 2 SSDs\u00a0working as raid 0. (1000MB\/s)
\n-When\u00a0cutting native 4k or 5k<\/span><\/span>\u00a0for delivery at 1080> set your sequence to\u00a01080 and make your previews even smaller\u00a0like 720p.
\n-In Sequence Settings > Video Previews, change the codec to one that matches your footage
\n<\/a>-Make a new sequence and copy\/paste the troubled timeline.
\n-If you get stutters on rendered green sections >update the GPU driver and check all playback related preferences.
\n–Check speed and file\u00a0locations all HDs.<\/a>
\nWhen\u00a0green sections stutter you know for sure that your hard drives or connections to them are too slow.
\nOpen Activity Monitor or\u00a0task manager\u00a0>performance tab\u00a0>resource monitor. Monitor disk or network speed when the system is working well and compare\u00a0when it stutters.<\/span>
\n<\/span><\/span><\/span>
\n<\/strong>10. “Error Compiling Movie” when rendering or exporting.<\/strong>
\nIf your renders and exports are not 1\/4 real time or better, you are not using an optimized workflow!
\n<\/a>ALWAYS<\/strong>\u00a0export using the “Match Sequence Settings” checkbox and “Use Previews”
\nNEVER<\/strong> transcode from timeline to some other format like MP4.
\nFrom\u00a0Adobe’s “<\/a><\/span>Error compiling movie” checklist.
\n<\/a>With export\/render errors try:
\nA.<\/strong> Switch renderer to “Software Only” in Project settings.
\nB.<\/strong>\u00a0Set the\u00a0rendering optimization preference to ‘Memory.’<\/a>
\nC. <\/strong>Remove Mp3, or any other compressed audio from the timeline, transcode to WAV or AIF and replace.
\nD.<\/strong> Export WAV. 24bit, 48k audio only, then cut that into the sequence as the only audio track without any master track filters or effects applied.
\nE.<\/strong>\u00a0Export via AME and turn preview on. Watch the encoding until it fails. That is the spot on the timeline you need to fix. (corrupt FX or transition?)
\nF<\/strong>.\u00a0Try exporting sections to see if you can isolate the issue.
\nG.<\/strong> With large images, turn on: Preferences>General>Default scale to frame size, BEFORE importing.
\nThis will match the sequence size, improving performance. Limit image size to 5000 pix longest side, or\u00a0Preferences>Memory>Optimize rendering\u00a0for>Memory (restart Premiere)<\/span><\/span><\/span><\/span><\/p>\n

Specific errors:<\/strong>
\n“File not found.”<\/strong>\u00a0Make sure all input (source) files are linked. (See\u00a0Relinking offline media<\/a>\u00a0for more information.)
\n“Disk full”<\/strong>\u00a0Make room on the hard disk that you’re exporting to, or choose a hard disk with adequate space.
\n“Duplicate file.”<\/strong>\u00a0Make sure that the name and destination specified for the output file is unique.
\n“I\/O error.”<\/strong>\u00a0Make sure the hard disk has adequate room and you have permission to write to the specified output location.
\n“Unable to save file.”<\/strong> Destination file is in use by Premiere” or \u00a0“Destination file is in use by Adobe Media Encoder.”\u00a0An application is using the destination file. For example, the destination file can also be in use as an input file for another operation. If possible, close the program using the file.
\n“Invalid output drive.”<\/strong>\u00a0The specified hard disk can’t be written to or found. Choose another output location.
\n“Out of memory.”<\/strong> To maximize available memory, set the rendering optimization preference to ‘Memory.’<\/a>
\n“Unable to create or open output file.”<\/strong>\u00a0Check that the hard disk has adequate room and you have permission to write to the specified output location.\u00a0(See\u00a0Managing the media cache database<\/a>\u00a0for more information on freeing up hard disk space\u00a0by clearing out cached media files.)
\n“You do not have permission to create or delete the output file.”\u00a0<\/strong>Choose a destination folder that you have write access to, or change permissions on the destination folder so that Adobe Premiere Pro has write access.
\n“Codec compression error.”<\/strong> This codec may be unable to support the requested frame size, or there may be a hardware or memory problem.”
\nTry an unconstrained codec, such as None in an AVI container or ProRes 4444\u00a0in a QuickTime container to determine whether the frame size is the issue. (See File formats supported for export<\/a> for more information.)
\n“Unknown error.”\u00a0<\/strong>The specific cause of the error is unknown by Adobe Premiere Pro. The Solutions for unknown errors<\/a>\u00a0section can help you identify the problem.
\n11. Check Preferences>Memory=set to\u00a0Performance.
\nPremiere will use up to 16 cores\u00a0for rendering, but sequences requiring large amounts of memory \u2013 like sequences with large stills \u2013 will need too much memory and your system will potentially\u00a0starve on RAM. You can make a struggling system more stable by changing this setting to Memory. Remember to change back to Performance\u00a0when done.
\n<\/span>12. Delete Media Cache Files (by trashing the folder in Explorer\/Finder)
\n13. Clean the Media Cache Database by pressing the Clean button,\u00a0If that doesn’t work,\u00a0manually delete the cache files from the media cache folder while Premiere Pro is closed. Then relaunch Pr and allow them to be regenerated.
\n14. Trash all Preview files (by trashing the folder in Explorer\/Finder) and re-render.
\n15. Update Premiere Pro to the latest version
\n<\/a>16. Run the Adobe CC Cleaner Tool<\/a> to resolve installation issues.
\n17. Run\u00a0“NUCLEAR” Scripts from VideoRevealed.com<\/a>
\n<\/strong>18. Ensure Adobe preference files are set to read\/write<\/a>
\n19. Before opening project, Sign out from Creative Cloud<\/strong>, restart Premiere Pro, then sign in
\n20.\u00a0Repair permissions.
\n<\/a>21.\u00a0Clean your font cache<\/a>.
\n22. Create\u00a0a new user profile in OSX or WINDOWS with ADMIN privileges\u00a0and try to run from there.
\n23.Warp stabilizer in Premiere doesn’t work with interlaced footage<\/a> > use\u00a0AE instead.
\n24. With\u00a0audio playback problems, make sure the Dolby codecs are installed, by doing an export H264 choosing Dolby as the export format. If they are not loaded they will automatically get loaded.<\/p>\n

Premiere in networked environment.
\n<\/strong>These tips apply only to\u00a0Premiere standalone systems.\u00a0Premiere Pro was not designed with a multiple editor workflow in mind. It is meant for one editor, one machine. Building a network based editing system shared by other editors can be a major undertaking. One which requires knowledge of data throughput, data rates, and networking, in general. If any of these things are out of balance, you may experience all kinds of issues. Differentiating\u00a0Premiere troubleshooting form Network\/Drive performance issues is important. For that, I recommend taking Premiere Pro off the network and troubleshoot the system standalone first.
\n<\/a>Do\u00a0not<\/i>\u00a0use network drives for Media Cache Database.<\/a>
\nIf Premiere Pro is trying to use a disk that is no longer accessible, or a directory (folder) that is read-only, it causes strange problems.
\nAdobe’s\u00a0<\/a>FAQ Speeding up rendering & exporting<\/a>
\n<\/a>
\n<\/strong>1. If moving between MAC<>WIN check permissions & file path<\/a>.
\n2.\u00a0Import sequence into new project
\n3.\u00a0Match\u00a0the 7 Scratch Disk and Media Preferences<\/a> on both systems <\/span>BEFORE<\/strong> opening project.
\n<\/span>4.\u00a0Right-click on problematic\u00a0shots that don\u2019t play in the timeline and \u201cRestore Unrendered\u201d
\n5.\u00a0Premiere might be\u00a0unable to access the preview files. Test by\u00a0setting \u00a0a new location for preview files (in scratch disks)\u00a0and re-render.
\n6. \u00a0As a last resort, trash all preview files and re-render.<\/p>\n

Crashes\/errors all the time, system never works right:<\/strong>
\nBuild\/Configure\u00a0a<\/a>\u00a0balanced system.
\nWhen\u00a0you drive a Porsche 928 with it’s 800+ HP engine in rush hour. The engine is mostly idle. The Porsche is no faster than the Fiat 500 in the next lane, despite the enormous power of the engine.\u2028\u00a0\u2028The CPU and memory need to feed the video card with data, in order for the video card to do its magic. If the data feed is no more than a trickle, the video card is mostly idle, waiting for the next trickle of data.\u2028\u00a0\u2028A faster CPU and more memory help to increase the trickle to a steady stream of data. That’s just talking about GPU, CPU and RAM,\u00a0the disk setup has to also be\u00a0very fast on all volumes with transfer rates in excess of 800 MB\/s or 6\u00a0Gbps.\u00a0Multi core\u00a0CPU (at least 8), Recommended RAM (at least\u00a05\u00a0gigs\u00a0<\/span>per core)<\/span>, GPU (at least\u00a04GB ram or\u00a01000+cores), <\/a>
\nSSD vs HD as system drive gives\u00a0about a 3x speed bump\u00a0in overall performance.
\nUse at least\u00a010G Ethernet<\/a> to connect to storage.
\nIn my experience the differences between MAC & WIN have disappeared. It\u00a0all comes down to configuration, settings, hardware, codec and ultimately workflow. Adobe has gone on record via their Adobe Hardware Performance Whitepaper<\/a> to point out that the performance of their software comes down to specs, not operating system.\u00a0But for\u00a0some projects (like when PRORES is involved) you want to be on MAC. PRORES does not work at all on PC!<\/a>
\nGeneral Tips:<\/strong>
\nWork your way through each of your hardware devices and visit the manufacturer’s Web site to download and install the latest drivers.
\nVideo card and audio card drivers are the primary causes of problems, but drivers for other pieces of hardware often cause problems too.
\nSometimes it may be better to revert to a previous version of your video or audio driver if the latest version causes problems.
\nBe aware that\u00a0New NVIDIA drivers will no longer support older CUDA GPUs<\/a>
\n<\/a>If you have AMD<\/strong> GPUs\u00a0or you are on a\u00a0MAC<\/strong>,\u00a0make sure CUDA<\/a> is not<\/strong> installed. On a MAC<\/strong>\u00a0use OpenCL as the renderer.
\nFor certain applications, such as Blackmagic DaVinci Resolve, CUDA drivers are automatically installed, even if you have AMD GPUs. CUDA must be installed in order for that application to launch. If other applications have issues, you may need to install a different version of the CUDA drivers. Currently, if you need to have CUDA software installed on AMD hardware, you can install the 5.5.28 CUDA drivers. In the future, consult support<\/a> for the manufacturer for the correct CUDA driver version.\u00a0If CUDA drivers do not need to be installed, please do not install them. It\u2019s best to not have CUDA drivers on non-CUDA hardware unless you absolutely need to, as in the case with Resolve.\u00a0Stay away from any Quadro card when purchasing GPUs for Adobe software. Quadros are crazily overpriced and only offer minor performance gains when used with software designed specifically for Quadro drivers of which Adobe software isn’t anyway.
\nNVIDIA Card with Yosemite and Premiere causing graphics failure MAC ONLY<\/a>
\n<\/a>
\n<\/strong>Excellent YouTube video about trouble shooting.<\/a>
\n<\/a>ADOBE\u2019s\u00a0Troubleshoot system errors and freezes (Windows)
\n<\/a>ADOBE\u2019s\u00a0Troubleshoot system errors and freezes (Mac OS)<\/a>
\n<\/a>Troubleshooting QuickTime errors with After Effects.
\n<\/a>Adobe’s “<\/a>Error compiling movie” checklist.<\/a>
\n
\n<\/strong><\/a>
\n<\/strong>
\n<\/a><\/div>\n
<\/div>\n","protected":false},"excerpt":{"rendered":"

Before troubleshooting\u00a0anything, make sure your WIN or MAC is optimized\u00a0for video editing by following the Resolve 12\u00a0Configuration Guide.\u00a0 Premiere crashes before opening. Delete the the file: “Effect Presets and Custom Items.prfpset”, which is stored here: WIN >C:\\Users\\<username>\\Documents\\Adobe\\Premiere Pro\\9.0\\Profile-<username> MAC>\/Users\/<username>\/Documents\/Adobe\/Premiere Pro\/9.0\/Profile-<username> Video file\u00a0errors: “The selected file does not contain video media used by clip references in … Read morePr Troubleshooting CC 2015.4 Summer 2016<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,8],"tags":[],"class_list":["post-524","post","type-post","status-publish","format-standard","hentry","category-technical-premiere-info","category-workflow"],"_links":{"self":[{"href":"https:\/\/editspecialists.com\/pr\/index.php\/wp-json\/wp\/v2\/posts\/524","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/editspecialists.com\/pr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/editspecialists.com\/pr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/editspecialists.com\/pr\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/editspecialists.com\/pr\/index.php\/wp-json\/wp\/v2\/comments?post=524"}],"version-history":[{"count":3,"href":"https:\/\/editspecialists.com\/pr\/index.php\/wp-json\/wp\/v2\/posts\/524\/revisions"}],"predecessor-version":[{"id":1497,"href":"https:\/\/editspecialists.com\/pr\/index.php\/wp-json\/wp\/v2\/posts\/524\/revisions\/1497"}],"wp:attachment":[{"href":"https:\/\/editspecialists.com\/pr\/index.php\/wp-json\/wp\/v2\/media?parent=524"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/editspecialists.com\/pr\/index.php\/wp-json\/wp\/v2\/categories?post=524"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/editspecialists.com\/pr\/index.php\/wp-json\/wp\/v2\/tags?post=524"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}