Unbelievably slow audio render times!

I've been dealing with his for a while now on this documentary I've been working on. When I export my timeline which is right around an hour, it takes around 2 HOURS just to render audio previews before it will export! The bulk of my timeline is a single track with no effects at all. Video renders faster than the audio! The only thing unusual about my project is it is largely composed of longish multi-cam sequences - about 30 sequences ranging from 30 mins to 90 mins. It's appears PP is rendering audio for every bit of my source sequences even though only a few seconds or minutes of each one is actually being used. I don't know what else could be happening.
I was thinking that since some of the audio was recorded at 44.1K maybe that was a problem and some of the sequences had several tracks of audio so to solve this I went through every sequence and rendered out a stereo mix at 48/16 and deleted the old audio. That seemed to help for a while as with CS6 I was getting a very annoying "rendering required audio files" message every time I hit play until I rendered the audio which as I said takes a really long time. Also I can render this but if I close Premiere and re-open I have to render it all over again. It is not keeping the audio render files. Premiere CC is better about playing back without the render message but it still needs to render for export. I have no idea why it would need to render audio from 48/16 source files.
I have reported this to Adobe but just thought I'd put this here to see if anybody else is having issues. If any audio rendering should ever be required in this day and age it should be extremely fast. This problem has really brought exporting to a crawl for this project.
Adobe CC, OSX 10.8.4 on a 12 core Mac Pro with a GTX 570 32GB ram, and BM Studio. My RAID is a 3 disk internal raid with 3 3TB disks in RAID 0. The video renders reload properly. The situation would be better if the audio renders reloaded at least but why it needs to render "audio previews" for such simple audio is beyond me. And as I mentioned I went through quite a bit of trouble to make it as easy on Premiere as possible by replacing all of the 44.1 audio with 48/16 wavs.

Let me start by saying I am only a hobbyist and do this more for my son and niece since they are musicians and play live in a number of venues.  I am not an electrical or audio engineer (I am an aeronautical engineer) so what I am about to say is based only on what seems logical to me…  First rendering audio should simply be faster than rendering video given the amount of digital data that needs to be processed.  That stated, I know that the Mercury engine using CUDA to process video vastly speeds the rendering of video.  Regardless, using today’s CPUs (i7 3930K in my case) should and does more than make up for the additional processing power for rendering video using CUDA. 
It seems to me that there is a bigger problem than whether or not we are flattening, nesting or locking our tracks.  It shouldn’t take as long as it is taking for some of us to render audio!!!
I only experienced this problem one time.  I am not even sure what I did to change the outcome on the same project that I have since edited and rendered many times.  But now the audio renders very quickly (less than a minute).  I will say that in almost all cases my music videos have different audio sources (44.1KHz, 48KHz 16bit, 48KHz 24bit, and 96KHz 24bit) and that I set all my sequences to 96KHz since my master audio sources are recorded at that.  I use an external firewire RME Fireface 800 using RME ASIO divers to handle all audio.  I do find that this setup can be stubborn in that there are times PPro CC doesn’t know what to do regarding my audio so simply won’t allow me to play any track.  When this happens I simply remind PPro CC of my settings by going to Edit/Preferences/Audio Hardware then check that the Adobe Desktop Audio is set to ASIO FireFace and click on ASIO Settings to check that the buffer size and sample rate are correct.  If they are not I read the flash from the RME and all is good. 
But I diverge, there is a problem Adobe and it needs to be fixed.  This never happened to me using CS6…

Similar Messages

  • 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.

  • Dramatically slower encode/render times from Premiere Pro CC 2014 via both AME 2014 and direct export via PP

    My recent update to Adobe CC 2014 apps has been an unmitigated disaster.  Was running the 2013 version until last week and everything was just dandy.  Very good performance and excellent render/encode times even for stuff with lots of filters and fx. 
    Since update 1-2 min videos with no fx or filters (or even transitions) have gone from exporting in under two minutes to well over 25 minutes.  These exports are with the same presets I regularly use (Vimeo 720HD H.264). 
    I've been poking around the forums here for two days looking for answers and can't find anything that works.  Tried the whole "App Nap" toggle as well as a few other tips.  Didn't do squat.  Looking for any hints/answers.  Thanks.
    Mac Pro Mid 2012
    2 x 2.4 GHz 6-Core Intel Xeon
    32 GB 1333 MHz DDR3 ECC
    ATI Radeon HD 5870 1024 MB
    OS X 10.9.5 (13F34)
    System SSD 500GB
    Cache SSD 500GB
    Media HD 1TB

    Hi MXSw,
    MXSw wrote:
    All right.  More experimentation has been done.  Seems like the renaming of Adobe folders fix prescribed in the link below might have helped a bit.
    Premiere Pro CC 2014 renders are painfully slow.
    You can rename folders, but I prefer to do it this way: Premiere Pro CC freezing on startup or crashing while working (Mac OS X 10.9, and later)
    MXSw wrote:
    Kicked out a 1 minute edit with some color/fx in under 10 minutes.  Not as fast as in the past but at least the CPU seemed to be cranking at 500% and above per Activity Monitor.  Its barely gone over 250% in previous attempts.
    That sounds a lot better.
    MXSw wrote:
    Same 1 minute edit took 35 minutes however when I exported from a PP timeline using MXF clips instead of QTs.  I assumed the QTs would speed up the process but in the past I've gotten great performance on big old RED raw files so still a bit of mystery why I can't approach the speeds I had prior to most recent CC update.
    Maybe updating your project file has something to do with it. I'll keep my eye on this issue. Thanks for reporting.
    Regards,
    Kevin

  • Nested = audio render

    I have a bunch of short sequences that I lined up into a stack reel for output to tape. So I ended up with one sequence that is comprised of a bunch of short nested sequences.
    When I went to ETT, I got a window telling me that it would take 16 hours to render my audio. (This for a 25 minute sequence.)
    Needless to say, I canceled the output. I tried various audio presets (mix to 2 channels, split to 4 channels) with the same huge audio render times when trying to go to tape.
    I worked around this by un-nesting everything (cmd-dragging the sequences into the stack reel). The ETT worked like it always does with no audio render.
    My question: what was causing the huge audio render times, and how can I avoid this in the future?
    All sequence were Uncompressed 8 bit and no sequence had more than 4 channels of audio.

    how can I avoid this in the future? seems like you already discovered a suitable workflow, ie sequence content rather than nests.
    alternatively, it seems to me that the nesting is causing the Real-time audio mixing buffer to overflow, so you might try increasing that number in your FCP > User Preferences, and see if that helps
    i'm guessing it is calculated such that each track in the master edit is a sum of all the tracks in the nest, do if you are doing a 4 channel output in both master and nests then that is equivalent to 16 tracks of audio
    hope that helps
    cheers
    Andy

  • 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

  • Forced to render same audio every time I export

    My source material is all synced with audio in 8 timelines ranging from 45 min to 4 hours and I am editing from those, nesting into new working timelines. These original sequences need to be rerendered nearly every time I am working, even though I haven't made any changes.
    If I try to export from a new timeline that includes bits of these nested sequences, the audio render gets held up indefinitely. It seems that to export any small clip, I need to open up all the original source timelines and rerender their audio individually, then render the working sequence. This takes up a huge amount of time and is really killing me.
    Does anyone have any ideas why I would need to continually render the audio from these original sequences even though I am not making changes, or have any ideas of somework around?
    Please let me know what else I can tell you!

    Thank you for your reply regardless!!!
    I found a years old thread that had a similar problem and the initial writer said he fixed it by unchecking the "save media cache files next to originals when possible" option in media preferences (although subsequent visitors to the thread were not helped by this fix). I did check that otion when setting up the project so I decided it's worth a try and I have today and tomorrow as buffer if all goes wrong. I unchecked it and changed the path for my media cache files and database. I waited through reconforming and had to render my avchd files again. The very weird thing is now the program is acting like all my MXF footage needs to be rendered when it never has been neccessary before. Do you have any idea about that?
    I still don't know if changing the media cache location and unchecking that option will solve my originial problem, but we'll see; it's the only potential I've found!

  • Rendering Hundreds of Audio Previews Upon Export, Long Render Times

    Hi everyone,
    I have an assembly cut of a feature, with footage and a timeline at 422 ProRes HQ, 24 fps, 96kHz audio.
    When I try to export any length of a clip, I get exorbitant render times and hundreds of audio previews to render.
    Video alone is rendered almost instantaneously.
    There are some audio files on the timeline (music and SFX) at 48k sample rate.
    Any ideas what the problem is?
    Thanks.
    Premiere CC 2014
    OSX Mavericks
    2 X 2.66 Quad Core Xeon
    32 GB memory
    NVIDIA Quadro 4000 w/ CUDA
    3 tB 7200 RPM - RAID 0

    Thanks, Ann. I'm thinking that may be a factor because this is the first time I've had to work with audio recorded at 96 and I've never had this problem.
    Can anyone else elaborate more?

  • 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.

  • 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.

  • Audio only render time takes forever??? not usually

    Usually the rendering of a clip audio takes moments, then whereever I move it on the timeline it doesnt require re- rendering time. but today thats not the case. Long render time, and if I move the clip, I must re- render it again??? help! I bought 2 more gigs of ram. It also gave me a general error, and an "out of memory" once. Maybe its just a setting hopefully. tried it both on a version of 4.1 and HD 4.5 same issue. Also cant capture straight from my camera without it stuttering, and then audio going out of sync.

    Hi, FCP 4.5 is not compatible with OS 10.4.9 -- you will need to downgrade to 10.4.8 or lower (http://docs.info.apple.com/article.html?artnum=305284)
    Also, are you sure the movie format your rendering is a quicktime file and not .dv/avi/etc. I've run into those same errors when working with other formats that are not native quicktime.

  • 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
    paul

    Thanks for the advice aka danke für den Tipp!
    I'll give it a try!
    Paul

  • 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 thanks

    Your 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.

  • 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 Typo

    Thanks 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?

  • 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