Premiere Pro CC and Media Cache

Hello!
I've read the documentation on Media Cache (http://help.adobe.com/en_US/premierepro/cs/using/WSF08BCDDB-FCD7-40a2-8290-8872EE725E6B.ht ml#WSa41b87baf39dd9b0-4a7aee25125bce32690-8000) but I didn't understandt what are exactly the formats/containers that Premiere Pro creates cache for?
Also, am I remembering wrong, but was in Premiere Pro CS 5.5 and CS 6 the cache for the project was kept in the same folder as the project?
Does Premiere clean the Media Cache regularly or I have to remember to do it from time to time?

I don't think that much has changed regarding the treatment of cache files from CS5 to CS6 to CC.
Here's how I manage the cache files:
1) Set Premiere to store media cache and media cache database in a drive folder separate from your project files (use menu: Edit / Preferences / Media and then browse to where you want them - I use "X:\premiere_cache"). This way, when you back up projects you are not backing all of this stuff up too.
2) They do not clean up for themselves - go to the same panel mentioned in #1 and click the "clean" button to remove all of the files. When Premiere Pro is closed, you can manually delete all of the folders created by Premiere and you will not destroy anything that is recoverable.
The purpose of cache files is to prepare some files additional your projects and media for performance enhancing reasons.
Regards,
Jim

Similar Messages

  • Premiere Pro CS6 and Media Encoder CS6 Color shift on export

    Hello,
    I am working on an early 2008 Mac Pro with 2 X 3.2 GHz Quad Core Intel Xeon Processors 32 GB of RAM a NVIDIA GeForce 8800 GT 512 MB Graphics Card and I am running OS X 10.8.2.
    I have the updated Version of Adobe Premiere Pro CS6 and Media Encoder CS6 through the awesome Subscription program that Adobe has started.
    My footage is shot with the Canon 1D Mark IV shot 1920X1080 at 24 FPS
    I am importing the camera files and then exporting them after I cut them up in to Quicktime Pro Res 422 HQ files
    With the technical explination out of the way here is my problem. I have color right from the camera files that I like. and with out doing any thing to change the color I export the footage and get a dramatic color shift. The exported file looks desaturated and slightly green.
    I have tried using Media Encoder CS6 to export my footage and that has the same result.
    I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
    I have attached three screen shots that show the color shift exactly. Now what I need is a solution. What I am not seeing is color settings for Premiere. I am totally open to any suggestions on what I might be doing incorrectly.
    Ben

    Benjamin Peterson wrote:
    I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
    I've been doing this for a few years now, and have come to some conclusions. Basically, the difference between still photography and video is like the difference between playing the trumpet and the sax. What you bring to the sax from playing trumpet is your ability to read music, what you know about composition, blending while playint with others, ect. But playing trumpet tells you nothing about how to physically play a sax. So it is with still photography and video.
    For starters, your carefully calibrated computer monitor is just that, a computer monitor. It doesn't display the correct working space for video. What you need for WYSIWYG in video is a monitor that can show you the Rec.709 working space. Rec.709 has a different gamut, a different gamma, probably a different white point (D65), different phosphor colors, etc., etc., etc. Enought differences that it's difficult to make a computer monitor that can successfully display Rec.709. Yet there are a couple of computer monitors that can do this (a few Eizos, one HP). The vast majority of people doing serious color correction work in video use a production monitor for just this reason.
    But a production monitor isn't enough. You also have to make sure that the signals you're sending the production monitor are correct. There's a sub-industry making signal converters for signals from NLE video cards (usually RGB based) -> signals for production monitors (usually YUV based).
    That said, it is certainly possible to get a very good match between your NLE suite and a DVD / BD as displayed on an HDTV. But it's not as simple or easy as a calibrtated computer monitor for still photography use.
    This is probably part of your problem. But Quicktime is probably the root of it. Quicktime is, well, I guess the polite way of saying it is that Quicktime is problematic. It gives all kinds of problems. Most people have abandoned it. You should too.

  • Problems exporting mpeg 2 videos using Premiere Pro CS6 and Media Encoder

    Using a Mac, I'm trying to exporting an mpeg 2 video from Premiere Pro CS6 using the queue process that opens the Media Encoder but when the process begins, it freezes and doesn't end.

    Using a Mac, I'm trying to exporting an mpeg 2 video from Premiere Pro CS6 using the queue process that opens the Media Encoder but when the process begins, it freezes and doesn't end.

  • Premiere Pro CC and Media Encoder won't start

    Hey everyone,
    I have a huge problem: My Adobe Premiere CC won't start. I've tried all the solutions I've found in the internet, but nothing seems to work for me
    I am using OS X 10.9.3.
    Here is a part of my report:
    Process:         Adobe Premiere Pro CC 2014 [1153]
    Path:            /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Identifier:      com.adobe.AdobePremierePro
    Version:         8.1.0 (8.1.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [235]
    Responsible:     Adobe Premiere Pro CC 2014 [1153]
    User ID:         501
    Date/Time:       2014-12-10 23:51:37.341 +0100
    OS Version:      Mac OS X 10.9.3 (13D65)
    Report Version:  11
    Anonymous UUID:  5BE9B722-1F73-691F-5EEF-9775088356E8
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000001650
    VM Regions Near 0x1650:
    -->
        __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_platform.dylib       0x00007fff9195abe6 OSAtomicAdd32Barrier$VARIANT$mp + 2
    1   libclh.dylib                   0x00007fff9076859f 0x7fff90765000 + 13727
    2   libclh.dylib                   0x00007fff90875305 clhCtxCreate + 101
    3   libGPUSupportMercury.dylib     0x00007fff94e2daab gldCreateQueue + 651
    4   com.apple.opencl               0x00007fff8f68e8ad 0x7fff8f688000 + 26797
    5   com.apple.opencl               0x00007fff8f68d32b 0x7fff8f688000 + 21291
    6   com.apple.opencl               0x00007fff8f68d211 0x7fff8f688000 + 21009
    7   com.apple.opencl               0x00007fff8f6a9fbe clCreateCommandQueue + 150
    8   com.adobe.GPUFoundation.framework 0x0000000109afbeb1 GF::CreateOpenCLCommandQueue(_cl_device_id*, _cl_context*, bool) + 65
    9   com.adobe.GPUFoundation.framework 0x0000000109ad521f GF::Device::InitializeContextImpl() + 2479
    10  com.adobe.GPUFoundation.framework 0x0000000109ad76ae GF::Device::InitializeContext(bool, void*, void*) + 622
    11  com.adobe.GPUFoundation.framework 0x0000000109af141a GF::Initialize(bool, bool, bool, void*, void*) + 2154
    12  com.adobe.DisplaySurface.framework 0x0000000111bb7f84 DS::Initialize() + 228
    13  com.adobe.Mezzanine.framework 0x000000010636c3cd MZ::(anonymous namespace)::FullInitializer::FullInitializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 6173
    14  com.adobe.Mezzanine.framework 0x0000000106369874 MZ::Initializer::Initializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 84
    15  com.adobe.Frontend.framework   0x00000001000abe97 FE::Initializer::PrivateImpl::PrivateImpl(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 1479
    16  com.adobe.Frontend.framework   0x00000001000aadc8 FE::Initializer::Initializer(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 40
    17  com.adobe.Frontend.framework   0x00000001000cdc32 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 226
    18  com.adobe.Frontend.framework   0x00000001000d4ea5 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
    19  com.adobe.AdobePremierePro     0x00000001000018ac main + 508
    20  com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

    AND Media Encoder won't start as well!!
    Process:         Adobe Media Encoder CC 2014 [1284]
    Path:            /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
    Identifier:      com.adobe.ame.application
    Version:         8.1.0.122 (8.1.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [235]
    Responsible:     Adobe Media Encoder CC 2014 [1284]
    User ID:         501
    Date/Time:       2014-12-10 23:59:55.226 +0100
    OS Version:      Mac OS X 10.9.3 (13D65)
    Report Version:  11
    Anonymous UUID:  5BE9B722-1F73-691F-5EEF-9775088356E8
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000001650
    VM Regions Near 0x1650:
    -->
        __TEXT                 0000000100000000-0000000100088000 [  544K] r-x/rwx SM=COW  /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib         0x00007fff93a9a292 __kill + 10
    1   com.adobe.dvacore.framework   0x00000001003a28ea (anonymous namespace)::SignalHandler(int, __siginfo*, void*) + 410
    2   libsystem_platform.dylib       0x00007fff9195b5aa _sigtramp + 26
    3   libsystem_platform.dylib       0x00007fff9195abe6 OSAtomicAdd32Barrier$VARIANT$mp + 2
    4   libclh.dylib                   0x00007fff9076859f 0x7fff90765000 + 13727
    5   libclh.dylib                   0x00007fff90875305 clhCtxCreate + 101
    6   libGPUSupportMercury.dylib     0x00007fff94e2daab gldCreateQueue + 651
    7   com.apple.opencl               0x00007fff8f68e8ad 0x7fff8f688000 + 26797
    8   com.apple.opencl               0x00007fff8f68d32b 0x7fff8f688000 + 21291
    9   com.apple.opencl               0x00007fff8f68d211 0x7fff8f688000 + 21009
    10  com.apple.opencl               0x00007fff8f6a9fbe clCreateCommandQueue + 150
    11  com.adobe.GPUFoundation.framework 0x0000000109ef7b01 GF::CreateOpenCLCommandQueue(_cl_device_id*, _cl_context*, bool) + 65
    12  com.adobe.GPUFoundation.framework 0x0000000109ed0e6f GF::Device::InitializeContextImpl() + 2479
    13  com.adobe.GPUFoundation.framework 0x0000000109ed32fe GF::Device::InitializeContext(bool, void*, void*) + 622
    14  com.adobe.GPUFoundation.framework 0x0000000109eed06a GF::Initialize(bool, bool, bool, void*, void*) + 2154
    15  com.adobe.DisplaySurface.framework 0x0000000107845f74 DS::Initialize() + 228
    16  com.adobe.ame.application     0x00000001000376e7 AME::app::MCInitializer::MCInitializer() + 12039
    17  com.adobe.ame.application     0x000000010002323a AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 250
    18  com.adobe.ame.application     0x000000010000d2ba AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 1802
    19  com.adobe.exo.framework       0x00000001057d2bd5 exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1141
    20  com.adobe.ame.application     0x00000001000167e6 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 3270
    21  com.adobe.ame.application     0x0000000100047828 main + 440
    22  com.adobe.ame.application     0x00000001000032f4 start + 52

  • Any issues with Premiere Pro CC and Avid Media Composer on same system?

    Hi all:
    Searched around for this but couldn't find similar question.
    Am a long time Premiere Pro user, but have something coming up where I'm having to use Avid MC to collaborate with a staff editor for the duration of the job.  Am wondering if I should expect any conflicts or issues to installing both Premiere Pro CC and Media Composer on the same system?  Any insight would be most welcome.
    Running Adobe CC on a Windows 7 HP Z820, Dual Xeon Processors, 128Gb RAM.
    Thanks!

    hi Jim,
    well it turns out that Premiere update 7.2.2. put my computer into disarray, and caused my multi-camera monitor to lag (about 6 seconds) behind my program monitor .. so my my multi-cam monitor (with my 2 or 3 camera feeds) would  be playing footage that is 6 seconds or so BEHIND what was playing on the program monitor.
    that's the gist of it..
    anyway the fine folks at Adobe, talked me through the process of going back to premiere 7.2.0 and that fixed the issue.
    i hope future updates resolve this issue so that i can get back up to the minute on my software
    thanks
    jahZ

  • We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason. Anyone else got that too with Premiere Pro CC and the new Media encoder? Thanks! bedrijfsfilm Companyfilms

    We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason. Anyone else got that too with Premiere Pro CC and the new Media encoder?

    We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason
    Anyone else got that too with Premiere Pro CC and the new Media encoder?
    Lack of detailed info makes your question impossible for anyone to answer you!
    eg. ...."Doctor it hurts...anyone else got something that hurts?" 

  • XDCAM HD workflow with Adobe Premiere Pro CC and Macbook Pro

    Hi folks,
    I have an assignment for a TV production to secure and convert the data (mxf files XDCAM HD 422 1080i 50 / 50 Mbit/sec with 8 audio channels) from Sony XDCAM camcorders (PDW-700) for postproduction.
    The producer wants me to convert the mxf files during production to Apple ProRes 422 (HQ) for faster and smooth editing during postproduction.
    I'm not sure about the final output yet, but I guess it will be either 720p50 or 1080i 25, since the production will be broadcast and as far as I know this is the standard for HD on German television. It is also not clear which NLE will be used for editing (usually one of the producers edits their projects with FCP, but this time they've got their hands full and are still looking for someone to outsource postproduction.
    Unfortunately, my Macbook is getting fixed as we speak, so I can't try things out.
    Since this is the first time I'm doing this workflow, could someone please check if I got everything right?
    1. Can someone please confirm that I can actually convert the mxf files using AME CC to Apple ProRes 422?
    Or do I need to install any other tools/converters for this task? Does MPEG streamclip do the job? Any other freeware?
    2. When converting to Apple ProRes422, the producer suggested to deinterlace the footage (1080i 50) to 25p, if 720p or 1080p I have to find out tomorrow since our conversation got interrupted this afternoon.
    In my opinion this doesn't make sense, though. First, if output to 1080i 25 it has to stay interlaced anyway. Second, in case the output will be 720p 50 I would edit the footage either natively or in Apple ProRes 422, but leave deinterlacing until the very end when outputting to the final format. This way I could use an advanced deinterlacer, e.g. the one from Magic Bullet Suite, rather than just checking some deinterlace box in the export settings for Apple ProRes 422.
    The reason the producer suggested to deinterlace right away when using  an intermediate like ProRes was that she and the client got irritated by the jagged lines from the interlaced footage when editing the last project with the same requirements on a progressive display.
    3. What would be the best solution to tackle this issue (jagged lines) during editing?
    As I said my Mac is getting fixed, so I have no way of trying things out,and I usually edit DSLR footage which is progressive anyway.
    But if I remember correctly I can switch my monitor between 1080p and 1080i. This should do the trick, shouldn't it?
    4. Can I keep all of the 8 audio tracks when converting to ProRes using AME CC ?
    5. Is ProRes422 (HQ) really necessary, or is the regular quality sufficient for this kind of job?
    6. Let's assume the whole project would be edited within Adobe Premiere Pro CC and  system specs as stated below:
    Since Adobe Premiere Pro CC has native support for  XDCAM HD is there any advantage of using an intermediate like ProRes at all?
    How smooth is native editing with XDCAM HD in Premiere Pro CC? I don't think there will be more than 3-4 video tracks in use...
    Thanks for your help!
    working with
    Adobe Premiere Pro CC and Adobe Media Encoder CC
    Apple MacBook Pro
    Intel Core  i7 Quad Core Prozessor
    2.3 GHz and 6MB L3 Cache
    16 GB RAM 1600MHz DDR3,
    256 GB SSD
    Intel HD Graphics 4000 512MB + nVidia GeForce GT 650M with 1 GB GDDR5 RAM

    Thanks Jim! I knew there must be a reason xdcam is widely uses for eng aquistion :) I think they used FCP 6 or 7 on their last project... So what about monitoring interlaced footage on a progressive screen? Any advice on that? Is there a converter built in to APP CC that deinterlaces in realtime when monitoring interlaced sources on a progressive screen? And would you agree that deinterlacing source material is best left right before outputting?

  • Premier Pro CC and Media Encoder crashing on long file export.

    Please forgive the length of this inquiry. But it is complicated and has a lot of variables.
    I have an hour long mixed format timeline both Red 3K footage and Black Magic ProRes 1080P footage that I want to make a DVD from and it takes forever and crashes half way through. I have tried doing it every way possible and the only way I was able to get even a partial export was using the "MPEG 2 DVD" export option in Premier CC. It goes fast at first telling me it will take about 2 hours but even though it starts quickly doing about 15 fps it slows down to less than 1 fps and finally just stops and crashes my Cuda Core enabled Macbook Pro Laptop.
    I really don't know who to ask about this since there are so many different variables. I never had a problem like this on my MBP with PP6 on a 4K timeline exporting to DVD or Blue Ray or to H-264 or Even Prores. But I wasn't mixing formats either. But on this project the first 20-30 minutes of footage goes through fine in a couple of hours but something seems to be bogging down the system on longer projects. My work around was to break the project up into multiple exports and combining them on the DVD timeline but I can't do this on every project. I thought maybe it was a corrupted clip somewhere in the timeline but when I broke the timeline up into several parts I had no problems.
    I did notice a dramatic variance in the time it took to export footage based on the sequence settings. A one minute timeline comprised Red 3K footage and ProRes 1080P footage Here are some sample export results:
    From a Red raw 3K timeline 2880x1620  with 1080P Prores footage upscaled 150%)
    to .m2v Mpeg 2 720x480 format    1:48 Minutes ***
    to .mov  Prores 422HQ  1080P                         22 Minutes
    to .mov H.264  1080P                    22 Minutes
    to .m2v Mpeg 2 1080P                                                22 Minutes
    From a 1080P timeline Prores footage at 100%  (Red footage downscaled to 67%)
    to .m2v Mpeg 2 720x480 format                         13 Minutes
    to .mov  Prores 422HQ 1080P                             13 Minutes
    to .mov H.264  1080P                                                             14 Minutes
    to .m2v Mpeg 2 1080P                                                            14 Minutes
    Since I am going to DVD,  I chose the fastest option  Red to m2v Mpeg 2 720x480 format which only took 1:48 per minute. Why? I have no idea. Maybe someone here knows the answer. But again these numbers are for a ONE MINUTE clip when I tried to convert the whole hour timeline to  the 720x480.m2v DVD File the Red timeline froze my computer after several hours even though I had set sleep mode to “Never” and turned the display off manually and I had to convert it in multiple chunks. In 20-30 minute chunks it did go fast about 1:48 per minute like the test indicated. But I would like to be able to convert the whole hour and not to have to try to stitch the clips together in my DVD authoring program.
    I don’t want to have to avoid using multiple formats on the same timeline or waste time transcoding everything to the same format.
    Can anyone give me any suggestions as to why the computer is crashing or bogging down in long exports and what timeline settings I should be using?
    I have plenty of room on my Scratch Disk and 8 Gig of RAM and according to my Activity Monitor during the export process  have about 800 Meg of System Memory during export but the CPU Usage is 98% and in my Activity Monitor I see under “Process Name” ImporterRedServer flashing up at the top of the list about every second during export.
    Why .720x480 mpeg DVD setting is so much faster than all the other export codecs?
    And if there are any other settings I can use to get higher speed exports in HD? 14x1 seems a little slow especially since every time it crashes I have to start over.

    Hi,
    Since a long time I did not encounter the crash of Media encoder with
    long file export.
    But I take care of a lot of details before the export :
    - clean up Media cache and Media Cache Files within PP CS6 and/or CC,
    - delete all render files with Preview Files,
    - rendering of sequences until the rendering is completed,
    - PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
    I guessed to leave Adobe but this company remains the last with a
    serious authoring software (Encore CS 6).
    I tested :
    - Avid Media Composer, Final Cut Pro X, both are very good software but
    no really authoring software for these video editing softs.
    Th only way is to "flood" Adobe with "bug reports" and "wish forms"
    which are not very easy to use.
    And also to call the Adobe support day by day until they send they
    escalate the bug.
    Le 16/05/2014 16:51, alainmaiki a écrit :
    >
          Premier Pro CC and Media Encoder crashing on long file export.
    created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
    /Premiere Pro/ - View the full discussion
    <https://forums.adobe.com/message/6384665#6384665>

  • Optimal Hard Drive Configuration for Premiere Pro CS5 and Pro Tools

    I am in the process of upgrading a workstation that is used primarily for multi-track audio recording in Pro Tools to use the following Adobe CS5 products for production of promotional videos in HDV (and AVCHD for the web) as well as printed marketing materials for bands and musicians: Premiere Pro, Encore, Photoshop, Illustrator and Soundbooth.
    Since Premiere Pro is probably the most demanding application of the group, I have been studying the suggested hardware configurations on this forum with great interest, particularly HARM's suggestions (including his Generic Guideline for Disk Setup) to determine which hard drives to purchase and the optimal manner in which to configure them.
    I am upgrading an HP Z800 with dual quad core 2.44 GhZ processors with hyperthreading (16 virtual cores), 12 GB of memory and an overclocked GeForce GTX 470.  Without setting up a RAID configuration (which I cannot afford at the moment), I would like to use the 4 available HDD bays in the Z800 in the optimal manner for Premier Pro, using currently available drives.  I am currently considering purchasing a 300GB VelociRaptor to use as my C drive because of the extended load times and demands placed on the drive by ProTools and the associated Waves plug-ins.
    I would appreciate suggestions to improve my following plan:  C (300GB  WD VelociRaptor) for OS and Programs; D (1 TB WD Black Caviar) for Media and Projects; E (1 250 GB WD Black Caviar) for Pagefile (approx. 18 GB) and Media Cache; and E (2 TB WD Black Caviar) for Previews, Exports and Pro Tools audio files.
    I have great respect for the knowledge of the members of this forum and eagerly await your suggestions.
    /Bill

    I very much appreciate the responses to my email because I know that all of your time is valuable and that you have chosen to use some of that valuable time to help an unknown individual.  This forum is remarkable because of the wealth of knowledge available and the willingness of so many to assist others.
    I now wish to narrow my questions to save you time and so that I can get specific advice.  I may not have not been clear that I have already upgraded to the HP Z800 with dual quad core processors and overclocked GTX 470, primarily for the improved performance it will provide in ProTools.  My question now is how to optimize its performance for Premiere Pro CS5.  Based upon my research, I am considering the following two upgrades, but I am open to other suggestions if they would provide better results at a similar cost
    1. I am considering purchasing a 600GB WD VelociRaptor ( WD6000HLXH) for my C drive on which I would place OS (Windows 7, 64 Bit) and programs in an effort to reduce loading times of large programs.  I have two questions: (1) Are members of the forum seeing a significant improvment in program loading times with the VelociRaptor because I am still not convinced that the price performance of SSD's justifies their use; and (2) There are so many models of VelociRaptors now that I want to be certain that I am purchasing the best version for my needs.  In addition to the usual 10000 RPM speed, this model has 32MB Cache and a 3.5" form factor as well as a SATA 6.0GB/s interface (which I doubt my motherboard can take advantage of but it might extend the useful life of the drive with future configurations).
    2. I currently have available for installation in the Z800 the following drives:  (1) WD 2TB Black Caviar; (1) WD 1TB Black Caviar; (2) Hitachi 1TB.  I believe that the Z800 can accept up to 5 SATA hard drives which I will have if I purchase the Velociraptor.  Although I am reasonably knowledeable when it comes to hardware, I have never set up a RAID configuration.  Therefore, it would be helpful if someone could recommend one of the various RAID configurations and brieflyexplain why it would seem to be best for my needs.  I can then focus my research on understanding that one configuration.
    I was planning to follow Scott's suggestion for my current 3 drives:  OS and programs on C (WD 600 GBVelociRaptor), media and projects on D (WD 1TB Black Caviar), export files and Pro Tools files (all live musician tracks, no samples) on E (WD 2TB Black Caviar).  However, I have been reading about the benefits of a RAID configuration so I am interested in further suggestions now that I have clarified my questions.
    Thank you all for your help.
    Bill

  • Premiere Pro CS5.  Media Encoder .dll interace message.

    Out of the blue, when I am working in Premiere Pro CS5 and want to export media, I get an error message about "this software could not find the required software interface .dll.  Reinstall the software and try again..."
    This just started several days ago.  I have changed nothing.  I did do as asked and reloaded the Adobe Premiere program and that worked for about a day.  And now it is back.  Also, my Premiere CS5 is starting to crash fairly often where as before it never did.  I haven't changed anything on the computer.  No new software added.  No windows 7 updates of any kind.
    Any ideas on what to do.

    I experienced this at one point.  Searching the WEB I saw suggestions that there was a problem with a recent version of Quicktime.  (I have no idea why the quicktime player would have an impact.)  However, reverting to an earlier version of Quicktime fixed the problem.  Search this board using quicktime as a search phase.  The quicktime web site allows you to download the earlier versions.  I'm not at my editing machine, but I believe that I am at version 7.5.2.

  • Premiere Pro CC and the New Mac Pro (2014)

    I'm expecting delivery soon of a new Mac Pro, nicely loaded, which I purchased mainly because of all the work I do with video. Yet, I read in a review that Adobe Premiere Pro isn't optimized to take advantage of the new Mac Pro, won't run faster, and I'm better off using Apple's Final Cut.
    1. Is this true?; and
    2. If so, will Premiere Pro be updated any time soon to run best on a 2014 Mac Pro?
    My new Mac Pro will have the following configuration:
    3.5GHz 6-core with 12MB of L3 cache
    32GB (4x8GB) of 1866MHz DDR3 ECC
    1TB PCIe-based flash storage
    Dual AMD FirePro D700 GPUs with 6GB of GDDR5 VRAM each

    My main problem is that when i export using gpu open gl it crashes hard boot the mac pro. A 3 min timeline with 4k footage n a bunch of color grading.  I get lucky if the timeline is shorter. But i think it is a gpu issue n my mac must be fixed. Currently under apple tech support. N my case is unique. No one has had the same issue and that makes it harder for me to figure the isse and to apple figure the issue.
    If i export using software only mercury then the export goes smoothe no mattrr how long. But that defeata the point of owning a mac pro with 2 GPUs
    Enviado desde mi iPhone
    El 29/03/2014, a las 01:51 p.m., BanksMeador <[email protected]> escribió:
    Re: Premiere Pro CC and the New Mac Pro (2014)
    created by BanksMeador in Premiere Pro - View the full discussion
    I have had my 12 core 2014 Mac Pro for a couple of weeks now, and I'm not very impressed with Premiere CC performance with 4K R3D on a 1920 x 1080 timeline.
    I understand that there may be an update soon that will take adantage of the CPU's and GPU's when it comes to the complex task of de-bayering the R3D footage, but it's just not there now.
    I get similar playback performance to what I experienced on my 09 Mac Pro tower.
    Any insights on getting better playback performance in this scenario would be greatly appreciated.
    Thanks!
    Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/6253414#6253414
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/6253414#6253414
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/6253414#6253414. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Premiere Pro at Adobe Community
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

  • Premiere Pro CC and the new Mac Pro - are all upgrades necessary?

    Monday I'm ordering the new Mac Pro because my Mid 2012 Mac Pro tower is simply too slow and crashy no matter how much money I sink into it. Thing is, every little upgrade I add onto this new Mac Pro is very expensive, so I want to make sure I don't add anything that won't make a difference in edit performance.
    My ultimate goal is to be able to work with 4k, and even 5k footage in 2014. More and more clients are giving me Red media, and my system right now can't handle it (I have to render proxy files for everything).
    Attached are my hardware upgrade options for my processor and graphics card. These options can only be offered when I order the computer. Neither the processor or the GFX card can be changed by me later. Note that these options alone almost double the computers's price (3600). As of now I assume that getting the fastest everything is the way to go, but is there any reason I should not go this high?
    jesse

    We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason
    Anyone else got that too with Premiere Pro CC and the new Media encoder?
    Lack of detailed info makes your question impossible for anyone to answer you!
    eg. ...."Doctor it hurts...anyone else got something that hurts?" 

  • I cannot import .mov files to Premiere Pro or Adobe Media Encoder.

    I cannot import .mov files to Premiere Pro or Adobe Media Encoder.
    How do I around this problem?

    We need to know a lot more if we're going to help you.
    What happens when you try? Do you get an error message? If so, exactly what does it say?
    What version of Premiere Pro? Have you installed the recent updates? What operating system?
    Does this happen for all .mov files or just some? Has this ever worked before? What version of QuickTime do you have installed?
    Here's a page written for After Effects, but the information is relevant to Premiere Pro and AME, too:
    http://blogs.adobe.com/toddkopriva/2011/02/troubleshooting-quicktime-errors-with-after-eff ects.html

  • Premiere Pro CC and Encore CC are ignoring the Target and Maximum Bitrates

    Adobe Premiere Pro CC and Adobe Encore CC are ignoring the Target and Maximum Bitrates settings in the export window, The files that are exported are much smaller than what the estimated size of the file should be shown in the export window and are highly compressed. What can cause such an issue?
    I haven't drastically changed my presets.

    There is a very definite bug in the Adobe Media Encoder engine which is used in both Premiere Pro and After Effects.  H.264 exports seem to randomly choose their own export quality, using 2-pass VBR.  I have found with some DV-size exports on 'match quality' in Premiere Pro, that setting the export above 10Mbps pushes the quality down to well under 1Mbps, e.g. 167kbps.  I've found that using the default min 6, max 8 seems to work the best.  I've worked with this on two different machines and fiddled with it extensively and this is definitely NOT an intended 'feature'.  In fact, I have found that exporting from the same sequence, if I select the first 20 seconds, I get very low bitrate, but if I select 30 seconds or more, I get the higher bitrate that I want!  And I tend to get different results when I enable and disable 'use previews'.
    I am also having some trouble with missing frames when exporting progressive animation files to h.264 mp4 files that never occured before.  Not sure yet if this is related to the same issue, but interestingly, I don't get the 'blinking' missing frames issue when the bitrate drops itself down to a very low 150-200kbps.  When I do get the export rate up higher, then the missing frames on just this animation clip return.
    So, after my tests, here is a screen capture of sample export settings (yes, 15Mbps is a very high bitrate for DV, but the same happens at 6Mbps or 7 or whatever I try in some cases):
    This gave me a 1.5MB file with a reported 167kbps bitrate and a quality level as shown below:
    A currently working 'workaround' is to use 1-pass VBR which gives me a crisp, clean 5.5MB file.  Would a few others please try to reproduce this so we can get it escalated to bug status?  I'll report it if you can confirm it there, this is happening on two computers here.
    Thanks,
    Sean

  • Hello, i use premiere pro cc and i would like to uplaod my sequence in speedgrade with direct link but it's not available. I can see the option but it's not clickable, somebody knows why ?

    Hello, i use premiere pro cc and i would like to upload my sequence in speedgrade with direct link but it's not available. I can see the option but it's not clickable, somebody knows why ?

    Oh i'm not sure they are on same, i downloaded speedgrade this morning and i didn't upgraded premiere so it's maybe this ! thanks i will try it and let you know

Maybe you are looking for