AME render time 2x SLOWER in CS6 than CS4
I just upgrade to CS6. A good portion of my projects are very long continuing professional education videos for streaming on the web. AME4 could render an 8-hour video into baseline, H264 700x290 in about 12 hours. (I know, strange, custom frame size. It's for side-by-side speaker and overhead presentation.) I opened the same CS4 project in CS6. It was resaved for the new version. I also created a new sequence and copied the files over, just to be sure. With EXACTLY the same export settings, render time is about 27 hours!
AME4 was not a 64 bit app, whereas AME6 is. So, my 16 GB of ram should be put to better use, I would think. According to Premiere, ram available for other apps is around 13GB. In task manager performace, processor is at the ceiling but memory use is only 6GB:
System specs are:
Media drive is Western Digital Caviar Black 2 TB SATA III 7200 RPM 64 MB Cache
GPU= AMD RADEON HD 6570 DP 1GB PCI EXPRESS 2.0 X16
How can I get AME6 to access more memory? Why in the world would the render speed more than DOUBLE with a newer version?!? Any suggestions would be greatly appreciated!
Yes. A CUDA card is on my wishlist, but my company may be tapped out for a while after new ram and an upgrade to CS6.
I did queue this one. I wasn't aware that this would make a difference. I'll try the direct export method next time.
RE: "encoding times have increased with the newer more feature rich versions" Really? So was I just mislead/misinformed that a 64 bit version of this encoder would be faster? Wow, that sucks. But is there no way for AME to access more than 6GB of my ram? I guess the slowness may be the price you pay for stability. My 8-hr project failed two times in AME4. I have 5 hours left of encoding on AME6. It's my last, best hope for being able to deliver this project on time.
Similar Messages
-
Render times in Premiere Pro CS6
In this otherwise very helpful article (link below) can anyone tell me if the numbers referred to in this table are hours: minutes, or minutes: seconds? In other words, by 8:16, do they mean 8 hours and 16 minutes, or 8 minutes and 16 seconds?
http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/products/creativesuite/produ ction/cs6/pdfs/adobe-hardware-performance-whitepaper.pdfminutes & seconds.
-
Render times very slow on new Mac Pro and Premiere CC
Hi there
I have a brand spanking new Mac Pro (specs below) working off a G Studio r 24 TB array. Rendering anything in Premiere is taking an age (2 minutes timeline is taking 30 minutes). I am cutting 4k Sony F5 footage (XAVC). I have done tests with 1080 material and this doesn't make any difference.
I have spoken to Adobe support and reset permissions plus all the basic workarounds suggested: but there has been no improvement. I was due a call back but have not heard anything.
Can anyone suggest a solution - i have several important deadlines coming up, and can't really deal with the downtime.
I understand 3rd party apps take longer, but even with PP effects, rendering is taking way too long: especially with a super fast system like this.
Regards
Louis
YOSEMITE 10.10.3
Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: 8-Core Intel Xeon E5
Processor Speed: 3 GHz
Number of Processors: 1
Total Number of Cores: 8
L2 Cache (per Core): 256 KB
L3 Cache: 25 MB
Memory: 64 GB
Boot ROM Version: MP61.0116.B11
SMC Version (system): 2.20f18
Illumination Version: 1.4a6
Serial Number (system): F5KPD0DDF694
Hardware UUID: 8975F4BE-0140-583C-9615-E3BD60BEC8F2If you go to the menu File > Project Settings > General and set the Renderer to Software Only, any change?
MtD -
3D Render is different in Photoshop CS6 vs CS4 when edited
Hope you guys can help me, because I’m really clueless on what changed in CS6 that is causing this. We have a 3D file that has a layer where we can change out the labels. The things is this, when I open the file in CS6, and try to edit it, the appearance totally change. Instead of seeing the full bottle with the label, it shows a dropper in black. Prior to the switch to the new Photoshop, I was able to modify the same file in CS4 with no issues. Is there a way I can modify the label of this 3D without it losing all of its render data in CS6?
Example of Render when not touched.
Example of Render when modified.Below is the System information.
System Information
Time of this report: 2/19/2015, 14:05:35
Machine name: NR102
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
Language: English (Regional Setting: English)
System Manufacturer: Hewlett-Packard
System Model: HP Compaq 6005 Pro SFF PC
BIOS: Default System BIOS
Processor: AMD Athlon(tm) II X2 B22 Processor (2 CPUs), ~2.8GHz
Memory: 12288MB RAM
Available OS Memory: 12284MB RAM
Page File: 10292MB used, 14272MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
Display Devices
Card name: NVIDIA NVS 300
Manufacturer: NVIDIA
Chip type: NVS 300
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_10D8&SUBSYS_0862103C&REV_A2
Display Memory: 4050 MB
Dedicated Memory: 466 MB
Shared Memory: 3583 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: EB2442
Monitor Id: GSM5942
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 8.17.0012.9708 (English)
Driver Version: 8.17.12.9708
DDI Version: 10.1
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 7/28/2012 09:43:00, 17682280 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-5398-11CF-6056-6E281CC2C535}
Vendor ID: 0x10DE
Device ID: 0x10D8
SubSys ID: 0x0862103C
Revision ID: 0x00A2
Driver Strong Name: oem13.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section034:8.17.12.9708:pci\ven_10de&dev_10d8&s ubsys_0862103c
Rank Of Driver: 00E60001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
Card name: NVIDIA NVS 300
Manufacturer: NVIDIA
Chip type: NVS 300
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_10D8&SUBSYS_0862103C&REV_A2
Display Memory: 4050 MB
Dedicated Memory: 466 MB
Shared Memory: 3583 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: EB2442
Monitor Id: GSM5942
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 8.17.0012.9708 (English)
Driver Version: 8.17.12.9708
DDI Version: 10.1
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 7/28/2012 09:43:00, 17682280 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-5398-11CF-6056-6E281CC2C535}
Vendor ID: 0x10DE
Device ID: 0x10D8
SubSys ID: 0x0862103C
Revision ID: 0x00A2
Driver Strong Name: oem13.inf:NVIDIA_SetA_Devices.NTamd64.6.1:Section034:8.17.12.9708:pci\ven_10de&dev_10d8&s ubsys_0862103c
Rank Of Driver: 00E60001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled -
Render times: what is expected?
Hello,
I recently went to render a project, and it estimated that it would take 44 hours to complete. That is, shall we say, less than ideal.
Some specs about my machine:
MacBook Pro
2.6 GHz Intel Core i7
16 GB 1333 MHz DDR3 RAM
The Disk Cache:
LaCie USB3 External SSD (200 GB allocated for cache)
Details about my AE project:
AE version: CS6
3:15 (3 minutes 15 seconds) duration
1920 x 1080 (1080p) resolution
Ray-traced 3D environment
17 light layers
3 cameras
All other layers are either shapes, solids, pictures, or pre-comps
I'm trying to render out to h.264 format. It seems to me that 40+ hours is extremely excessive for a 3:15 long video, but I'm not positive that's the case. I'd love to hear thoughts back on expectations and how I can reduce this time (either through settings or better hardware).
Thank you!rhannebaum wrote:I chose H.264 because it seemed the most common HD video output, and I didn't want to use QuickTime (.mov) because the resultant .mov files were huge. Very hard to transfer around after the fact.
Oh, I was pretty sure that was your reasoning.
Yes, the resulting file will be huge (unless you're rendering to an image sequence in which case the mass of resulting files will be huge ) . You then take that file (or image sequence) into Premiere or the Adobe Media Encoder to create your easy-to-transfer file - in your case, h.264 is probably your best bet. But, for the reasons I enumerated, you do not want to do the h.264 right out of AE.
There are other options to a lossless Quicktime or an image sequence (although the crashing rescue alone is worth the image sequence option). Where I work we use the Cineform codec from GoPro. It's free and it's close enough to lossless for our workflow, but the file size is significatly smaller. Another great choice is the DNxHD codec which is free from Avid. It has the same benefits as the Cineform codec.
rhannebaum wrote:
Are image sequences simple to import into Premiere? Also, is Media Encoder faster at rendering than AE? I know the obvious benefit is that I can keep working in AE while a comp renders in Media Encoder, but not sure beyond that what ME's value is.
Image sequences are as easy to import into Premiere as any other video format. It's great!
Media Encoder is not faster than AE - and, in some cases (as others have mentioned), it can be much slower. However, it does a much better job of encoding H.264. The quality is higher for the same data rate. That (among other reasons) is why, in the new version of AE CC, the H.264 render option has been deprecated.
For your workflow, I would not suggest sending your AE comp to the AME; render a lossless (or nearly lossless) file out of AE and then use the Adobe Media Encoder to create your final deliverable.
One cool thing about the Adobe Media Encoder is that you can set up watch folders so that any time an uncompressed file lands in that folder, it gets encoded per your specified settings.
rhannebaum wrote:
Is Cinema4D a plugin native to AE CC? I'm afraid my upgrade options are limited to what my company approves, but if there is a legit improvement in render times in CC over CS6, that may seriously persuade them...
Cinema4D is the industry standard 3d animation software for creating motion graphics. It's also got some good scuplting, modeling, and character animation tools and is fast becoming one of the big players in all aspects of 3d animation. One of the reasons for its rapid growth (besides the fact that its easier to learn than its competition) is that it integrates very well with After Effects.
Bundled with (and integrated with) AE CC, you get a lite version of C4D. It doesn't have nearly the power of the full program, but it's worlds better than messing with the 3d ray-traced stuff and gives you a lot more tools to work with.
Bottom line: if your company is going to want you to do more 3d stuff, you really need to get into a plugin like Element, 3d Invigorator, or ShapeShifter. They render much faster.
And, if they really want you to do some great 3d, they'll need to get a full-fledged 3d program for you (and the requisite training). Upgrading to the CC version of AE is a great halfway step though. -
Help - Getting slower render times with AE CS6
Hi everyone
Wonder if anyone else is getting as described?
I have a 3m37s project which is predomnantly motion graphics using live shot footage (.MXF files), Illustrator and a few JPGs.
In CS5 AE I get render times which average around 45mins, so I thought I'd see how quickly CS6 could crank it out by - as you can see I'm getting times which are in excess of 2 almost 3hours!
The project contains a few 2.5D moves as well as tiny bit of Trapcode 3D Stroke
I have mentioned on this forum that I'm having the Error 5070 problems with start up and Ray Trace is unavailable but these times seem seriously wrong to me.
Mac Pro 3,1 (2x 2.8GHZ)
20GB RAM
OS 10.7.4
NVIDIA GeForce GT8800
NVIDIA Quadro 4000 both on GPU Driver 207.00.00.f06
CUDA Driver 4.2.10
All files are on a 2TB drive (7200rpm)
Rendering to a 1TB drive (7200rpm)
Corsair SSD 60gb Cache drive
As an observation when I watch the frames counter ticking over, CS5 seems to steadily work it's way through the render at around less than a frame a second, CS6 seems to crank out 2-6 frames then hold for 30secs before working on another batch. It crawls to a halt near the end.
Can anyone offer any help or advice?
So far I'm not having a great time with my CS6 transition
Thanks
Rob
Message was edited by: Bokeh Creative Ltd
because of a TypoThanks Rick - Yes what confused me was that it only took 45mins in CS5 even with MP 'on'
Still having no joy with Ray Tracing though, even though I have a Quadro 4000 card, I get the 5070 error on start up. Any ideas? -
CS5 on mac 10.6.4 slows system to a crawl, render times really long
We recently upgraded our towers to 10.6.4 and all productivity has slowed to a snails pace using After Effects. On 10.5 the speed was almost TOO fast on our renders...it was awesome. Now I'm looking to get that speed back.
I have a few very simple comps. 1920 x 1080, 23.98fps, 5 layers (4 QT renders from final cut XDCAM and Animation codec, 1 adjustment layer with levels and hue/saturation for color correction). Approx 40 seconds long each.
I've followed the Adobe advice of turning the multiprocessing on and using the following settings from here http://forums.adobe.com/thread/543440
leave 4gb for other apps, set minimum 3gb per processor = 33min render
setting it back to what WAS screaming fast on 10.5:
leave 3gb for other apps, set minimum 0.75gb per processor = 19min render
turning multiprocessing off = 5min render
same project on 10.5 system with multiprocessing turned ON with the above mentioned settings = 2min render
what is going on here? is there a compatibility problem with CS5/10.6 and Animation codec files? that seems to be the bulk of the slowdown, but still over twice as slow?
additionally, when AE is rendering the rest of the system becomes unusable...every action, even dragging a finder window around, results in beachballs and a 30 - 40 second lag in response. this happens with or without multiprocessing.
I just want to get back to work...any ideas on how i can configure this beast to get back to my former speeds?
8 core mac Pro
OS 10.6.4
12gb RAM
many thanks in advance. i'm willing to send beer for a winning fix.Good to know, thanks for the update. 10.6.x does manage memory differently, but our testing for performance has shown a slight improvement in the newer OS. So I am guessing that the OS update is not the issue. I just ran another test on a Mac with your configuration and saw a 4% improvement on 10.6.4 over 10.5.8.
It's uncertain what state the system memory was in when you started your tests. That's why I asked for a restart of the computer. The times reported seemed like there was a possibility that the OS was swapping. XDCAM footage places a high demand on system resources. But it's hard to say without being there.
What I was seeing with the initial post was that the two extremes of allocation per background cpu were tried, but not the middle ground. To better see this, launch the Activity Monitor utility or look at the last line of the MP preference. With the 4GB reserved and the 3GB/ bkgnd cpu setting you weren't getting any extra processes spawned for multiprocessing. You can see this in the preferences multiprocessing section as "Actual CPUs that will be used = 0". Then, by setting the pref to .75GB/bkgnd the app launched 8 bkgnd processes, but for the task at hand, I am guessing that they were starved for memory and sometimes failed to render. This was faster than the first test, but still slow. By setting the pref to 1.5GB/bkgnd cpu you were now getting 4 new processes spawned for multiprocessing. The background processes had enough memory to succeed so that made it render faster still.
Now, try setting it to 1GB/bkgnd cpu. That will launch 6 processes which should render faster as long as that is enough memory for the task. If the Memory pref for Reserve RAM for other apps is set back to 3GB, it will allow the spawning of 7 bkgnd processes. If that is a successful balance for this project then it will be the fastest render time. But, our testing shows it will be at the risk of starving the OS for memory, thus the more conservative 4GB recommendation for a 12GB system.
It's a fine line and why we are recommending that one give up a little speed by reserving more memory for other apps. True, there will be less processes spawned for multiprocessing, but there will also be less chance for the OS to start swapping to disk which greatly slows down performance for all tasks. If that compromise is not acceptible, then the alternative is to buy more ram so that all 8 processes can adequately receive enough memory for the job, and yet still maintain adequate reserves for the OS and other apps. -
Render times of certain project slow down
Hi,
i have a certain tv-promo-project where i have to render several comps which all include the same amount of text and just a hand full of additional graphic elements, e.g. a lensflare and a glowing line which separats the text blocks.
The text of the specific promo-comps are read out of a "main text comp" by expressions. The expression is as follows:
txt = comp("Master Textkomposition").layer("Textebene").text.sourceText;
txt.split("\r")[0]
The rendertimes of the project are constantly slowing down as the render queue and the process goes on. The first comp takes about 8 Minutes to render (it is only 10 sec long) and the second already 20 min, where the third comp reaches like 2 hours of render time.
I also recognized that even the preview in the timeline is really slow, although the used effects are usually not that performance heavy.
My System specs:
After Effects CS6 11.0.4.2
Mac Pro 5,1
Processor 2 x 2,93 GHz 6-Core Intel Xeon
RAM 24 GB 1333 MHz DDR3 ECC
Graphic NVIDIA GeForce GTX 680 2048 MB
Software OS X 10.8.5 (12F45)
Drive c: 500 GB SSD (Apps & Disk Cache)
Drive d: 2 TB HDD (Project & Source Media)
Drive e: 1 TB HDD (Render & Media Cache)
Does anybody have a clue what this problem could be about?
Any help is appreciated
Cheers
paulThanks for the advice aka danke für den Tipp!
I'll give it a try!
Paul -
Slow render times with large jpegs - complete system lag
In a project i'm working on I have two large jpegs with a small zoom scaling effect. Going from 100 to 103 percent.
I've noticed that both Adobe Media Encoder and Premiere Pro experience a heavy slow down in render time as soon as the jpegs have to be rendered.
Not only does the render speed almost come to a halt, the complete system lags very heavy, even the mouse cursor won't respond well.
This happens when i have GPU acceleration enabled and when i do a 2 pass H264 encoding.
When I have the GPU acceleration disabled the render goes very smooth, and doesn't seem to slow down...
The jpeg is 4023 x 2677, and 6,97 MB large.
Scaling the jpeg down to about 1920x1080 in Photoshop and put that one in the timeline made the render go a lot faster.
I understand that a large picture takes a bit more time to be rendered, but we're talking about a 10minute render whit the large jpeg file and a 2 minute render with the jpeg resized.
The total time of the two jpegs in the video is 5 seconds in a 3 minutes video.
So, that made me think that the render times are exponentially long.
In the timeline everything runs really smooth.
Is this considered normal, I can't remember having such big differences in CS5. It's not a major thing, but I wanted to share anyway.
My system:
Premiere Pro CC (latest)
i7 4930K
32 GB RAM
2xGTX480
Footage and project on a Raid0 disk
Previews/Cache on a Raid0 disk
System and Premiere on SSD
Render to a single 7200 rpm drive.>wanted to share
Yes... known issue... I think some of the below is about P-Elements, but the same ideas
Photo Scaling for Video http://forums.adobe.com/thread/450798
-HiRes Pictures to DVD http://forums.adobe.com/thread/1187937?tstart=0
-PPro Crash http://forums.adobe.com/thread/879967 -
After Effects CS6 super long render times.
I am trying to render multiple 30 second long compositions and the renders are reaching over 5 hours each. There is nothing special in any of the compositions. I have rendered these same compositions in the past with minor changes in AE CS5 and they finished in seconds using the Open GL renderer. I understand CS6 uses a different engine for rendering. I have ensured my video card is in the supported list (added it), and ray tracing is set to the GPU. I triple checked all the drivers and everything is up to date. I have tried every combination of settings I can think of with no results. Help!
System Specs:
i7-3930K
GTX 770
32gb ram
Windows 7 64bitFive hours is not an unusual render time for a 30-second composition, depending on the details of the composition.
See this page for resources about making After Effects work faster: http://adobe.ly/eV2zE7 -
FCP 7.01 Render times 5-6 times longer than FCP 6
I just upgraded to 7.01. I am doing the same job I was doing last week. Exactly the same. The week with 7.01 render times are approximately 5-6 times longer. How can that be possible? I have FC Studio, can I go back to version 6 just for FCP? I'm amazed because FCP 7 has been out for months. Isn't everyone else seeing the same problem??
I work to complete the same day. So render times increasing means that I can't work with FCP 7! Does anyone know if Apple are going to solve this problem asap?
The sequence is Prores 422, various media in the sequence: H.264, Prores, graphics.. but the point is that last week with FCP 6 it was 5-6 times faster! I've been working with FCP fro years. There is no doubt in my mind that the render jobs are exactly the same but FCP 7 is rendering them 5-6 times slower..I have not had a similar experience but I do always follow these two rules whenever I upgrade.
1) Do not upgrade during the middle of a project.
2) Do a clean install, don't just upgrade the software.
I presume you have double checked that your sequence settings are correct? It could be a corrupt file and you should be able to determine if one particular file is the problem. You may have to render sections or single clips in your sequence to do this.
You may also want to consider that H.264 is not a recommended edit format. It is a deliverable format. I realize more cameras are shooting it and many people claim success while editing with it but there are numerous posts on Creative Cow and other sites that do not recommend doing it. They recommend converting it to ProRes or some other format. -
Slow render time, can anyone help?
I have recently installed some plugins and since it seems that render times are really slow. After every tweak of a filter I'm having to re-render for playback.
I have a one minute clip in the timeline for example, I add a vignette from my Magicbullet Plugin, nothing more and it takes 4 mins to render! My timeline is set to DV-PAL Anamorphic and my video captured as the same.
Any more info required please ask
Many thanksYour RT settings don't improve final render times, but they may improve your editing experience by allowing better playback of effects without having to render your timeline. You should experiment with the settings in the sequence to see what works best for your particular setting. Generally, if you choose Unlimited RT you'll get more real time playback, and therefore won't have to render as often while editing. But you'll likely experience more dropped frames during your sequence playback. You still have to render your final output though.
Have a read of the manual and experiment. There are no hard and fast rules for settings as every system is different. Obviously, the more you tax your system the less it's able to play back in real time.
Best of luck. -
Slow render times in Premiere when linking After Effects media
I'm an Avid Media Composer editor but I just switched to Premiere for a special project that needs to have non-interlaced output. I've been pretty impressed until I integrated an After Effects project into my timeline. My render times have now increased exponentially, despite the fact that the After Effects effects are quite simple - single layers of video with very simple moves. Can anyone else chime in with their experience integrating After Effects projects into Premiere? This just seems too horrible to be true.
I've found that the time to render out of After Effects versus the time to render a Dynamic Link comp in PPro is roughly identical. In fact, in many cases it's a bit quicker.
For heavy duty comps, I'd expect to see PPro struggle a little bit more, but definitely not with the basic work you seem to be talking about. -
Adding Masks Slows down render times massively
Adding any sort of vignettes/mask when using DL in Premiere CC creates massive render times in premiere. On a two minute promo it takes 15 minues to render what took 4 minutes without Masks.
Anyone know how to improve this? In the middle of a production, and this alone makes me want to use Resolve.I should add that I'm Exporting to Media Encoder.
Leaving Renderer to CUDA or CL seems to be the culprit.
Setting ME to 'Software only' seems to improve render times. -
Render Times Slow on iMac Core i7 Quad
Is there any way to speed up export and render times in FCP? Right now only 30% of my processor gets used.
I have a cluster made for encoding via Compressor, but wasn't sure if there was a way to get the most out of my processor while in FCP.
On a side note, can't wait for the 64-bit version.I understand that this post was answered over a month ago, but the way that I understand to speed up FinalCut Pro is when you render with compressor, you have to setup multiple instances of Compressor using Qmaster. Look at this guide for more help: http://www.digitalrebellion.com/blog/posts/usingcompressor_with_multiplecores.html
However, with Final Cut Express Compressor isn't available, so you can render out in to ProRes 422 or Apple Intermediate Codec to create your "master" file, then use a utility that is multiple processor aware such as MpegStreamClip to re-compress out to your final format. This process actually works pretty well using Final Cut Pro, Studio and Express, so this is the method that I use most of the time.
Maybe you are looking for
-
How to find where is bottleneck oracle 11.2
I am running oracle 11gr2 on windows server 2008 R2 having ram 20gb. I am taking statspack report on database and following is it: i am not getting where is actual bottleneck is and some time there is problem regarding procedure hangup which having b
-
Trying to recover my data My Micro SD Card became corrupted after JB Update
Can someone please help me? Here is the issue: Background: I have a Samsung Galaxy S3 phone that I transferred my micro SD Card into from my previous smart phone. About a month ago I realized that some of the pictures were corrupted and called veriz
-
like many other, I had the problem that when I edited my movies in iMovie and iDVD the audio was fine, until I started burning them on DVD or disk image. Than there was either no audio at all, or after some minutes (usually 5-15) the audio was gone.
-
Hi After executing the payment run,when we take the printout system is sorting by vendor code ,now i am looking for solution which will sort the payment list by vendor name in alphabatical order.eventhough vendor number will not be in order that is n
-
How to go from mac oxs 10.5.8 to mac osx 10.6.8
I bought an Iphone 5 and i can't use itune because I need a newer version but I can't have it because I don't have osx 10.6.8... where do I find it ?