Michael Gissing
195
COW Coins
190
DaVinci Coins
3
Solve Coins
Forum Replies Created
-
Standard def is interlaced and the Boris crawl does a great job as long as you are rendering the final sequence in ProRes or uncompressed. DV codec is bad for titles so copy your final into an uncompressed sequence and use the Boris tool.
Don’t deinterlace titles. It just makes them less smooth
-
Firstly the Boris text tools are better than the FCP ones. If they look bad, my guess is that you are using DV codec in your sequence and also not viewing the result on an external interlaced monitor.
The solution is to use ProRes or uncompressed for your final sequence. However it is more important if you want help to trouble shoot, to give us basic information about your camera codec, sequence codec, settings, frame rates, monitoring etc
-
Timebase correction will certainly help. Color Correction can be done after capture.
If you capture straight to hard drive, then use the codec that you are editing with or as Rafael says ProRes or even uncompressed.
-
Firstly your audio needs to be converted from CD to 48khz wav or aif.
If you shot @ 24 and used the CD as playback, then your telecined footage is running .1% slower. So your audio needs to be slowed by that amount to sync. This is negligible for pitch but if not done, you will see a drift over the length of the song. If the drift is greater than that, then there may be a different problem.
-
Going to DV means converting the analog signal to digital. If you do that with your typical DV recorder or using an external converter, the results are likely to be the same.
I think what you are perhaps confusing is advice to put the analog signal into a timebase corrector and stabilise the video sync. Also there can be enhancements of the signal in the analog domain prior to conversion to digital.
-
I have only seen that sort of behaviour once an it was a still with huge resolution (something like 4000 x 3000 pixels). I resized it to something sensible and the disappearing act stopped.
I don’t think it is a function of the type of plugin, but just FCP not managing any sort of plugin with that resolution. If you have a move on the still, then Shane’s idea of making a QT file is best.
-
Before you needlessly throw away resolution by deinterlacing (unfortunately the common answer to interlacing problems), try adding the shift fields filter (found in the effects tab>video folder.
It might be that the camera uses a different field order to your sequence. You can always check what FCP thinks is the field order by looking at the attributes of the clip.
-
Copy protection is a bit of a waste of time. It gets in the way of legit use and doesn’t worry the pirates.
The real issue for me is not the storage size of HD DVD as multi layering technology means that five layer disks are feasible so 100 + gig storage on HD DVD was almost available when they pulled the pin.
The real issue is the much higher install costs for mass duplicators. Bluray is much more expensive. The other great cost is the high reject rate on Bluray disks. So the ability to make money off the format is in the short term difficult until reject rates are as low as HD DVDs were. The world is moving on anyway so HD DVD/ Bluray are limited commercial options. Meanwhile really cheap multi layer red laser disks are likely to become available to archive 100+ gig material.
-
Lots of potential issues here. Firstly you have a DV sequence and a Blackmagic card. I assume you have selected the correct Blackmagic DV Easy Setup which gives you an SDI output from the card into the digi beta and RS422 machine control.
If so, can you see your Final Cut output looping through the digi beta deck? If yes, then do you have common reference video going to both the digi beta and the Decklink card? Next,is the digi beta setup to reference the input signal or the reference signal?
Finally is the assemble editing picking up during the timecoded pre black section. Also the timecode needs to be setup correctly although it sounds like you have problems back in the SDI and reference area. Lets solve them first.
-
I am running FCS on a G5 dual 2.5 with the last Tiger (10.4.11). So if you want to just upgrade your OS rather than switch to Leopard, then I can tell you that FCP 6.0.5 is working without problems on my G5.
If you are going for the complete OS and FCS, then David’s advice to do a clean install on a new drive is wise. That way the old drive can be left in and used to alt boot if you need to. I still have 5.1.4 installed on an alternate boot drive.