Premiere CS5 poor ram usage...

I'm running premiere pro cs5 on windows 7, with the following specs:
i7 860 quad core
8 Gigs of Ram
NVidia XFX 7600GS
1TB Samsung F3 Drives - Raid 1
500 gig scratch drive
I'm trying to export some HDV files, 24p, Cineform etc, but I'm receiving very poor performance.  When exporting my CPU usage is only 25%-30%, which I think is rather pathetic.  I've assigned 6gig of ram to premiere, why is it using so little memory? I've found rendering footage in Virtual Dub uses about 80% of my CPU, which is much more to my satisfaction.  Is there a way to adjust premiere to work more efficiently?
Thanks...

Even though you reserved 6Gigs of Ram for Premiere, The OS itself will probably use/reserve more than the 2 Gigs you've left it (AFAIK). After the OS and the other programs you might have running at the same time take/reserve what they need, I bet there's a lot less than those 6Gigs Premiere can use.
About the CPU, make sure you have Priority for PPro and the Encoder set to "Normal", or better yet, High or even Realtime. Should be Normal by default but doesn't hurt to double check (Task Manager > Processes ). I know some folks are saying this doesn't make a difference but I've found it does on my system, albeit not a lot.
Thoughts?

Similar Messages

  • Problems updating projects to new versions of Premiere (CS5 to CC and CC to CC 2014) Memory consumption during re-index and Offline MPEG Clips in CC 2014

    I have 24GB of RAM in my 64 bit Windows 7 system running on RAID 5 with an i7 CPU.
    A while ago I updated from Premiere CS5 to CC and then from Premiere CC to CC 2014. I updated all my then current projects to the new version as well.
    Most of the projects contained 1080i 25fps (1080x1440 anamorphic) MPEG clips originally imported (captured from HDV tape) from a Sony HDV camera using Premiere CS5 or CC.
    Memory consumption during re-indexing.
    When updating projects I experienced frequent crashes going from CS5 to CC and later going from CC to CC 2014. Updating projects caused all clips in the project to be re-indexed. The crashes were due to the re-indexing process causing excessive RAM consumption and I had to re-open each project several times before the re-index would eventually complete successfully. This is despite using the setting to limit the RAM consumed by Premiere to much less than the 24GB RAM in my system.
    I checked that clips played; there were no errors generated; no clips showed as Offline.
    Some Clips now Offline:Importer  CC 2014
    Now, after some months editing one project I found some of the MPEG clips have been flagged as "Offline: Importer" and will not relink. The error reported is "An error occurred decompressing video or audio".
    The same clips play perfectly well in, for example, Windows Media Player.
    I still have the earlier Premiere CC and the project file and the clips that CC 2014 importer rejects are still OK in the Premiere CC version of the project.
    It seems that the importer in CC 2014 has a bug that causes it to reject MPEG clips with which earlier versions of Premiere had no problem.
    It's not the sort of problem expected with a premium product.
    After this experience, I will not be updating premiere mid-project ever again.
    How can I get these clips into CC 2014? I can't go back to the version of the project in Premiere CC without losing hours of work/edits in Premiere CC 2014.
    Any help appreciated. Thanks.

    To answer my own question: I could find no answer to this myself and, with there being no replies in this forum, I have resorted to re-capturing the affected HDV tapes from scratch.
    Luckily, I still had my HDV camera and the source tapes and had not already used any of the clips that became Offline in Premiere Pro CC 2014.
    It seems clear that the MPEG importer in Premiere Pro CC 2014 rejects clips that Premiere Pro CC once accepted. It's a pretty horrible bug that ought to be fixed. Whether Adobe have a workaround or at least know about this issue and are working on it is unknown.
    It also seems clear that the clip re-indexing process that occurs when upgrading a project (from CS5 to CC and also from CC to CC 2014) has a bug which causes memory consumption to grow continuously while it runs. I have 24GB RAM in my system and regardless of the amount RAM I allocated to Premiere Pro, it would eventually crash. Fortunately on restarting Premiere Pro and re-loading the project, re-indexing would resume where it left off, and, depending on the size of the project (number of clips to be indexed), after many repeated crashes and restarts re-indexing would eventually complete and the project would be OK after that.
    It also seems clear that Adobe support isn't the greatest at recognising and responding when there are technical issues, publishing "known issues" (I could find no Adobe reference to either of these issues) or publishing workarounds. I logged the re-index issue as a bug and had zero response. Surely I am not the only one who has experienced these particular issues?
    This is very poor support for what is supposed to be a premium product.
    Lesson learned: I won't be upgrading Premiere again mid project after these experiences.

  • Poor RAM management in Photoshop CS4 - need help!

    I have done numerous hours of research over the years only to give up and come back to this subject later on. I will try again!
    I must ask: is there ANY way to get Photoshop CS4 to automatically flush used RAM after closing image files? I'm tired and annoyed of CS4 eating more and more RAM without freeing anything after an image has been closed. An image shouldn't still eat up memory when it isn't even open anymore. It seems to be terrible RAM management of the program itself and how Adobe has forgotten to write that little snippit of code to clear the RAM after an image has been closed.
    I know this is not because of:
    Cache levels
    Setting too large of a saved history state; purging history cache or any kind of cache still never frees RAM
    A lack of updates; I have been up to date with CS4 very punctually as they were released
    The computer I am on; this poor RAM management has been around since CS2 and it's the same on the last 4 computers I have used
    Does CS5 still do this too?

    Your historically conditioned to believe software apps should swap data a standard way. The way your using the system is probably not the most effective processing for your workflow.
    -  I have hundreds of TIFFS that take 60-120MB each in processing, and 8gb  of RAM. The more total RAM actually usable that I can use the better.  How the heck can using less of what is actually available RAM enhance my  workflow? Standard are standards for a reason. The ink industry for  printing is non-standardized and people waste $3-5 billion+ a year only  increasing on unused ink that is still remaining in their cartridges, because there is no standard way of manufacturing ink, filling cartridges, or monitoring how much ink is actually left in a cartridge. I'd love for more standards in more markets. Unless natively stable, all other programs on my computer work flawlessly with said demonized traditional methods and standards, even in high bandwidth applications a hell of a lot more intensive than  Photoshop CS4 will EVER be. Currently people keep disregarding the fact that in my situation CS DOESNT FREE THE RAM.  CS4 is balloon. Balloon inflate. Never deflate even when emptied. Overflow into other rooms of critical OS space where balloon shouldn't be when it fill the room full. How many analogies must I give? Must I use sign language? Binary?
    You don’t have enough experience with these topics. This is actually a
    true statement. Most companies with systems large and small have to
    think about what it costs to process specific jobs. If one in a thousand
    jobs swap, a decision must be made to know how much it would cost to
    retrofit a very expensive environment to keep that one job swap from
    occurring. Most times it is better to let the swap happen for this
    non-mission critical item than pay $50,000 to upgrade all systems.
    I said NON EMERGENCY SITUATIONS.  Emergencies are once in a while. You're repeating what I said like a parrot, but in different longer sentences with more words telling me I don't get what I'm talkinga bout. You're missing the full picture of what I am actually saying. That 1 in 1000 overflow would be exactly true in my situation with 7GB used, but it's not. Why not? Because the CS4 balloon will not deflate itself or reuse the empty space inside the balloon when it's needed, and the OS isn't given back any of the empty space to work with to know it doesn't need to page anything. In turn CS4 is going to try and scratch too when the OS is telling it that is has no more RAM left when indeed it does, but its hiding it in its own reserve balloon from itself. If a company needed just 700MB more room and either they spend $50k to upgrade to that, or get CS4 to release some space once in awhile, they'd sure as hell bother Adobe or write their own mod to force CS4 to release unused allocated RAM to get it.
    Self inflicted only because I want to push the limit of what is actually usable on my machine, not some 'safe zone' with high tolerance. My system is tuned for a fine line of performance and I know what it can hande. I know what it uses and it does not spike usage for random OS operations. It can handle 7GB to 7.2GB of RAM of freely used RAM to one active program if it needs that big of a workspace to work. If CS4 isn't going to reuse the hollow areas in that balloon, then that's not my fault. My OS can handle the fine tuning, and CS4 is what cannot, obviously, since it can see that much RAM but not use the last %10 correctly.

  • Premiere CS5 & GTX470, 2.5Ghz quad performance ?

    Hi All,
    Thanks for the great contributions in this forum.
    I am having trouble with a multicam project with 5 video layers of HD (2 layers 1440 x 1080 HDV and 3 layers 1920 x 1080 from Canon DSLR's) at 29.97.
    The playback performance is stuttering and freezing but the sound keeps going. The sequence is setup as HDV 1080i30 (60i).
    I wanted to know if my system specs. up to scratch to handle this multicam edit? Should I expect a smooth uninterupted edit or are my expectations too high?
    Has anyone else have similar issues and how did they reslove them.
    GPU is definitely enabled as the renderer, but the processor is maxing out.
    The overall computer RAM usage is 2.8 Gb, but watching the processes in the task manager, Premiere seems to not use more the 2Gb RAM.
    I have distributed the video across 3 hard drives plus a separate OS drive.
    I have just upgraded my videocard to a Gigabyte GTX470 hoping take advantage of the mercury engine.
    Computer specs as follows:
    I am running Premiere CS5 version 5.0.2 on freshly installed W7.
    Motherboard P5K; CPU Q9300 2.5Ghz quad
    4 gig ram
    Gigabyte GTX470
    750Watt Antec Truepower
    4 x various 7200 drives

    Thanks Baz and Harm for your recommendations,
    I will start with a RAM increase then try the CPU. I don't normally have this many heavy layers at once. It is a one-off job.
    Otherwise will go for the full upgrade.
    Best wishes

  • Long load times normal for Adobe Media Encoder from Premiere CS5?

    When I export a sequence from Adobe Premiere CS5 using Adobe Media Encoder, the system freezes for several minutes before giving me the exporter screen.  Then, when I've loaded my settings and clicked "export," the system again freezes for several minutes before beginning to encode.    I'm using a system with an Intel I7 CPU 930 @ 2.80Ghz 2.80 Ghz., 24 GB of ram, Windows 7 Ultimate 64 bit operating system and an Nvidia quadro FX4800 graphics card..  Everything else is fast, but AME is slow.  Is this normal? Should I reinstall AME?

    Not sure what you mean about the process.  From Premiere CS5, I click on "export" which brings up a menu. I select "media" from the menu which brings up the Adobe Media Encoder.  I adjust my settings and click "export" from the bottom of the screen to immediately render the Premiere file.  Clicking "Queue" would put the program into the AME Queue.  Am I missing something?  On the slowness issue, looks like I need to reinstall AME. I've been reluctant to do that, partially because I'm using some Matrox hardware and I'll have to reinstall the Matrox softare to populate the matrox settings into the media encoder. Looks like it may be worth it.
    Thanks.

  • Screen goes black for 3 seconds in premiere CS5 every time I click

    This is the first time I run Premiere CS5... On a fresh system install.
    I suspect it's not playing well with my video card, a Radeon HD 4870 with 1GB Ram... Very standard stuff.  I am running window 7 64 bit with 12 gb RAM, a week old build. I have all the updates and latest drivers, sigh. After Effects CS5 runs fine, Maya 2010 runs fine, Quicktime runs fine... What gives.
    Here's what happens: I only need to launch Premiere, right away I get the problem. The screen goes black 3 seconds before the prompt to create a new project. Once I create the project, the application workspace comes in, but if I click any menu, drag a tool window (whatever they are called), the screen goes black 3 seconds then comes back. Its basically impossible to work...Huge drag.
    Update:
    The problem stopped after I went into the 'device settings' in preferences and set the device to 'none'....When I clicked on the device settings panel, my monitor went black, and there was a 'no signal' warning that came up, as if the DVI-D  signal was dead. I was able to restore the signal by hitting ctrl-alt-del which switched me out of Premiere onto the desktop. Clearly, there is some issue with video. I switched back into Premiere and was able then to set to no devices.
    I'm not doing any capture at the moment, but I can only pray that it's some sort of bug related to not having a device connected? I plan on bringing footage from a RED in the next month. I upgraded to CS5 specifically so that I could use more than 4 gigs of RAM and for the new features.

    THank you for sending this.
    I followed the benchmark directions, and I get an error at the final step
    when I run the script:
    line 99
    Error: path not found
    I tried for an hour different things, namely to re run the whole test
    procedure, deleting the output files, etc... he script is looking for
    something in the preview files that it is not finding. I think the procedure
    was written for a previous version, because the metadata settings are
    different in my version of AME, and I don't know how much that affects it.
    Also, AME increments the file names when it renders them so that I did not
    get the right output file names at the first render. I had to turn off
    incrementing and manually name each clip before rendering. The vb scricpt
    looks for these names, so I understand it is important. I can't figure out,
    however, what the script is looking for in the preview folder and not
    finding.
    After spending almost two hours trying to troubleshoot the script, I gave
    up. I can tell you tho that it takes about 6-7 minutes on my box to encode
    all the videos.

  • Premiere CS5 - Project Monitor playback is jerky after resintall of operating system and CS5

    PROBLEM: Premiere CS5 - Project Monitor playback is jerky
    This had NOT been an issue prior to reinstalling the operating system and all software.  I have read numerous articles on the forums and have tried everything I can find...with no results.
    STEPS TAKEN TO RESOLVE THE PROBLEM:
    I have scoured the articles here http://www.adobe.com/cfusion/search/index.cfm?loc=en_us&term=choppy%20video&cat=support&pr oduct=premierepro and others at Cretive Cow
    I have installed all updates for CS5 Master Collection, immediately following a fresh install of the operating system and SC5 Master Collection.
    I have ensured that sequence settings match resolution and frame rates of footage - the problem persists.
    I have tested by importing both standard def AVI files created from tape and high def SONY MP4 files - the problem persists.
    I have ensured the latest Video drivers are installed (clean installation selected, so that the Windows default would be removed) - the problem persists.
    I have tried the 3D settings in NVIDIA control panel | Program Settings tab... selected Adobe Premiere Pro from the drop down menu | and chaged 'Multi-display/mixed-GPU acceleration from the value of 'Multiple Display performance' to the value of 'single display performance'; although, I ran two monitors before using this latest NVIDIA video driver and I didn't experience this jerky footage issue - the problem persisted after affecting that change; so, I switched it back. 
    Since I have 96 GB of RAM, I don't use a pagefile.  A zero MB page file is the same setting I had prior to rebuilding the C:  Regardless of whether I have a pagefile or not, the problem persists.
    I have tried creating a fresh user profile, where the user profile is created on the C: drive by default; and, where I left it there on C: to test for the jerky playback in a new PrPR project  - the problem persists.
    Regarding the C: (system drive) and why I reinstalled everything, it had become unstable and was locking up.  I ran DISK ERROR CHECKING with the FIX parameter and the system was still locking up on me.  Keep in mind that the System drive is a solid state drive.  Anyhow, I had no choice but to dive in and reinstall everything.  I wiped the system partition of the SSD using quick format and started installing the operating system.  Now, I've read the CLAIM that this cuases performance issues; but, the only place I see issues is in the video monitor playback in PrPr.  Everything else - Office applications...printing...browsing the Internet...works just fine, everything is responsive, whereas, I couldn't do ANYTHING with it before.
    SYSTEM CONFIGURATION:
    The Operating system and all software is installed on C:
    All data files and most profile related folders are stored on D:
    C:\ (one Intel Solid State Drive - SYSTEM DRIVE)  Used Space: 57.5 GB  Free Space: 388 GB
    D:\ (four Western Digital 2TB drives in an on-board INTEL hardware RAID5 array & hotswapable backplane) used space: 1.28 TB Free space: 4.16TB
    Adobe Premiere Pro CS5 VERSION: 5.0.3 (005 (MC: 218798))
    Operating System    Microsoft Windows 7 Ultimate Version    6.1.7601 Service Pack 1 Build 7601
    System Manufacturer    Intel Corporation
    System Model    S5520SC
    System Type    x64-based PC
    Video    NVIDIA Quadro FX 4800 driver v.320.78
    Display        Dell 27" LCD (DisplayPort)
    Display        Dell 27" LCD (DisplayPort)
    Processor    Intel(R) Xeon(R) CPU           X5680  @ 3.33GHz, 3326 Mhz, 6 Core(s), 12 Logical Processor(s)
    Processor    Intel(R) Xeon(R) CPU           X5680  @ 3.33GHz, 3326 Mhz, 6 Core(s), 12 Logical Processor(s)
    Installed Physical Memory (RAM)    96.0 GB
    Page File Space    0 bytes
    PREMIERE PRO CS5 SETTINGS:
    Monitor PLAYBACK RESOLUTION: Full
    Monitor PAUSE RESOLUTION: Full
    (regardless of this setting, the problem persists)
    PREFERENCES:
    MEMORY:
    Installed RAM: 95.9 GB
    RAM reserved for other applications: 10 GB
    Optimize rendering for: Performance
    (Changing this setting to 'memory' does not resolve the problem)
    MEDIA:
    Media Cache Files
    X - Save Media Cached files next to originals when possible
    LOCATION: D:\Users...\AppData\Roaming\Adobe\Common
    (User Profile folders were relocated to D:\ from within the properties of each folder's 'LOCATION' tab.  This is the same configureation I had prior to rebuilding the C:\drive.  Testing under a new profile where it's allowed to stay on teh system drive does NOT resolve the problem.)
    Media Cache Database
    LOCATION: D:\Users...\AppData\Roaming\Adobe\Common
    PROJECT SETTINGS:
    Scratch Disks
    Path: D:\Users...\My Documents\
    General
    Video Rendering and Playback: Mercury Playback Engine GPU Acceleration
    (Setting Viideo Rendering and Playback to 'Sofware' does not resolve the problem)
    If any of y'all have any other suggestions, I'm all ears.
    Thank you.

    I'VE RESOLVED THE PROBLEM!
    PREFACE:
    OK, I am hoping that through this week-long Operating-System-and-Software-reinatalltion excerise of mine, I have revealed something that everyone -- whom have been cursing Adobe over -- can apply to their systems to resolve this jerky video problem within PremierePro CS5 (and quite possibly other versions, too). 
    If you've read my post above, you've seen all the steps I've taken to resolve the problem.  I've read many posts, some of which have mentioned  hardware upgrade / opitmization steps that one may take to enhance performance, and hopefully resolve the problem.  I've read where people have taken these steps and have still experienced the problem...and then they curse Adobe.  Fer-shame, fer-shame, fer-shame! (nod to Gomer Pyle). 
    In my case, I knew it wasn't an Adobe issue, as it had worked flawlessly before; and, it wouldn't require a hardware upgrade or reconfigureation, as my system is completely maxed out with two processors, a system drive and a hardware RAID5 array, a CUDA-suported nVIDIA 4800 FX card, and 96 GB of RAM.  bla bla bla, puke...whatever.  Bottom line is this:
    It's not a software issue.  It's not and Adobe issue; and Gawd no!  It's NOT a PC vs. Mac issue!  HA HA.  The software had worked swimmingly well prior to the reinstallation / 'lobotomy' I perfomed on the system drive.
    SOLUTION FOR ME:
    Download and install the updated drivers for the motherboard.  Mine is an Intel Workstation Board S5520SC.  Intel has an INTEL DRIVER UPDATE UTILITY which automatically scaned my Intel system and identified drivers which needed updating.  A very handy, time-saving tool!!!  Here's the URL: http://www.intel.com/p/en_US/support/detect?iid=dc_iduu
    The scan revealed two Intel drivers needing an update:
    Intel Chipset
    Wired Networking
    and one non-intel driver:
    Creative Labs Sound Blaster X-fi
    I downloaded and installed these three drivers, rebooted, and tested PremierePro, and was extatic to find this resolved the problem.
    If you have a motherboard from another manufacturer, then you may want to navigate over to their wibsite to locate chipset and other updated drivers for your motherboard. 
    ROOT CAUSE:
    While Microsoft Windows 7 Ultimate was able to install certain default drivers during the Operating System installation (keeping in mind that this was done on an Intel Solid State Drive that I formatted using Quick Format) these default chipset drivers apparently weren't current and were ultimately the root cuase of the jerky video playback within PremierePro CS5.
    Peace

  • Runaway RAM Usage leading to Kernel Panic using FilmConvert Plugin (updated x3)

    Hello, filed a bug report on this but cuious if anyone sees it.
    Late 2012 27 iMac, top line i7 with 680MX, 32 GB RAM.
    Promise R6 TB RAID.
    Trying to render out a 15 min edit from Premiere that has each clip with 3 filters on it - MB Looks, MB Colorista, Filmconvert.
    Since 7.01, every time I render previews or encode out, RAM use skyrockets way past the 25GB I allocated. I get up to a 50GB swap file in fact before the computer just craps out and I can't finish my render. (Nothing past 15 min anyway, I can do under that length ok.) As of this moment PPro Headless in Activity Monior has allocated 40GB and climbing....
    Any ideas?  Kind of a major issue. Does not happen on CS6 with same filters and similar project.
    PS - The same issue is happening with the same project on my Macbook Pro 15" retina with 16GB of RAM. It's creating a huge swap file. On the iMac with Fusion drive I can't complete the render at all due to the system SSD filling up on the Fusion drive. It eventually crashes and reboots. I can complete the render on the laptop, but it ends up with a 50+ GB swap file.
    UPDATE 1:
    I had my suspicions a Plugin I am using, the excellent (but now unusable for over 10 min projects) plugin "FilmConvert" was causing the issue on all my Macs.
    To prove it's the plugin, I removed duplicated my main 15 min sequence, removed the FilmConvert plugin from all clips while keeping the two Magic Bullet effects on. So, all filters (MB Looks, MB Colorista II) BUT filmConvert.
    Result?
    RAM usage stays where it should be (at the limit set in Premiere Pro CC) and there is zero swap file usage. Same project, same filters, same everything except FilmConvert was removed on this duplicate timeline.
    As it stands, the plugin is unusable for longer projects.  I'm still curious if anyone else has seen this, or if Adobe has any input.
    UPDATE 2: I developed a workaround workflow and the vendor wrote back and thinks it's a bug in PPro CC, but will try to see if they can't code around it:
    "We have had one other very recent report of this type of behaviour, but when rendering through the CC version
    of Adobe Media Encoder or Premiere (but not After Effects). I believe the issue is with Media Encoder / Premiere,
    although it's probably preventable within our plugin. The problem I believe is that Premiere and Media Encoder
    create many instances of the plugin during a  render, one instance per frame, and it seems in CC those instances
    do not get cleaned up until after the render finishes.
    As each plugin instance is expecting to be called many times, to render multiple frames, it keeps a certain amount
    of memory allocated, in order to gain a speed advantage."
    I am using the render previews workflow to deal with it for now. I set my sequence to my master codec (in this case ProRes 422 HQ, with maximum quality checked). Then I preview chunks of the timeline setting in/out, render. Then I quit the program, which frees up the RAM and the need for the swap file, which starts reducing itself. Then I run PPro again, and preview another chunk, and repeat the process until done.
    To export final piece, I just export using previews matching the sequence (which is ProRes 422 HQ) and it is a straight copy at that point and quick. This is a useful workflow if you are making tons of minor edits for a client anyway, as it vastly speeds up re-renders of the final file.  No loss in quality as the previews are the same as my final encode would be anyway.
    Still, it would be nice if Adobe/FilmConvert or both could fix this bug so I can just queue up a whole sequence and walk away without chunking it up if I need to.
    Update 3: If only Adobe could move so fast. Rubber Monkey sent me a new version to test today, and it fixed the problem. Amazing customer service!! It has not been released yet but I suspect it will be at some point. Case closed.

    Glad I'm not the only one. My temporary solution was to download the kernel and wl package from December 2012 found http://repo-ck.com/PKG_source/ and then mkpkg and install it. It'll work as an alternative for now, without messing up the primary kernel setup.

  • Can I have a dedicated external monitor in Premiere CS5/CS5.5 using two nVidia GPUs?

    Hi there one and all.
    I have a new Windows 7 64bit system and I am trying to work out if I can use my 2nd graphics card in a way to give me a dedicated external monitor output when using Premiere CS5.5? (and After Effects too if thats possible???)
    My cards I have are the nVidia MSI GTX 470 and I have the choice of either my old nVidia 8800GT or old nVidia Quadro FX3700.
    I can hook up 4 monitors as a desktop no problem, but I do not know if or how it is possible to display my Premiere timeline on the external monitor as a dedicated connection? If not do I maybe need something like the Black Magic Intensity/Shuttle card or Matrox Mini?
    Any help would be very greatly appreciated.
    Thanks - Bradley

    Thanks Harm for such a quick response! much appreciated.
    I see you said a GTX 450 would work to give the dedicated external monitor, does this mean that my poor old 8800GT has finally dried up in terms of helping my system or is it possible to use this card to provide a source monitor for Premiere?
    With regards to the setting up of the 2nd card to not use the Hardware MPE, is this set from within premiere?
    Thanks again!
    Brad

  • When rendering - low RAM usage

    When rendering in Premiere CS5, my machine won't use more than about 3GB of RAM. I have 16GB installed.   In the memory preference, I allow it to use up to 13GB.  Any idea why it isn't utilizing all of my RAM?
    Thank you!

    It is not needed. PR only uses what it needs, nothing more.

  • Premiere CS5 crash in new Mac Pro 2010

    I have two problems:
    1. Sometimes when I make double cick in premiere icon, the program don't start. I see the previous premiere window with the 4 last projects, but I can not select anything, because the pointer mouse become a beach ball. I have to turn off the program with Alt+Cmd+esc.
    2. The big problem. Premiere CS5 5.0.0 crash editing while I'm making marks In and Out in Source window or playing the timeline. The 3 monitors became black or freeze, mouse disapears, sounds freeze and I have to restart with power button.
    I have last Mac Pro 2010, 2,8GHz Quad-Core Intel Xeon, Mac OS X 10.6.4, 8GB RAM, ATi Radeon 5870, 3 x Hard disk 2 TB, 3 monitors connected trought DVI double chanel, and two minidisplayport-DVI double chanel.
    Sorry for my english.
    Any help or doubt about my explanation?

    Thanks Todd!
    I install Premiere Pro CS5 (5.0.2) update, and the graphics update from apple but the problem persists. I disconnected two monitors, too.
    It's very extrange because I had a configuration system running ok, premiere running ok, everything good, but the system hard disk crashes.
    The problem is when I reinstall a backup copy of that system in a new hard disk, then Premiere don't start, and when start then crashes editing. All of the programs are running well, and other adobe CS5 applications, too.
    The old hard disk is a Hitachi 2TB (originally from apple), and the new hard disk is a Western Digital caviar black 1TB.
    I make the backup system from a *.dmg file. I tried with time machine, with disk utilities and with Carbon Copy Cloner. The result is always the same. Premiere won't start.
    I think I have small ghosts inside my computer =)
    Maybe is question of a bad clone but this is not a complicated task.
    Maybe is question of permits. But I resolve the permits question with disk utilities.
    Do you think is question of the clone image?
    Now I'm reinstalling a new copy of Leopard SO after formatting the new hard drive western digital 1TB. I will install only the CS5 adobe master collection, to tried in a clean system.

  • Premiere CS5 AME Export slower than direct export?

    Hello everyone,
    I am testing premiere cs5 premium, and having some issues with AME export render times.
    When I export media to AME it shows about 6hours to render a sequence which is 15min long.
    Export settings :
    H.264 1280x720 25fps
    VBR, 2-Pass, Progressive
    Target 8Mbps
    Max 10Mbps
    Input Squence is directly from AVCHD handycam with native settings no resizing but some simple color correction
    However when I do the same export directly from Premiere Pro the render time drops to 38mins (which is btw also not so optimal)
    My Hardware Specs:
    Intel Core2Quad @ 2,40Ghz
    Ram : 8GB (premiere uses 6GB)
    Scratchdisk: non raid 1TB with 130Mbps average read/write
    (Raw Files on Scratchdisk)
    I used to export similar sequences alot faster with cs4 on the same machine..
    What could cause this problem?
    Thank you in advance for your answers

    Thank you for your quick reply, but It couldnt solve the issue..
    Harm Millaard wrote:
    First of all, the remaining time indication in AME is not very accurate.
    well thats also my experience, but after waiting over an hour, it was still below 25% on the scale.. so I paused and switched to direct export
    Harm Millaard wrote:
    Most of the time and especially with H.264 exports, there is no significant difference between direct export and AME.
    Obviously in this case "most of the time" wont apply.. because I did export it directly from within Premiere 6 times faster..
    There must be a problem somewhere between AME and PremierePro during reading the squence and rendering it.
    Hardware Accelaration is turned on, and I have a supported Cuda Card

  • Laptop with Adobe Premiere CS5.

    Hi
    I'll buy a new laptop, and i'll use Adobe Premiere CS5.
    Processor: Intel® Core™ i3-370M
    • 2,4 GHz, cache memory L3  3 Mo with HM55 chipset
    RAM: 4Go DDR3
    HDD: SATA 750 Go (5 400 r/min)
    GPU: NVIDIA GeForce GT 520M (1 Go DDR3 )
    OS: Seven prenium family 64 bits
    Can I run Adobe Premiere CS5 or CS4 correctly ? In Online mode or Offline mode ?
    Thanks for you answers

    This is the minimum you need for Laptop Video Editing PC
    http://www.sagernotebook.com/
    -or http://www.adkvideoediting.com/systems/viewsystem.cfm?recordid=118
    -or another brand laptop with the following features
    -the newer sandy bridge 2720 or 2820 quad processor
    -and nvidia graphics preferably the 460m, 485m is a bit much
    -1280x900 display with OpenGL 2.0-compatible graphics card
    -and 8 or 16 gig ram and Win7 64bit Pro
    -and 2 internal 7200 HDDs minimum

  • Premiere CS5, Render with Filters/Plugins or Export with Filters/Plugins without Render???

    Hey People, my Very First Question on Here,
    Does anyone know if i use CS5 Premiere, and used a Plugin such as NeatVideo or even a Filter, do i first need to render the file before i export or can i just add the plugin make the changes and export to a file format of my choice.?

    Great Thanks for this, i used Canopus Eduis 5 to edit this footage from AVCHD to Canopus HQ. Then Exported the file to a Uncompressed AVI RGB File and Imported into Adobe Premiere CS5, Applied the Neat Video Filter, Setup it up and Now its ready for Export. But you have Said i Can Export Without Render and It shoul dbe fine. Which is Good. As Render would have taken 55Hours on my Intel i7 X980 CPU with 12GB Ram. Export will Take about 42Hours into a AVI File.
    Thanks for you help if you think of anything else to sace time please message me.

  • Premiere CS5.5 y CS4 andan lento Problem: ¿Hardware o Software?

    Buenas, como estan?
    Mi problema es el siguiente, tengo la siguiente PC:
    AMD Athlon X3
    ATI RADEON HD 5770
    4 Giga RAM
    Mother GIGABYTE 870A
    Disco 1 TB partido
    SO Windows 7 64 Bits
    Instale el Premiere CS5.5, y con desdicha descubri que la visualizacion de los videos andaba los primeros 5 segundos de manera fluida, pero luego se trababa, andaba lento y a los tirones, de manera imposible de editar.
    Procedi a desinstalarlo e instalar el CS4, con el cual descubri que los videos practicamente no se movian al reproducirlos.
    El sonido siempre anduvo fluido.
    El video con el que hice las pruebas es formato Pelicula AVI  720 x 576 25Cps,  son 18 minutos en un peso de 711 MB para que se den una idea.
    Como dato adicional aclaro que el sistema operativo lo instale yo desde cero, pero que baje Direct X 11, los drivers son todos originales (los que me vinieron con las partes de la PC) y que instale un pauqete de Codecs.
    Espero que haya una solucion que no tenga que ver con la placa de video oel procesador, ya que necesito ponerme a editar ya!!
    Muchas gracias por escuchar el problema.

    Requsitos hardware para Premiere 5.5:
    http://www.adobe.com/products/premiere/tech-specs.html
    Respecto al hardware, la CPU utilizada (AMD X3 ?) cumple el mínimo requerido aunque un Intel i5 actual ofrece benchmarks 2 veces más rápidos.
    La memoria mínima es de 2GB, Adobe recomienda 4Gb o más, respecto al disco indicas su capacidad pero no el modelo para conocer la velocidad de rotación y el tamaño de cache.
    La tarjeta gráfica es adecuadad para juegos y trabajos gráficos, (Photoshop, etc.) pero Adobe recomienda otra clase de tarjetas para edición de video.
    Te recomendaría que abras el Administrador de tareas y desde la pestaña de Prestaciones la del Manager de Recursos y veas lo que consume de memoria, etc.
    En el lado del software te aconsejaría que contactases al soporte de Adobe. (Gratuito para productos originales)

Maybe you are looking for