Compressor takes 3 hours to render a 2 minute clip?

Ok what could I possibly be doing wrong.  I have a 01:58 minute clip that I have appied "Old Paper" and a few credit title screens, and I'm rendering on an 2007 iMac with 4GB memory, and a 700Gig Hard Drive.  Why on earth if exporting it to use Apple Pro Res 422 would it be taking over 3 hours to render??????

Ok here is an update.  GET THIS!!!   I read in another forum that you should just export QT from FCP and then import into compressor so I tried it.
My FCPX export Apple Pro ResHQ took...... (drum roll).... 79 SECONDS to export compared to the 20 minutes that Compressor did.
Quality of the two MOV's were identical and the FCPX version was slightly smaller 2.57GB vs 2.75GB for Compressor.
Now I'm totally confused.  I've I'm using the MOV to import into Adobe Encore to author my DVD, what is compressor to be used for ????

Similar Messages

  • In attempt to burn blu-ray, I get QuickTime error 0.  Takes hours to export a 7 minute movie from timeline, then get notice it fails.  What's going on here?

    New problem just started 24 hours ago.  When I try to export from the time line to create a QuickTime file, a 7 minute movie on time line takes 3 hours to export and then the export fails, where as a few days ago, that export would take about 10 minutes at most.  I get the same failure notice when I try to share to blu-ray, DVD, or Vimeo.  Tried to use compressor, no such luck as compressor failed to make a .mov file.  I get QuickTime error 0 message about 5 minutes into trying to share to Blu-Ray now.   Does anyone know what is going on here?  I'm running latest update of Snow Leopard on an intel Mac Pro and the latest update to Final Cut Pro X.  I've also installed QT 7.6.6 to use in creating time lapse movie files.

    Same problem here, too. Final Cut Pro X 10.0.3 on OS 10.6.8. However, it is only doing it on ONE of my projects. A 4-second test project burned successfully.
    I'm  actually going to use iDVD to burn copies for a few people, so I only need the movie file from FCPX.
    Would someone please post best export settings for use on a DVD? In FCPX, the project is  in HD (1080p) with all media optimized to ProRes 442. I know it will have to be down-sampled to DVD resolution, but I've always been curious to know what settings will result produce the best possible quality in DVD resolution.
    Thank you!
    Bart

  • 12 hours to render a 1 hr clip?????

    I have an HDV 1080i hour long clip that I have put color corrections on just about every clip because the black levels were low. I have very limited hard drive space left on my boot up drive BUT I'm not even rendering or saving any FCP files to my boot up drive. I have 4 gigs of memory and my processor is 2.5 GHz Intel Core 2 Duo.
    Why is my computer so slow when rendering in FCP? I'm exporting to a external USB2 drive that I just bought. How can I make my rendering process quicker?
    Thanks for your help!
    Jonathan

    evolution video wrote:
    I have digitized my HDV footage in as ProRes BUT it creates a clip each and every time I turn my camera on and off, which is a HUGE pain to edit. Does this happen to you when you digitize your footage in as ProRes. It also seems that it takes just as long to render and export in ProRes. < </div>
    Something's wrong on your end. You do not need your camera at all. Once your Prores has been transcoded and your sequences match the video codec, you should not need to render anything except yoru effects and transitions.
    Let me ask you this. Will it help for me to get a new iMac with a lot of internal drive space, etc.
    Thanks for your help.
    Jonathan
    Probably not. A common error is to believe a new Macintosh is the answer to everything. What you need to do is work backwards from your desired output goals which should be based on your ability to either make money from your video or to remain within a reasonable out of pocket budget. What do you want to produce and how are you going to pay for it? Then you figure out what camera and support equipment will satisfy that desire and then you figure out what kind of hardware you need to do the job.
    HDV is not a good choice for many reasons and you can research them easily. Prores solves most of them and introduces its own by complicating the ingestion process and presenting many options for proxies and reconnecting or redigitizing at higher resolutions. All easily researched int your manuals but not necessarily easily understood; FCP is a deep and complex application at all levels.
    bogiesan

  • Compressor decoding takes hours

    hi there, I have MacPro, Intel Core Xeon and decoding of project from FCP X with compressor takes hours.
    Its a 4 minute project - even using clusters does not reduce decoding time....
    a) has somebody the same problemes
    b) has compressor app to be open at other macs that are in the cluster?

    What's the frame size of your source?  I notice compressor 4 is taking longer on jobs that need frame re-sizing than compressor 3 did.
    I did have the same problem, despite 8 plus 8 virtual cores fully uitulised, there was endless disk activity and it was taking ages.
    Have you set the number of instances to half the number of your cores (or virtual cores)? - some debate about the number of instances to set.
    In the preferences there's a default option to 'copy source as required', I found it help to set it to 'always copy source'

  • 8 hours to render 30 minute movie

    I must be doing something wrong. I'm assuming it shouldn't take 8 hours to render a 30 minute movie. iMovie version is 7.1.4 I used share with web browser so it would be a "large" movie. Does anyone know why it's taking so long??? It's driving me crazy I loved the old version 4.0.1 and that'll be my next question

    1) Is your source material high definition? If not, rendering in Large is not going to improve SD very much.
    2) LARGE movies in MobileMe look great but they take a great deal of time to load when watching (and a great deal of time to upload.
    3) I recommend that you make a short five minute movie. (For example you can control-click/Duplicate on your project name and make a duplicate project. Then delete everything but the first five minutes.) Then Share it to either iTunes or the Media Browser in Large and Medium. It should take no more than 10 minutes to do the rendering. Then share this five minute movie in Large and Medium to Mobile Me. It may take 30 minutes or more, but it is already rendered, so this is all web transfer time.) Now watch it in both Medium and Large. You will notice that the Large movie takes about 5 minutes to load before it starts playing. The medium movie should start playing almost immediately. Then decide which which way to go for your 30 minute movie. The upload time will be 6 times or more the upload time for your 5 minute movie, and the rendering time will be approximately 6 times the rendering time for you 5 minute movie.

  • AME is taking 20 hours to render 30 min clip from AE

    Hello.
    I am new to Abode After Effects CC and its Adobe Media Encoder CC
    I have made a video in AE cc for youtube purpose.
    I saved the file as a AE File and opened the AME cc Encoder,
    I have opend the AE file in AMEcc and put it in H.264  - HD 1080p 29.97 (Target Rate 32Mbps)
    When I tell it to render, It says its going to take 23 Hours. It started at 8 hours, and went all the way up to 26 hours, and has now sat at 23 hours.
    Its a 30 Minute clip
    Please can you tell me where I am going wrong.
    I used to use AE 5, and I used to render  30 minute videos with AME 5 within an hour, maybe an hour and a half,
    I have only a 4GB RAM But we have moved this file that we are trying to render to another PC that has 8GB of Ram// Win 7,
    Please Help
    Emily.

    It almost killed me, I tell ya. But I FINALLY got it figured on this end. I don't know if this will help you, Emily,, but after the war I just waged, I gotta tell somebody.
    Okay, I uninstalled, and cleaned everything up - the CIA would have been jealous of my deletion skills.
    I reinstalled only Premiere, AE, and of course Media Encoder came a long for the ride, and stopped there - and tried again.
    As you can see - it's only 1 minute long and I got it down to 23mb.
    But then we give it to ole Media Encoder.
    20+ HOURS! But that's still HD, so I scrubbed everything out and tried with the tinest, lowest rate encoding I could dig up.
    I don't know if y'all can see that down at the bottom - but I really did get it down to 2mb just for this experiment. I happily clicked the button and got ....
    *head desk!* *Head desk!* *head desk!*
    Oh them's fighting words! Errr... numbers!
    So, I started researching, overhauling, generally driving myself in circles. Now my video card is decent, but it's not CUDA - but I discovered the card maker had a new driver out - it's beta, but fingers crossed.
    It helped - doesn't have a lot of the bells and whistles, but I have a small but notable difference.
    Media Encoder still crashes upon the second time I open it, or send anything to it, I have to reinstall from the patch file. Now this project I'm doing, I'm in a serious time crunch - so silly me thought it would be easier to get a template, and slap it together and go on down the road.
    I should have known better. The first two templates I used, worked like a charm. Under an hour to render, and we zipped along just fine.
    But now I realize I ow Media Encoder an apology. Not a big one - it's still giving me fits - but a little one.
    It's the way the templates are set up. It would have been faster for me just to build this stuff from the ground up. I ended up ripping these suckers apart and putting them together in a much more efficient fashion.
    I've never had this problem before, I never really looked that hard at this stuff. When I did - I was really to kill someone.
    So, I ended up stripping these things down, and really streamlining them. I also started pre-rendering stuff.
    I pre-compose all the time, but really haven't messed with pre-rendering, I do short trailer stuffs.
    But pre-rendering helped a TON too!
    I got that sucker lined out like you wouldn't believe!
    AND  DRUM ROLL!......
    41 hours
    Well, since this wasn't working like I planned, I went back to AE and tried all sorts of different formats. I couldn't figure out why it worked just great on my first two renders, and it wasn't working with these last two.All four templates are different.
    Then I realized it was because the last two were still awful despite me trying to fix them. I went back to my original template which is about the same length, and it has trapcode - but I tossed something together with that.
    And rendered in 20 min in AE.
    Media Encoder and I still aren't speaking.
    I still haven't been able to get the second two templates to work - but I just got done rendering my project on the first template and it worked like a charm. So that's when I decided to pop over here.
    What exactly do you have going on, Emily? I'm wondering now if not only pre-composing, but pre-rendering as much as you can will help. At least I hope it will!
    It's either that or take a sledgehammer to it - which is still a possibility for me. hehe!
    Cheers,
    kath

  • 3 hours to capture/transcode 40 minutes AVCHD- ProRes 422

    hey all...
    just testing a new core i5 imac (4 gigs ram) - capturing 40 minutes of avchd footage (from nxcam) using log and transfer. transcoding to ProRes 422 and it's literally 3 HOURS to capture this 40 minute clip.
    for this test i'm transferring directly from an sd card to the root drive on the imac.
    does this sound right to you? looks like i'm currently packing up the imac and driving it back to the store for a mac pro tower. i thought the imacs would be fast enough but geez - what's the bottle neck here?
    what's your experience with this kind of log and transfer?
    karl

    Yup...that's an issue with the new AVCHD format that the NXCAM camera employs. Clips under 10-15 min, transfer in near real time. Go over 20 min...BOOOM, it takes HOURS. 30 min typically took me 5 hours. NOT GOOD.
    http://lfhd.net/2010/04/05/avchd-the-pilot-job/
    The solution is third party software. www.clipwrap.com. $50, and now works with the NXCAM footage. I worked with the developer to help solve this issue. The new version of the software now does great. And is tons faster with the smaller clips too.
    Shane

  • Why does it take hours to import mp4 files into iMovie

    I have some home movies I imported from VHS-C and compressed to mp4 files and now I want to start going through them in iMovie but it takes hours just to import a single clip (~575 meg).
    What can I do to speed this up? Would getting a Mac Pro with loads of RAM and CPU's help? Would converting to a different video format before I import work?
    Right now I have all this video I converted to digital and thus far spent days just importing and haven't been able to do anything with it yet!
    I'm using an iMac core duo with 2 gig RAM and the upgraded video card (best one they had at the time).
    Any help is appreciated!

    This worked fine for me, was exactly what I wanted.
    1 - Create the project in iMovie HD and then save and close.
    2 - Locate the file on your computer. Ctrl-click on the file and it will say "show package contents". Click on that.
    3 - You will then see some folder items inside that. Open up "Media" and then drag and drop your mpeg file into it.
    4 - When you reopen the project, you will be notified that there are files in your trash. You want to view them to find the file you just moved there.
    5 - Take that file and drag it back onto the project and you're in.
    A major blessing!

  • Need help to figure out why AE is taking 20 to 30 hours to render 5 minutes of Virtual studio

    While I have been doing video editing for years, I am new to After Effects....Still, I went through the tutorials and Lynda.com, and I think I know my way around it well enough so that my renders should be working far more effectively than they are.
    The big problem is the duration it is taking to have After Effects render a virtual Studio clip, whether I just use a 20 second clip of my reporter with a video playing behind them in an LCD tv set, or if I try to run a full 5 minute version of the entire show....Friday night I tried to run the full 5 minute version of one of , and it took over 36 hours!!!  I am not getting any real help from Blue FX...either the support they offer is really for people that have been using After Effects for many years, and they can't imagine the issues I am having..or, maybe they feel that my issues are more After Effects issue than template issues.
    When I first bought the template a month ago, the PC I had been editing with for years was not powerful enough by most accounts I have read, about what is useful for AE....So I put together a new PC, this one with 32 gigs of ram, an Nvidea 760 video card with 2 gigs of RAM, 8 hard drives and tons of fans for 24 hour operation.
    Some of the things I don't know..... How long "should" one of these 3D virtual studios take to render, where you have already stripped out the greenscreen and are feeding the reporter video in with alpha channel on a quicktime 32 bit animation codec video....and have a 1080p hi res video playing in the TV behind the reporter--in the virtual studio...and you have all the 3 D renders and shadows and effects of the studio template being rendered? Do people really wait 24 to 30 hours for a 5 minute long finished rendering?
    To give you an idea of the studio template and what my computer is having to process, here is a sample we did, no script, just trying to see how this would produce.....and this one I did in 25 second and 10 second chunks/renders, assembling later in Premiere,....still, the rendering was close to 20 hours.
    Beyond the Beach - YouTube
    If any one can suggest what might be going on wrong, that is taking so long, I'd appreciate it. One are I wonder about is whether something needs to be collapsed--I read that some elements need to be collapsed prior to rendering--but how would I know which?

    Rendering composites has always been slow. It is much faster than it used to be. MP rendering still does not work for all situations. Temporal effects and MANY, let me repeat that MANY codecs do not respond well if at all to MP rendering so you should turn that off unless you know for sure your comp and your codec work with MP rendering. I seldom if ever use MP rendering for anything that is not rendered to an image sequence. It is not uncommon for my complex composites to take 2 or 3 minutes a frame. I have had many that take longer. Simple projects, on the other hand, can render as fast as 2 or 3 frames a second. It all depends on the project. That's the way compositing goes.
    Compositing is almost always faster than 3D rendering. I had a 3D project last week that took 25 hours to render 100 frames. You just have to plan for it early in the project.
    Here's what my usual workflow is:
    Avoid Ray-traced rendering unless there is no other way to achieve the design (I also minimize the ray traced paths in 3D apps because it is very slow)
    Pre-render and replace footage elements that I am going to re-use. For example, if I pull a key and I'm going to need to use that key for 5 or 10 layers to pull off a convincing composite I'll pre-render the keyed footage to a lossless production codec and replace the keyed layer in the comp with the rendered file
    Render and replace all Warp Stabilized footage with a suitable DI (lossless digital intermediate)
    Use the Adobe Media Encoder render all deliverables, including production proofs and production masters, usually directly from an AE project file, then start or switch to another AE project and continue working while the AME is chugging away
    Render Image Sequences whenever possible in the production pipeline because it's easier to make changes to frame 200 through 220 when the client wants a change in less than a second of a 30 minute project.
    NEVER try and edit a movie in AE. AE is for sequences or shots, your NLE is for editing
    I have not sat around twiddling my thumbs waiting for AE's render cue to churn out a project in years. The only time I wait for anything is for ram previews. I also have some workflow suggestions for that.
    Just as cell animators do, run motion tests with the most basic of your project's elements. By that I mean set Comp Resolution to automatic, set the Zoom factor to 50 or 25% and check how the motion works before you add any effects that are going to slow things down. If you have already added effects you can temporarily turn them off in the Timeline view
    Check only critical frames or a few critical frames that are in transition (moving) at full resolution because RAM previews at full resolution are short and slow to render and you don't have time to mess around
    If you have long sections to ram preview to verify timing follow rule 1 but modify the ram preview settings to use only every other or every fourth frame
    THE MOST IMPORTANT RULE: Remember that video moves and that you cannot judge the final quality of a video by nit picking a single frame. You must watch playback in real time on the playback device that will be used to see if your scene is working.
    Last rule, if you have gone over the same few frames of a sequence trying to fix something about it for more than 10 minutes, step away from that project and do something else for at least 20 minutes. You'll be amazed how good it looks when you get back to it
    I have one more suggestion for a new AE user. Actually, this is for anyone that works at a computer for a living. Never sit staring at the screen and pounding at the keyboard for more than one hour without standing up and walking at least around the room for 5 minutes to let your head clear and get the blood circulating. You'll be happier, more creative, and have better health and posture.

  • Why does Compressor take so long to export a 10 minute video clip from Final Cut Pro?

    I've been trying export a 10 minute clip from Final Cut Pro. so it can be used with DVD Studio Pro and burned. However, the rendering process has taken 12 hours! The clip I'm exporting has minimal effects, no music, and is in 1080i 30fps. Does anyone know what's going on or what I can do to speed up the process?

    First: How are you exporting? Are you using the Share feature or  Send to Compressor?
    Second: You haven't said anything about your system configuration or really very much about your movie. What is its format… is it really 30fps or 29.97? Whatever it is, are the project settings identical to the clip properties, or were they changed?
    Russ

  • Exporting 48 minute film takes hours. Could you check my workflow?

    Greetings.
    I have just finished editing a project and am trying to export a QT file to be used in IDVD or toast and am wondering if I am going about this in the right way.
    First, a bit of background about my project, settings, and system. G5 1.8 4GB ram. External Lacie 1TB FW 800 drive connected to FW 800 port on G5. The Lacie is where my project file, media,, etc. are on. I have 700GB available space on that drive. My internal drive has 16GB space left, that has the OS, FC, apps, and so on.
    My project was captured from a Canon HV30 via FW using AIC 1080/60. No weird files imported, everything rendered prior to export. The footage was shot HDV30P. The final length of the video is about 48 minutes.
    I added four chapters markers, but none at begining or end as I've learned. I did add an "In" at very beginning of timeline and an "Out" at the very end of project. ( honestly, I'm not sure whether I even need to do this) I rendered everything before export.
    I then went to File>Export QT and un-checked make self contain file. Clicked Ok and a few minutes later I had the file that has the FC logo on my desktop (internal drive)
    Next I opened that file in QT, went to file>export settings were H.264, good quality, Automatic frame rate and clicked Save and directed QT to save that file on my 1TB Lacie. I did not alter the size, I left that at 1280x 720(?)
    My first problem is the time it takes to export this thing.
    My first attempt started yesterday at 4:30PM, I left it going all night and the export was still only about 1/3 the way done the next morning. That attempt was to try and save the export to my desktop (internal drive with only 16GB left on it). Thats when I figured maybe I needed more space for the export, so I'm doing the same thing above right now, but I am now exporting the .mov file to the Lacie 1TB drive. I see by the blue blinking front light on the Lacie that some activity is going on.
    So I guess my first question does it normally take hours/days to export a HDV project to H.264, good quality for a 48 minute project?
    My second question is my goal is to get the project onto DVD using IDVD. I'm assuming I start an IDVD project in widescreen so that my project is viewed on my rather old Sony 4:3 TV, it will appear letterboxed (black bars on top and bottom). This is what I would like.
    Is my work flow good? Do I just need to be patient and make **** sure thatr project is exactly the way I want it before export?
    Sorry for the LONG post, but I wanted tto give as much info as possible for you to access.
    Jonathan
    Message was edited by: Jonathan Levin2

    Ok, so you captured the HDV footage as AIC. Can you double check and report back the actual Item Properties for one of these captured clips ... select one in the browser and press Cmd-9 then post back with the settings listed there. Do likewise for you sequence.
    Then you edited and exported a reference movie ... thats fine if you need to save disk space and you're not intending to use AIC as your edit master version, but still a self contained export would be more robust and further processing would generally be faster/more reliable than working with a self contained media file.
    (A bit off the point, but I also note that you say that +the Lacie is where my project file, media, etc. are on"+ ... Danger, Will Robinson! Or at least, potentially so. Don't throw all your Easter Eggs in one basket. Make sure your project file is not stored in the same physical location as your Autosave Vault directory, else if the drive fails you'll have no means of recovering all your hard work.)
    Next you opened that reference movie in QT Player and used it to create an H264 movie ... is that an intended target? Other than creating a SD DVD copy you don't note the intended audience / delivery for this piece. Creating an H264 version would not be a suggested part of the workflow for SD DVD delivery. You also note that you left the file size at its default, guessing that was 1280x720 ... can you double check that? As noted above already, 1280x720 denotes a HD 720 frame size, not an HD 1080 frame size. Unless you are doing this with specific intent then you'll probably want to leave it unscaled for your edit master.
    Anyhoo, if you're looking for a good workflow for creating an SD DVD from an HD edit then you'll find a lot of good advice here:
    http://www.kenstone.net/fcphomepage/hdv_timeline_to_sddvd.html
    This one may be interesting t you also:
    http://www.kenstone.net/fcphomepage/hdv_to_prores_with_chapter_markersstone.html
    Both of the above are ProRes based workflows but should work equally well if you substitute AIC if thats your preference.
    Best
    Andy

  • Why is Mac OS X 10.7 so much slower than Snow Leopard? It isnt smooth, applications are slow and most dont respond, and dowloads take hours, minutes.

    Why is Mac OS X 10.7 so much slower than Snow Leopard? It isnt smooth, applications are slow and most dont respond, and dowloads take hours, not minutes.

    Something is seriously wrong with your installation or you are critically low on RAM, like below 2 GB.
    How much RAM is in your machine?
    Have you tried a Recovery?

  • Is it normal that rendering 18 minutes long 1080p movie takes hours?

    Hi
    I've got a little question here. Im creating game clips with Premiere Pro.
    Is it normal that it takes hours for 18 mins movie?
    Spec:
    i5 3570k @ 4.2 gHz
    MSI GTX 770 OC
    16 GB DDR3
    1.8TB WD Raid 0

    Thanks for the grab, that is helpful, however what codec is the original footage? I see it's an .avi file, but what codec was used, what screen cap app? I notice the source is 1920x1033 and output is 1920x1080, so you're scaling and that takes extra power. I'd recommend editing in a 1920x1080 sequence, and turn off the "Max Render Quality", and also I don't see the purpose of using 2-Pass VBR encoding when Target and Max are the same, just use CBR in that case. These things should reduce render time quite a bit.
    You can create a 1920x1080 sequence right now, then Copy/Paste contents of the 1920x1033 sequence into it, then try a CBR export (without Max Render checked)
    Thanks
    Jeff

  • Compressor takes FOREVER

    a video file that exports out of FCP 5 (12 minutes long) that takes 4 hours to render, takes over 84 hours in compresser 2! i let it go for about 20 hours, and then i had to stop it, at that point compressor was informing me that there was 85 hours remaining!
    Any help appreciated,
    Nick

    I just finished some tests comparing encoding times with Compressor versions 2.0 and 1.2.1. These tests were done on an 800MHz PowerBook with 512MB DRAM. No other applications were running other than Compressor and Batch Monitor. Compressor v2 was running on Tiger, while Compressor v1.2.1 was running on Panther with QuickTime 6.5.2. In all cases both the source video and output were on the PowerBook's internal 40GB drive (with just over 5GB available -- free -- disc space).
    Quickly stated, Compressor v2 was about 26% slower for each MPEG2 encoding _pass_. Thus, high-quality 2-pass took 52% longer under Compressor v2 than it did under Compressor v1.2.1. Other variables were the Mac OS (Tiger versus Panther) and QuickTime v7.01 versus v6.5.2.
    Below are the actual MPEG2 encoding times for an interlaced, 1 minute long, NTSC/DV25 video clip (configuration C1: Panther with QT v6.5.2 and Compressor v1.2.1, configuration C2: Tiger with Compressor v2):
    The following setting is equivalent to the '60 minute' high quality MPEG2 preset in Compressor v1.2.1 (called 'DVD: Best' and '90 minute' under Compressor v2).
    MPEG2 4:3, 29.97 fps, 2-pass VBR (best motion estimation, 7.5Mbps max):
    C1: 9m 39s
    C2: 14m 39s (52% longer)
    The following setting is equivalent to the 'DVD: Fastest' 90 minute MPEG2 preset in Compressor v2 (a so-called '60 minute' encoding under Compressor v1.2.1).
    MPEG2 4:3, 29.97 fps, 1-pass VBR (good motion estimation, 7.5Mbps max):
    C1: 1m 52s
    C2: 2m 21s (26% longer)
    Each test was run twice and all trials repeated within 3 seconds of each other (timed with a stopwatch). The times for each trial included output of the DV's original audio track into PCM 16-bit stereo (in each case, the audio processing took about 10 seconds). The source clip was 1 minute long and included a good mix of scene transitions (many), cuts, fades to black, 'talking head' and high motion shots. The output MPEG2 files ranged in size between 44MB (C2, fastest) and 49MB (C1, high quality) with Compressor v2 producing slightly smaller files (between three and one MB smaller).
    While the times in Compressor v2 are certainly longer, I'm not seeing the nearly complete failures in encoding speed that some others are reporting. However, things to watch out for are the newly integrated Dolby AC3 audio encoding (obviously slower than simple PCM audio) and the new 'Frame Controls' options for frame rate conversion, resizing, and de-interlacing. While the latter controls (new to Compressor 2) can apparently produce some very high quality results the operations themselves can be quite slow.
    In my tests with Compressor v2 I left the frame control settings on 'automatic.' However, I did perform one trial (high quality/best) with the frame control explicitly set to 'off' and there was no difference in the encoding speed. Thus given my source material and output preset the 'automatic' setting apparently caused no additional processing (equivalent, I suspect, to 'off').
    The output quality looked pretty much identical to me, no apparent quality differences between Compressor v2 and v1.2.1. Strictly speaking, these tests were _not_ done to judge relative image quality but even the 'fastest' 1-pass encodings were good enough that I doubt that the average viewer would be able to determine a difference between the original DV and the MPEG2 output when viewed on a standard television. I did not look for quality differences between the two and one pass encodings, but I suspect that if there were any visual differences they were very minor.

  • 12 hours to render? is that normal?

    I have a G5 dual 2.7GHZ machine with 8GB of RAM. 250GB internal drive with 140GB available space, 500GB external Lacie drive with 300GB available space. and I keep all my project files on the external drive when I work on any project.
    So, I recently finished an edit that was 28 minutes, 30 seconds. it was an infomercial, so it had a lower third overlay during the entire edit, a few transitions, but mostly cuts, and a few filters on some shots, nothing too intense. I rendered the sequence which took a few hours, not sure.
    then I exported to compressor for DVD, and chose the 90 minute option with one pass- faster encode. 4 hours have elapsed, and I have 8 hours to go.
    is that normal?
    I've been using FCP5 for the first time on a new G5 for a few months now, and all the projects that I've rendered out for DVD so far, I just exported and walked away, and usually came in the next day and it was done, so I never really monitored rendering time until now. I upgraded from a G4 500MHZ single processor using Premiere 6.5, and my render times were not nearly that long. I was thinking that with a G5 that was nearly 8 times as fast, my render time would be much shorter, only it got longer. I love FCP5 much more than Premiere, and OSX is great, but render times are just insane.
    again, from the info that I provided, should my render times be that long, or am I doing something wrong?
    thanks for any insight anyone can give.

    checked my settings, and I had it set to normal.
    while I had that window open, I clicked on the Render Control Tab, and noticed that under Render & Playback, all three options were checked- Filters, Frame Blending For Speed, and Motion Blur. could this be a reason? and if I unchecked say Filters, would that mean, it would render the sequence without any filters I had applied?
    one other problem I have been having just this week with this particular project is that FCP seems to be running really slow. other programs run normal, so I'm pretty sure its an issue specific to FCP. for example, just now when I had the sequence settings window open, and I was click on the tabs, from video processing to render control, there was a hesitation before it would display the tab. Its like driving on flat tires or something. and at this time, I have no other program open except Safari, so its not like I"m taxing my resources. what could cause FCP to bog down?
    thanks for your help.

Maybe you are looking for

  • Call function 'gui_download'

    Hallo Friends, I am using the above fuction in my program. I want the header of my internal table to be writen als header in the text file. So, I created another Itab (Itab-col_1) and appended all the headers in this, which I later use as below. Prob

  • Document message bar not visible when participating in Shared Review

    Hi, I have initiated a Shared Review using Acrobat Pro 8 Immediately after I finished sending out the notification to other reviewers, the _Review.pdf version of the document is opened for me and the Document Message bar is visible. Therefore I have

  • Classloader problem with exploded EAR

    I'm trying to un-jar an EAR file and then un-jar the EJB jars within EAR and putting all the EJB and other classes from those jar files in the main application directory like application/com/abc/***. I have few WARs within EAR but I'm trying not to e

  • ALC-PDG-001-000-ALC-PDG-010-015-The conversion operation timed out before it could be completed. Please report this error to the system administrator.

    I am getting the error when trying to convert a word file to pdf. My Adobe Lifecycle ES is  installed on 2GM RAM . Is this the issue for the below error. ALC-PDG-001-000-ALC-PDG-010-015-The conversion operation timed out before it could be completed.

  • Designer repository question

    We currently have our designer repository at configuration 4.0.12.96.16. We were told that this version could be accessed by both Designer 6i and Designer 9i. The repository resides on an 8i database right now and we want to go to a 10g database. I'v