Rendering slowing down?

When I used to render, I rendered 720p in real time with h264 on a video bitrate of 4-5 (no need for high quality, as my video host degrades it a lot). I had to do a system wipe, and reinstalled PPro. I'm now using the same settings as I used to, but my bitrate is now 2-3 and it takes around 2-3x the time of my video to render. What is going on?
I have a decent computer. It has a nVidia GTS 250 1gb, AMD Phenom Black II x4 at 3.1ghz, 4gigs of ram, and i'm rendering to a 320gig 7200rpm hard drive. Do I need to reconfigure something?

Why are you only using 2.5GB of your 8GB?
Tell us about the size of your composition frame (i.e., how large your movie is) and what the sizes of your footage items are. If, for example, you have a large footage item used in your composition, then 0.75GB per process might not be enough, so the background rendering processes are going to shut down and all rendering will be done by a single process. See this post for more about memory settings.
Tell us about what kinds of footage you're using, too. It may be that the decoder used for one or more of your footage items is the bottleneck.
Also, have you installed the After Effects CS5 (10.0.1) update?

Similar Messages

Rendering speed is slowing down during process, almost up to freeze

Hello there!
First of all, I'm a new person to After Effects. I bet I just doing something wrong, but anyway I would like to ask an advice how to fix my issue because googling such subject won't solve it.
The point is following:
I rendering 120-minutes long video for YouTube. It almost static with no effects, just with a few simple fade-in/out transitions on couple of layers. You can find an example of such video on YouTube by this link: Daniel Lesden - Rave Podcast 056: guest mix NitroDrop (Israel) - YouTube (for some reason, specifically this video was rendered successfully previously).
Process is going very well at first, 1 minute of playback rendering for about 30 seconds, so first hour of the video rendering for 30 minutes.
The problem starts at about 70% of overall progress: it start to slowing down, and then goes to 1 frame rendering for 1 second. As you can imagine, it's a pain for such long videos, it will take a days to finish last 20-30%.
Composition and render settings are following:
Size: 1280 x 720 px
FPS: 30
Format: Quicktime
Codec: ProRes 422. I've also tried: Animation, Photo JPEG, another ProRes and even H.264, but outcome was the same.
Output module settings screenshot:
Multi-processing settings:
On this point I have to say that I've tried many different options with amount of CPU, RAM or with Multi-processing option turned off completely, but in the end it all was the same.
After Effects version: CC 2014 (still on trial version, but it shouldn't be a problem since Adobe don't have any limitations for trial versions as far as I know).
Computer and OS information:
Any advices please? I'll very appreciate every possible solutions.

"open AE preferences>General then move to the bottom tab and set AE to purge every 10 frames or so"
— I've set this parameter to 10 as suggested, and here are the last render queue results:
First 60-minutes video rendered superb good for 1 hour 17 minutes.
Second 120-minutes video goes really badly: it took 8 hours to render about quarter due to error. Here is what I found in the error log: "There is an error in background rendering so switching to foreground rendering after 246 frames completed out of total 216000 frames. (26 :: 142)".
Later I've tried to render second video again, and it was great almost till finish: 1 hour 45 minutes has been rendered for less than an hour. But then it suddenly slowed down (as described in the original post), so I had to stop it. I installed Memory Dig and "optimized" memory before rendering and once during process, but it didn't help. In the end I just rendered last 15 minutes of the video (with no issues) and just merged it into 120-minutes long file using Video Joiner. Pretty sad method, although.
On a third attempt everything was fine until rendering stops by a new error in popup window: "After Effects error: internal verification failure, sorry! {could not find itemframe we just now checked in}".
So the original problem still wasn't solved yet unfortunately.

System slowed down after Mavericks update (10GB RAM)

Hi,
I have recently updated to Maverics on my mac pro, 2 x 2.8 GHz Quad-Core Intel Xeon, 10GB RAM.
When I perform regular tasks it's all normal. Unfortunately I do some much more than that. I use Aperture on a daily basis and it seems to have slowed down a bit. The issue is more apparent when I use Final Cut. I can't have any other design/photography/video software on the background anymore. My computer can't deal with. But it could before Mavericks! It will also complain about not enough memory when rendering...
I understand that kernel task is heavy on the memory and after an EtreCheck I also realised how much memory spotilight is using. I already excluded a lot of items from spotlight, and it's way better, but still, why is my computer so slow?
Please can someone look at my check and tell me if there's anything I can do to boost my system back to it's previous glory?
thank you
Hardware Information:
          Mac Pro (Early 2008)
          Mac Pro - model: MacPro3,1
          2 2.8 GHz Quad-Core Intel Xeon CPUs: 8 cores
          10 GB RAM
Video Information:
          NVIDIA GeForce 8800 GT - VRAM: 512 MB
System Software:
          OS X 10.9.1 (13B42) - Uptime: 1 day 5:55:10
Disk Information:
          WDC WD2002FAEX-007BA0 disk0 : (2 TB)
                    EFI (disk0s1) <not mounted>: 209.7 MB
                    Disc 4 (disk0s2) /Volumes/Disc 4: 2 TB (493.89 GB free)
          ST3000DM001-1CH166 disk1 : (3 TB)
                    EFI (disk1s1) <not mounted>: 209.7 MB
                    Disc 2 (disk1s2) /Volumes/Disc 2: 3 TB (49.2 GB free)
          ST31000528AS disk2 : (1 TB)
                    EFI (disk2s1) <not mounted>: 209.7 MB
                    Disc 3 (disk2s2) /Volumes/Disc 3: 999.86 GB (3.26 GB free)
          ST31500341AS disk3 : (1.5 TB)
                    EFI (disk3s1) <not mounted>: 209.7 MB
                    disk3s2 (disk3s2) <not mounted>: 1.5 TB
                    Recovery HD (disk3s3) <not mounted>: 650 MB
USB Information:
          Apple Inc. iPhone
          Apple, Inc. Keyboard Hub
                    Apple, Inc Apple Keyboard
          Generic Flash Card Reader
          Apple Inc. Bluetooth USB Host Controller
FireWire Information:
Thunderbolt Information:
Kernel Extensions:
Startup Items:
          HP USB EWS Gateway: Path: /Library/StartupItems/HP USB EWS Gateway
          HPlaserjet Trap Monitor: Path: /Library/StartupItems/HPlaserjet Trap Monitor
          MySQLCOM: Path: /Library/StartupItems/MySQLCOM
Problem System Launch Daemons:
Problem System Launch Agents:
Launch Daemons:
          [System] com.adobe.fpsaud.plist 3rd-Party support link
          [System] com.adobe.SwitchBoard.plist 3rd-Party support link
          [System] com.microsoft.office.licensing.helper.plist 3rd-Party support link
          [invalid] com.oracle.java.Helper-Tool.plist
Launch Agents:
          [System] com.adobe.AAM.Updater-1.0.plist 3rd-Party support link
          [invalid] com.oracle.java.Java-Updater.plist
          [System] com.wacom.pentablet.plist 3rd-Party support link
User Launch Agents:
          [not loaded] com.adobe.AAM.Updater-1.0.plist 3rd-Party support link
          [not loaded] com.adobe.ARM.[...].plist 3rd-Party support link
          [not loaded] com.google.keystone.agent.plist 3rd-Party support link
          [not loaded] com.spotify.webhelper.plist 3rd-Party support link
User Login Items:
          Dropbox
          Spotify
          HPEventHandler
Internet Plug-ins:
          Flip4Mac WMV Plugin: Version: 2.2.3.7 3rd-Party support link
          FlashPlayer-10.6: Version: 12.0.0.44 - SDK 10.6 3rd-Party support link
          Default Browser: Version: 537 - SDK 10.9
          AdobePDFViewerNPAPI: Version: 11.0.01 - SDK 10.6 3rd-Party support link
          AdobePDFViewer: Version: 11.0.01 - SDK 10.6 3rd-Party support link
          Flash Player: Version: 12.0.0.44 - SDK 10.6 3rd-Party support link
          JavaAppletPlugin: Version: 14.9.0 - SDK 10.7 Outdated! Update
          QuickTime Plugin: Version: 7.7.3
          SharePointBrowserPlugin: Version: 14.3.9 - SDK 10.6 3rd-Party support link
          Silverlight: Version: 5.0.61118.0 - SDK 10.6 3rd-Party support link
          iPhotoPhotocast: Version: 7.0
Audio Plug-ins:
          BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
          AirPlay: Version: 1.9 - SDK 10.9
          AppleAVBAudio: Version: 2.0.0 - SDK 10.9
          iSightAudio: Version: 7.7.3 - SDK 10.9
3rd Party Preference Panes:
          PenTablet 3rd-Party support link
          Flash Player 3rd-Party support link
          Flip4Mac WMV 3rd-Party support link
          Growl 3rd-Party support link
          Perian 3rd-Party support link
Bad Fonts:
          None
Old Applications:
          /Library/Application Support/Microsoft/MERP2.0
                    Microsoft Error Reporting:          Version: 2.2.9 - SDK 10.4 3rd-Party support link
                    Microsoft Ship Asserts:          Version: 1.1.4 - SDK 10.4 3rd-Party support link
          Solver:          Version: 1.0 - SDK 10.5 3rd-Party support link
                    /Applications/Microsoft Office 2011/Office/Add-Ins/Solver.app
          SLLauncher:          Version: 1.0 - SDK 10.5 3rd-Party support link
                    /Library/Application Support/Microsoft/Silverlight/OutOfBrowser/SLLauncher.app
          SuperDuper!:          Version: 2.6.4 - SDK 10.4 3rd-Party support link
          /Applications/Microsoft Office 2011/Office
                    Microsoft Graph:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    Microsoft Database Utility:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    Microsoft Office Reminders:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    Microsoft Upload Center:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    My Day:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    SyncServicesAgent:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    Open XML for Excel:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    Microsoft Alerts Daemon:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    Microsoft Database Daemon:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    Microsoft Chart Converter:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    Microsoft Clip Gallery:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
          /Applications/Microsoft Office 2011
                    Microsoft PowerPoint:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    Microsoft Excel:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    Microsoft Outlook:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    Microsoft Word:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    Microsoft Document Connection:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
          Microsoft Language Register:          Version: 14.3.9 - SDK 10.5 3rd-Party support link
                    /Applications/Microsoft Office 2011/Additional Tools/Microsoft Language Register/Microsoft Language Register.app
          CrucialMacScanner_UK:          Version: 1.0 - SDK 10.0 3rd-Party support link
                    /Users/[redacted]/Documents/Software/CrucialMacScanner_UK.app
          Microsoft AutoUpdate:          Version: 2.3.6 - SDK 10.4 3rd-Party support link
                    /Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate.app
          Spin Doctor:          Version: 1.0 - SDK 10.5 3rd-Party support link
                    /Applications/Toast 11 Titanium/Spin Doctor.app
Time Machine:
          Skip System Files: NO
          Mobile backups: OFF
          Auto backup: YES
          Volumes being backed up:
                    Disc 2: Disk size: 3 Disk used: 3
          Destinations:
                    TMMacpro2013 [Network] (Last used)
                    Total size: 21
                    Total number of backups: 63
                    Oldest backup: 2013-05-28 23:04:49 +0000
                    Last backup: 2014-02-13 15:51:39 +0000
                    Size of backup disk: Excellent
                              Backup size 21 > (Disk size 3 X 3)
          Time Machine details may not be accurate.
          All volumes being backed up may not be listed.
Top Processes by CPU:
             191%          Final Cut Pro
               5%          diskimages-helper
               4%          WindowServer
               2%          Google Chrome
               1%          backupd
Top Processes by Memory:
          1.00 GB          Final Cut Pro
          338 MB          mds
          328 MB          mds_stores
          256 MB          Finder
          205 MB          com.apple.IconServicesAgent
Virtual Memory Information:
          3.52 GB          Free RAM
          3.93 GB          Active RAM
          1.63 GB          Inactive RAM
          942 MB          Wired RAM
          12.92 GB          Page-ins
          0 B          Page-outs

Beware of perceived RAM use. 10.9 uses RAM more efficiently:
About memory management in OSX 10.9 Mavericks
Memory is managed differently, and more efficiently in 10.9. It is (mostly) unique in the industry, but may become trend.
Let’s start with the basics. Mechanical disk drives are very slow, with access speeds in the 10s of milliseconds and transfer rates in the 200-400 Mbps range real world. SSDs are much faster, on the order of a couple of ms access and typically 1200-3000 mbps transfer rates. RAM is much faster than either, in the nanosecond access and transfer speeds of ~8 Gbps effective (1 GHz x 8 bits/byte).
These are rough numbers for comparison purposes only.
So the goal is to keep as much in RAM as possible. But if you run out of RAM what do you do?
Traditionally you take the least used RAM and write it to a special part of the disk, in a way that you can access it most efficiently - minimizing the disk delays. This is called a swap file because you swap RAM in and out of it.
10.9 has a new trick: it compresses RAM using the main processors. Rather than swapping stuff to disk (disks are slow), it actually uses the processor to compress memory and make, for example, 1 GB of physical RAM hold as much as 1.5GB. Similar approaches are used to make MP3 files 10x smaller than the real thing - there is redundancy in data and you can take advantage of that. Apple is making the following calculation: the processors can compress way faster than the disk can swap. And its also predicting that the processors are often partly idle - waiting for swap files or disk access. So rather than swap files around, its compresses the files ***in RAM***.
Compression works,. Tests show that on average it is faster, and that 4GB (i have 4 GB RAM) acts like 5 1/2 - 6GB. Wow.
So, 10.9 will load up most of your RAM, knowing that it can compress some when it needs to. So don’t worry too much that it may look like all your RAM is taken - yea, it is, but its OK.
The measures to look at are:
1. amount compressed. Compression means it has run out of RAM and needs more. As long as compression is low this is fine. In fact this is how 10.9 uses RAM more efficiently than 10.6,7 or 8. Contrary to common wisdom, it requires LESS RAM than 10.8. The colored indicator tells you who this is going - green (good), yellow( iffy) and red (bad).
2. amount swapped. Once it cannot compress any further, or can’t do so efficiently, jot begins old-fashioned swapping. This is a major slow-down and means you would benefit from more RAM. Tiny amounts are OK.
here's an article by Apple - but on th pre-10.9 memory management techniques....mostly still true, but read on.
http://support.apple.com/kb/HT1342?viewlocale=en_US
Bottom line - compression makes 10.9 use RAM more efficiently than previous OSX versions. It also makes the “ram used” indicator less meaningful, and mans you should monitor “compression” .
That said, RAM has always been one of the most cost effective upgrades possible. People spend too much on new machines and too little on more RAM.
Hope this helps,
Grant

LR 2.5 slows down after upgrading to Snow Leopard

This is my first post, so first of all I'd like to say hello to everybody here and apologize for my poor english
My computer is an iMAC with an Intel Core 2 Duo, 4GB RAM, 500GB HD and a graphic card NVIDIA GeForce 8800 GS with 512 MB VRAM.
The LR database is contains, up to now, about 5000 photos most of them in NEF format (my camera is a Nikon D300)
In the last month I noticed that the performance slowed down consistently as thumbnails refresh started taking a long time as well as editing photos and the overall LR2 (executing at 64bits) working.
I started monitoring the system, but despite the low LR2 performances I still had a lot of free RAM and the cores weren't really working a lot.
I can't say this for sure, but I could bet that the performance problems began with the upgrade to Snow Leopard.
Can anybody help me to solve this issue?
Thanks a lot in advance
Roberto

Ian Lyons wrote:
Lightroom performance should not have deteriorated as a result of upgrading to Snow Leopard. Things that you should check are:
1. that you are indeed running Lightroom in 64-bit mode (open System info under Help menu and check that Application Architecture shows x64)
2. that you have all of your previews rendered to at least Standard-size
3. that you have at least 20% free hard disk space
You should also run the Catalog Optimisation option in Catalog Settings
1. Yes, LR2 was running in 64 bit mode before upgrading to Snow Leopard, then (don't know why) gets back to 32 just after the upgrade and I manually set it to 64 bit (checked in the application and on the process monitoring while running)
2. I have the preview rendered 1:1 in the folder I'm working on (done again tonight)
3. I have 55% free HD space
4. I run a Catalog Optimization many times, The last one was tonight
In other words I've checked and tried all these things many times. I've red on the internet that it might be a geforce 8800 issue, but I've found only windows references. Don't forget that neither RAM nor CPU are stressed when LR2 is working and all other applications run normally

Browser based InfoPath Forms in SharePoint 2010 performance has slowed down after SharePoint 2010 SP2

hi All,
Our Browser based Infopath forms have slowed down drastically after applying SharePoint 2010 SP2. Prior to this, we had SharePoint 2010 SP1 and the timings was around 10 seconds (single user) for the entire infopath form to be displayed which has 10-12
views and 5 data connections and 15 business rules and around 100 fields.
But now after applying sharepoint 2010 sp2, the performance has slowed down and it now takes for a single user around 50 seconds.
Refer to the link below, which we followed by applying the patch as well, but the performance is still the same very slow.
http://social.technet.microsoft.com/Forums/sharepoint/en-US/0b673324-01c4-49f7-86cb-647aa43fefd6/infopath-browser-forms-extremely-slow-after-service-pack-2-upgrade?forum=sharepointadminprevious
We have raised a ticket with Microsoft, but there is no concrete resolution as to what component of the infopath has made the form rendering and display slow.
Can someone point me to the right resource or knowledge base where i can do a kind of debug, which tells me exactly which infopath dlls are the issue or which part of my form is taking more time. I am using AOLPageTest and Fiddler, but they do not give me
any details where exactly is the bottleneck.
Any tools that give me the details of the bottleneck.
Thanks and appreciate your help in this.
Regards
Ram
Thanks Ram

hi inderjeet,
The application has gone live and its on production, the same application is on pre-prod and UAT, system testing and integration environments.
The infopath form used to work very well on all these environments before we installed sharepoint 2010 sp2. but the moment we installed sharepoint 2010 sp2, the infopath forms have slowed down.
Microsoft has acknowledged that there is an issued with sharepoint 2010 sp2 and infopath form performance, but they are not able to provide an appropriate fix on this.
We have another environment where there is no sharepoint 2010 sp2 applied only sp1 is applied and the infopath form works very well within fraction of seconds.
So your point no. 1 and 2 and 3. does not reveal anything. Fiddler does not give any detailed component by component breakup where the time is taking more.
The form used to work very well before we applied sp2.
I want to know a tool that gives me exactly component by component grant chart kind of breakup of time taken when the infopath url is requested on the browser.
Thanks
ram
Thanks Ram

Lightroom workflow slows down after modifying an image

Hi fellow users,
Lightroom 4.3 runs smoothly if I work on unmodified images.
However, if I apply modifications on an image, retouching it afterwards becomes much slower, even if I render a preview AFTER I made modifications on the image.
I tell you an example: I import a raw file to the program and I render it`s preview. Then I retouch the image - it works very fast, no waiting time, no Loading overlay.
Where the problem starts: I import a raw file, I apply some modifications on it (for example a preset), then I render it`s preview - then I want to do more modifications on the image, which becomes very slow.
I was monitoring the cpu usage of the computer. In the first case, the cpu usage during modifying the image is normal.
In the second case, it goes up to 100%.
It seems that applying modifications on an image makes working on it slow, no matter if you have the most up-to-date preview or not.
Anyone knows if it is normal or not?
Is there any solution to this?
Thanks,
Tamas
My configuration:
Windows 7 64 bit (up to date)
Lightroom 4.3 64 bit
Fast PC
lightroom settings:
camera raw cache: 20gb
video cache: 10gb

First of all, you can forget about the preview rendering, that's irrelevant. Previews are only used by the Library module, not the Develop module. In Develop, it's handled by the ACR cache.
Now, as for slowing down after initial adjustments, that's a variable I haven't looked out for. But it could well be correct (it would explain some weird results I got across two machines recently).
In general, Lightroom 4 performs well below expected standards on some systems, while others fly along, and it seems nobody can explain why. Long story, do a search on this forum and you'll come up with several lengthy threads. The problem is that there are so many variables in this that it's almost impossible to even define what "slow" means. And now you've added another (interesting) one...

Render Queue Slows Down with Large Queue

I recently bought a 2014 Mac Pro for the specific purpose of rendering large volumes of After Effects Compositions.
I am rendering approximately 40,000 After Effects Compositions - the reason being that I am using an After Effects Script to create personalised videos from a CSV file.
I've segmented the list into batches of around 1,000 at a time and each film is 1m25s long. I am also using the Mercury Playback Engine GPU Acceleration (OpenCL). The videos are added from After Effects into AME.
The Problem
When I start the render, it churns them out at about 3 minutes per video. If I leave it for more than around 9 hours, the render time dramatically slows down. After leaving it for more than 24 hours (a weekend) I've seen render times of around an hour per composition.
Question
Is there a way to stop the queue from slowing down?

I've noticed it with more than 40+ objects in the Queue as well. Now I just save the Queue and stop and exit and re-open if it looks like it's slowing down. Mind you this is a 4Ghz Hex core, 64GB Ram and Quadro 5000 + Tesla C2075 so I know it's not a system issue. CC prior to CC (2014) I never experienced this issue.

Heavy Retouch Editing Really Slows Down Aperture!

I've been editing a few images in Aperture 3.0.1 that have require a significant amount of Retouch editing. Once I've reached about 70-80 Retouch edit brush strokes, Aperture starts to bog down. If I go over 100 Retouch brush strokes, Aperture REALLY starts to slow down, particularly if I try to export a file to be edited in Photoshop or NIK plugins. In fact, exporting is DRAMATICALLY slowed down, even if just exporting a 800x800 JPG. If I hit 150+ Retouch brush strokes, the Export Version function in Aperture becomes all but unusable. It can take 20-30 minutes to actually export the version! And that's just for a single image.
Once Aperture has caught up with itself, I can go and export a lightly edited image and it will happen in mere seconds. Go back to that heavily Retouched image, and export takes forever!
I sure hope the next release of Aperture resolves this issue! As best I can tell, it is directly related to RETOUCH (both Repair and Clone) and not so much the other Adjustments.
BTW, I have already shared my experience with the Aperture Team via Aperture Feedback.
Mark

I've seen this slowdown as well.
I think that, to some extent, that this is an issue that will exist with the type of application that Aperture is. It is dynamically applying your edits and rendering a final image to your eye, and if you have 150 retouches Aperture has to do a LOT of work. I mean, really, the math and calculations required are extreme. Maybe there's a magic bullet for this in how Aperture renders the output, but I don't know from the non-destructive nature whether this is possible. It could just be that I can't think of an easy way.

AME CS4 Batch - Slow Down After First File

I've been using AME to batch timelines from various different Premiere Pro projects. Problem is the first one in the batch will take the normal amount of time around 2 hours. Then everyone in the batch after that takes 5 hours.
If I stop the encode once it gets to the second file and slows. And then restart the program and put that one as first it renders in a fraction of the time....
Why does AME drastically slow down after the first file in the queue?

Where do you close the ResultSet?
Where do you close the Statement?
Presumably you only create one connection for all users or you close it somewhere.

Slow down effect won't work...

I recently upgraded to iMovie HD and when I try to use the slow down effect it renders it but it stays the same clip. Any suggestions on what is causing this?

You're not alone.
Unfortunately that's the only thing I can say and do for you...
Numerous posts deals with this bug. We can state that it appears in those cases:
- Ilife'05
- MiniDV film importation
This effect was so funny and usefull in previous versions of ilife.

FinalCut Pro Slow down in Dual G5

Hi All,
First the specs:
Dual 2. Gh G5 with 5 gig of ram, and over 35 gig of spare drive space on the boot drive and 480 gig of drive space on the media drive. The software I am referring to are the latest FCStudio Package and the latest operating system.
The other system in place: First generation 17" MacBook Pro with 2 gig of ram, 28 gig of spare space on the boot drive and 526 gig spare space in media drive.
Neither system is connected to the other or internet.
So last week, rendering a 5 minute timeline that contained 100% titling effects from Live TYPE took approx 38 minutes long.
Yesterday, two timelines version of the same timelines, also 5 minutes in length each took almost 5 hours to render.
Very strange and sudden decrease in efficiency!
On a lark I put one of these same timelines on the Macbook Pro and it was all done in an hour.
Thanks for any help!!!
PS I have a similar comment in compressor because the slow down is in BOTH software packages.
Thanks for any help!

I'd use /Applications/Utilities/Activity Monitor to see what's eating your resources...
Patrick

Long project slowing down

hi everyone
i need some advice cuz i just screwed stuff up.
i am working on a doc film. i have edited about 30 mins so far on timeline. lots of overlays/trans/music/some effects- i am on a pwr mac g5/ have all files on an external lacie drive with 115 gigs free/ for some reason i have fce3 doc folder on both internal and external drive but looks like all the project files except render files are going on external drive folder for fce3. my computer is starting to move really slow, especially fce. Rendering is taking forever all of a sudden. I deleted the render files like an idiot, so now i have to re-render everything and keep getting an "operation error" box. i think thats cuz its timing out, not sure. but real question is --what should i do? i have plenty of space left on the drives-why is it slowing down so?
any advice is appreciated
thx
jim

The project file should be on the internal system drive of the computer. The media and the render files should be on the media drive. Move the project files there. Trash prefs and repair permissions. Run Disk Warrior on your drives. Open a previous project from the autosave vault and put it on the system drive and see if it runs properly.

Preflight check in CS5 dramatically slows down file opening

The preflight check option in InDesign does not seem to run in the background. As a result, it now takes around 5 times longer to open a file, as you have to wait for the preflight check to finish before you can do anything. Sure you can turn it off, but that kind of defeats the point of having it. Is there any way to configure it so that it runs in the background, or is this just another feature that is basically rendered unusable?

What I am seeing is this: I open an InDesign file. The spread appears and all the objects placed on that layout appear, just as usual. Then I get the spinning beachball, which coincides with the preflight checking the file (you can see the word "checking" in the bottom left of the frame). The beachball stops and I can finally access the file once the preflight chack is complete. So, on that basis, it doesn't seem to be running in the background. Turning preflight off eliminates the problem. So yes, the file is open and visible, but I can't get at it until the preflight check is complete.
For reference, I am using OS 10.6.6 and InDesign 7.0.4.550.
Note that using the Basic preflight check, I don't get these problems, but using a custom profile, I do. I started trying to see if I could pinpoint what in the extra checks was causing the problem, but I failed: I took the basic profile, which works fine, and added the first extra check from my custom profile, which is to Check OPI Links in LINKS. I immediately got the slow down. But unchecking that in my custom profile, didn't speed things up, which suggests that it's more than one thing. If it helps, my custom profile is cheking for:
LINKS
Links missing or modfied
Inaccessible URLs
OPI Links
COLOUR
Transparency blending space
Colour spaces not alowed
Overprinting applied to white
Registration applied
IMAGES & OBJECTS
Image resolution
Interactive elements
TEXT
Overset text
Font missing
Glyph mising
Font types not allowed
DOCUMENT
Bleed & slug setup

Timeline slowing down playback / deleting tracks remedies problem

Here's a nasty bug I've been running into lately.
I've noticed (on the latest version of Premiere CC 2014) that sometimes a timeline/sequence in a project will start to slow down during playback. It slows down not only the advance of the playhead (in terms of how often it's refreshing) but more annoyingly, it slows down video playback in the program monitor. It happens even when footage has been rendered and should exhibit minimal stress on the system.
To illustrate that it's just the timeline, not the video itself, the problem can be "fixed" in three ways:
1. Zoom in on the timeline until playback smooths out again. If a small enough piece of the timeline is visible, it seems to smooth out playback again.
2. Maximize the program monitor window (so that it's the only visible window in Premiere) and then again, immediately playback snaps to full speed again. I can full-screen the video playback, etc, without issue. And un-rendered portions of footage with effects applied play better as well.
3. Reduce the number of video/audio tracks. This is what I think is actually slowing down Premiere. But the problem is, I don't have that many tracks to begin with. On the project I'm working on right now, I have 4 video tracks and 5 audio tracks. Simply deleting the bottom 3 audio tracks (which are sparse and only have a few incidental effects) fixes my video/GUI playback problem immediately.
So my question is... why is Premiere slowing to a crawl just because I added a few audio tracks to a project? Apparently my machine is fast enough to edit 4K material off the GH4 with effects applied and not drop a frame. But add a few tracks of stereo audio? Premiere slows to a crawl.
It wasn't like this in previous versions, guys. Please advise.

Try accessing your audio from a different drive location.

Strange slow down

ok, so i'm trying to wrap my head around how this happened. i opened fcp and it loaded all my open projects at a normal speed.
than i quit fcp and had to do a file transfer. i've two macs hooked up via ethernet and started transferring files. none of these files are in any of my fcp projects.
i opened up fcp during the file transfer, and it took like ten minutes to load just 1 project. it was massively, ridiculously slow. so i quit fcp, stopped the ethernet transfer, reopened fcp and it loaded at normal speed.
how and why did the ethernet transfer slow down the opening of fcp?

Not only that, but FCP on startup scans mounted drives for footage/renders. If your remote drive is mounted FCP will wander off looking there. This is exasperated by the bandwidth occupied by the copy in progress...
Patrick

Rendering slowing down?

Similar Messages

Maybe you are looking for