Compressor, FCP 7 and Snow = SLOW

Well, I am enjoying Final Cut 7, and I love the quickness of Leopard Snow. However, I am having major “beach ball” problems that I did not have when I used Leopard and Final Cut 6. I edit a few National daily and weekly TV programs, so I have a heavy workload. Now, when I am using the Compressor to create Blu-Ray files and web editions of the episodes, Final Cut Studio 7 is slowed down to a crawl. When I insert a clip or some music to my timeline and then try to play it, I get a beach ball for 15-20 seconds. After it finally plays, I click on the time line to begin an edit, and again - 15-20 seconds of a beach ball . . . you can see that this becomes annoying quickly and greatly disrupts my work flow.
Now, if I do not run compressor, then FCP7 works like a dream. I was wondering if anyone knows if it is possible to configure the features of Grand Central Station in Leopard Snow or to change hyper-threading in FCP? In my activity monitor, I see that when I have FCP open, I am still running 34 threads on something called CompressorJobController and FCP 7 runs about 46 threads. When I am using Compressor, the activity monitor reads about 40% CPU usage and 50 threads. I really need to multitask to get my work completed. Any suggestions?
Thanks,
d Starr

What Brian Gary is saying, "Was FCS already on you computer (OSX 6) and you just did an upgrade to FCS 3 from FCS 2."
What you really need to do (I think others will agree) is to do a clean install of you OS (not an archive and re-install). And then do all the updates to the OS, and repair permissions. Then do an install of FCS, with updates and repair permissions. With this proceeder everything should work. And if you have third party program install those too.
If you have an extra hard clone this over to the new hard drive as a bootable drive. And in three or six months clone this back over to your Hard Drive and you have a fresh copy of the OS and FCS to work from again. I do this every three months or so...it only takes an hour or so to clone over a fresh copy.
SuperDuper is free and will clone your hard drive.
http://www.shirt-pocket.com/
Jerry Hofmann a few weeks back posted an excellent thread on how to (step by step) install FCS. I don't have the URL. hopefully someone can post that URL.

Similar Messages

Problems with FCP after Snow Leopard Installation

I'm editing canon 5d footage in FCP. I use MPEG Streamclip to properly convert the footage before importing to fcp. Everything was working absolutely fine until I installed snow leopard. Now, all of the clips in the timeline have those weird lines as if I imported the footage without converting it. I have a deadline and if I have to re-edit this entire project it's not going to be pretty. I have installed all of the updates for FCP and Snow Leopard. I tried a test by creating a new batch in MPEG streamclip and the footage is fine. It appears that I might have to re-edit everything.   Can someone PLEASE offer some assistance? I can't afford to re-edit this project.
Thank you

Yes... I am aware of the canon plug in for converting 5d/7d footage. I either use that plug in or MPEG stream clip and they both have been working fine.   "Properly" meaning... FCP does not recognize H.264 (5d and 7d) therefor we need to convert the video using either MPEG stream clip or the free canon plug in. The best codec to edit this footage is ProRes 422LT ProRes422 - I only use the 5d and or 7d cameras for my projects and have been editing this way for some time without any problems what so ever. The problems immediately arose after upgrading to Snow Leopard. The problem lies in my EXISTING FCP projects that are already in the works. I am still able to convert footage for new projects without a problem. I am using the latest updated versions of SL and FCP. I did the following to trouble shoot:
1. Did a clean reinstall of FCP - STILL HAPPENING
2. On an existing project I deleted a few of the problem clips. Took the original and converted it again using MPEG Stream clip. Renamed it and from the FCP project, I located the new clip. SAME PROBLEM
3. On an existing project, I deleted a few of the clips completely. Converted the original again using MPEG SC. Imported the entire new clip in FCP, re-edited it and dragged it into the time line. NO PROBLEM WORKS FINE
4. Opened a new project in FCP.   Took some of the original problematic clips. Converted them using MPEG SC. Dragged into the timeline. NO PROBLEM, WORKS FINE
5. Played both the original clips (before conversion) and the converted clips in Quick Time - NO PROBLEM WORKS FINE
6. Exported part of a problematic project to Quick Time - NO PROBLEM WORKS FINE
7. Opened up one of the same projects from the same hard drive on my other mac (Mac Book Pro) and there are NO PROBLEMS. THEY WORK FINE
Based on everything I've listed above, the problem seems to be happening in the Viewer and Canvas on my I-Mac which I just upgraded to Snow Leopard. The exported projects are fine. Am I to assume that I should continue working with these existing projects and everything will be fine? I've spoke to 5 or 6 friends that are experienced and no one can come up with an answer.

Is there a deus ex maquina for the hashed over HDV- DV conversion issues in the temples of FCP and Compressor??

I want to create a good quality SD DVD from 1080i/60 footage (20 minutes duration) from a Sony ZiU camera (mini DV tape) using FCP and Compressor. I can't do it. My hair has fallen out, but I don't want to throw in the towel.
I have imported the same footage with different FCP presets. The video quality in FCP is excellent.
But once I send the footage to Compressor. I end up with video exhibiting gradations of the following: blurry, jagged edges, jerky movement, darker color. Poor quality especially if a subject (kids playing football) runs fast.
The QT conversion process in Ken Stone’s article (May, 2008/updated in Jan, 2011) provides the most helpful information in getting a quality SD DVD. (Quality means looking as good as SD video DVDs). Except for the fact that the DVD is widescreen, the better quality alternative may just be to stick with the old 4:3 shooting, editing, burning methods that I’ve used for years. Unless of course, I am missing something. Hence my appeal to the knowledgable.
FYI Equipment/software: MAC Pro (OS 10.6.8); ATI Radeon HD 4870; terabytes to spare on 2 internal hard drives; FCS - FCP 7.0.3, Compressor 3.5.3, DVDSP 4.2.2. All applications are on Drive 1. FCP project files, scratch and other setups are on drive 2.
My current settings in FCP appear below. What's wrong here? Better alternative? Or it just may be HDV should not go to a SD DVD.
CAPTURE PRESET: HDV - APPLE PRORES 422
DEVICE CONTROL PRESET: Sony HDV FireWire
VIDEO PROCESSING Render 10-bit material in high precion YUV
I now send the Sequence to Compressor I've tried various settings, and the split screen preview in Compressor reveals on the right side the jaggy, blurred, darker video. Same shows up after submitting; and of course if I try to burn a DVD in DVDSP. I've followed Stone's Aug 31, 2009 article on Compressor 3.5. I experiemented with changes here and there without success (like changing field dominance of even selecting DV NTSC, etc).
If you got this far, thank you. And I really could use the help.
Sorry.Presets: Apple Pro Res 422 1440x1080 60i 48 kHz, HDV- Apple ProRes 422, Sony HDV FireWire. Capture Preset: HDV-Apple ProRes 422; Device control Sony HDV FireWire. Sequence Settings: 1440x1080 HD (1440X1080) (16:9), PIixel HD(1440x1080), Upper/Odd, 29.97, Compressor Apple ProRes 422. Message was edited by: Richard Fera

Michael,
Thanks for the helpful comments. Two tactics today helped. Where ever field dominance was indicated I made sure "upper/top" was the same everywhere throughout FCP and Compressor. That almost eliminated the jagged edges. Also, in the easy setup, I selected Apple ProRes 422 as the format, using HDV to ProRes HQ - Sony -1080i60. Sending direct to Compressor rather than through QuickTime conversion also help produce a clearer, less dark picture.
I'll try your suggesstions especially adding compression markers. I'll check back with you on results.
Thanks

Compressor from FCP very very slow

Why is it that encoding (for DVD) a sequence from FCP using compressor takes so long.
9 hours for 1 hour video through FCP
Going through compressor directly takes 15 min.

I don't understand the workaround though. Why export from FCP and then again from Compressor. If we're going that route why not just export directly from FCP, uninstall Compressor, and trash the user manual??

Exporting from FCP and using Compressor at the same time?

Is it ok to export from FCP and use compressor at the same time? I am exporting a Self-Contained, Current Setting Quicktime Movie, and using Compressor to compress a similar HDV file to Mpeg2?

Only in FCP 7.

FCP 10.1 slow timeline and editing - Any suggestions to improve speed?

Recently updated to OS X 10.9.1 and FCP 10.1. Now experiencing very slow editing and movement in timeline. FCP is responding some 2 to 5 seconds after providing an editing command. The slowest response is to scrolling in the timeline - 2 finger scroll does not respond for up to 10 seconds after doing it.
Render times are fine and similar to previous FCP X versions.
Never had this problem in previous versions of FCP X.
So far I have done the following things based on forums and a call to apple support(?).
Deleted all plug ins.
Started from scratch a project that I was half way through and imported all clips from scratch to a new Library (external Hard Drive).
Deleted FCP and reinstalled including deleting all preferences.
Timeline is quick in the early stages of the project but gets slower as I progress - about 3 minutes into my project now (approx 200 clips) and editing time is becoming impossible.
Am using Mac Book Pro with 2.5 GhzIntel Core i7, 8GB 1333 MHz DDR3, Intel HD Graphics 3000 512 MB.
Anyone able to assist with further suggestions?
Thanks

Hi Ian and Russ
Thanks for your interest.
Hard drive is 500GB of which I have used approx 300GB. I am using an external hard drive for this project.Footage is from Canon 7D/70D which is H.264 which is the same as other successful projects.
Yes I do have a number of photos (say 30 @ 18mp) that I am using as part of the project although I have used these before in previous versions of FCP X without impact.
Tried activity monitor (first time I had used it).
When scrowling through time line (one of the problem activities) memory does not move much- Real memory approx 925mb, Virtual memory 6GB, shared memory 44mb, Private memory 75mb. Interstingly though when performing this task CPU usage goes > 100% and averages 130%.
Does this help with any potential diagnostics and solutions?
Thanks
Re: FCP 10.1 slow timeline and editing - Any suggestions to improve speed?

Exporting Time FCP and Compressor

I have a PowerPc G5, Leopard and FCP 6.
My footage is Apple ProRes 422. This is the first time I'm using this HD footage. (my first movie and all the videos I've made in the past were miniDV)
When I exported through the Export Quick Time Movie the hour long edit took about 10 - 15 minutes. The info for the footage is -
1920 x 1080
HDV 1080p24 integar (Big Edian) Timecode
1:01:57 Time
The problem is it's 11.48 GB and DVD Studio Pro will not compress it so I can make a DVD. (my first miniDVD movie's export was 18gigs and iDVD compressed it to a single DVD) I nolonger have iDVD and I have to use DVD Studio Pro.
I put this movie into Compressor and tried compresssing it. When it finally starts compressing, it says it will take at least 47 hours. Which seem outragous for an hour long movie. The first two times it failed after 6 hours.
Then I went into FCP and tried exporting half the movie (30 minutes) with H264, Quality High, Size 680x382 (current). In 12 hours it was 25% with another 27 hours to go.
Is this normal?
How long should it take to export an hour of HighRes 422 clips?
Is there a setting that I can export fairly quick so I can watch this on my PC and burn a DVD so I can see what it looks like on my TV? It has to be very good, but not the best quality.
This is the first half of a movie that will eventually be close to 2 hours. I can't imagine how long the completed project is going to be.
Thank You!

It actually just said Fail. No reason, no nothing. What might have happened is I've been trying for over 2 days to get this working right, and nothing worked. Last night I exported the sound to AIFF and burned a CD of it, and there's nothing there.
After that, I shut down the computer for a little while, and went back to work. It might have been a glitch that formed from one of the export attempts.
I'm doing this just to watch it on other TVs and computers.
So I went into Export Using QT Conversion
Chose OPTIONS
Changed Settings to Medium Quality, One Pass
Changed Size to NTSC 720 x 480 16:9
I have a movie that about 1gig and looks pretty good. It didn't even take 3 hours.
Now I just have to see what it looks like on other machines.
In Compressor I used the Best Quality for 90 minute DVD and it just sat there for hours not registering anything. I might try again if the DVD I burn of this 264 looks like absolute garbage on my TV. But, for what I'm using it for, it doesn't have to be perfect yet. That comes after I edit the second half.
Thanks for the help!

Why is Compressor 4 so darned slow?

Hello all,
Using Compressor 4.0.6 and FCX 10.0.7. Have a few iMac's, all core i7's, 2011 or later, all with a minimum 8GB Ram. The projects I create are on average 2 hours long, and I produce about 160 of them a year.
I've exhausted trying to find answers on the dicussion forums and online and I can't figure this out. I'm probably an idiot overlooking something, so I'm here seeking guidance.
I finally completely dived into FCX this past month after all the great updates. I LOVE the program. There's been some growing pains getting myself up and running, but I'm pretty much to the point where my workflow is becoming second nature like it was in FC7.
But, Compressor 4 is leaving me stumped. Here's my issue. If I take a master H.264 file that I produced from FCP (7 or X, doesn't matter), that's between 8-10GB's in size and put it in Compressor 3, not changing anything about it's native settings or anything with Q-Master and/or clusters (picture installing it, then instantly create a DVD image file from a master H.264... not touching any preferences), it'll shoot out a disk image file in about 2 hours for me. A Bluray image in maybe 3-4 hours.
This all using i7 quad-core processors in iMacs.
If I try to do the same in Compressor 4, it might take 4-6 hours to produce a DVD image file. 6-8 hours for a Bluray image file.
This isn't isolated to one computer, but on any computer I try. It's PAINFULLY slow. Being 64bit, I was expecting it to be twice as fast as C3.
Then I got into clustering and Q-master and all of that. I've spent days trying to get it right with a lot of trial and error. But whenever I create a cluster following tips on these very forums and others that match the specs of my machines, there will be no dramatic increase in these speeds and most of the time I'll get some crazy number like 36 hours to process. In which case I turn the virtual cluster off and have to settle for the usual 4-8 hour timeframes for it to spit out files (whether they be DVD files for Bluray).
Can somebody with extensive knowledge of C4 please tell me why it's not fater than C3 (I'd be happy with equal results) and what, if anything, I'm doing wrong.
If it helps, one of the computers I'm using is an iMac quad core i7, 2.93ghz, 8GB ram. Just want to throw that out there so if anyone wants to offer "step-by-step" instructions on how to maximize the power of C4 for me on one computer (not interested in daisychaining imacs, yet), they have the vitals for one of my computers that I'll apply those settings to and hopefully figure this thing out.
Thanks to any help or advice in advance!!

Hi David,
Thanks again for your taking the time to investiage some of this stuff for me. I never would have thought to even try a ProRes file, so you learn something new everyday. After your tests and results above, I decided to do some tests of my own. I took 35 seconds of raw footage from FCX and exported using "Master File" and changing the settings to 'LT'. The resulting file was 490 mb's in size, but only took about 6 seconds to export (impressive). I then tried the m4v 1080p route. The resulting file was 44.9 mb's in size, but took a little under real time (about 32 seconds) to export. Both videos look exactly the same when played back in QT.
I then dumped both in Compressor 4 and had the same results you had. The m4v took twice as long as the LT file to export to DVD (one pass) and four times as long in two pass mode.
The next thing I'm going to do is burn a couple test DVD's, one with one pass and one two pass and see if there's any difference in quality. I've been exporting as two pass and if one pass is twice as fast, I'd be extremely happy with that.
As must as I'd like to go the Pro Res LT route for faster Compressor exports, the resulting master file sizes would be way too big for me. I tested a two hour long video and according to FCPX estimates (I didn't actually export the video in this case... just going by what the program is estimating), a Pro Res LT file would be 96.7 GB's in size vs. 8.87 GB's for an m4v file.
Since I include the m4v files as part of the package I return to the client so they can play them in iTunes or Quicktime, on top of DVD's, even if I used the ProRes master file I'd still have to produce an m4v from that.
So for my workflow and for storage reasons, I'll probably stick to creating m4v files as masters since I see no difference in quality. I'll just have to live with the time it takes to produce the DVD's, but if I'm able to get away with 1 pass vs. 2 pass, that would dramatically speed things up.
So you've helped me on two fronts Dave... one with the number of instances for the clusters, which has worked wonders on real projects here for me the past couple of days (and going forward), and the second with the insight about ProRes files, which led me to determining if one pass or two really makes a difference when exporting m4v files.
Thanks again!

IMovie and Snow Leopard... snow rhymes with.... ??

SLOW!
iMovie is unbearably slow under Snow Leopard. Every scene addition, every transition every MOVE brings out the rainbow wheel.
YIKES!!
Any thoughts besides waiting for a fix?

Snow introduces three types of QuickTime.
1) The new QT X player is used as a replacement -- sort of -- to the old QT Player.
2) To support FCP and iMovie there is a QT Framework -- which may also support QT X.
3) There is a version of the previous QT Player you can install.
It appears that while FCP was checked out to work under Snow, the same was not done with iMovie 09.
All folks can do is wait for Apple to release a fix to Snow and/or iMovie 09.

Aperture 2 and 3 and Snow Leopard

My system with Aperture 2 was perfect.
Then I believe that Snow Leopard killed Aperture 2.
When I first installed Snow Leopard my machine felt like new again but slowly and slowly over the last few months the whole system seems to feel less and less snappy.
I don't use many video-intensive applications - my main one is Aperture 2, so this is where I find my main cause for concern.
Painfully slow adjustments with lagging, beach-balling, CPU-hogging, and RAM theft.
The main culprits seem to be Highlights/Shadows, Straighten, Crop, and Retouching… although my open mind says that could simply be because they form the latter part of my tweaking process.
There seems to be a thumbnail generation issue. Every adjustment that is made generates a new thumbnail - as you work through your tweaks that process seems to get backed up and slow everything down.
There seems to also be a video issue. Tweaking horizontal photos in full screen causes twice as much lag as a vertical image. Why? Take a look - it's obvious - in full screen edit a vertical image is about half the size of a horizontal one.
There seems to be a memory issue. Aperture seems to use a large amount of processor and RAM and sometimes doesn't let go of it or it gets caught in some kind of a loop. I've no idea what I'm talking about here. All I know is when I look at Activity Monitor the numbers are going through the roof and I can barely concentrate on them because of the noise from my fans.
There have been various and quite diverse suggestions on this and other forums as to what the underlying problem is and I have done my best to look into those and see what can help.
I have an early-2008 MBP 4,1 - 2.6 Intel Core 2 Duo - 4GB (factory-fitted) RAM - GeForce 8600M (512MB) GT.
I have done everything possible: all software totally up-to-date, re-installed combo updates, rebuilt Aperture libraries, run consistency checks, fresh Aperture install, fresh Snow Leopard install, repaired permissions, booted in 32bit, booted in 64bit, run hardware tests, deleted plists, cleared caches, downloaded and run applications like Onyx and Snow Leopard Cache Cleaner (amongst others) to ensure everything is in ship-shape along with various test applications to gauge if components like my hard drive are dying.
I keep my system clean and tidy. I have now stripped out bloat. I even took out iPhoto in case its 'iLife' browser link to Aperture was an issue. I have 85GB free on a 200GB. All components are original as factory-fitted by Apple.
Everything that any seemingly intelligent person on any decent forum has suggested has been done - in particular I thank the many users here on the Apple forum for all their information sharing… I try to read them all.
From what I see on the forums, I am not alone.
Nothing has fixed this problem.
I (and no doubt many others) have fed this information back to Apple.
Aperture 2 and/or Snow Leopard has a problem that has not been fixed.
Aperture 3 got released and I trialled it and swiftly uninstalled it because the exact same problems are there - even with one single photo in it.
My concern is that Apple will not fix the cause of the problem which seems to lie outside of Aperture.
If Apple concentrate on making Aperture 3 work better inside a possibly shaky Snow Leopard then I will be very disappointed.
I'm not forking out for a new version of software just because Apple broke my current software. Don't get me wrong - I do actually WANT to buy Aperture 3 because it has functional improvements and advancements that I would love to be using providing it works properly - and for me (and it appears for 'quite a few' others as well) it just simply doesn't… and neither does Aperture 2 any more.
I am no technical expert (as you've probably noted already) but a MAJOR bug seems to lie in the relationship between Snow Leopard, graphics cards, and the way it handles memory - and so in turn graphically-intensive applications like Aperture are high-lighting these problems more than others.
I am sure there are people without these problems. Perhaps these problems relate to specific hardware configurations. My configuration is Apple standard. I really shouldn't have these problems.
Until Apple fix this major bug I cannot remotely consider Aperture 3.
Until Apple fix this major bug I could never buy Apple again.
Up until Snow Leopard you had a VERY happy camper. I had a perfect machine and I was shouting Mac from the rooftops to anyone that would listen.
And then it seems Snow Leopard broke my machine.
What a shame.
I really want to use Apple, I actually really like Snow Leopard, I really want to use Aperture, I really want to carry on telling people how wonderful the Apple Mac experience is (or was...) but Apple are currently making it very difficult for me to continue doing so.
Please fix Snow Leopard.
This will hopefully fix Aperture 2 and Aperture 3.
Unless anyone else has a fix?
Sincere apologies to all for banging on for so long !!

Thanks for your input setwart.
When I make adjustments I do want Aperture to provide me with a new version so that I can see the original image and also that I have a version which I have already adjusted. I've previously tried changing that preference before with no improvement in performance unfortunately, but it's not really what I was referring to.
Versions, thumbnails and previews were very confusing terms to me for a while… actually, in some ways, they still are but my understanding is 'a little' better now.
That said, I probably used the wrong term.
What I meant was that every time you make an adjustment Aperture seems to produce a 'record' or 'snap-shot' of your image including that latest adjustment. In so doing you have an entire history of each adjustment you have made. In my head I picture this like a movie film-strip with each frame differing slightly. You increase your saturation by a single point? Another snap-shot. Fancy another single point on your saturation? Another snap-shot… and so on.
It is typical that I will make a bare minimum of 20 adjustments on each image, and that's before even thinking about straightening, cropping, and retouching… and then maybe I'll go back and tweak everything again !!
Somehow, my system is having difficulty in keeping up to speed with all of those snap-shots of individual adjustments. Certain adjustments will drastically slow things down more than others, and then I get to play with the beach-balls.
But - it used to handle these things just fine and that's what I'm trying to get back to.
Thanks again for getting involved.

Using still image in FCP and Motion

I'm using still images in Motion (and FCP) and exporting them to Quicktime movie files. What's the best size and resolution for the images and are JPGs or TIF best? I'm exporting for 720 X 480, and currently my JPGs are 4 x 6 at 300 dpi with a pixel width and height of 1312 x 2000. I'm adding some behaviors to the images in Motion (motion paths and shrink/grow).
My FCP project is setup as a DV NTSC 48kHz, 720 x 480, editing timebase=59.94, timecode Rate=same as editing timebase, compressor-DV/DVPRO-NTSC, quality 100%.
When I export to Quicktime the movies are very low quality--lots of noise and moire pattern etc.
How do I get the best qualtiy using still images? Is it my FPS setting, image pixel size, compressor setting? Also, do the movies need to be deinterlaced?
The preview in the FCP browser and canvas looks a little better but I do notice noise (moire patterns) along the sharp edges of the still images.
I've seen QT movies of these very same images (done by someone else who is no longer around) and they are much better quality.
Does anyone have an appropriate workflow for this type of project? The final movies are to be shown on a flatscreen monitor from a local computer, so the file sizes can be relatively large (300mb).
I can post an example of he movie files if that might help.
Thanks.
Pedro

David, your a genius!!! You posted your reply on my birthday, and I missed it until today!
Fotomagico is devastatingly easy to use and absolutely makes me want to cry at the amount of time I wasted creating photo slideshows in FCP!
I opened Fotomagico up and created a slideshow, one that I had already created in FCP and had take me FIVE HOURS to create... in TEN MINUTES!!!!!!!!! Aaaaaaaaah.
I couldn't believe it. I thought there had to be a catch or something. This was too easy the quality can't be there... but it was. It's amazing and I can't thank you enough for all the future hours you have saved for me.
Al Romero

Green in viewer and very slow

My first couple of days with FCP X. I have 2 x major problems - that maybe related.
The first problem is that it feels like it is slowed down by background rendering but when i check the background tasks everything is idle.
Second as I scroll or play from either event browser or timeline a blank green image appears in the viewer - suspect that this maybe causd by the slowness. it has now got to a point where I cannot continue as almost at a complete halt. I hav equit and restated FCP and also restarted the computer - I have replaced finalcut.plist from the user library.
I am using an iMac 27" - Jauary 2010 - 16 Gb ram. Hard disk external WD firewire 800.
Does anyone have any ideas?

Many many thanks - It was not until I read your reply that I remembered that the footage I was using was from a corrupt Card, that was not recognised by FCP 7 (or iMovie for that matter) and it had been extracted (some months ago) by a converter to H264.
I converted it via Streamclip, this morning, before importing it again into FCP X and all is well.
All the same I had asked FCP X to optimize it on original import. BUT it may not have completed that, as FCP X told me there were background operations in progress when It quit it to do a reboot. Now that might mean that FCP X does not continue to optimize when it restarts - must check that out.
You have saved my bacon. Thanks

Significant color shift between FCP and COLOR?

Hi there,
I get a significant color shift when sending footage - either adjusted or unadjusted/unmodified - from FCP to COLOR.
Before anyone asks, the color shift is visible both internally or on an external broadcast preview monitor.
From within COLOR, I 'send' back to FCP this sequence - which is still without any form of adjustment (apart from being sent to COLOR), the apparent color shift is now visible/added to the imported sequence (from Color).
I've tried this on three separate Macs:
1. The Mac above (6.0.6). (Leopard)
2. A Mac with the same version of FCP as above. (Snow Leopard)
3. FCP and on a third Mac with an earlier version of FCP. (Leopard)
Does everyone have the same problem?
If not, does anyone have a solution?
Cheers,
Dan
PS: I've tried:
FCP > Color ProRes contrast shift
http://discussions.apple.com/thread.jspa?threadID=2150962&tstart=75

I had the same problem except that I am using version 1 of color and Final Cut Pro 6. I isolated just the video and double checked that I had no filters or if I did I turned them off. I had a smooth cam filter on one shot, but that didn't effect it. I was then able to send it to color without issue, once I had no sound or filters or transitions messing up the pass between final cut and color. Try doing the same, just duplicate or copy your timeline to a new timeline. I would have rendered your footage out to ProRes however as using the DVC Pro codec is probably not ideal. Color also only works with actual full raster files, not so good going from HDV or DVC Pro as they have an anamorphic frame size. This may be causing issues also.

Final Cut Suite 1 and Snow Leapard - Can't install

Final Cut Suite 1 and Snow Leopard - Can't install
"Your computer doesn't have the required hardware to run this software, see Read Me for details."
I take a look at the 'Before You Install' file, since there is no 'read me' file and it's hardware requirements are basically ancient for what this computer has.
I assumed that Final Cut Suite 1 was simply too old for Snow Leapard, but my searches are not hitting in Goggle or here at the FCP Forums.
Any ideas would be great, thanks for your time!
-Monty

What is the Final Cut Pro version included in your Studio 1 suite?
If it is a 5.0.x version, then it is Power PC only. That version will install on an Intel based Mac but exhibit some odd quirks. In short, it was incompatible to start with.
A 5.1.x version should [at least in theory|http://snowleopard.wikidot.com>, work without problems.

Anyone using Lion and Snow Leopard? I will be soon.

I will soon be using both Lion and Snow Leopard on my newly upgraded hybrid hard drive.I know that I should need to partition the drive into three 1 for Lion 1 for SL and 1 for data/applications.
The problem is how is how much space should I give each partition?
Has anyone done this before or have any good ideas how to go about it?
Some extra info:
I am currently using a MacBook Pro (mid 2009 13")
I am currently using Lion OS X v10.7.4
The new drive is 750GB Seagate Momentus XT 7200rpm 8GB(solid-state) hybrid drive
The soon to be replaced drive is a stock 250GB 5400rpm HDD
Thanks all help appreciated

It's important that you leave a minimum amount of free space for the OS to use. You will see anywhere from 16 to 30 GBs for your OS and iLife apps. You need enough space to allow for all your third-party applications and document files. When fully set up you may have only 30 GBs of free space which is an appropriate amount to have, but not less than 20 GBs. That makes 60 GBs a reasonable minimum size.
If you haven't put everything in concrete, I might suggest going with a 500 GB Seagate XT hybrid together with a 128 or 256 GB SSD using an OWC DataDoubler replacing the optical drive. I suggest that mainly because using the same hard drive for the OS and Data partitions will actually make file I/O slower. Having two drives and using an SSD for the startup volume will enhance file I/O operations. Only two partitions on the SSD - each 60 GBs - fit neatly in 128 GBs.

Compressor, FCP 7 and Snow = SLOW

Similar Messages

Maybe you are looking for