Is Rendering automatic before Export to Compressor?

Hi, I have some automatic compression set for 45 minutes, but I sent a sequence to Compressor and used 2 settings [ProRes 422 and NTSC DV] for the sequence. The sequence had a green line above it, so I assumed it was already rendered for the Color Correction. However on looking at the sequence later it was "finished" and blue....
I'm wondering if I sent a rendered or unrendered file to Compressor. I thought I would be blocked from sending the file if it were not completely rendered...
Thanks
Jeff

Jefferis Peterson wrote:
I'm wondering if I sent a rendered or unrendered file to Compressor. I thought I would be blocked from sending the file if it were not completely rendered...
Just to clarify, if you're using the *File > Export > Using Compressor* method, you can export unrendered material and, as mentioned, Compressor will render filters & effects from FCP directly into the new file. However, the only circumstance where I've seen this as being beneficial is when exporting directly an MPEG-2 encode. Having Compressor render material directly into the MPEG-2 stream usually results in a pronounced difference (especially for extensive color correction) if you're using a lower quality editing codec (DV, in particular).
Other type of (interframe) compressed encodes (MPEG-4, H.264, MPEG-1) don't benefit quite as much. In fact, I don't think it makes a bit of difference for h.264 material (like encoding for iPods). Same for transcodes (8-bit Uncompressed to DV, DVCPro to ProRes422, etc). In those cases, it's best - from a quality vs time needed standpoint - to render in FCP, then have Compressor perform the transcode from an exported reference movie.
Michael and Jerry have all the other bases covered...

Similar Messages

  • Is the rendering essential before export with AME?

    Hello guys!
    My sequence has red and yellow lines. This means I have to render it for preview. I don't want to render it because I 'm sure for the preview result (I did the same with other projects)
    It needs to be rendered before the export with AME or not?
    I'm not sure, but once I forgot to render warp stabilization effect and the blue line appeared on my footage...

    Hi Yiotal,
    You should not have to render before exporting a project either through the integrated or stand-alone version of AME.  If you got a blue line in your footage, it must have been a bug in PP/AME.  I've had errors exporting projects when using linked AE projects, so outputting bugs do exist.
    Rendering is meant for smooth playback while editing (especially clips with a red bar.  Any decent system will do fine with the yellow bars).  Even if you do render everything before exporting, never use those render files in your output (i.e. make sure the 'Use Previews' box is UNchecked).  I've done some tests and the image quality you get when using render files is inferior.
    Hope this helps!

  • Do I need to render before exporting?

    I have just put together a small project with three sequences in it. Nothing crazy, renders in about an hour on a PB G4/1Ghz. My question though — do I need to render before exporting to a Quicktime movie? Or will it render automatically before exporting?
    Thanks,
    Kristin.

    On a PB/G4, an hour isn't that bad. I started editing on Sawtooth G4s, and had render times of 2-3 hours for not much video. Of course, it all depends on titles, layers, effects, etc.
    Well, if you think about it, exporting a movie to Quicktime IS rendering. I don't think FCP is going to stick a blue "Unrendered" box in, or encode at Dynamic RT quality when making a movie file.

  • When exporting through compressor do you have too...

    Was just wonder if when exporting through compressor does the TL have to be rendered first before you export through Compressor?
    OR will Compressor render the TL out then proceed with doing it's thing?
    Thanks
    AM

    would you recommend trashing all the render files with the render manager before exporting through compressor (something i never do. i always make self-contained QTs first then import to compressor)?
    Yes indeed.
    In fact, that's exactly what I do. I do a Print To Video first - from a rendered timeline, obviously - but then I trash all the render files from that project and send the master timeline out to Compressor before I head home.
    Personally, what I notice most is an almost total removal of the "mosquito noise" (seemingly) inherent in DV -> MPEG2 enocoding. If you're testing on DVD/TV setup using S-Video or Component connections, it's most noticiable. (again, in my experience)
    Give it a shot and tell us if you see any improvement.

  • Do clips need to be rendered before exporting project to video camera?

    I am in the process of exporting an Imovie project back to my video camera for storage on a tape. When I start the export process I get a message that says clips need to be rendered prior to exporting. When I click the button to render clips Imovie goes through the process of rendering the clips and after several minutes the Imovie project starts to export to the camera and runs for about 2 seconds and the Imovie quits.
    Imovie also gives the option of not rendering the clips.
    Do i need to render the clips before exporting them to my video camera?
    iMac4,1   Mac OS X (10.4.9)   Intel Core Duo, 1.83 GHz

    Does the project reside on an external drive? If so, make sure the drive uses the Mac OS Extended disk format, which iMovie requires.
    http://discussions.apple.com/message.jspa?messageID=4176921#4176921
    The crashes are most likely occurring because of external factors, not because of a flawed rendering routine. These can include the wrong disk format, QuickTime add-ons and obsolete iMovie plug-ins.
    http://discussions.apple.com/message.jspa?messageID=2920540#2920540
    Do i need to render the clips before exporting them to my video camera?
    It may depend on what type of clips they are. If they are photos imported with the Ken Burn checkbox turned OFF — which are not rendered as they are imported — iMovie will ask to render them. Do NOT allow iMovie to render the photos at this time for there's a bug that adds lots of jaggies to the images, reducing their quality.
    Karl

  • Render files missing after export using compressor

    The deets:
    Render file path is correct.
    Render files live on an XSAN, shared by multiple users.
    The FCP Sequence is fully rendered before output through compressor.
    After compressor is done working, sequence becomes unrendered.
    Any ideas?
    Manually relinking is not a viable solution - we work with a buttload of media. Each program is 30 mins & takes enough time to render to make this a major issue.
    Thanks in advance!
    -Rich

    I'm sure there's a reason for this to happen, which given the info provided I have not quite identified, however, to keep things going...
    After full render of video and audio export as QT movie "reference" ( uncheck self-contained box before exporting) that will take a lot less to export and a LOT less space.

  • Exporting via Compressor - submit - failed

    When I use Export via Compressor - and I use QT Pro Res - and destination is Movies Folder, then submit - then in the History window it has returned "Failed" 3 times now. The status bar shows, but never any indication that it even starts to work its magic or anything - just after a few seconds, maybe a minute, the word Failed appears. Argh. The motn project is 5 minutes long full of stills and a little video with audio. Help - what am I doing wrong?
    In looking thru this forum, I thot the best export would be QT ProRes - is that causing the failure?
    I previously exported via QT(not compressor) and the resulting file is 10gb which doesn't run smoothly but jerks and hiccups like a pre-rendered file. And 10gb wont fit onto DVD which is where this project will go - as a gift.
    help

    I surely do not take it personal. I have learned that you folks in this group are the best resource I have. I know I am in way over my head. I truly do not know about codecs.
    I have taken Motion directly in to FCP - but I didn't think it would work this time. I should have tried.
    Someone came along at work and told me to use Visual Hub and use setting for mp4, and also try using the DV - ready for FCP - I did both. I really never think of it as wasted effort if I can learn by what I doing, and that is occurring as you are all explaining to me what I should be doing.
    Now as for workflow - I think I did the right thing by starting with Motion, then with the big file sizes went to Visual Hub - but probably could have just gone to opening the Motion files in FCP - then rendering out for DVSP.
    System settings are a boggle to me - so I just use NTSC - DV 720x480 and hope that works - so far the results in my projects are good.
    Again, Thank you for taking time to explain - I appreciate all comments.

  • Exporting using Compressor problem

    I have a 3 minute Motion sequence that I can't export in Compressor - it takes over 5 hours to get halfway through the process. It looks as though Compressor has crashed, it goes so slow.
    Basically I need to make a DVD in DVDSP, urgently. I exported as an H264 Quicktime, which was a breeze, but that comes up as incompatible format when I import this asset into DVDSP.
    What to do? Another CODEC? What MPEG 2 setting might work in Compressor?

    I should add I've read a few posts hinting that Motion is pretty rubbish at lengths of 3 minutes and when you have masks, particles, replicators and a load of images (as I have) it's hard to export. I didn't know that - the manual doesn't warn us!!
    Does rendering in Motion help with the export, or does that just help with smooth playback in Motion itself?
    I exported the file as 10 bit uncompressed, just to see how big that .mov was, and it comes in at 4.3Gb. Hopefully that gives readers of this thread an idea.

  • Exporting in Compressor VS. exporting in FCP

    Hey guys,
    I've noticed that when I send a sequence for exporting through compressor it normally takes almost as 10 times longer for it to export compared to when I export directly in FCP. Why is it doing that and what can I do to make compressor export as fast as FCP or at least faster than how it is right now? I installed 8GB or ram on my iMac because I thought that would help but I guess not.
    Thanks

    Exporting using the Export QuickTime Movie command creates a clip using the settings selected and the render files generated by FCP. From a fully rendered timeline, even a self-contained movie can be output rather quickly.
    Exporting using the Export Using Compressor command causes FCP to disregard the render files and re-render every frame in the timeline using the source footage and all applicable effects and filters. This can under some circumstances create a higher quality clip for Compressor to work with. The downside is that it takes a great deal of time and does not support all third-party filters. Another issue is that high quality .mov file is output for "insurance", so if Compressor fails or if you need to create another version of the timeline, you have to go back to the timeline and export again.
    Many editors use a workflow that includes an Export QuickTime Movie to create the "insurance" clip, then load it to Compressor for whatever versions if the clip are needed (for example, MPEG-2 for DVD and H.264 for web distribution.) I have no data, but most editors feel that this workflow is substantially faster and involves less risk. The final upside is that FCP is not tied up for extended periods doing the export.

  • Export Using Compressor locks up FCP

    Im kind of a newb to compressor so bear with me.... I was under the impression that when you export using compressor from FCP that you were still able to edit and work within FCP as compressor is a separate program. However, whenever i use the export using compressor option i get a dialogue box in FCP that says 'compressor processing' and then it goes through my whole FCP timeline frame by frame. I know in the past i have exported using that option and was still able to work inside of FCP while compressor rendered. Could i have possibly changed some settings in compressor to cause this to happen?

    This also is normal when compressing an HDV source sequence into h.264.
    HDV is a Long-GOP format, which requires a lot of processing power to decode. H.264 is also a highly compressed format, which also takes processor power to use.
    Depending on your machine, you may want to look into how to set up a Quickcluster.

  • When exporting to Compressor, it starts re-rending everything!  Why?

    I edited a 2-hour project with 5 cameras in multiple images so could see all the cameras at once. It took a long time to render, many days, but at least that is done. Now, when I export to Compressor to make a DVD, it starts re-rendering everything! Not only that, it does not use any of the render files, because I noticed the compressed m2v does not include all the rendering. It will take more than 80 hours to compress! Not only that, when it is compressing, I can see it jumping a few frames forward, a few frames back, forward, back, etc...but I told it to do 1-pass compressing! Arghhhhhh.....! (Mac G5 Dual 2.3 GHz, 1 GB Ram.)
    I tried a test of sending just a simple project with one video track and cuts only to Compressor, no rendering needed and no rendering done, and it charges ahead at high speed!
    Does anybody know how to send the rendered project to Compressor, not the original unrendered sequence?
    Mac Mini   Mac OS X (10.3.9)  

    Now, when I export to Compressor to make a DVD, it starts re-rendering everything! Not only that, it does not use any of the render files, because I noticed the compressed m2v does not include all the rendering.
    Can you detail what, exactly, is happening? Do you mean to say that you get a 'Rendering' progress bar? And when you say your ".m2v does not include all the rendering," what does that mean?
    The reason I ask is because I always send unrendered timelines directly to Compressor. That way, Compressor does all processing - for filters, motion effects, compositing, etc - directly to the .m2v file, producing much better quality in most cases. I've never seen a Render progress bar though, and I've been using this method since August or so.
    It will take more than 80 hours to compress! Not only that, when it is compressing, I can see it jumping a few frames forward, a few frames back, forward, back, etc...but I told it to do 1-pass compressing! Arghhhhhh.....!
    Unrendered timelines - depending on how much and what needs to be processed by Compressor - take anywhere between 2x-4x as long as sending a rendered timeline to Compressor. Think of it this way: Compressor is both encoding and doing the processing that rendering would have done. You mentioned that it took days to render, so in that regard 80 hours doesn't seem outrageous if you timeline is now unrendered.
    Also, the 'Processing Frames [#=#]' process bar 'jumping' that you're seeing is a necessary part of creating the GOPs that MPEG-2 uses. That happens regardless of a 1-Pass or 2 Pass setting.
    Having said all that, if you can't afford the time commitment of this workflow, then I'll second Thrillcat Editorial's recommendation: Export as a QT movie.

  • Compressor is not working. When I export to compressor from FCP to encode DVD, FCP freezes and Compressor appears to be working but the progress bar never fills no files are created. I'm using a MacBook Pro 10.6.7 version 2.66 GHz core 2 Duo 4GB 1067 MH

    Compressor is not working. When I export to compressor from FCP to encode DVD, FCP freezes and Compressor appears to be working but the progress bar never fills no files are created. I'm using a MacBook Pro 10.6.7 version 2.66 GHz core 2 Duo 4GB 1067 MH. I'm not new at this. I re-installed FCP successfully. I trashed the preferences. Please help.

    Do you have any filters applied to your clips?
    This happened to me before, I accidently had applied a broadcast safe filter to a color matte that was black....
    I figured it out by duplicating my sequence and deleting items from my timeline 1 by 1 until I was able to export a reference movie.
    Anywho, export again, this time with "self contained" movie selected.
    Then try to import to Compressor.

  • Quality differences between "Export Using Compressor..." and Drag & Drop

    There are quite a few people out there discussing the 24p workflow for the new Canon HV20 (on hv20.com, dvinfo.net, etc.). The HV20 can shoot 24 progressive frames/sec, but stores them as 29.97 interlaced HDV on tape, with an arbitrary cadence.
    One of the better workflows is to capture into FCP using HDV over Firewire, and use Compressor to extract the progressive frames from the interlaced. Its Reverse Telecine seems to automatically figure out the cadence. I've been testing this using the "Other Workflows > Apple Codecs > Apple ProRes 422 for Progressive material (HQ)" preset, with the following modifications, Frame Controls: On, Deinterlace: Reverse Telecine, Frame Size: 1920x1080.
    That's just background.
    The problem is this. If I export the HDV clip from FCP, "Export > Using Compressor...", the resulting 24p footage is extremely high quality. However, if I drag & drop the HDV clip directly into Compressor, or set up a Compressor droplet (arguably more straightforward for batch conversions), the resulting footage has obvious resizing artifacts (jaggies).
    Obviously, I'm keeping everything consistent setting-wise, and have thoroughly examined the resulting .movs. The only difference is the actual image quality.
    Anyone seen anything like this?
    I'm less concerned about this specific workflow than I am about Compressor producing non-identical results from identical footage with the same settings, dependent on your chosen workflow...
      Mac OS X (10.4.10)  

    What I need to know if it is a dramatic different in quality that I should use DVD Pro instead of iDVD.
    If you want a DRAMATIC improvement in quality, shoot sharp, high quality content like Hollywood (usually on film) and have it compressed by high quality hardware encoders.
    There is a good reason Hollywood DVDs look better than iDVD/DVD Studio Pro DVDs.
    F Shippey

  • NEW & IMPROVED! Export Via Compressor

    I just noticed that Export via Compressor no longer ties up FCP! Once you submit your batch, you're free to go back into FCP, close that project and open another and work.
    Sweetness.
    I'm on 5.1.4, not sure when this was implemented.

    EDIT, FALSE ALARM.
    I just realized after I posted the topic that I had added a surround sound group to my batch before submitting it. When I looked at the monitor, it was working on the surround sound group. Once it hit the stuff off the timeline, it grabbed FCP again, so, false alarm.

  • Is it required to render before sending to compressor?

    I was curious, is it required that you render a sequence before it is sent to compressor for compressing? I have a number of sequences where the difference between one and another is simply a cut/paste of one track, usually 15 to 20 mins long, and then the sequence is ready to compress out for delivery to the web. I realize that rendering will allow me to be completely sure everything with a track is ok but 9 times out of 10, I can check the new track in the viewer and if it's ok, just drop it into the sequence. Because there are some text overlays, it requires a full re-render to see the cut, which can be rather lengthy, about 10-15 minutes on my machine. I'd prefer to just cut/paste and send to compressor. Given that sequences are reference based I figured that rendering for compressor is not required as compressor does not use it but thought I would check in case I was miss-understanding something.

    My understanding is that you will get the best quality by NOT rendering before sending to compressor as you will be rendering directly to the target compression rather than to the sequence compression first and then recompressing. However, I doubt you'll see the difference unless you're doing very complex compositing.

Maybe you are looking for