Send to compressor feature crashes compressor 4

Hi everyone. Totally new to this forum lark, so please go easy on me... I updated Final Cut Pro X to 10.0.4 as it was released, and along with it, updated Compressor 4 to the latest version. Since then I've been unable to use the 'Send to Compressor' feature to export my footage as when compressor opens, and I drag a preset onto my clip, I get the spinning beachball of death. (I note that the CPU is hardly being used - Viewing Activity Monitor). I then have to force-quit compressor. I am able to use compressor as a stand alone app - no problem. Simillarly, FCP-X allows export via the apple device presets within its own interface. Wondering if this is something anyone else has experienced since updating? I've removed the Qmaster folder, and emptied the trash, even re-installed both FCPX and Compressor 4, plus repaired permission etc. Im using a Mac Pro 8 Core with 16gb RAM and OSX 10.6.8. Many thanks. Scott.

Thanks Andynick. Funny thing is I did a clean install of Snow Leopard about a week ago (Just as a house keeping exercise really). Everything else seems to be running well. That said, playback on FCPX started to slow and become choppy, audio was distorted too first thing this morning. I checked the Activity monitor and the system useage of the CPU had redlined! FCPX was using 1200% or some such silly amount. I restarted FCPX and all has been fine since. Not had that before either. If a clean install (again) is the only answer then so be it. Have a deadline for a production to complete tonight, so will carry on editing. I can export the completed vid, then drag that to compressor, and all is well. When compressing, the CPU does not get above 40% though, which seems strange - especially as I used qmaster to assign 8 clusters (Half my avail RAM as recommended). Ho-hum.

Similar Messages

FCP 10.1 Crashes when sending to Compressor

Since automatically upgrading to FCP 10.1, I can't send any jobs to Compressor (4.1). When I do File>Send To Compressor, FCP, just crashes. Also, if I just try to open Compressor on its own, it crashes and fails to open.
Please help!
Thanks,
Mark

I thought I wes being pretty precice when I said:
Since automatically upgrading to FCP 10.1, I can't send any jobs to Compressor (4.1). When I do File>Send To Compressor, FCP, just crashes. Also, if I just try to open Compressor on its own, it crashes and fails to open.

I can't export to compressor with FCPX send to compressor button.

I installed FCPX, Motion 4, and Compressor 4. When I try the "send to compressor" button, nothing happens. I can open compressor 4, I can "export using compressor settings" but I can't send a file to compressor to render. What I really want to do is render a new clip from part of my timeline. FCPX seems to only let me export (share) the entire timeline. Any insight into my problem would be apreciated.
Thanks

There are a lot of features I would like to request, how about being able to rename a duplicate project. Anyway, thanks for the answer. I still can't send even a full project into compressor using the send to compressor button. I did find I can use the export using compressor settings, then using the advanced menu I get a send to compressor button that does actually send my project to compressor. I can then select an in and out point and render a small sellection from my timeline.

I try to send to Compressor. It says I need to buy. Compressor is already installed. Help!

I try to export a project from FCP X. When I send to Compressor is says I need to purchase it. I already have it on my computer. Very frustrating and makes me want to move to Premiere.
Please help!

FCPX works with Compressor 4. You cannot send to Compressor 3.

Exporting direct from FCP vs. sending to Compressor?

I've done both, but the choice ends up being a coin toss. So I'm curious if there's any accepted wisdom as to the Pros & Cons of each workflow (using the current versions of each app, and in a hypothetical All Things Being Equal scenario)?
In other words, if you were to create the exact same "Master File" from a given FCP Project using each route (in terms of the finished file's dimensions, frame rate, etc), and you selected the exact same codec/quality options to create that file (assuming the identical options exist to be chosen), would there still potentially be any significant difference between the two files? Either in terms of file size, length of time it takes for the file to be created, or any appreciable difference in image quality (despite the theoretically identical file settings)?
Because a difference in any one of those three categories might be enough to tip the scales towards using one workflow vs. the other, depending on the priorities in a given situation.
(And for the sake of this comparison, I'm leaving aside the issue of which app could still be used for other tasks while the export is in progress. Let's just assume for the sake of argument that in both cases the machine would not be being used for ANY other work during each of the exports.)
Any theories? Real-world experiences? Or has some 3rd-party test site already attempted this kind of direct comparison (using the latest versions of FCP-X and Compressor 4.x)?
Thanks,
John B
Toronto

Without considering every possibility, here are a couple of general thoughts.
Given the same Compressor preset there should be no quality difference between the output from a master fie to Compressor and sending it from the timeline to Compressor. There are speed differences and exporting from FCP X is the fastest workflow. Lately, I've found second fastest to be Send to Compressor. But the inferences differences aren't great.
Most of this depends on one's workflow preferences. The most lengthy workflow is to first export a master file and then bring that into Compressor;. Funnily enough, that is how I work because I want to have an iFrame master file that I can compress for different purposes over time.
One user recently posted that he used Send-to-Compresssor because it gave him the opportunity to pause the processes without losing his work.
In the past (particularly with legacy FCP) the Send-to-Comnpressor workflow was something I avoided. It was slow and unreliable. 10.0.x to 4.0.x was faster but troubled in other ways. The latest versions, however, seem to get it done efficiently.
Final thought: if you do your own tests, check o ensure you have similar amounts of free memory. Otherwise, it's not a "fair fight"/
Russ
edit: override the auto complete

Send to Compressor issue

I felt this should be in the FCPX discussion, not the Compressor discussion...reason below:
I'm on FCPX 10.0.3 and Compressor 4. I have a 4:3 project I want to export as DV/NTSC using Compressor (Leightronix Nexus does not accept ProRes). Anyway, if I select Share > Send to Compressor", it renders for a bit and I get the "3x encoder type unavailable error" that I see in previous posts (yes, I did a search in both FCPX and Compressor communities...all posts were old and unsolved).
But when I select Share > Export using Compressor Settings, it renders out successfully.
Same timeline, same settings, just different Share export.
Any ideas why?
Thanks.
Jonathan

What would you use instead Tom? Isnt letting compressor handle the renders better quality?
Thanks for your help!

Compressor 4 stalling after "send to compressor" FCPX

I just installed compressor, checked for updates to make sure I had the latest version, and tried to use "send to compressor" in FCPX. Compressor 4 stalls and nothing occurs. Wheel of death occurs and I must forcequit to exit. Have any suggestions for this issue? I am trying to send a 2hour video (and a 5 min video).
What is the best way to resolve this issue? Computer shouldn't have any problems with processing this request.
Processor 3.4 GHz Intel Core i7
Memory 16 GB 1333 MHz DDR3
Graphics AMD Radeon HD 6970M 2048 MB
Software Mac OS X Lion 10.7.5 (11G63)

aziliak wrote:
Is it best to export file form FCPX and then import the exported file into Compressor?
IMO, yes. It's more reliable and – even with an additional step – fast. Not everyone likes this approach, but many who know more about what goes under the hood than I do also follow the two step workflow – whether using the new or legacy versions of FCP.
Hard to know why Compressor isn't happy with the 20 minute file. What format are your clips; what are your project settings; what encoding settings are you using in Compressor?
Russ

Help! I am getting: Quicktime error -50...when trying to use the "Share" and "Send to Compressor" function. I need to export my show! Thanks for your suggestions! (using FCP7)

Help! I am trying to export my show and commercials from the timeline. Both Share and Send to compressor are not working.
Its starts compressing then I get Failed"Quicktime Error -50". I appreciate any suggestions.
SYSTEM INFO
Model Name:          Mac Pro
Model Identifier:          MacPro5,1
Processor Name:          Quad-Core Intel Xeon
Processor Speed:          2.4 GHz
Number Of Processors:          2
Total Number Of Cores:          8
L2 Cache (per core):          256 KB
L3 Cache (per processor):          12 MB
Memory:          10 GB
Processor Interconnect Speed:          5.86 GT/s
Boot ROM Version:          MP51.007F.B00
SMC Version (system):          1.39f11
SMC Version (processor tray):          1.39f11

First try exporting a self-contained movie from FCP, the using the resulting file in Compressor. To do it, go to File->Export->QuickTime Movie (do NOT use QuickTime Conversion). In the export window, check the self-contained option but do not "recompress all frames."
Once the export is finished, launch Compressor then use the self-contained file as the source. If that fails, you may want to try using theis: http://www.digitalrebellion.com/compressorrepair/
-DH

Failed batch send to compressor

Hi guys
I'm trying to export a huge amount of footage from FC to Compressor (FC6.06) for a client review. My project disks, in FC and all my destinations on Compressor are set to the external disk. Yet when I run the batch I get a start up disk almost full message from the finder. I have 2 free gigs on the startup dick (I know! I know!), but why would my start up disk be used? Is there a setting for the FC cache, and does that get used when sending to compressor?

But is the OS writing files when FC exports to Compressor?
Constantly.
You can move FCS media content to an external drive: Copy the top level folder to where you want it, then point the application at the new location. Delete the original.
Let's remove some stuff you don't need by installing more!
Download [Monolingual|http://monolingual.sourceforge.net> and remove all the foreign language packs from your applications -most come with a variety of localization files in languages that you neither speak nor read. If you never use iTunes with Latvian menues, it can go. (Apologies if you are in fact Latvian -but you get the idea). If your Mac OS runs in a language other than English, you must still keep it. This will save around 2.5 GB on a standard Mac OS X installation.
Download [Applejack|http://applejack.sourceforge.net> and clear out system and user cache files. Applejack is also an excellent maintenance utility. Read the instructions carefully.
How many printers do you have? Mac OS X installs over a gigabyte of printer drivers from various manufacturers. Get rid of them and install drivers for the device you actually use.
Read Me files, License.txt and other documentation. You already read them, you don't need those items any more. Off to the trash.

Losing in an out points when sending to compressor

Hi
Have just upgraded to FCP7.
In the past I could set in and out points on my timeline in FCP and when exported to compressor it would just compress the material between those points. This was very useful but is not happening in the new version. So for example, if I have some black at the beginning of the timeline it is compressing that despite the fact that before I could set IN at the beginning of the edit and it would automatically go from there. I am exporting it by using the Send to compressor method.
Thanks,
Pete Snowdon

You'll have to step into the nest, select all the clips you want, then send them to Motion.

Export vs Send to Compressor question

I am new to FCP. I have a DV sequence (not HD). What would be the difference between Export > QT Conversion and Send to Compressor for an iPhone movie? Both methods have an iPhone option.
Thanks,
Sonny

Send to compressor and share are basically the same . . . they both save you one step vs the export to QT and then to compressor. The big advantage, for instance in my case, is I post some clips to youtube and it takes care of the entire process. . . asks you for your username and password and then once compressed, sends it directly to youtube. Sort of like an "in house" publisher.
Craig

Compressor 4 breaks "Send to Compressor in FCP7"

Is there a way to set FCP7 up to send to Compressor 4, or at least link it back to 3.5? Compressor 4 IS a standalone app, after all...right, Apple? Current behavior in FCP7 after Compressor 4 install is that clicking Send to > Compressor results in an error tone.

Thanks Adam, please elaborate. What's working? Is FCP7 sending to C4? Is FCP7 sending to C3.5?
After moving apps back and forth a bit (FCPX and C4 are in Applications root, and FCP7 and C3.5 are in Applications/Final Cut Studio), FCP7 is now sending to C3.5 once again. This is fine with me, I just want my old software to integrate as it should again. Ideally, I'd like FCP7 to send to C4, but I'll take the old way.
Wish there was a trial version, I really don't like what I've seen in FCPX so far.
Also, thanks for that link J.K. ROFLing.

Export movie is slow... but why Send to Compressor is so much faster!)

Hi,
I have a question. I had a about 60 seconds long animation to render and as usual, I just whent to Share > Export Movie and wondered how on earth it can take more than 30 minutes to render... After 20 minutes and estimate time was still rising, I just clicked cancel.
Then, for some reason I clicked Send to Compressor and suprized how much faster it rendered! Same file, same settings and same output took only 6 minutes!!! Why???

Good question... I didn't think of that. I have a bluetooth keyboard and mouse, both made by Apple. My friend has a wired keyboard and mouse, plus an external hard drive. I am using wireless internet and my router is about two feet from my computer, and my friend is using wired internet. He has DSL, I have cable. He has a printer connected, and I have one connected to my router.
I know some of those details may be irrelevant... If you need any more information, just ask.

Send to Compressor stopped opening a new batch window

Hello. I am a professional video editor with 22 years of experience, and have been a registered Final Cut Pro user since version 1.
I just finished exporting 14 segments of a documentary using SHARE: SEND TO COMPRESSOR from Final Cut Pro X. Everything worked as expected until I made some changes to a project, then used SHARE: SEND TO COMPRESSOR again. For reasons unknown to me Compressor 4 has stopped opening a new batch window when I send a job to it. It THINKS there is a batch open, because it asks me if I wish to save or discard my changes before closing.
Any ideas?
OS X Lion, Final Cut Pro X, Compressor 4 are all the most recent upgrades running on iMac Quad Core i5 with 8GB RAM.
Regards,
H.
Astounding Pictures

Helo, and thanks Russ. I neglected to mention I was moving forward without Compressor by using SHARE: EXPORT MEDIA. I thought I'd put it out there to see if anybody else had encountered this bevavior. Teething problems are to be expected, though. The beta releases of OS X come to mind. However, I wouldn't trade these new editions for anything except future updates and releases. As a fellow who has had the fortune to work with film, analog video, and linear editing systems, I welcome the radical shift in focus from the older, tedious workflows to something more suited for a data-based age. Mind you, it took about six months to get enough courage to take the plunge, but I'm glad I did.
Sincerely,
H.
Astounding Pictures

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.

Send to compressor feature crashes compressor 4

Similar Messages

Maybe you are looking for