13   Hour render hole

Hey all,
   So, last night, as I have done countless times in the past, I set up a long Render Queue (22 items) and started it up before setting off for the night.  I came in this morning, expecting it to all be done.  What I found instead was that, while nothing was frozen, item number 5 in the queue had begun rendering at 7:04 PM, and here it was 13.5 hours later and the item was still rendering.  What was odd was that the render Queue was displaying that it had only been rendering for 7 minutes, not 13.5 hours (the average render time for these scenes is about 25 minutes).  It is as if my computer entered some sort of time vacuum overnight.  The rest of the queue rendered out normally.
   I did notice the render log text file showed the 15 + total hours, but none of the jobs in the queue have render times that account for this.  I have disabled all 'sleep' settings for my computer, so the most obvious cause is out the window.  I'm just wondering if anyone else has experienced this, and perhaps knows the cause, so that I can avoid it in the future.
   Stats wise, I am running the most currently available build of AE CC 2014 on latest generation, fully spec'd MacBook Pro on OSX 10.9.5.
Thanks in advance,
  - Will
(forgive any grammatical oddities or typos, I had to write this out in a hurry)

It's hard to say without knowing anything at all about your composition. Most likely cause is running out of memory. When ever I have long, potentially problem filled renders in the cue I'll set the Secret Preferences to purge every frame and if I'm really nervous about the outcome I'll render an image sequence and turn that into a deliverable later using the AME. It safer.
To expose the Secret preferences hold down the Shift key as you click your After Effects Preferences>General option and browse to the last tab.

Similar Messages

  • Render time.   Is 11 hours render time reasonable for a 90 minute file?

    I started with a 120 minute AVI file, trimmed the last 30 minutes off and am rendering it to an identical format AVI file. Is 11 hours render time reasonable?  Have I set something improperly?

    More information needed for someone to help... please click below and provide the requested information
    -Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
    AVI is a wrapper, what is inside YOUR wrapper?
    Exactly what is INSIDE the video you are editing?
    Codec & Format information, with 2 links inside for you to read http://forums.adobe.com/thread/1270588
    Report back with the codec details of your file, use the programs below... A screen shot works well to SHOW people what you are doing
    http://forums.adobe.com/thread/592070?tstart=30 for screen shot instructions
    Free programs to get file information for PC/Mac http://mediaarea.net/en/MediaInfo/Download
    What effects have you applied to the video?

  • I get 120 hours render time on quicktime h.264 usualy setting

    My Computer :
    Processor : Radeon HD graphics APU A10-5745M 2.10GHz
    Ram installed : 16 Go ( 15.52 usable , 12go on AAE CC )
    Graphic cards :  R7 m260 and HD 8610G
    My project : 10 min long , 3 audio spectrum with glow and a '' bass shake fx on all of them ''
    Usual render time for 1 audio spectrum 5 min long song and bass shake FX = 30 min  , Same setting
    My setting Quicktime H.264 , Lossless sound , Best quality .
    I try to render and i alway get between 80 and 120 hours ... make no sense , it should be max an hour . theres 20k frames to be rendered .
    Now when i installed media encoder it does not help it and still is Sooooooo long to render .... im not sure how to fix this without losing quality

    It seems to be helping quite a bit , but the render is still up at like 41 hours so .... i don't understand ? does having multiple audio spectrum and a bass shake effect on all of them for 11 minute increase the render time by so much ? my first video was quite fast even on h.264  ?  it doesnt look that fancy to me lol

  • After Effects and the simple 20 hour render

    Hi,
    I have this HD scène that is about a minute in playtime. When it was done it rendered out in about 1 hour and 20 minutes on my Intel Quad Core 2.4 GHz. That seems pretty reasonable to me.
    I decided to add some lightwrap and edgeblur for some bad matching cg objects. For this I precomposed transformed layers so I had maybe about 20 preComps. For every preComp I added a matte layer, adjustment layer and light layer. So that's 60 layers. Note that all this is divided over about 10 parent comps (shots) so it's not all in the same comp.
    Anyway, don't think so much about it, it hardly changed render time in the preview. Every frame still takes about 10 seconds to show up on screen when there's no cache, which is the same as before and seens reasonable.
    But after the changes, render time was 20 hours!
    This is ridiculous. It has no crazy stuff at all. Any cg was prerendered in other software and they together didn't even take that long.
    I remember I had crazy render times some other time when I had a LOT of precomps. But the internal preview worked just fine then also.
    It made me think about After Effect's efficiency so I put my CPU monitor gadget on screen (Windows 7 Pro x64) and it shows that After Effects is only doing a half decent job!
    You see that all cores are working. The idle start and first peek is when I loaded the project and started rendering.
    Two questions:
    Why is After Effects lazily using between 20 - 70 % of my CPU? There is clearly no HD I/O bottleneck involved, because 20 hours is enough to copy the internet as a figure of speech, and how can I force it to speed up?
    Can I get a detailed log or something about what is rendered and how long it takes on a per-layer basis so I can see what is the bottleneck?

    Thanks for this information.
    Though partially misunderstood me, pherhaps I said it wrong. Sorry for that.
    I am not having 20 lights. This is a relatively simple 2d composition. I added lightwrap: a copy of the background over the middle- and foreground with some glow and holdout to pretend the subject fits in better.
    I do a lot of compositing, cg and rendering, and anyone in my shoes would agree one maybe two hours is a reasonable render time for what I am doing. The preview time remained the same or increased by a neglitable amount, but the final render time increased 10 times. That strikes me as odd to say the least.
    I have to examine the More Information note from "Information shown for current renders" to see if I can get per-layer rendertimes but it is not mentioned. I will check that on my next render.

  • 9 Hour Render Time?

    Well, I cannot find anything on the internet about why this is happening.
    Earlier, my friend and I recorded some things on the computer, not too hard, right?
    Well, we recorded the footage in 1920x1080 (1080p) for the best looking picture, still following?
    Now, here's what I don't understand, and, keep in mind these are only maxing out at like 18 minute videos. It took about 9 hours for the video to render with the H.264 codec! (On maximum detail, all that jazz)
    If this IS what's supposed to happen, it'd be very helpful to know that, otherwise, some assistance would be nice .
    Thanks!
    Computer Specs:
    Windows 7 Ultimate x64
    10 GB DDR2 RAM
    2 TB HDD/120 GB SSD
    Nvidia GeForce GTX 9800+
    Thanks once again for the help!
    -Chris

    Well, yes and no. If your 9800 GTX+ has only 512MB of VRAM, then you cannot use MPE GPU acceleration at all (and thus you're permanently stuck in MPE software-only mode) because MPE GPU acceleration requires at least 765MB of free, unused VRAM in order to work at all. And 768MB cards cannot enable MPE GPU acceleration because the Windows GUI itself eats up more than 15MB of VRAM. As such, the CUDA hack has no effect whatsoever if your particular 9800 GTX+ has only 512MB of VRAM. So, only those rare 9800 GTX+ cards with 1GB of VRAM can use MPE GPU acceleration at all.
    And in any case, you will see a rather significant improvement in performance in CS5.5 when you upgrade to at least a GTX 560 Ti (even the standard one with 384 CUDA cores): That 9800 GTX+ card is an old design that has only 128 CUDA cores and has only 256-bit access to its DDR3 VRAM. If that card is a 1GB variant, it would still be slower than even a GTS 450 (or Quadro 2000) due to the limitations I described earlier in this paragraph (the GTS 450 and Quadro 2000 both have 192 CUDA cores).

  • Relink render files?

    Does anyone know if there is a way to relink render files???
    We had a crash during the night after a 3 hour render and we really don't have the time for a full re-render of the project. Is there anyway to relink the render files?

    When you first open the FCP project, if the project file thinks there are render files that should be available, it will offer you the option of relinking them. If you do not get that option, it is likely the crash happened in such a way as to not remember (record) the existence of them.
    Sorry,
    x
    Do your part in supporting your fellow users. If a response has been Helpful to you or Solved your question, please mark it as such as an aid to other lost souls on the forum.
    Also, don't forget to mark the thread Answered when you get enough information to close the thread.

  • CS4 Media Encoder Crash after rendering - two files, help?

    I'm not a professional so I would appreciate any advice you can offer.  I was encoding a WMV HD video (edited in Premiere Pro from CS4) that was just under 2 hours long.  On an i7-920 with 9GB of RAM, it took just over 16 hours.  At the end of the encoding, the Media Encoder bar displayed 0:00:00 time left.  But it then froze at that point for about 30 minutes.  Then the program crashed.  I planned to take these WMV files and put them, via Encore, onto a dual-layer DVD with a few other special feature-related videos. 
    I now have two versions of the file in the destination folder, one that has the title I gave it and another that has a "._00_" before the title.  Both files are .wmv files and the one with the normal name is 6.64 GB whereas the one with the ._00_ before the name is 6.60 GB.  Both have problems if I try to play them beyond the 60% or so point.
    Is there a way to salvage these files without another 16 hour render? 
    How long should I expect, on a normal/successful render, for Media Encoder to continue to process the file after the countdown reaches 0:00:00?
    Thanks.  Any advice for this very untrained editor would be appreciated.

    On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
    I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
    Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
    I cant even
    If I find a way to fix either of these problems, I will post straight away.

  • THANK YOU!

    I've been a lurker in this forum for awhile, and so appreciate all the great help that is available here. I was especially needy in that, although I'm an experienced FCP user, I was attempting a large HD project for the first time. I have now completed this project and wanted to offer some help as a "thank you" for what I have received from this forum.
    I have just completed the HD project (108060i) on Final Cut Studio 2 using a dual core G5 (not the fastest anymore). It involved hundreds of clips, lots of rendering, and a "print to tape" final that was over an hour long. So I wanted to share what I discovered to make it smooth (which it was).
    1. There are three settings that must be absolutely correct, or the program simply won't let you work. They are (as you already may know), EASY SETUP, AUDIO VIDEO SETTINGS, and SEQUENCE SETTINGS. There are some quirks…
    a. Easy setup will automatically change the Audio Video Settings, but NOT the Sequence Settings. So you must manually set up the sequence settings for your HD project. It you don't do this correctly, the program will continually try to re-render your timeline every time you open and close. Look at all the Tabs!
    b. HINT: Use the new Apple ProRes 422 as the codec for HD (sequence settings tab "render control")
    c. On my G5, FCP doesn't keep these settings unique. In other words, when you open a Standard Definition project, FCP still has the HD settings! (Yikes). So you have to reset everything for SD, then set it back for HD when you return. This is DANGEROUS and might cause a whole re-render of your HD product when you return and have to re-set all the parameters. So try to stay with the HD until it's finished (not always easy… but just a hint). Perhaps this is only on my machine?
    I have made screenshots of every setup screen for SD and HD just in case my brain can't remember all the settings that work.
    2. SAVE after every single render! Just get used to it with a quick keystroke. If an when you have an issue (and you may), you can simply go back to the save bin and get the last version. I did this many times and it works well. For whatever reason, I was minding my own business and suddenly a render screen popped up and said "4 days to render"! (honest). The timeline turned red, and I was in trouble. I simply went to the bin and got my last save and it all reverted back to five minutes ago (yeah!). Who knows what happened?
    3. Although this version of FC allows for SD and HD on the same timeline, be aware of an issue: Start the timeline with a real HD clip. If you don't, for whatever reason, FCP will "look" at it and often decide attributes for the whole clip. So make certain your first video clip is full HD.
    4. When you go to "print to tape" (for HD, it's practical since we can't make DVD's just yet), be aware of a whole new deal… a new render screen "CONFORMING TO HDV VIDEO." This gets it ready for tape, and it's an entire timeline rendering. My 72 minute program took 4 hours on my G5. Then it returns to a screen that asks you to push the record button. I did four versions of my program, each one requiring this render time to print to tape. In each case I did it before I went to bed, and awoke with it ready to record. No problems.
    HINT: If you have an HD deck (I have a Sony HVR-M15), sometimes it requires a bit of trial and error for FCP to actually "see" it (changing AV and Deck settings to match each other). So I use a 30 second TEST SEQUENCE and do the "print to tape" to make certain it actually is going to work before I do a 4 hour render and find out it won't.
    All in all it went very smooth with the expected learning curve, and I made my deadline. It's a nice system when you listen to it, don't go too fast, and allow for a few hitches (save often!).
    Thanks to all of you for your fine hints!
    LC
    G5   Mac OS X (10.4.7)  

    Thanks for your post allasone.
    Glad you were helped along the way. I still learn new tricks and tips reading these threads as well.
    Couple of minor points/corrections in response to your long and worthy post:
    1. There are three settings that must be absolutely correct, or the program simply won't let you work. They are (as you already may know), EASY SETUP, AUDIO VIDEO SETTINGS, and SEQUENCE SETTINGS. There are some quirks…
    a. Easy setup will automatically change the Audio Video Settings, but NOT the Sequence Settings
    actually Easy Setup does all of the above.
    when you choose an Easy Setup, you are choosing a precofigured set of Audio / Video Settings, which includes amongst others your Sequence Settings.
    there should be no special need for you to mess about with either Audio / Video Settings or Sequence Settings if you choose your Easy Setup correctly.
    when you create a new project, FCP automatically creates a sequence for you using the Sequence Preset as set in your Audio / Video Settings. if you create a new project, and then choose an Easy Setup for your project that is not the same as the previous setup, then the Sequence Settings of your automatically created sequence will need to be changed.
    of course, Easy Setup does not retroactively change the settings of an existing sequence!
    the very easiest thing to do, rather than messing with those settings though is, after changing your Easy Setuo, simply delete the original automatically created sequence, and then press Cmd-N to create a New Sequence. The new sequence will carry the settings of your newly chosen Easy Setup.
    however (as you mentioned in point 3) FCS2 also has a new feature configured in the User Preferences, to allow the Sequence to be auto-conformed to the settings of the first clip dropped into it ... and yes, very good advice, if you intend to use this facility when working with mixed formats, you need to make sure that first clip is in the native format that you wish the timeline to conform to.
    c. On my G5, FCP doesn't keep these settings unique
    FCP can have many projects open simultaneously (HD & SD, NTSC & PAL .. whatever) hence settings cannot be based on project. FCP's settings are system wide.
    You should set them as you need them, when you need them ... as mentioned above it is easiest to use the Easy Setup feature to do this.
    2. SAVE after every single render!
    a little extreme! I would suggest as "general" advice to all, make sure you configure your autosave settings instead to the least amount of time you can afford to lose. however, it may well be that in your workflow, the save after every render was the best solution.
    4. When you go to "print to tape" (for HD, it's practical since we can't make DVD's just yet), be aware of a whole new deal… a new render screen "CONFORMING TO HDV VIDEO."
    its not an HD thing per se. this is specific to HDV and other MPEG HD formats and has been with us since FCP 5. darn good advice though to those working on long format HDV projects
    cheers
    Andy

  • Lines and title flashing across the program monitor and in final export

    I'm seeing very thin lines flashing across the program monitor when playing a complex sequence with 7 video tracks. They draw at various angles and span the entire screen. There can be one or more showing at any time. They are colored and each line appears to be only one color, but different lines can be different colors. Some lines are solid, others are dashed. There is also a ghosty-white representation of one of my titles flashing around the screen for only a frame or two, then it flashes somewhere else.
    Sequences and Tracks:
    Base Sequence: AVCHD with disolves and color correction
    Next Sequence Layer: Base Sequence placed on tracks 1 and 2. Motion is applied to both tracks. LInearWipe and Opacity are applied to Track 2.
    (This creates an image in the center of the screen with a reflection.)
    Next Sequence Layer (1st track of the final 7): Animates Basic3D and Motion (position, scaling)
    2nd, 3rd and 4th of the seven are just like the1st. So there are 4 video screens flying around with reflections and perspective. Kind of like the iTunes album art widget - screen flies in, goes center stage, then flies back.
    Layers 5 to 7 are titles. They are also nested sequences having reflections and Basic3D, but their positions are not animated.
    My system:
    Phenom II x6 1055T
    8 Gb DDR3 1333
    3 Drives 7200 rpm (one program, one preview/conforming, one video)
    nVidia GeForce GTX 260 (3 fans attached)
    3 Case fans plus the side is open - running very cool
    MSI 890GXM-G65 Mobo
    My Project:
    Originated as a CS4 project, opened with CS5 and converted (did not import). Fixed all the title screwups, missing fonts, graphics, hooked up the off-line media etc etc. There are a couple of 1.5 hour nested AVCHD multi-camera sequences which look and play great. Then there are 2 of these monster sequences which are actually used as DVD menus and are about 44 seconds each. When I render these 7 layer menu sequences and play them back, these lines start flashing across the screen.
    Of course the GTX 260 has the GPU unlocked and that works great for the 1.5 hour programs. But if I attempt to render the 44 second monsters Premier stops responding and I have to EndTask it (all CPUs drop to idle while not responding). These monster sequences might test the power of the Quadro CX. So when I work with the menu sequences, I set Premiere to use software GPU and not MPE. Then I can render (2 hours render time to preview 44 seconds with six cores at near 100%). So it does render, slowly.
    I'm exporting an mpeg2 file now and will let you know if the lines show up in the final rendering. I can see the lines showing up on the MediaEncoder's small preview screen as it renders. Doesn't give me comfort.
    OK worst case scenario. The lines ARE in the final mpeg2 file. Makes the file unusable garbage...
    Is anyone else seeing flashing lines and titles?
    Here's a link to a still from the export to illustrate the artifacts.(face and name were blanked out by me)
    http://img23.imageshack.us/img23/5051/premierecs5lineandtitle.jpg
    Thanks

    The crop workaround was successful for removing the lines - worked great. There was the issue of the ghost text which you can see in the screenshot link provided above. This was not removed by crop. Crop removed the lines, but not the ghost. Thankfully, the 4 point garbage mask did work on the ghost and I was able to eliminate it. I had to apply the garbage mask on the sequence where Basic3D was applied not its parent sequence where VerticalFlip was used. The most important thing is that I've successfully migrated this CS4 project to CS5 and can now take advantage of 64bit processing (more RAM) to tame the beast. I'm using this sequence as a menu for a series of DVDs so my time expended will pay me back again and again.
    The asset generating the ghost was built like this...
    In the titler: Text was placed over a logo (.tiff file for logo and it was scaled and moved)
    Base Sequence: Title was brought to two, stacked tracks. VerticalFlip, and LinearWipe were applied to one which was then moved to look like a reflection of the other
    Next Sequence: Layed the Base Sequence down. Applied Basic 3D and moved it's XY position. (This is where I applied the GarbageMask to remove the ghost)
    I tried separating the logo from the text thinking that the logo feature of the titler might be the problem. So I used a separate video track and pulled in the .tiff file directly. It didn't eliminate the ghost. Applying the GarbageMask to the base sequence also didn't help. It was only after Basic3D was applied that the ghost would appear. And since I have Basic3D applied to other reflected text-only layers which do not exhibit the ghost artifact, the bug has something to do with the text/graphic combination with VerticalFlip and Basic3D.
    To top it all off, I can no longer recreate the problem. I've turned off the garbage mask and it's not showing up. While I was testing, the ghost was easy to recreate, but now I can't do it. So I don't appear to be able to drill down deeper. Perhaps it will come back at some point and I can test it further and update this thread.

  • Slow rendering from DVCPro-HD to MPEG2-DVD?

    I have a home built PC with a quadcore 9450 chip, 8GB ram, Vista-64 Business, Mercury rendering (GTX460) - so it's not a particularly slow machine. My current project is 2 hours, 45 minutes long, shot on DVC-Pro HD 720-30P.  It is one continuous take from a concert.  I've added chapter points for each song, but otherwise have not edited it (besides mixing the audio levels.)  With CS5, to export to MPEG2-DVD (VBR-one pass, quality level 5) takes about 16 to 17 hours.  A friend with an i7 computer (which I built for him) says I need to contact Adobe because it should not be taking that long to render.  If I import the Premiere sequence directly into Encore, that render takes only a few hours (not sure of the exact time) but the quality sucks.  My 17 hour render looks pretty awesome for such a long project.   With CS4 and a similar length project, it was around 7 or 8 hours with the same machine.   Is something wrong, or is it normal for such long render times?

    If I understand it correctly, your time-line is 2:45 (hh:mm) long and takes around 17 hours to export. Correct?
    That is pretty good for a Q9450 with 8 GB RAM. Those systems are on average around 15 - 20 times slower than a fast system with MPEG2-DVD export, so it would take a fast system around 1 hour. Now that looks like a perfectly acceptable figure. You have to keep in mind that with hardware MPE you can only compare that with CS4 export times with MRQ (Maximum Render Quality) turned on, and my guess is that you are comparing it to CS4 times WITHOUT MRQ.
    Have a look at the PPBM5 Benchmark and notice where the Q9450 systems are. They are all pretty close to the bottom of the list.
    Seeing those results, one can argue your statement.
    so it's not a particularly slow machine.
    Of course much depends on your particular time-line, but if I take my benchmark results (with a lowly i7-920) versus another Q9450 system, I guess that my export times with your time-line would be around 1:06.
    Maybe not the reaction you were looking for, but I can't change statistical results.
    @ Colin: The OP never said he has MRQ enabled. Where do you get that from? He said he had hardware MPE enabled. And with his timeline, setting MRQ on would not influence his export times, since there is nothing in his single track time-line to profit from MRQ and it is all handled by the MPE engine. At least in this case.

  • Premiere Pro and Adobe Media Encoder running slow

    Hello everyone,
    I'm having trouble with CS4, which is running significantly slower than CS3 did on a older machine. The CS4 suite is installed on a Dell Precision M6400:
    Windows Vista 64-Bit
    Intel Core 2 Duo CPU T9400 @ 2.53 GHz
    8 GB RAM
    NVIDIA Quadro FX 2700M Graphics with 512MB dedicated memory
    The OS is running on a 57.5 GB HD (C:) and the Adobe suite is installed on a 298 GB Solid State HD (D:), except for Adobe Media Encoder, which is installed on the C: drive.
    My project has 4 15-16 minute sequences. The sequences are in DV NTSC, 29.97 fps,  My scratch disks are set to a folder on the C: drive. Media Cache Files and the Media Cache Database points to a folder on the D: drive.
    These are some of the problems I'm having:
    - Premiere Pro CS4 generates peak files every time I open a project
    - It then takes 3-5 minutes to render before I can preview a 16-minute sequence
    - Adobe Media Encoder takes 5 hours to render a 16-minute sequence (as flv) that has been previously rendered
    - AME takes 1 hour to render every 15 minute sequence that has never been rendered before
    Are my settings affecting their performance? Is there any way to improve it? Thanks.
    (Premiere Pro is the only app that is slow)

    The data rate for replay is one thing, the data rate from disk to memory then from memory to CPU and back the other way are different matters and ought not to be confused. It is well-established that for a computer to edit AVCHD you need top end components, and note that I said there were three tasks to distinquish with increasing hardware requirements, namely merely replaying the video, specifying edits in the editor and then the rendering. It is commonly accepted by all the industry vendors that to do remotely commercial AVCHD rendering you need a minimum Quadcore CPU then that eats data fast, in order to not let it go to waste you need a fast motherboard bus fast memory and in order for none of those to go to waste you need the fastest disk set-up you can manage. I in fact have a 4-disk RAID0 volume using SATA (I think the disk model is SATAII but I have to await return from the repair center before I can confirm). For this RAID0 volume I have run speed test software from BlackMagic because I have one of their HDTV capture cards. It recorded that this volume which remember is doing parallelised IO is just fast enough to receive a encoded HDTV stream from the BlackMagic card but too slow to receive an uncompressed HDTV stream, indeed when I tried both I found the volume did keep up with compressed but fell behind with uncompressed. Remember that with a RAID0 volume of 4 SATAII disks a given file gets spread over the four disks and hence IO is spread over those 4 3G/s data lanes. Also remember with these disks 3G/s is just a burst speed, for AVCHD we are interested in sustained serial IO which is much less.
    Before my machine broke down, I found that it took 5 hours to render 33 minutes of HDTV albeit as it went along it transcoded from AVCHD to a Microsoft HD format for Vista-only. Another interesting thing is that I found that the longer this render ran the slower it became, the estimated time started at 3 hours but the actual was five and the last one third took maybe 3 hours. Because the machine broke after that run I couldn't figure the bottleneck. For my machine bear in mind that at the repair shop we found that the Quadcore had only half the necessary electrical power plugged in, the monitor software showed however that it constantly ran around 90% of whatever capacity that reduced power supply permitted. Now then we can puzzle over why it got slower and slower and yet CPU consumption remained consistent and near to full capacity, memory was not the bottleneck because that was constant at 6.4G. But you can say that this was maybe performing like a Dualcore and was hitting some sort of wall, if you had a 1 hour render with that rate of degeneration of performance factored in what would happen to the render time, and for 3 hours you could be running indefinitely. I hope when the machine comes back the correct power supply will make it behave like a Quadcore should for this type of application. Anyway I have two theories for the degradation. First is just that PrProCS4 was getting its knickers in a twist and thereby just doing more computation per minute of video to be rendered as time went by, maybe internal resource management related to OO-type programming maybe, or related to disk IO falling behind, both these theories have problems, for the latter the CPU usage should then have dropped also.
    Anyways, you need really a Quadcore system and blazing fast disk to work fully with AVCHD commercially, we found an external SATAII disk so if I were you I would just go get one and move on with your life.
    Message du 03/06/09 16:08
    De : "Jim Simon"
    A : "JONES Peter"
    Copie à :
    Objet : Premiere Pro and Adobe Media Encoder running slow
    For AVCHD you MUST have FAST disks.
    AVCHD actually has a lower data date than DV. You need lots of CPU muscle, but disk speed is really not a factor specific to AVCHD. Anything that works for DV will work just as well for AVCHD (and HDV as well).
    >

  • Quicktime Export causing Out of Sync Audio?

    I'm trying to export a self contained Quicktime movie from my timeline, and every time I try, the audio ends up being out of sync. What am I doing wrong?
    The audio is set to just the defaults, 16 bit, 48khz.
    Sequence settings: HDV1080p30
    When I bring the final exported movie back into FCP, it plays out of sync.
    Exporting through the Share feature to bluRay resulted in perfect sync audio, so I'm at a loss as to why this isn't working.
    Please help!

    Allright, since nobody out there seems to have the answer - I'm going to share what I discovered so that the next person will actually get an answer without having to spend hours and hours finding it in other forums. Here goes:
    Problem: Audio plays in sync on the timeline, an export from the timeline through Share to bluRay results in correctly synced audio; but a Quicktime Export with current settings results in a final movie where audio is out of sync with the video.
    Solutions: I found two solutions to this problem:
    1- When exporting to Quicktime Movie, check "recompress all frames". This solution had mixed reviews, with lots of people saying you should never do this, as it will reduce the quality of your final output; while others said the reduction in quality was not noticeable to the naked eye. I guess you can try it and be the judge.
    2- In your sequence settings, change the compression setting to Apple Pro Res. This is the setting I decided to go with, as I'm currently awaiting the 10 hour render.
    I did do a quick and dirty test on the ProRes option, where it appeared to work. Since the audio is correctly synced in the beginning of the video and then slowly falls out of sync (obviously the 30p to 29.97 problem), I had to run a test using my entire sequence. If you run a test on a 2 minute sequence, it will appear to be correct, because it is a slow falling out of sync issue - the problems occur later in your project (just fyi). Here is what I did (in case you want to try it on your project):
    I created a new sequence and then changed the compression setting from HDV1080-30p to Apple Pro Res 422. I dragged my sequences into this sequence (so they were nested). I unlinked the audio and then selected about a 20 second area from about 3/4 of the way through the project. I sliced this section and then removed all the video before and after (so it would speed up render time and only render black, but I would still be able to see if the audio synced up later - I hope that makes sense - this made my export time only 12 minutes). After it exported, I reimported the movie, found the little 20 second area, and it was correctly synced. So, now I am exporting the whole thing. I sincerely hope this works. I don't have lots of 10 hour blocks just lyin' around!
    Since my audio issue was most likely due to the fact that I captured and edited in 1080 30p, I believe it must be a bug in FCP that exports the Quicktime movie in 29.97 regardless of whatever your sequence settings are (believe me, I tried to change it to 1080-30p and it didn't work). That is why I think the Apple Pro Res option works, but it involves a total re-render of your project. This is also why I believe it plays fine in the timeline, because my timeline was set to 30p. Again, I also believe that is why my export to BluRay through Share resulted in correctly synced audio - the bluRay export I believe uses the Pro Res codec (which, by the way, took 19 hours).
    Wish Apple would fix this bug.
    Message was edited by: Chermeier1

  • Kernel Problems

    When rendering out HD video in multiple formats, I begin having computer problems. I have a brand new 17" Macbook Pro with 4gig Ram. Sometimes the ram fills up and the graphics card freaks out. Everything on my mac becomes garbled and I have to force it to shut down. I started closing and re-opening Motion periodically to solve that. Now I'm having a Kernel problem. When rendering a file that is only 30 seconds long and very simple, the CPU cycles start spiking. To the point where the computer freaks out. About a third of the way through the render it will render for 10 seconds, computer freezes for 10 seconds, render 10 seconds, and so on. When you quit Motion this continues. Even with the RAM flushed. It's very hard to save everything when the computer and mouse freeze in 10 second increments. Even with everything closed, the computer continues doing this and must be shut off by holding down the power button. I checked Activity monitor. Kernel_Task is at 2% CPU, then the computer freezes for exactly 10 seconds, then Kernel_Task is at 102% CPU for a second and back down. Something is freaking it out and causing it to use so many CPU cycles that it just craps out and even the mouse stops working. This happens on HD projects constantly. It makes a 5 minute render become an hour render. Plus, I have to reset after every render. Very frustrating.

    There were a bunch of errors like this. I'll spare you all of them...
    =====================================================================
    Aug 12 22:59:03 dave-kosss-macbook-pro [0x0-0x22022].com.apple.motion[228]: 0 bytes NOT freed (0 blocks)
    Aug 12 22:59:03 dave-kosss-macbook-pro [0x0-0x22022].com.apple.motion[228]: Maximum blocks allocated at once: 0
    Aug 12 22:59:03 dave-kosss-macbook-pro [0x0-0x22022].com.apple.motion[228]: Total blocks used: 0
    Aug 12 22:59:03 dave-kosss-macbook-pro [0x0-0x22022].com.apple.motion[228]: =====================================================================
    But then after all that I also had this error in the system.log
    Aug 12 23:39:56 dave-kosss-macbook-pro kernel[0]: (default pager): [KERNEL]: no space in available paging segments
    I have no idea what it means, but since it came after the Motion errors and the time stamp was when the error occurred, I think this may be relevant.

  • How to Import an Editable Sequence?

    In Premiere 6.5 to add an existing project to the timeline I just went to File-Import-Project-(select the .ppj project)-choose Beg/Edit Line/or End-OK and the project's timeline would appear on my timeline. I cannot figure out how to do this in Premiere Pro. I can import an entire project, but if I drag the sequence onto the timeline, it appears as a solid item. No clips, no transitions. I hate Premiere Pro.

    I can not remember much detail about 6.5 but if you are more comfortable with it , than thats what you should use.
    >Undo used to tell you what is was undoing. If you are undoing one action it's no problem but for several actions it is a problem.
    Checkout the History Window and you can Undo what ever action from there. Its very easy to see all the actions.
    > can fully open my audio waveforms and they are no way as clear as those in 6.5.How can you even argue the point?
    No point to be made. The waveforms are as clear as required in my system. Maybe its your graphic card. (Post a screen shot.)
    >When rendering in 6.5 the CTI shows you exactly where you are in the timeline. It was clear and convenient. If I have a 15 minute clip that requires a one hour render in Pro there is no movement until it is completed.
    The red render bar shows the progress of the render. Cant actually see the point of why the CTI or the Render bar would make any difference to you. Rendering is Rendering and it takes its course no matter what.
    A/B Editing is your choice. If you feel it the best way for you no reason not to stick with 6.5

  • Is there a way to force GPU acceleration when using After Effects template project?

    I am using the template feature in after effects to create most of my text in a timeline, for about five minutes of text I am sitting on a half hour render. There are two Quadro K4000 GPUs that are spiking at around 8%. Does any one know of a way to force premiere to utilize the GPUs more fully?

    If the After Effects comp is in the timeline, Premiere Pro does the render. At least that's what I'm seeing. Even if the comp is first rendered in After Effects, putting it in the Pr timeline gives the red line. I don't know why you are seeing such long render times just for text -- seems odd. I tried it for a five-minute text comp on Win 7 and it took about 15 seconds, and only used the CPU.
    I remembered seeing a way to tweak the nvidia card to use it more efficiently. Never tried it but here is the link in case you want to explore. The Quadro K4000 is on the list there. Let us know if it helps at all.
    http://www.studio1productions.com/Articles/PremiereCS5-2.htm

Maybe you are looking for