SpeedGrade render not using GPU, slow render speeds

atHi!
I'm grading a fan-made feature-length film situated in this really obscure place called Middle Earth, and I'm currently rendering the final output.
Rendering speed has been really slow all along, so I decided to check upon GPU usage with a nVidiaInspector. It shows that GPU usage is between 0-5%. I'm able to get GPU usage to spike by switching to Monitor view (and scrubbing in timeline) instead of Output view in SpeedGrade. I understand that SpeedGrade is supposed to be GPU-accelerated throughout (not counting frame decompression made by codecs?), and now it seems that my CPU is doing all the lifting. CPU usage is around 100% all the time.
Render speed varies between 0.7 FPS and 6 FPS, which is far less than I expected, as I got reasonably fluid real-time previews all along the timeline when grading. Most typical clips have two primaries, two secondaries and a vingette mask primary on top. Total render time for 1 h 50 min timeline is expected around 12 to 18 hours.
My source material is 25 FPS 1080p CineForm AVI.
My output format is CineForm in Quicktime container (as AVI output with CineForm coded is not supported at present time) with automatic color calibration on, no audio, alpha discarded. Framing options are not in use (Full image (no proxy), 1:1 pixel aspect ratio, same size as proxy), and rendering is happeing  at Online Quality.
My machine's specs are:
- Intel i5 2400S quad-core
- 16 GB of DDR3 RAM
- nVidia MSI GeForce GTX 470 with 1280 MB memory
- Windows 7, 64-bit
- SpeedGrade 6.0.4x25
- GeForce 310.70 drivers
Any input is appreciated.

Maybe due to cineform quicktime?  Try other codecs to see what render speed you get. 
Regards,
Mark.
PS I am geetin slow renders to cineform quicktime files from other app's (Premiere, Media encoder...)

Similar Messages

  • Does it use GPU to render?

    I have a 1.1 MacPro with 2.6 quad and ATI X1800.. Will upgrading my GPU to a ati 4870 5770 help with render speeds?
    Does Compressor or FCP use GPU during transcodes or log and transfers for either encode or decode?

    No.
    See Shane's answer to your other post.
    bogiesan

  • Media Encoder CC not using GPU acceleration for After Effects CC raytrace comp

    I created a simple scene in After Effects that's using the raytracer engine... I also have GPU enabled in the raytracer settings for After Effects.
    When I render the scene in After Effects using the built-in Render Queue, it only takes 10 minutes to render the scene.
    But when I export the scene to Adobe Media Encoder, it indicates it will take 13 hours to render the same scene.
    So clearly After Effects is using GPU accelleration but for some reason Media Encoder is not.
    I should also point out that my GeForce GTX 660 Ti card isn't officially supported and I had to manually add it into the list of supported cards in:
    C:\Program Files\Adobe\Adobe After Effects CC\Support Files\raytracer_supported_cards.txt
    C:\Program Files\Adobe\Adobe Media Encoder CC\cuda_supported_cards.txt
    While it's not officially supported, it's weird that After Effects has no problem with it yet Adobe Media Encoder does...
    I also updated After Effects to 12.1 and AME to 7.1 as well as set AME settings to use CUDA but it didn't make a difference.
    Any ideas?

    That is normal behavior.
    The "headless" version of After Effects that is called to render frames for Adobe Media Encoder (or for Premiere Pro) using Dynamic Link does not use the GPU for acceleration of the ray-traced 3D renderer.
    If you are rendering heavy compositions that require GPU processing and/or the Render Multiple Frames Simultaneously multiprocessing, then the recommended workflow is to render and export a losslessly encoded master file from After Effects and have Adobe Media Encoder pick that up from a watch folder to encode into your various delivery formats.

  • Media Encoder not using GPU in CC2014.2

    I updated to CC2014.2 yesterday.
    Rendering a project from Premiere Pro's Export function engaged the GPU as expected, I hear the fans spin up, renders are fast.
    However, when sending to Media Encoder, project render times are astronomical, the GPU is not engaging despite CUDA being switched on in all applicable options. The difference is a few minutes vs 2 hours. No non-native plug-ins are in use.
    This was not a problem a few days ago with CC2014.1. For the moment I'm stuck to exporting directly from Premiere until it's fixed. Has anyone else experienced similar bugs?
    Windows 7 64
    GeForce 580GTX 3GB
    Driver 341.44

    Hmm it seems we both broke the rule of "don't update mid project!"
    Still, hopefully this will lead to a quick fix, since it will affect many professional quite badly.
    Yes for me it's just no GPU rendering in Media Encoder. I've been able to get through this by using Export, which is extremely fast.
    My timeline playback works fine too as does Speedgrade, so it appears this is an issue with Media Encoder alone on my machine.

  • Premiere Pro CS6 Warp Stabilizer not using GPU/CUDA why?

    Hi,
    I installed CS6 and tried the Warp Stabilizer, I undestand that only part 2 of the process (stabilize part) is GPU accelerated, but I can't get any acceleration from GPU, my GPU is idle at 1% usage (GTX580) and all the processing is going to CPU. The renderer/playback is marked CUDA so its not that.
    Is there anything I'm missing?
    Thanks

    OK, this surprised me a bit. I have a state-of-the-art new PC with plenty of RAM, a fast processor and lots of cuda cores. See the specs here: http://www.stevengotz.com/
    It took over 10 minutes to stabilize one minute of video - 1800 frames. It wasn't all that shaky to begin with, but it was handheld and therefore looks better after using Warp. There was one section that was so bad, I sliced the clip up and chose not to stabilize that part after the fact. So I thought that it might have added a little to the problem. But no. I tried just 180 frames of reasonably stable hand held video from the same clip and it took almost a minute.
    Now, once the process was finished, I had no problem playing it back in realtime without rendering. But what is taking so long? I understand that there is a lot of work to do, but why isn't it using the power I have provided?
    This is a screen shot of my resources about two minutes into the process.
    I would love to know what I need to do to speed up this process. I get that it is working in the background. Is it possible to make it work in the foreground? I would not mind if it maxed out the RAM or the CPU or both if it would help.
    edit: I just submitted a Feature Request to let Warp run in the foreground using every available resource.
    Steven
    Message was edited by: Steven L. Gotz to include additional information.

  • Adobe After Effects, Premiere and Encoder does not use the GPU (CUDA) ?

    Please! Explain me. Why? Adobe After Effects, Premiere and Encoder does not use GPU (CUDA) ?
    Everytime i have GPU Load from 0 to 10% !!! (GeForce GTX 970) And also my CPU load is not full. Any suggestions?

    seg.48162731 wrote:
    At the moment i use AE, AP and ME CC 2014 8.2 with the latest updates. I have GTX 970 and AMD 8350. What's my problem?
    Which chipset is on your system's motherboard? Which motherboard is your PC equipped with?
    If the motherboard is using an AMD 790 or 970 series chipset, the HyperTransport bus will be running at a reduced speed, and thus the CPU performance will be worse than a quad-core Intel i5 CPU without hyperthreading. In many instances, this means that the GPU will be laying idle, waiting for the CPU to catch up.
    If on the other hand the motherboard uses an AMD 990FX chipset, then it's likely that there is something else bottlenecking your PC.

  • Premiere Pro CC / Adobe Media Encode CC not using GTX980 EVGA

    Generation of movies using h.264 encoding is not using GPU. Based on the logs from video card there is no usage even if the selected renderer is Mercury Playback Engine GPU Acceleration (CUDA). How can I enable its usage?

    Hi mate, same here.. I can't do it work, simply.. I select GPU in Premiere and AME (gtx 970 in my PC and gt755M in my laptop, neither is working), GPU is 0% of use to do a simple video conversion.
    To show that is a Adobe problem, this guy create his own exporter plugin ( SHAME ON YOU ADOBE!). With it AME work very, very fast, but i have issues too when change the video format to MP4.
    NVidia GPU-accelerated H264-encoder plugin, ready for public testing
    I don't know what i do. I think Nvidia and Adobe messed up very bad this feature.. Nice Adobe, i have a good GPU but i have to wait very long times (1hr videos conversion) because you guys can't do a simple exporter plugin that use GPU power.. So, stop collecting our money only and GO TO IMPLEMENT OUR NEEDS! Have a nice day.

  • Is the GPU used for final render?

    Hi,
    I started using Speedgrade on my Mac Pro, and I really like it.
    I'm getting great playback of my 3K r3d files - realtime at 1/2 res with my ATI 5770,
    but when I'm doing my final render from the output tab it will only render 0.7 fps in both online and offline quality.
    So I was thinking about getting a GTX 580, but will Speedgrade use the GPU for final renders or only for playback? If it's only for playback it wouldn't make sense for me to buy one.
    I'm also struggling with getting my project from Premiere to Speedgrade,
    I can export an EDL, but this will only contain one video track - and I usually use multiple.
    Is there any way to export a sequence with more than one video track?
    Thanks

    Hey azton,
    Speedgrade is using GPU for playback and CPU for rendering.
    Regarding Rendering Speed:
    what kind of input resolution do you use? - this is crucial to improve  render time. If you want to render out Proxies for example, its recommend using input-res below FULL, generally speaking of 1/4 ... 1/2 etc Res.
    By changing InputRes only you wil already notice a speed-up, activating OFFLINE quality should give a additional boost.
    What is your Output format? DPX? QT? Your Output Resolution?
    Rendering from a 3K image + Colorcorrection/Masks/Secondary + Resizing to XXX OuputRes + Codec (h264, DNxHD) wont be ultra fast though.
    EDL:
    multiple videotracks are not supported in the CMX3600 EDL standard. You have to deal the EDL as a traditional FINAL/MASTER edit.
    hope that helps,
    D-A

  • I am trying to use the Filter-Render-Lighting Effects tool but the Lighting Effects is in light grey and I can not access it can anyone hel please

    I am trying to use the Filter-Render-Lighting Effects tool but the Lighting Effects is in light grey and I can not access it can anyone help please?

    Hi again is this what you are looking for?
    Adobe Photoshop Version: 14.2.1 (14.2.1 20140207.r.570 2014/02/07:23:00:00)
    x64
    Operating System: Windows 8 64-bit
    Version: 6.2
    System architecture: Intel CPU Family:6, Model:10, Stepping:9 with MMX, SSE
    Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
    Physical processor count: 2
    Logical processor count: 4
    Processor speed: 1796 MHz
    Built-in memory: 3977 MB
    Free memory: 1203 MB
    Memory available to Photoshop: 3289 MB
    Memory used by Photoshop: 60 %
    Image tile size: 128K
    Image cache levels: 4
    Font Preview: Medium
    TextComposer: Latin
    Display: 1
    Display Bounds: top=0, left=0, bottom=768, right=1366
    OpenGL Drawing: Disabled.
    OpenGL Allow Old GPUs: Not Detected.
    OpenGL Drawing Mode: Advanced
    OpenGL Allow Normal Mode: True.
    OpenGL Allow Advanced Mode: True.
    AIFCoreInitialized=1
    AIFOGLInitialized=1
    OGLContextCreated=1
    NumGPUs=1
    gpu[0].OGLVersion="3.0"
    gpu[0].MemoryMB=2052
    gpu[0].RectTextureSize=16384
    gpu[0].Renderer="Intel(R) HD Graphics 4000"
    gpu[0].RendererID=358
    gpu[0].Vendor="Intel"
    gpu[0].VendorID=32902
    gpu[0].HasNPOTSupport=1
    gpu[0].DriverVersion="10.18.10.3379"
    gpu[0].Driver="igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igdumdim32,igd10iumd32,igd10 iumd32"
    gpu[0].DriverDate="20131218000000.000000-000"
    gpu[0].CompileProgramGLSL=1
    gpu[0].TestFrameBuffer=1
    gpu[0].OCLPresent=1
    gpu[0].OCLVersion="1.2 "
    gpu[0].CUDASupported=0
    gpu[0].OCLBandwidth=0
    gpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="1.30 - Build 10.18.10.3379"
    gpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[1447]
    gpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[8]
    gpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[96]
    gpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[16]
    gpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[16]
    gpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
    gpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
    gpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[4096]
    gpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[64]
    gpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
    gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
    gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
    gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
    gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
    gpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
    gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
    gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
    gpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
    gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
    gpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=0
    License Type: Subscription
    Serial number: 96040664679779475738
    Application folder: C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\
    Temporary file path: C:\Users\Trisha\AppData\Local\Temp\
    Photoshop scratch has async I/O enabled
    Scratch volume(s):
      C:\, 452.3G, 51.7G free
    Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CC (64
    Bit)\Required\Plug-Ins\
    Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CC (64
    Bit)\Plug-ins\
    Installed components:
       ACE.dll   ACE 2013/10/29-11:47:16   79.548223   79.548223
       adbeape.dll   Adobe APE 2013/02/04-09:52:32   0.1160850   0.1160850
       AdobeLinguistic.dll   Adobe Linguisitc Library   7.0.0
       AdobeOwl.dll   Adobe Owl 2013/10/25-12:15:59   5.0.24   79.547804
       AdobePDFL.dll   PDFL 2013/10/29-11:47:16   79.508720   79.508720
       AdobePIP.dll   Adobe Product Improvement Program   7.0.0.1786
       AdobeXMP.dll   Adobe XMP Core 2013/10/29-11:47:16   79.154911   79.154911
       AdobeXMPFiles.dll   Adobe XMP Files 2013/10/29-11:47:16   79.154911
    79.154911
       AdobeXMPScript.dll   Adobe XMP Script 2013/10/29-11:47:16   79.154911
    79.154911
       adobe_caps.dll   Adobe CAPS   7,0,0,21
       AGM.dll   AGM 2013/10/29-11:47:16   79.548223   79.548223
       ahclient.dll    AdobeHelp Dynamic Link Library   1,8,0,31
       aif_core.dll   AIF   5.0   79.534508
       aif_ocl.dll   AIF   5.0   79.534508
       aif_ogl.dll   AIF   5.0   79.534508
       amtlib.dll   AMTLib (64 Bit)   7.0.0.249 BuildVersion: 7.0; BuildDate:
    Thu Nov 14 2013 15:55:50)   1.000000
       ARE.dll   ARE 2013/10/29-11:47:16   79.548223   79.548223
       AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830
    66.26830
       AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
       Bib.dll   BIB 2013/10/29-11:47:16   79.548223   79.548223
       BIBUtils.dll   BIBUtils 2013/10/29-11:47:16   79.548223   79.548223
       boost_date_time.dll   DVA Product   7.0.0
       boost_signals.dll   DVA Product   7.0.0
       boost_system.dll   DVA Product   7.0.0
       boost_threads.dll   DVA Product   7.0.0
       cg.dll   NVIDIA Cg Runtime   3.0.00007
       cgGL.dll   NVIDIA Cg Runtime   3.0.00007
       CIT.dll   Adobe CIT   2.1.6.30929   2.1.6.30929
       CITThreading.dll   Adobe CITThreading   2.1.6.30929   2.1.6.30929
       CoolType.dll   CoolType 2013/10/29-11:47:16   79.548223   79.548223
       dvaaudiodevice.dll   DVA Product   7.0.0
       dvacore.dll   DVA Product   7.0.0
       dvamarshal.dll   DVA Product   7.0.0
       dvamediatypes.dll   DVA Product   7.0.0
       dvaplayer.dll   DVA Product   7.0.0
       dvatransport.dll   DVA Product   7.0.0
       dvaunittesting.dll   DVA Product   7.0.0
       dynamiclink.dll   DVA Product   7.0.0
       ExtendScript.dll   ExtendScript 2013/10/30-13:12:12   79.546835
    79.546835
       FileInfo.dll   Adobe XMP FileInfo 2013/10/25-03:51:33   79.154511
    79.154511
       filter_graph.dll   AIF   5.0   79.534508
       icucnv40.dll   International Components for Unicode
    2011/11/15-16:30:22    Build gtlib_3.0.16615
       icudt40.dll   International Components for Unicode
    2011/11/15-16:30:22    Build gtlib_3.0.16615
       imslib.dll   IMSLib DLL   7.0.0.145
       JP2KLib.dll   JP2KLib 2013/10/29-11:47:16   79.248139   79.248139
       libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
       libiomp5md.dll   Intel(R) OMP Runtime Library   5.0
       libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r)
    Fortran Compiler   12.0
       LogSession.dll   LogSession   2.1.2.1785
       mediacoreif.dll   DVA Product   7.0.0
       MPS.dll   MPS 2013/10/29-11:47:16   79.535029   79.535029
       msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.8428
       msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
       msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
       msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.8428
       msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
       msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
       msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.8428
       msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
       PatchMatch.dll   PatchMatch 2013/10/29-11:47:16   79.542390   79.542390
       pdfsettings.dll   Adobe PDFSettings   1.04
       Photoshop.dll   Adobe Photoshop CC   CC
       Plugin.dll   Adobe Photoshop CC   CC
       PlugPlugOwl.dll   Adobe(R) CSXS PlugPlugOwl Standard Dll (64 bit)
    4.2.0.36
       PSArt.dll   Adobe Photoshop CC   CC
       PSViews.dll   Adobe Photoshop CC   CC
       SCCore.dll   ScCore 2013/10/30-13:12:12   79.546835   79.546835
       ScriptUIFlex.dll   ScriptUIFlex 2013/10/30-13:12:12   79.546835
    79.546835
       svml_dispmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r)
    Fortran Compiler   12.0
       tbb.dll   Intel(R) Threading Building Blocks for Windows   4, 1, 2012,
    1003
       tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   4, 1,
    2012, 1003
       updaternotifications.dll   Adobe Updater Notifications Library
    7.0.1.102 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   7.0.1.102
       WRServices.dll   WRServices Mon Feb 25 2013 16:09:10   Build 0.19078
    0.19078
    Required plug-ins:
       3D Studio 14.2.1 (14.2.1 x001)
       Accented Edges 14.2.1
       Adaptive Wide Angle 14.2.1
       Angled Strokes 14.2.1
       Average 14.2.1 (14.2.1 x001)
       Bas Relief 14.2.1
       BMP 14.2.1
       Camera Raw 8.4.1
       Camera Raw Filter 8.4.1
       Chalk & Charcoal 14.2.1
       Charcoal 14.2.1
       Chrome 14.2.1
       Cineon 14.2.1 (14.2.1 x001)
       Clouds 14.2.1 (14.2.1 x001)
       Collada 14.2.1 (14.2.1 x001)
       Color Halftone 14.2.1
       Colored Pencil 14.2.1
       CompuServe GIF 14.2.1
       Conté Crayon 14.2.1
       Craquelure 14.2.1
       Crop and Straighten Photos 14.2.1 (14.2.1 x001)
       Crop and Straighten Photos Filter 14.2.1
       Crosshatch 14.2.1
       Crystallize 14.2.1
       Cutout 14.2.1
       Dark Strokes 14.2.1
       De-Interlace 14.2.1
       Dicom 14.2.1
       Difference Clouds 14.2.1 (14.2.1 x001)
       Diffuse Glow 14.2.1
       Displace 14.2.1
       Dry Brush 14.2.1
       Eazel Acquire 14.2.1 (14.2.1 x001)
       Embed Watermark 4.0
       Entropy 14.2.1 (14.2.1 x001)
       Extrude 14.2.1
       FastCore Routines 14.2.1 (14.2.1 x001)
       Fibers 14.2.1
       Film Grain 14.2.1
       Filter Gallery 14.2.1
       Flash 3D 14.2.1 (14.2.1 x001)
       Fresco 14.2.1
       Glass 14.2.1
       Glowing Edges 14.2.1
       Google Earth 4 14.2.1 (14.2.1 x001)
       Grain 14.2.1
       Graphic Pen 14.2.1
       Halftone Pattern 14.2.1
       HDRMergeUI 14.2.1
       IFF Format 14.2.1
       Ink Outlines 14.2.1
       JPEG 2000 14.2.1
       Kurtosis 14.2.1 (14.2.1 x001)
       Lens Blur 14.2.1
       Lens Correction 14.2.1
       Lens Flare 14.2.1
       Liquify 14.2.1
       Matlab Operation 14.2.1 (14.2.1 x001)
       Maximum 14.2.1 (14.2.1 x001)
       Mean 14.2.1 (14.2.1 x001)
       Measurement Core 14.2.1 (14.2.1 x001)
       Median 14.2.1 (14.2.1 x001)
       Mezzotint 14.2.1
       Minimum 14.2.1 (14.2.1 x001)
       MMXCore Routines 14.2.1 (14.2.1 x001)
       Mosaic Tiles 14.2.1
       Multiprocessor Support 14.2.1 (14.2.1 x001)
       Neon Glow 14.2.1
       Note Paper 14.2.1
       NTSC Colors 14.2.1 (14.2.1 x001)
       Ocean Ripple 14.2.1
       Oil Paint 14.2.1
       OpenEXR 14.2.1
       Paint Daubs 14.2.1
       Palette Knife 14.2.1
       Patchwork 14.2.1
       Paths to Illustrator 14.2.1
       PCX 14.2.1 (14.2.1 x001)
       Photocopy 14.2.1
       Photoshop 3D Engine 14.2.1 (14.2.1 x001)
       Photoshop Touch 14.0
       Picture Package Filter 14.2.1 (14.2.1 x001)
       Pinch 14.2.1
       Pixar 14.2.1 (14.2.1 x001)
       Plaster 14.2.1
       Plastic Wrap 14.2.1
       PNG 14.2.1
       Pointillize 14.2.1
       Polar Coordinates 14.2.1
       Portable Bit Map 14.2.1 (14.2.1 x001)
       Poster Edges 14.2.1
       Radial Blur 14.2.1
       Radiance 14.2.1 (14.2.1 x001)
       Range 14.2.1 (14.2.1 x001)
       Read Watermark 4.0
       Reticulation 14.2.1
       Ripple 14.2.1
       Rough Pastels 14.2.1
       Save for Web 14.2.1
       ScriptingSupport 14.2.1
       Shake Reduction 14.2.1
       Shear 14.2.1
       Skewness 14.2.1 (14.2.1 x001)
       Smart Blur 14.2.1
       Smudge Stick 14.2.1
       Solarize 14.2.1 (14.2.1 x001)
       Spatter 14.2.1
       Spherize 14.2.1
       Sponge 14.2.1
       Sprayed Strokes 14.2.1
       Stained Glass 14.2.1
       Stamp 14.2.1
       Standard Deviation 14.2.1 (14.2.1 x001)
       STL 14.2.1 (14.2.1 x001)
       Sumi-e 14.2.1
       Summation 14.2.1 (14.2.1 x001)
       Targa 14.2.1
       Texturizer 14.2.1
       Tiles 14.2.1
       Torn Edges 14.2.1
       Twirl 14.2.1
       Underpainting 14.2.1
       Vanishing Point 14.2.1
       Variance 14.2.1 (14.2.1 x001)
       Variations 14.2.1 (14.2.1 x001)
       Water Paper 14.2.1
       Watercolor 14.2.1
       Wave 14.2.1
       Wavefront|OBJ 14.2.1 (14.2.1 x001)
       WIA Support 14.2.1 (14.2.1 x001)
       Wind 14.2.1
       Wireless Bitmap 14.2.1 (14.2.1 x001)
       ZigZag 14.2.1
    Optional and third party plug-ins: NONE
    Plug-ins that failed to load: NONE
    Flash:
       Mini Bridge
       Kuler
       Adobe Exchange
    Installed TWAIN devices: NONE
    On Tue, Feb 24, 2015 at 10:29 PM, Benjamin Root Photography <

  • Slow render speed

    Hi
    As I am new to iMovie HD I have been experimenting with imported clips. I have overcome importing mpeg2 and have been testing adding effects etc and have found that the render time in the timeline for the effect to be 'ready' is slow.
    I am using a 2.1Hz iMac G5 (iSight) with 1gb of Ram. I have ensured that all other apps are not running but this does not noticebly increase the render speed.
    Any help would be greatly appreciated.
    Thanks

    "Slow" is quite a vague term...
    But be aware that appling effects to clips needs a lot of your machine power, as each frame has to be "redrawn". Longer the clips, longer the time needed.

  • Lightroom 6 / CC2015 - Facial Recognition Terribly Slow, not using all of CPU or GPU, still keeps going when paused.

    This is actually a couple of issue but wondering if others are experiencing it and worked through it.
    I am using a Dual Xeon CPU 3.2 ghz Mac Pro, Catalog on SSD, Images files on Mirrored Pair, Dedicated GPU (max I can install in my version of Mac Pro) and hardware acceleration enabled in Lightroom.
    I watched the Lightroom 6 Facial Recognition tutorial which leaves out a lot of the bulk editing and says basically let it loose on your whole catalog.. NOT recommended.
    I started out with a couple small portrait galleries that identified a couple hundred total people to seed facial recognition so it didn't suggest everyone is the first person I confirmed (which it will do otherwise). I have also optimized my catalog multiple times.
    I have encountered the following serious performance issues and bugs with Facial Recognition.:
    Lightroom Facial Recognition goes to a ridiculous crawl after about 2000 images to be confirmed. (i.e. 2000-2300 in a couple hours, 800-1200 in the next 12 hours)
    Lightroom becomes largely unresponsive after having a fair number of images to be confirmed, even after pausing Address and Facial Recognition. So even selecting 4 rows of images can take 5 minutes with several long pauses.
    Once I select and click confirm it takes up to 2 minutes to update the "to be confirmed" list again.
    When I click on an individual at the top of the page, pause facial recognition and address lookup it still continues to "Look for similar faces" [BUG!!!!!!!!] even though all I want to do is just confirm some individuals more quickly in bulk with the images already identified.. not continue to look for more as a work around for the painfully slow responsiveness of the module.
    The odd part is that with all of the performance issues Lightroom will not use more than 20-30% of my two Xeon CPUs, barely touches my GPU (<10% CPU, 30% memory), my and no more than 35% of my memory. Computer Temps are also barely above startup temperatures and 15-25 degrees cooler than when I run other applications which will consume my entire CPU and memory if I let it. I have explored Lightroom's settings but seen nothing further I can configure to speed it all up.  I have also attempted the operation on images on the SSD, my drobo (known to be slow), an independent fast disk I have, and a pair of raided disks and have the same issues.
    I will also note that all of my other applications seem to continue to operate just fine.. the slowness seems to be contained to the Lightroom application itself.
    Lightroom version: 6.0 [1014445]
    Operating system: Mac OS 10 Version: 10.10 [3]
    Application architecture: x64
    Logical processor count: 8
    Processor speed: 3.2 GHz
    Built-in memory: 18,432.0 MB
    Real memory available to Lightroom: 18,432.0 MB
    Real memory used by Lightroom: 5,537.5 MB (30.0%)
    Virtual memory used by Lightroom: 32,240.6 MB
    Memory cache size: 4,342.0 MB
    Maximum thread count used by Camera Raw: 8
    Camera Raw SIMD optimization: SSE2
    Displays: 1) 2048x1152
    Graphics Processor Info:
    NVIDIA GeForce GTX 285 OpenGL Engine
    Check OpenGL support: Passed
    Vendor: NVIDIA Corporation
    Version: 3.3 NVIDIA-10.0.31 310.90.10.05b12
    Renderer: NVIDIA GeForce GTX 285 OpenGL Engine
    LanguageVersion: 3.30
    Application folder: /Applications/Adobe Lightroom
    Library Path: /Users/DryClean/Documents/Lightroom_Catalog/MyCat_LR6.lrcat
    Settings Folder: /Users/DryClean/Library/Application Support/Adobe/Lightroom
    Anyone have any suggestions?

    A big problem continues to be that once you wait for it to index all your faces you find it missed over half of them. There are many cases where it missed the subject of the photo but managed to find a tiny waiter off in the shadows. I don't know how this will ever get fixed; it seems it'll require an update that lets you rerun the indexing a few times, maybe with different levels of granularity. I doubt that's coming.
    It stands to reason that a system that hands you thousands of false positives for every face can't recognize if something is or isn't a face in over half the cases. Faces in profile or tilted down, especially with the eyes looking down, are bypassed completely. I have directories with a thousand people shots in them, many with multiple people, and instead of LR6 returning an index of 1.5k or so, it gives me 385. I'm not sure how valuable the search advantages will be in this case; I can see it not returning some favorite shots of people.
    Anyway, for anyone looking to get past the spinning wheels, work on one directory at a time. Then once a directory is done, keep it selected so you have the same thumbnails of identified faces in the confirmed area, and control-select the next directory. You won't have to reseed the confirmed faces area this way and things move much faster when you're not working with the entire library. It also helps to click each person in the confirmed faces and work in that view sometimes. It'll return faces of family members of that person and you can rename those. You can watch it focus its top results as you confirm but, annoyingly, it doesn't narrow the total suggestions but actually expands them the more faces you confirm and the fewer correct positives remain. (This seems opposite to how it should work. It should give you fewer faces the more you confirm as it gets a better idea what the person looks like and has fewer shots left unconfirmed of that person.)  Yet, even with the expanded results, faces will still escape it and pop up in other people's results as false positives.
    Bottom line: It's only a little better than manual tagging, and not as thorough because of the poor hit rate of the initial indexing. But it works better if you stick to isolated directories and occasionally individual people. At least that way you don't have to wait for it to re-sort tens of thousands of results with every click.

  • Using Compressor To Render - Slower in 3?

    I'm doing a new project in Motion 3 and I use Compressor to render the thing because I have a 16:9 custom setting in Compressor that I use. Is it my imagination, or is it rendering a lot slower?
    I have a play range of about 1 minute rendering and it has taken 20 minutes to render half of it.
    This is a simple project too - no video footage, animated text and shapes with some Photoshop TIFFs.
    Thanks

    no for me compressor is faster. Although i have had occasions when motion couldnt export to Compressor. it booted compressor up but then i just got the spinning pizza wheel of death. A re boot fixed it.
    not much help to you except to confirm that there's something odd going on with your system. But then you probably already knew that
    adam

  • 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

  • GTX 680 4GB and slow render/export

    Hopefully someone can help me out.
    I used to have a crappy old graphic card and recently upgraded to a EVGA GTX 680 4GB (CLASSIFIED model).
    My systems specs are:
    i7 930 @ 2.8Mhz
    EVGA GTX 680 4GB
    Win 7 64 Ultimate
    24GB DDR3
    PP CS6 (6.0.3) installed on SSD drive
    Scratch disk - Source/Export are seperate drives (both 3TB USB 3.0 drives)
    I am currently editing a music video with DSLR 1080p footage. At most, 2 layers of footage, basic transitions and some sharpening/color correction layers. Nothing that my old card was fussy about.
    The MPE (GPU CUDA acceleration) is enabled in Premiere Pro. I do see a difference when building my clips, the timeline stays mostly yellow instead of completely red. My CPU isn't freaking out as it used to with my old card, so I do see a performance increase at that level.  However, if I try to render my timeline or export, it takes so long! To export my 3 minute music video clip, I takes approx. 43 minutes (in 720p).
    I know each video project is unique, but similar projects processed with my old card appeared to be exported/rendered faster than with my new card.
    What am I doing wrong? Any obvious pointers?
    Any help/tips will be appreciated.
    Thank you so much!

    =======
    so even with a powerful GTX 680 4GB these rather basic video edits (color correction/de-noiser) will take that much time?
    =======
    Todd has some stuff he wrote in help files about this stuff... spread out over various areas of forums ( ae, pre pro, etc. ).. and basically what you're getting out of cuda with cool card is very good and fast ( using graph card ram, gpu etc ). So really ...it does make editing faster and smoother etc...
    BUT when you get to the export stage you're using the CPU , not the GPU anymore...although I think you can play around with pre rendering stuff and maybe then use 'rendered' files ...and gain a fraction of time on export.. I'm not experienced much with this at all...so what I'm saying is based on what I've read over the last year or so here in the forums etc.
    What you call " basic" and simple really isn't so basic and simple in terms of what the program(s) is doing.. as the stuff has is really math intensive ( cpu is working it's little heart out )...and you are getting the product..but it's gonna take the time it takes using what it can use....
    sorry, but there's no magic solution to making changes and then switching from gpu to cpu final export etc.
    I just bought a custom made computer I call the " pig " ( it is HUGE )..and working with mov h264 native ( which is great cause before that had to be converted to avi etc ).. in the long run I save ton of time editing native with pig, but exports are slow even with pig...its fact of life , but cs6 and pig is doing well with it so far...

  • FCPX Project Render Settings - Can you edit in h.264 and Transcode/render only used clips on timeline to Prores during render?

    I have a question on the PROJECT RENDER settings in FCP X. It’s seems to me that one could theoretically import and edit entirely with original h.264 video files without needing to Transcode to ProRes422. Once you’re done with your edit and want to get the added benefits of COLOR GRADING in ProRes422 color space, it seems that FCPX will automatically render your edit in ProRes422 according to these preferences. In that case, a color grade could be applied to the whole edit, and be automatically transcoded/rendered into ProRes 422 during the render process. After rendering, what would show up on the viewer and what would EXPORT would be the rendered Prores files and not the original h.264 files. This saves a lot of time and space of transcoding ALL your media, and in theory should enable you to edit NATIVE video formats like h.264, with automatic benefits of ProRes during render.  I'm assuming the render may take longer because FCPX is having to convert h.264 video files to ProRes422 while rendering. This may be one drawback. But will you your color grade actually use the 4:2:0 color space of the h.264 native media, or will it utilize 4:2:2 color space, since the render files are set to render to ProRes422 ? Can anyone please confirm that this theory is correct and optimal for certain work flows?? Thanks!

    Thanks Wild. That's what I thought - in that the render files would be converted to ProRes422 codec. So do you or anyone else think that there is an advantage to having the 4:2:0 original file be processed in a 4:2:2 color space?
    Yes there is an advantage, any effects and grading will look better than in a 4:2:0 space.
    Most professionals online seem to think so. Also - will rendering of heavy effects and color grading take longer using this method because it's having to convert h.264 media to ProRes during render?
    Yes, it will definitely take longer.
    Can anyone verify from a technical standpoint whether editing and color grading in this workflow will see the same benefits as having transcoded the h.264 media to ProRes in the first place?
    Same benefits from a final product view point, you lose on rendering time though and if you have lots of effects things will seem slow as it will have render everytime from the h264 file rather than a Pro Res file for every change you make. This may be fine on a higher end mac but I'm sure just pummels an older lower end mac as to being almost useless.

Maybe you are looking for

  • Error when clicking on EDIT button on CCM 2.0

    Hi Experts, we are experiencing lot of errors when we click on the "EDIT" or any other button on CCM of a CATALOG. The Error message we are getting is "Errors while reading catalogs,errors while reading master catalog". When we check the Display logs

  • How  to implement PCCD001 exit for new field in AENR table

    Dear experts, I am implementing PCCD0001 exit for a new field in AENR table secnario below. Tcode CC31/CC32/CC33 required additional field which stores value in AENR table. in AENR in implemented include(CI_AENR) and added new field. After i implemnt

  • "returned form...."statement email subject line & body

    How do I remove or edit the "returned form...." statement/text in the subject line and body of the email that is automatically generated with the email button?

  • Dm package(process chain: /cpmb/load_infoprov_UI)

    HI Friends, i'm trying to load data from bw cube to bpc, using data manager package(based on process: /cpmb/load_infoprov_ui). Which allows user to selectively load data. With this DM package,  succsfully loaded data for few combinations, but i faile

  • Synchronizing ipod?

    After i purchased songs on my itunes account i tried to transfer them to my ipod classic but it doesnt work. The ipod screen says "synchronizing" but it doesnt transfer my songs to the ipod. The five "R"s of troubleshooting didnt help. I cant transfe