Reason for "RAM Preview Not In Realtime" error

I think I found a reason for why the "RAM Preview not in realtime" error pops up on the OSX version of AE. If you have your desktop background set to change every X seconds, the preview seems to suffer from that process going on in the background. Having OpenGL enabled/disabled doesn't seem to make a difference. Disabling the background image from cycling seems to remove any existing playback inconsistencies. This might have existed in earlier versions of AE than I'm using right now (as well as earlier versions of OSX), but I can't confirm that. The system I'm on is a 14GB 2.8 octocore, GeForce 8800GT, raptors & barracudas,OS 10.5.6, AE CS4 (updated).
If others can confirm this behavior, we can submit it to aebugs.
Thanks, and Happy Holidays!

Whoops.
Well, what I meant to say was, I think I found a reason for why the "RAM Preview not in realtime" error pops up on the OSX version of AE. If you have your desktop background set to change every X seconds, the preview seems to suffer from that process going on in the background. Having OpenGL enabled/disabled doesn't seem to make a difference. Disabling the background image from cycling seems to remove any existing playback inconsistencies. This might have existed in earlier versions of AE than I'm using right now (as well as earlier versions of OSX), but I can't confirm that. The system I'm on is a 14GB 2.8 octocore, GeForce 8800GT, raptors & barracudas,OS 10.5.6, AE CS4 (updated).
If others can confirm this behavior, we can submit it to aebugs.
Thanks, and Happy Holidays!

Similar Messages

RAM Preview - Not in realtime

Hello
On my computer, whenever I try to playback somehting to see a preview, it plays at 17 frames per second, with red text saying, Not in realtime. Is there anyway that this can be remedied?

Make sure you are depressing the Zero key for ram preview. I bumped into this the other day because I had selected AJA Kona as my display option in Preferences. When I switched it back to Computer it played back in real time. The other reason might be a very complicated sequence on a computer with slow processers or not enough ram. You always need to share the details of your system when asking questions like this so folks know what you are using.

Reasons for billing documents not being created ?

I am trying to create a billing document from a delivery (VF01). When I enter document number and save, it says 'no billing documents genereated, see the log'. Where to see the log and what do you think could be the possible reasons for billing document not being created ?
Thanks in advance,
Krishen

Hi,
In VL02 transaction, Its the 2nd button on the toolbar With an `!` mark on the icon along with triangle. CLick that button. It will display the errors bcz of which delivery is not created.
In VL01, goto EDIT-> LOG.
The explanation of errors is usually pretty detailed.
Best regards,
Prashant

HT201335 Any technical reason for iPhone 4 not to have mirrorring feature?

Any technical reason for iPhone 4 not to have mirrorring feature? It does support YouTube , photo slide show.

Airplay mirroring requires an h.264 encoder in hardware. iPhone before the 4s and macs before mid 2011 don't have this hardware, so it won't work.

EM Jobs Service is down (fatal). Reason - "Reason for delay could not be determined"

Hi all -
I'm having a problem with my em jobs service. It's listed as down. Severity is "Fatal". For the incident creation DATE it has the following:
"Reason for delay could not be established."
Note that it's the DATE column where it ways that the reason could not be established. Under "message" it has Dec 28, 2013 8:46:29 PM.
Target Name
Target Type
Severity
Message
Incident Creation Date
Incident Last updated Date
Escalation Level
EM Jobs Service
EM Service
Dec 28, 2013 8:46:29 PM
Reason for delay could not be established.
Jan 27, 2014 7:48:44 PM
None
Does anyone have any clue as to why this is happening and/or how to fix it?
Thanks,
Tom

Hi,
Follow the below steps
1. Click on Repository Database Target in Cloud Control
2. Navigate to : Administration -> "Oracle Scheduler" -> Home -> click on "Oracle Scheduler" it will return, "Scheduler Jobs"
3. Check that the scheduled jobs are running at their correct schedules. Check if the "EM_JOBS_STEP_SCHED" job is disabled.
4. Select "EM_JOBS_STEP_SCHED" and click on "Edit job Definition" ensure that the job status is "enabled". Then click apply.
5. Check the "EM Jobs Service" status , it should now be shown as UP.
Also
1. Login to 12c Console, Targets --> All Targets --> EM Jobs Service
2, click on Monitoring Configuration tab
3. click on System Configuration
In the Availability Definition screen, under Key Component column, check all the check boxes
4. Similarly, in the System Configuration screen, under Key Component column, check all the check boxes
Wait for 5 minutes and then check the status of the target again.
Regards,
Rahul

HD RAM preview not playing in realtime through Blackmagic

I've recently upgraded one of my company's Blackmagic Multibridge Pro NLEs to CS5:
PROBLEM:
AE CS5 does not play realtime RAM preview of HD1080 video when displayed through the Blackmagic video output (even as low as 1/8 resolution).
INFO:
1.) Lowering resolution (even down to 1/8) does not help.
2.) Matching scale % to resolution % does not help.
3.) Doing #s 1-3 in combination gets very close to realtime, but CS4 did not require all of this.
4.) If I switch AE output to "computer monitor only" I get realtime.
5.) SD comps played through Blackmagic output achieve realtime.
In CS4, HD Blackmagic output WAS realtime. I have made all memory/multiprocessing settings match the CS4 configuration, but this has not helped.
Also, both AE and the Blackmagic driver are the most current version. I have no desire to revert to CS4... Anyone have any ideas?

To answer my own question:
I lowered the project's color settings to 8 bits per channel--and now all HD RAM previewing (even at full resolution) seems to be playing back realtime!
Hope this thread can be helpful to anyone else experiencing the same issue.

Multiprocessing works for RAM preview, extremely slow and aeselflink crashes when in Render Queue

Hello all,
System specs:
Hackintosh
OSX 10.9
3.5Ghz (overclocked to 4.2Ghz) Core i7
Geforce GTX 580 classified 3GB Cuda GPU
AMD Radeon HD 6870 1GB Display GPU
32 GB of RAM
System SSD
5 drive internal RAID
After Effects CC 12.2.1.5
Cuda drivers up to date
I'm having a problem with the render queue and multiprocessing. I have a moderate sequence with several effects and 3D layers. When I'm working in the composition, everything goes great. I can RAM preview and all my CPU cores will kick up to 100% and render the composition in no time all; with full resolution with no skipped frames. It works fantastically.
Then when I go to render the exact same composition with the same multiprocessing settings, AE will hang at the "initializing background processes" for at least 5-10 minutes, during which the CPU will ramp up to 100% but no frames will be rendered. AE still remains responsive, as I can hit the stop or pause buttons and the queue will be cancled. But then the aeselflink processes (up to 8 of them depending on my settings, I've tried several) will still continue at 100% cpu load even with AE not set to render anything. I will have to go into the activity monitor and force quit each process. If I leave it for 5-10 minutes, it will finally stop initalizing and start the render, but the CPU will still run at 100% but the frames will crawl slowly forward at about 1 frame per minute, with an estimated 28 hours to render frames that were rendering in under a minute during RAM preview.
I have tried both reducing the number of cores AE will use, adjusting the allocated RAM, and disabling multiprocessing alltogether. When I disable multiprocessing, the render slows to a complete crawl, and it will render around 1 frame every 5-10 seconds. Again, this is on a composition that rendered in less than a minute on full resolution with RAM preview.
The only way to get this composition to render is to export it to Media Encoder, which will render it (without multicore processing, unfortunately) in about 8 minutes, still not the blazing fast RAM preview but at least it finishes it in under 3.5 hours (the amount of time that the multiprocessing disabled render in AE will take).
Here's the multiprocessing settings that have been very stable and carried me through other projects. Disk Cache is not enabled. The only other thing that is disabled is the "Disable Layer Cache" under the Secret menu as the plugins I'm using (Plexus 2 in this case) doesn't like to update when the camera moves so this option has been disabled to force it to reset each frame.
Does anyone know what is going on?
Also, please don't tell me that I should not use multiprocessing or instruct me on basic steps as to increase preformance on my machine. I have been tweaking my memory and multiprocessing settings for a long time now, and it is completely stable in everything but this setup. So please no answers saying "just don't use multiprocessing". It was made for a reason, it's effective, and it's needed. And please don't say that it's the hackintosh, either, as it's the most stable and powerful computer I've ever used. Sorry for the disclaimers, I just want to have constructive help.
Thank you in advance for your ideas!

Hi Rick, not sure if you saw the part where I said please don't reply with turning off Multiprocessing, and I did not say that it works and is effective in all areas. However, if you actally take the time to read my post, you will definately notice that RAM preview with multiprocessing takes under a minute to render a scene. Multiprocessing disabled and rendered in AE takes 3.5 hours. In Media Encoder it takes around 8 minutes. Clearly it IS working and IS effective for my case and my rig. Any vendettas against MP does not help my situation at all.

After Effects will RAM Preview not in real time

Hi, we have 3 adobe After Effects CC up to date here, we are working on a 60fps project in HD 1080. Nothing crazy.
We have 20 Gigas of ram. Mac OS 10.8.5 octo core 2011. ATI Radeon HD 5870 1024 Mo. SSD disque crucial m500 256 gigas.
We have a lot of problem with Ram Preview. (on every project)
Everything works fine until, we don't know why, the ram preview is getting not realtime, like 30fps or under.
Sometimes purge memory do the trick but not always.
We need to reboot and it works again, but few minutes.
We made a test on CS5 and it works well realtime, but same problem on CS6.
I tried to delete all the preferences to check but no difference.
We are working with nfs network account but i always redirect disk cache to local disk (set to 20 gigas) and also media conformed cache (database and cache)
We are getting mad, it's really hard to work that way, rebooting each time.
Maybe an issue with Global performance cache introduced in CS6 ?
It's not a footage/project issue because the entire project (a blend of tiff, png, prores422) can be played 120 frames/sec without any problem on after CS5, after CS6 (when it works), CC (when it works).
The problem is when working on project, changing layers, adding effects, After CC starts not be slow and not realtime using Ram Preview.
Also, when we are previewing, a lot of ram is not used, it only uses like 20% of the ram.
We hope for a nice patch very soon ....

60 fps is a very high frame rate not usually supported. If your footage is shot at 60i then it is probably 29.97 fps when converted to progressive video. If the footage is actually 60 fps then you will be better off, and by better off I mean more folks and streaming services will be able to view your video at the proper speed.
So my recommendation is to first determine your audience and then set up your comp appropriately. In all my years in the business I have only delivered one high frame rate project and that was 48 fps.
The other thing I would recommend is to optimize your system for AE. That does not necessarily mean throw all your available ram and processors at the app. There are some good recommendations here: Optimizing After Effects Performance

CC 2014 space preview not in realtime

Hello, I just recently purchased an 27-inch iMac, and installed the trails for CC 2014 fully updated and found that After Effects would not render in realtime when I pressed space. I would RAM preview it and it would be fine, but when I pressed space I was getting 20fps out of the 25 comp, even when it was fully rendered and cached. I am using the GPU settings, and have turn on/off the render multiple frames and that has not fixed the problem.
I have done compositions in 4k, 1080p, 720p and even created a 10 pixel x 10 pixel composition with only a single solid and it still only renders at 20fps when I press space. I have also created a composition with nothing in it at all at the aforementioned resolutions and when I press space I get 20fps not realtime. I have tried different preview methods (Full through to quarter) and fast draft, full and adaptive, and still getting the exact same problem.
Any help on this would be very grateful.
iMac Specs:
iMac (27-inch, Late 2013)
Processor: 3.4 GHz Intel Core i5
Memory: 16 GB 1600 MHz DDR3
Graphics: NVIDIA GeForce GTX 775M 2048 MB
OS: OS X Yosemite 10.10.1

Hi Rick, thanks for your response.
I am aware that After Effects is not a video editor, I come from 10+ experience in Adobe products, at work I use iMacs and Macbooks all the time and have never had this problem when it comes to trying to render a simple solid or even nothing. What I'm saying is that now, on my new home iMac, if I try to render NOTHING through the basic preview, I'm getting frame drops, which is something I don't understand.
I'm getting frame drops on a composition that has already been ram previewed and cached, and at work I can press space and get full 25fps playback (of course, if I press space with unrendered footage it will framedrop as it renders it, then if I press space it is back to 25fps playback). I'm getting framedrops on a 4x4 composition with nothing in it, it's like the basic preview is capped at dropping frames no matter what, and it's very frustrating being used to realtime space previewing after the composition has been rendered.

Black magic and Adobe After effect cs6 Ram Preview not real time

Hello,
I'm on a MAC PRO with the OS 10.6.8 and 8Go Ram, the problem is when i turn on my preview video on the Blackmagic the video monitor is not in real time and the after effect is so slow. When i put it off (computer monitor only) it's ok but i havn't my video monitor of course....and i need it. Is there some tricks for having my black magic (1080 i 50) ON and a RAM Preview in real time ??? ! My drivers Black magic is the 9.5.3 it's the highest driver for MAC OS 10.6.8 + ADOBE CS6+ FCP7. Thanks for the read. ( i tried update adobe, change qt library, change aspect ratio, pixel, preview ram settings, change drivers black magic and other but nothing work )

What is the color bit depth of your project? (8, 16 or 32?) Have you changed that recently, or have you changed the frame rate or frame size of your comp?
Performance with video preview to an external monitor is almost always related to the pure bandwidth requirements of the frames you're sending to it. If the frames require more memory, it may be slower. Frame size, frame rate, and color bit depth all affect the memory requirements of the frames.
If none of those parameters has changed, troubleshoot the general performance of your machine. If there are other processes (look in Activity Monitor) that are using significant processor and/or memory resources, they may be causing a bottleneck for the frames getting out.

Process Order API -Reason for change either not provided ...

I'm calling Process Order API to update shipped_quantity for a RMA receipt. Nothing has changed about this code but now I am getting :
"The reason for this change is either not provided or invalid. (OBJECT=ORDER) "
We installed a patch last weekend to speed up Ship Confirms I wonder if we went backwards in OM. Any suggestions ???
Process Order code snipet:
l_header_rec.header_id := p_header_id;
l_header_rec.operation := oe_globals.g_opr_update;
l_line_tbl(1) := OE_ORDER_PUB.G_MISS_LINE_REC;
l_line_tbl(1).line_id := p_line_id;
l_line_tbl(1).shipped_quantity := p_rec_qty;
l_line_tbl(1).shipping_quantity_uom := 'EA';
l_line_tbl(1).flow_status_code := 'RETURNED';
l_line_tbl(1).operation := oe_globals.g_opr_update;
Call Process_Order
OE_Order_pub.Process_Order(
p_api_version_number => 1
.

Please review the documentation about process order API as there are several things you might want to revisit about this call to process order:
Following are my observations:
- you are updating shipped quantity. I think this field shoud not be updated using the API. As it shoudl be updated by a process(shipping process)
-You are also trying to update the flow_status_code. This field is also not supposed to be updated.
My suggestion is that you try to follow the same process step by step that one should follow to update the shipped_quantity on RMA order. (e.g. receiving the item against the order using inventory api's or probably shipping the order line using the shipping api's). I am afraid, using the given code you might create data discrepancy.
Hope this helps,
Nitin Darji

Ram Preview not working correctly

On one machine here, when the artist goes to do a ram preview, they only get grey frames in the comp window. Either that or they get a freeze of the first frame in the render region, but no motion.
I have tried deleting prefs, zapping Pram, deleting the cache, purging memory. turning open GL on and off, all to no avail.
Any thoughts?
Thanks in advance
Sam DeWitt

I'm not sure if RAM issues really show up during normal work. In most cases the operating system will constantly rearrange the memory allocation, so it may never touch upon that one damaged memory block. You wouldn't even know it, if it caused a crash once a week, because it could be anything. I'll admit that it's a far shot, but nonetheless one should not rule out what seems to be impossible at first sight. the only other thing I can think of would be a tool that suppresses screen refresh, which could be some widget ort system extension...
Mylenium

Ram preview not playing from first frame

Anyone else having problems with Ram preview playing back from a different spot in the timeline OTHER than the first frame? I have seen this happening consistently since the latest update (2014.2). I checked my preferences, and made sure nothing is accidentally selected to play from the last keyframe or something odd. But no. I am on a Mac Pro, running Yosemite, I googled this, and haven't seen anything. I haven't trashed my preferences yet, because I'm not sure it's a preference issue, and god...if I have to rebuild my render setting one more time...
So to give you more detail.
- I hit "0" on my number pad to launch a ram preview
- It LOOKS like it's rendering each frame in order
- When I hit "0" again to playback, it starts from a random location usually about 2 - 5 seconds from the beginning of the timeline.
- It will loop back and then play from the start of the timeline.
It's not using the current time indicator line or anything that would make sense. It's random, but near the start. I suspect it's pulling keyframe information from a nested pre-comp and using that, but there is not a keyframe in the comp I'm previewing.
I also do not have the "From Current Time" checked box in the Ram Preview options, and there are 0 skip frames in that setting as well.
If anyone has any ideas what this may be...I'd appreciate it.

Here's the page with the known Yosemite issues:
After Effects with Mac OSX v10.10 (Yosemite)

After Effects RAM Preview not showing first 50 frames or so - Mac OS

So I'm on a 2012 iMac, and when i RAM preview, it plays audio but video does not show until about 50 or 60 frames in, its like a glitch or lag thats started recently, so it makes ram previewing from a certain time a real pain as i then miss the exact part i want and it c matches up with video a second or two later, i can't find any solutions, please help!!

As Andrew says, Adobe and Apple are working on figuring this bug out. See the known issues section of this page: After Effects good to go with Mac OSX v10.10 (Yosemite)
If you let the RAM preview loop at the end of its playback and play through again, it should be smooth and issue-free.

How to track reason for Preventive maintenance not completed?

Hi Gurus,
We know that when Maintenance plan was created then base on that maintenance call objects should be generated at particular date specified in Plan. I have requirement that due to certain reason (e.g. Machine not available due to production) if this preventive maintenance not completed at specified date, so how we can assign these reason for call objects (Notification/Order).
Thanks in advance......

I'd suggest using either
1) Confirmations with Reason Codes
or
2) Notifications with Catalog Codes
or
3) User Status profile on Orders.
EDIT: Note that for the former you might need to first have the Orders released, which might not be desirable, and you can't use this in conjunction with the "Do not complete" / "Wrap" / BABL transaction (to set status NCMP). The latter two options don't have this constraint.

Reason for "RAM Preview Not In Realtime" error

Similar Messages

Maybe you are looking for