Back to Blog
![]() What I didn't see (may have missed of course) is. and I know as I have worked with that as the best available method at times to split disc activity up. It is pretty much a one-way trip for the drive. USB3.0 can be utilized for footage on projects particularly with either a high-speed flash drive or an SSD that has a fast cache/write/read system. having so many mixed codecs (and processor-intensive ones also) in so many clips "living" on a USB3.0 drive has a built-in slow-down. some people doing long timelines, like over an hour, will split up the timeline via sequences or projects, and combine them later in a master timeline, to avoid large project issues with premiere. he also had a massive project file itself, which seemed to be caused by data from the warp stabilizer effect storing data in the. he was never able to transfer all the media to internal drives, so we don't know if that would have fixed it. There was a similar post from another user a while ago, that had a very large project on multiple usb3 drives, he noticed a new project with a few files on an internal hdd ran smooth. it looks like the cpu speed of those xeon's are on the slow side, but if you can check the computers resources while premiere is stalled/hanging, you can see if perhaps the cpu or usb3 drive/transfer is maxed out. having the project file and cache/previews all on a fast internal drive should help premiere not have to transfer as much data over the usb3. many do use a dedicated scratch disk, depending on the speeds of disks available, some use scratch on a drive being used for other things as well. i also dont know of any limitation to imported clips, size or number of. I would say no, this is not what most premiere editors go thru, or premiere wouldn't be around any longer. Generic performance guide: optimizing for performance: Adobe Premiere Pro and After Effects | After Effects region of interest so the ram usage will change depending on the timeline media and whats being done. premiere will mostly uses ram to hold previews of the timeline during playback. also this Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, an. You can try setting the memory preferences, "optimize rendering for" to "memory". Mac OS 10.6.8 | 2 x 2.26 GHz Quad-Core Intel Xeon | 32GB RAM | Premiere CS6 Tips for optimizing through-put for large projects with all the bells and whistles appreciated. Is this just what Premiere editors have to suffer through? Does Premiere have a cap on how many source movies it can import, or how large the file size? Also, do I need to have a scratch disk? Rendering the entire work area takes all day and then the next time I go to edit, the same delay issue pops up again. When I come back a half hour later, often its ready to go again. Premiere doesn't even give an alert that it's having problems, it just stalls out. Each time I move to a different part of the sequence to work - and most of the time when I push the space bar (play) - nothing happens at all, until I save, which takes 5-10 minutes. I routinely have to wait between 3-8 minutes while Premiere "does its thing". I understand this kind of project would be processor intensive. ![]() ![]() Also lots of split screens and motion effects. My projects typically have between 3 or 4 and up to 25 different videos imported, some high-res, others scaled up to fill the frame, edited in to several hundred clips with video and audio tracks. ![]() Most of these live on an external drive with USB3 connection. I'm compiling 1280x720 sequences from a wide variety of sources, mp4, wmv's, m4v, avi's. ![]() How to get Premiere to use all the RAM I have? Even though I have 32 GB of RAM installed, my OS Activity Monitor app shows that Premiere is using only 1.5 GB at any time. Premiere constantly hangs, drags, virtually freezes up and makes editing somewhat torturous. ![]()
0 Comments
Read More
Leave a Reply. |