After effects takes too long to render, broadcasting time is soon, so I'm in a lot of trouble!!! :(

Hello!
I started to render a pretty easy animation 13 days ago.
The animation is 4.30 minutes long, and there's no 3d involved. Only illustrations from Illustrator and some textures.
After these 13 days of rendering, and finishing 4 minutes, it felt like crashing. So it did.
This animation is for Belgian television (broadcasting time is soon), along with 20 more, so I am in deep deep trouble.
I use my mac pro, from a seagate hard drive.
> codec apple prores hq (this is what the company wants)
Could really use help to solve this problem!!
Thanks a lot
Ellen

Hi!
I agree, something is very wrong with your scene or setup. I would recommend the following actions:
1. Make a RAM preview in After Effects, in full resolution. If you have layers with frame blending or motion blur, make sure to enable the frame blending and motion blur boxes in the top of the timeline so that it shows up in the preview. Also, check the Preview settings window and make sure that no frames are skipped and that it renders in full resolution.
If the RAM preview is rendered as slowly as your final render, then the problem is inside of after effects or with your source files. If the RAM preview is a lot faster than the rendering, the problem is likely in the codec or Adobe Media Encoder (if you render through AMC that is).
2A: IF your RAM preview is extremely slow, try hiding the layers one by one and making more RAM previews to locate problematic source files.
2B: If the RAM preview worked fine, try to render into a different, lossless format – like an uncompressed quicktime or avi file or a quicktime animation with max quality – directly from after effects (In the top menu: Composition/Add to render queue, where you'll likely find some lossless preset). Make sure you have A LOT of free hard drive space before rendering. If this rendering works fine you are left with a lossless file that can be compressed to the apple prores hq-format in any compatible software. For example, you can try opening the file in Premiere and render the Prores from there. With a google search you will probably find lots of ways to render Apple Prores files.
You could also check the resolution of both your main composition and your pre-comps. Avoid using unnecessarily high resolutions, it will only slow things down.
Restarting your computer to clear RAM memory and close eventual bugging processes could also be a good idea.
Good luck!
/Simon

Similar Messages

After Effects Rendering too long

I am trying to make about a 7 second clip of some photography (converted into that cool 3D paralax effect) with a lens flare and a CC light rays effect. The damn thing took two hours and was less than halfway done, which seemed extremely long to me. Here is my setup:
i7 4770 (2 processes for system, and 6 for AE, with 2 gigs per process)
Nvidia 760 4bg
32 gigs ram (4 set aside for system and the rest for Creative Cloud stuff)
SSD: system, media cache
HDD: projects, files
Everything else I've tried to render has been reasonable times. For instance 5 minute clips usually take about 15 minutes. I've tried variations of the multiprocessing tab to no avail, and changing the media cache to HDD which didn't work also. Just seems like something is going terrible wrong.
So I guess my question is twofold.
1) How important would it be to get another drive? (I'm between adding one SSD or getting 2 HDD's per my budget, which presents another question of would a 2 SSD, 1 HDD setup be better than a 1 SSD, 3 HDD setup)
2) Do I possibly have something configured wrong?
Thanks in advance!

If your comp is huge, that could certainly explain it.
Also, your assets should only be as large as they will ever be in the screen. That is to say, once you've got them clipped out how you want them in Photoshop, you should save a copy of the asset that have been resized down to 1920 wide or 1080 high max. Although, if you're planning to scale it up in AE or move the camera closer to it, adjust that number to whatever you need. Basically, the smaller your assets, the quicker AE will be able to work. (In most situations.)

After Effects CC seems to automatically render every time I make a change. HELP

A yellow bar appears under my compostion window above my time line. I can't even type a sentence with the type tool without it trying to render every letter. Its making my computer and my worklow painfully slow and it's also irritating me. I don't kno why it suddenly started to do this while I was editing audio layers. Can anyone tell me how to turn it off? Please?
Update: it also makes it so my RAM preview only renders 1 frame at a time and it cannot store any rendered frames so it has to always start over and rerender everything.

You have not provided system information and other details. That aside, standard procedures apply - trash the prefs, flush the caches, check your configuration, verify that the source files are intact, reinstall the program if necessary.
Mylenium

After updating my iphone 5s to 7.1 ... the keyboard is crashing and it takes too long to respond, what is the solution? if there any link from which we can download the original 7.1 firmware for A1533 Version?

After updating my iphone 5s to 7.1 ... the keyboard is crashing and it takes too long to respond, what is the solution? if there any link from which we can download the original 7.1 firmware for A1533 Version?

Restoring the iPhone will reload its firmware.
Plug the iPhone into (the current version of) iTunes on your computer.
Let it sync. Then choose "Restore" from the iPhone's summary page in iTunes.

Compressor takes too long

OK, I have a huge problem with both FCPX and Compressor both taking too long to export a 2 min itunes.
I created a motion graphic project using Motion 5.0.7 - The project was 26 seconds long.
I opened the project in FCPX 10.0.8 and lengthened the clip to 2 minutes, thus slowing the project down. I then changed text and added some video clips to the generator / project into the drop zones.
There were 2 video clips, both no longer than 30 seconds.
I allowed FCPX to complete the render process, which took 10 hours.
I then exported / sent the project to Compressor 4.0.7 - to export to Apple TV3 in HD format.
I am using a rMBP 15" 2.3GHz i7 with 8GB RAM and running OSX 10.8.3
The video in total is 2minutes long, however Compressor estimates the encoding process to complete in 6hrs
I find this ridiculous to say the least - 10 hours for rendering and another 6hrs to encode before I can view the resulting 2 minute video clip ? Is this normal ?
I have all applications closed only compressor running.
I even tried sharing from within FCPX to export to iTunes 1080p - and it only ran to 15% after 5 hours . (at this point rendering and exporting was taking place at the same time) So I then allowed rendering to complete (10 hrs) , and now Compressor says 6hrs.
I would really appreciate anyone shedding more light on this ...

Thanks for the quick response.
Within FCPX I was using H.264 Better Quality - and changed that to H264.Faster Encoding. Both however took too long to encode the final video.
In Compressor I used "Apple Device 1080p 10Mbps" - this also gave a long delivery time.
It has only been with this one project. To give more info, I was trying to create a 3D Motion Graphics template that I could use to promote a companies products. So the template would be usable in FCPX where I can edit just the text and add images customised for any company.
I tried doing all the editing in Motion - but Motion has too many keyboard shortcuts - so when I am editing the text boxes in motion, if I accidently forget to click on the text section within the inspector, and start typing, all sorts of shortcuts are pressed and I can't undo them. I have to close the project without saving, and start again. That's why I prefer to edit the text in FCPX - becuase I am "safer" with the shortcuts.
I'll try working on the template within motion, at a slower pace - to avoid "accidently" hitting short cuts, and see if it helps.
I only started using Motion about a month ago, so still getting used to how effects work.
I still don't understand why FCPX takes so long to render and export. With normal video footage, and adding simple transitions, I have no problems.
I'll also try doing a simpler template in Motion and see if it performs the same.
Thanks
Manesh

AME CS6 rendering with AE and Pr takes too long

Hi Guys,
Need some help here. i have rendered a 30 secs mp4 video with 1920 x 1080 HD format 25 frames w/o scripting in AME for 4 hours!
Why does it take too long? I have rendered a 2 minute video with same format w/ scripting but only spare less than 30 minutes for rendering.
Im using After Effects and Premium Pro both CS6 and using Dynamic Link in AME.
What seems to be wrong in my current settings?
Any help would be appreciated.
Thanks!

This may be a waste of time, but it won't take a minute and is something you should always do whenever things go strangely wrong ............ trash the preferences, assuming you haven't done it already.
Many weird things happen as a result of corrupt preferences which can create a vast range of different symptoms, so whenever FCP X stops working properly in any way, trashing the preferences should be the first thing you do using this free app.
http://www.digitalrebellion.com/prefman/
Shut down FCP X, open PreferenceManager and in the window that appears:-
1. Ensure that only FCP X is selected.
2. Click Trash
The job is done instantly and you can re-open FCP X.
There is absolutely no danger in trashing preferences and you can do it as often as you like.
The preferences are kept separately from FCP X and if there aren't any when FCP X opens it automatically creates new ones . . . instantly.

RTF export takes too long

Hi all,
you know why a report with a lot of data and many pages (about 300 pages), if I export this in PDF format using short time (1 min) and if I export this in PDF format takes too long (even 10 minutes) and sometimes even times out.
Have an idea?
Thanks

re: Paul. Not true, or shouldn't be. XDCAM HD timeline, XDCAM HD output.
re: Michael. Well, close. I mixdown the edited timeline, then place that into another sequence where I apply a Broadcast Safe filter and hit it with a bit of audio compression. I render that, ridding myself of the dreaded "red lines". However, when I splat-E, I get red lines all over again while I'm exporting. When the export is done, the red lines disappear. Now as an aside, I do experience actual "missing" render files, but that occurs when I quit a project and then re-open it later...they sometimes don't seem to re-link. As I mentioned in this post, I have a feeling that's because this system is set up in the worst way possible (a single RAID5 which acts as system drive and media storage).
Don't blame me, I'm just trying to work within the confines of what I'm given. My major concern here is that it seems to be getting worse.

RPURMP00 program takes too long

Hi Guys,
Need some help on this one guys. Not getting any where with this issue.
I am running RPURMP00 ( Program to Create Third-Party Remittance Posting Run ) and while running it in test mode for 1 employee it takes too long .
I ran this in background during off hours , but it takes 19,000 + sec to run and then cancels .
The long text message is No entry in table T51R6_FUNDINFO (Remittance detail table for all entities) for key 0002485844    and     Job cancelled after system exception ERROR_MESSAGE
I check the program and I found a nested loop within the program (include RPURMP02 ) and decided to debug it with a break point.
It short dumped and here is the st22 message and source code extract.
      ----Message -
" Time limit exceeded ".
"The program "RPURMP00" has exceeded the maximum permitted runtime without
Interruption and has therefore been terminated."
      ----Source code extract -
Include RPURMP02
172 &----
173 *&      Form get_advice_info
174 &----
175 *       text
176 ----
177 * --> p1        text
178 * <-- p2        text
179 ----
180 FORM get_advice_info .
181
182 * get information for advice form only if vendor sub-group and
183 * employee detail is maintained
184   IF ( NOT t51rh-lifsg IS INITIAL ) AND
185      ( NOT t51rh-hrper IS INITIAL ).
186
187 *   get remittance items employee number
188     SELECT * FROM t51r4 WHERE remky = t51r5-remky. "#EC CI_GENBUFF "SAM0632658
189 *     get payroll seqno determined by PERNR and RDATN
>>>>>       SELECT * FROM t51r8 WHERE pernr = t51r4-pernr
191                             AND rdatn = t51r5-rdatn
192                             ORDER BY PRIMARY KEY. "#EC CI_GENBUFF
193         EXIT.
194       ENDSELECT.
Has anyone ever come across this situation? Any input from anyone on this?
Regards.
CJ

Hi,
What is your SAP version?
Have you checked if some OSS notes is there on performance.
Regards,
Atish

Sql Query takes too long to enter into the first line

Hi Friends,
I am using SQLServer 2008. I am running the query for fetching the data from database. when i am running first time after executed the "DBCC FREEPROCCACHE" query for clear cache memory, it takes too long (7 to 9 second) to enter into first
line of the stored procedure. After its enter into the first statement of the SP, its fetching the data within a second. I think there is no problem with Sqlquery. Kindly let me know if you know the reason behind this.
Sample Example:
Create Sp Sp_Name
as
Begin
print Getdate()
Sql statements for fetching datas
Print Getdate()
End
In the above example, there is no difference between first date and second date.
Please help me to trouble shooting this problem.
Thanks & Regards,
Rajkumar.R

i am running first time after executed the "DBCC FREEPROCCACHE" query for clear cache memory, it takes too long (7 to 9 second)
Additional to Manoj: A
DBCC FREEPROCCACHE clears the procedure cache, so all store procedure must be newly compilied on the first call.
Olaf Helper
[ Blog] [ Xing] [ MVP]

RPCPRRU0 takes too long

Dear Experts,
Report RPCPRRU0 takes too long to complete ? We have already tuned Memory , Oracle and other parameters only this job takes too long to complete.
Please suggest
Thanks,
Yoga

@Arjun - After running statistics on the table, it was much better. The Report was running for 15hrs and now its been reduced to 2.30hrs.
@Augusto - Thanks for the information. As you said, Yes, We are also running the payroll for every week . The Job actually runs dedicated BG job server and sometimes we tried running on CI and DB server, still same result.
Could you please share your experience on what are the optimization you done on the report ?
Thanks in Advance,
Yoga

Why does it take too long to open attachments from email account?

It takes forever to download attachments from my email account. I have tried to do the following tasks explained on the vista forum :http://windowshelp.microsoft.com/Windows/en-US/help/6b046ae9-1434-4423-9303-400ff6fe686b1033.mspx#ESD but none of the possible fixes work.
After clicking open on the pop up box asking whether i want to open or save the attachement It takes too long to download it. The transfer window stays open showing that it is ready to download but stays at that bhox window. I press cancel and try to open again, if lucky it opens that file, otherwise it takes forever forceing me to cancel. The files very small files most of the time, usually between 50kb so should take seconds.
I have even tried to save the files but again same process. The transfer box stays open but does not download.
Any one any ideas.
Thanx in advance.

Hello
It is not easy to say what happen exactly but it must be something with email account provider and their page. For me this case is not some typical Vista problem but you can try to find solution on Microsoft Vista IT Pro forum.
By the way: do you have alternative mail address by some other provider? Is there the same situation?

Why finding replication stream matchpoint takes too long

hi,
I am using bdb je 5.0.58 HA(two nodes group,JVM 6G for each node).
Sometimes, I found bdb node takes too long to restart(about 2 hours).
When this occurs, I catch the process stack of bdb(jvm process) by jstack.
After analyzing stack,I found "ReplicaFeederSyncup.findMatchpoint()" taking all the time.
I want to know why this method takes so much time,and how can I avoid this bad case.
Thanks.
帖子经 liang_mic编辑过

Liang,
2 hours is indeed a huge amount of time for a node restart. It's hard be sure without doing more detailed analysis of your log as to what may be going wrong, but I do wonder if it is related to the problem you reported in outOfMemory error presents when cleaner occurs [#21786]. Perhaps the best approach is for me to describe in more detail what happens when a replicated node is connecting with a new master, which might give you more insight into what is happening in your case.
The members of a BDB JE HA replication group share the same logical stream of replicated records, where each record is identified with a virtual log sequence number, or VLSN. In other words, the log record described by VLSN x on any node is the same data record, although it may be stored in a physically different place in the log of each node.
When a replica in a group connects with a master, it must find a common point, the matchpoint, in that replication stream. There are different situations in which a replica may connect with a master. For example, it may have come up and just joined the group. Another case is when the replica is up already but a new master has been elected for the group. One way or another, the replica wants to find the most recent point in its log, which it has in common with the log of the master. Only certain kinds of log entries, tagged with timestamps, are eligible to be used for such a match, and usually, these are transaction commits and aborts.
Now, in your previous forum posting, you reported an OOME because of a very large transaction, so this syncup issue at first seems like it might be related. Perhaps your replication nodes need to traverse a great many records, in an incomplete transaction, to find the match point. But the syncup code does not blindly traverse all records, it uses the vlsn index metadata to skip to the optimal locations. In this case, even if the last transaction was very long, and incomplete, it should know where the previous transaction end was, and find that location directly, without having to do a scan.
As a possible related note, I did wonder if something was unusual about your vlsn index metadata. I did not explain this in outOfMemory error presents when cleaner occurs but I later calculated that the transaction which caused the OOME should only have contained 1500 records. I think that you said that you figured out that you were deleting about 15 million records, and you figured out that it was the vlsn index update transaction which was holding many locks. But because the vlsn index does not record every single record, it should only take about 1,500 metadata records in the vlsn index to cover 15 million application data records. It is still a bug in our code to update that many records in a single transaction, but the OOME was surprising, because 1,500 locks shouldn't be catastrophic.
There are a number of ways to investigate this further.
- You may want to try using a SyncupProgress listener described at http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/SyncupProgress.html to get more information on which part of the syncup process is taking a long time.
- If that confirms that finding the matchpoint is the problem, we have an unadvertised utility, meant for debugging, to examine the vlsn index. The usage is as follows, and you would use the -dumpVLSN option, and run thsi on the replica node. But this would require our assistance to interpret the results. We would be looking for the records that mention where "sync" points are, and would correlate that to the replica's log, and that might give more information if this is indeed the problem, and why the vlsn index was not acting to optimize the search.
$ java -jar build/lib/je.jar DbStreamVerify
usage: java { com.sleepycat.je.rep.utilint.DbStreamVerify | -jar je-<version>.jar DbStreamVerify }
-h <dir> # environment home directory
-s <hex> # start file
-e <hex> # end file
-verifyStream # check that replication stream is ascending
-dumpVLSN # scan log file for log entries that make up the VLSN index, don't run verify.
-dumpRepGroup # scan log file for log entries that make up the rep group db, don't run verify.
-i # show invisible. If true, print invisible entries when running verify mode.
-v # verbose

Indexing and categorization takes too long - why?

I have set up a news publishing system where journalists access a folder and publish their news there using an xml form. So far so good.
Readers of the news access a page with a km-navigation iview that points to a taxonomy folder. The query based taxonomy is set up to categorize news based on property-values chosen by the journalist in the xml-form. This also works as supposed.
Lifetime (time based publishing) is activated for the folder the journalists access to publish their news. Corresponding start and end dates/times for setting lifetime for an article is set by the journalists. This also works as supposed.
BUT: after saving each article the system takes awfully long to actually categorize the news and thereby make the articles visible for others than the journalists. It might be as long as half an hour or so. This also repeats itself every time an article is edited.
I also feel that basic indexing of all other documents in the portal takes too long. I want all new documents to be indexed as soon as they're saved.
Any tips?
Henning

I have set up a news publishing system where journalists access a folder and publish their news there using an xml form. So far so good.
Readers of the news access a page with a km-navigation iview that points to a taxonomy folder. The query based taxonomy is set up to categorize news based on property-values chosen by the journalist in the xml-form. This also works as supposed.
Lifetime (time based publishing) is activated for the folder the journalists access to publish their news. Corresponding start and end dates/times for setting lifetime for an article is set by the journalists. This also works as supposed.
BUT: after saving each article the system takes awfully long to actually categorize the news and thereby make the articles visible for others than the journalists. It might be as long as half an hour or so. This also repeats itself every time an article is edited.
I also feel that basic indexing of all other documents in the portal takes too long. I want all new documents to be indexed as soon as they're saved.
Any tips?
Henning

MAcbook takes too long to boot

From one day to another our macbook takes too long to boot. The problem is since we push the power button until the first grey apple shows up, it can take up to 30 seconds. Since the apple shows up it boot in a few seconds. All the process up to 1.20 minutes.

Also... once you are in OS X, go to System Preferences and Startup Disk. Make sure your OS X volume is selected. Sometimes this can change causing your system to look for another startup disk... and it needs to "time out" before it moves on to the next. This is most common after removing a BootCamp installation of Windows... but can happen for any number of reasons.

11gR2:crsctl, srvctl commands takes too long to respond

Hi,
I have successfully configured *11gR2 two node RAC on ASM on Win 2008 64bit.*
Everything work very well like connecting to database, querying database. Node restart also takes acceptable time to go down & restart the clusterware & database.
But when I execute crsctl status resource -t or srvctl status database -d db_name commands from any node takes 10-15min to give output.
They give output & everything completes successfully but takes too long to respond.
The questions are:
- If everything works fine then why crsctl, srvctl takes too long to respond?
- what could be blocking these command to gather clusterware and database status on all nodes?
- what additional info would be helpful that I can provide?

dag wrote:
I dont have this issue either. are you auto starting mpd?
that time is how long it is up in other words you opened it then closed it at that time
I'm not sure if you are referring to me or not, but in my screenshot I am timing the lag in ncmpcpp by pressing 'q' in the terminal during the delay, so it quits ncmpcpp immediately after the lag. The lag is longer for ncmpc because the interface loads before the program connects to mpd, so I have to stop it manually immediatly after it connects.
WonderWoofy wrote:I don't have this problem... if you are starting it as a systemd user service, maybe there is relevant information in the journal.
The journal did not reveal anything relevant sadly. I have now tried launching mpd without systemd, and the lag remains. I have also noticed that a small mpd programming project I am writing also experiences the same lag when it tries to connect to mpd.

After effects takes too long to render, broadcasting time is soon, so I'm in a lot of trouble!!! :(

Similar Messages

Maybe you are looking for