Michael Gissing
195
COW Coins
190
DaVinci Coins
3
Solve Coins
Forum Replies Created
-
3 hours sounds like a dual layer disk for a playable DVD. You have to use mpeg2 for DVD. A DVDR single layer won’t actually get more than 3.7 gigs so the quality will be poor.
A double pass VBR encode will give best quality for smallest file size. I don’t know if compressor has a preset for that length.
-
Are you sure about your file size? 50 gigs of HDV is over 4 hours. If so it won’t fit on a DVD
-
[Stuart Simpson] “I’m glad to say that here in the UK we can pretty much ignore 4×3 safe, and for broadcast we can use 14×9 title safe which gives us a wee bit more room…”
Until you get the tech reject from the international distibutors which usually happens months down the track after you have dumped the media from your drive.
Here in Australia, subtitles have been allowed that are not 4:3 safe both height and width, so make sure your producer writes that into your contract so the make good is their cost. I speak of course from bitter experience. The distributor had never heard of 14:9 and couldn’t be bothered beyond their tech specs which were largely written last century.
-
I have found the broadcast limiter does the same in PAL. I don’t use broadcast limit anymore, but the RGB Limiter. However, it is best to use the 3 way CC first to lower the peak whites and trim gamma. The RGB limiter is for me just a final safe for the odd spike I had missed.
It is also not fool proof but does seem to give you the same levels post render unlike the broadcast safe.
-
First and foremost, ask the audio facility what they want. I never want BITC, as all I need to know is what is the first frame the file starts on. BITC can get in the way when doing foley so please ask.Also your audio people will advise you on the handle size they prefer.
For pics again ask. If they can run H264, it is a smaller file size. A DV file can be much larger and for long form shows, never fits on a DVDRom so you have to either break it up or send it on a drive.
In short, there is no best way so ask.
-
DVCProHD is 4 times the file size of HDV so it is not a good idea to use it for your rushes. Staying HDV is the most bandwidth friendly.
I am using a dual 2.5 G5 and using HDV 1080 50i with the render set to ProRes. I have no problem running this on my hardware off a LaCie 1TB FW800 drive, outputing to HDCam via SDI (Decklink card)
Your final edit can be output via the Kona to a DVCProHD deck via SDI. I would see that as the easiest workflow with your hardware.
-
I set the render to ProRes and then output HD SDI to an HDCam via my Decklink HDPro card.
-
I am doing final online & grade so I have a combination of HDV plus graphics & text including roll credits etc. So far, I have had no issues with HDV and those elements on long form docos up to 90 minutes. I am using a fast RAID but have also used Lacie FW800 drives as well.
The grades are done with 3 way CC plus lots of extra filters like Nattress gamma curves. I need to render anyway so I do the grade, render to ProRes and play out to HDCam. That work flow has been reliable and simple for me. I hear people go on about the horror of editing a long GOP codec but I have no problems so I am unsure of what they see as a problem frankly.
Your hardware is fine except for using programs like Color.
-
I have the CHV set and I use the clone tool to fix lots of little issues like stealing a patch of sky to paste over a blob of dirt on the lens or to mask a mic dipping into shots. I can be keyframed and has the usual ability to vary size and edge softening etc.
It is a quick and simple fix for issues and can also be used to multiply objects in a shot.
-
I have a G5 dual 2.5 and am running 6.0.4 on the last Tiger (10.4.11 from memory). I have found no issue with HDV native, ProRes render with that hardware (plus a Decklink HDPro card). I don’t see the point in transcoding to AIC when you can stay native and do your final renders in ProRes. Also HDV, shot on the Sony Z1, is interlaced and upper dominant.
I would recommend upgrading to FCS2, staying with Tiger, rather than using FCP 5.1.4. I will eventually be upgrading to a Mac Pro and Leopard but have enjoyed waiting for the dust to settle.