-
Compressor won’t allow send to from FCP
I am using FCP to export a DV PAL compressed timeline of 1 hour which is 40GB big. Every time I try and use Send To I am met with a beep like an error beep. Compressor has worked fine for the last year and I am confused. I know the obvious thing would be re-install but I don’t have it on disk any more. Is it a memory thing? I have 90GB of free space. Thanks in advance.
-
13 Replies
-
[Catherine Tosko] “I am using FCP to export a DV PAL compressed timeline of 1 hour which is 40GB big. “
A 1hour PAL/DV should be around 12/13 GBs.[Catherine Tosko] ” Every time I try and use Send To I am met with a beep like an error beep.”
Those problems when sending to Compressor normally are related with problems on Apple Qmaster.
The best option is trying to reinstall it, but if don’t have the discs that’s difficult.
You can always export a self-contained movie from FC and import it to Compressor. The process will be even faster.
rafael -
I would avoid using send to compressor in general. Instead export self-contained with current settings and bring that file into compressor. Although many people advise against unchecking “self-contained” to export a reference movie, I never had a problem. But I only used reference movies as one-time-use-only files specifically for immediately opening in compressor to compress. I liked it because its a fast export and small file size. I really miss my reference movies now that FCPX and I are exclusive. 🙁
-
Yeah I am avoiding X right now! OK I will give it a go, seems like a plan to use a reference movie and try it out – although it should be a 0/1/yes/no situation on a computer I find this is still a creative process and therefore experimentation can work better than what “they” say. Thanks! Any idea though why the send to has stopped working? I am worried even if I won’t use this workflow as it’s peculiar.
-
The reason it’s so big is that it has cutaways of HD footage and random other clips – it’s a documentary. I should probably use media manager first, but yes, OK, seems like that is the best plan to do the ref movie – thanks! Seems like the beep is a memory issue then?
-
Digital Rebellions helpful Prefs managmenet tools include Compressor prefs trashing. This may be the problem. Making a self contained (not reference) file is still a better option as COmpresor can work in the background and you don’t tie up FCP.
-
[Michael Gissing] ” Making a self contained (not reference) file is still a better option as Compressor can work in the background and you don’t tie up FCP.”
That reminds me, I should mention that in my good experiences with REF’s, I always closed FCP while Compressor is working. But I didn’t think that using the REF in Compressor tied up FCP at all, I closed it for Matrox driver issues. Using an exported Reference movie in another App does not tie up FCP, does it?
-
Send to ties up FCP. Self contained versus reference is another matter. There have been lots of posts over the years about peoples systems spending ages looking for deleted reference bits.
With a self contained no such problems.
-
Yeah, I guess it was just your phrasing that made me think you meant that using a reference movie in compressor also tied up FCP (which I was SURE was not true). I see now that you were referring to “send to”.
It is because of all those people having problems with Reference movies that I made sure to treat them as “throw away” files, always exported with “REF” added to the end of the name so it can easily be found in a smart folder for deleting. Great for quickly exporting a long video, so long as you don’t expect to keep the REF around for future use.
-
[Catherine Tosko] “it has cutaways of HD footage and random other clips “
Then absolutely avoid touch the DV codec.
Render/process/export to a better one.
Prores is always the best option.
rafael -
OK thanks – I will give trashing prefs a try, didn’t try that yet!
Reply to this Discussion! Login or Sign Up