Craig Seeman
2
A.I. Coins
96
Apple Final Cut Pro X Coins
4
Audio Coins
162
COW Coins
Forum Replies Created
-
You really need to answer Ed’s questions. There’s no one size fits all answer.
Internet connection can range from dial up to fast cable modem (or faster).
Computers can range from “state of the art” to a 10 year old PC with Windows 98 and Windows Media Player 6.4
Viewers can range from those in a corporate officer in which IT refuses to allow users to install certain players to a kid with the latest version of Quicktime.
You have to decide WHO you want to view the video and what type of computer and internet connection you think the have.
It’s like asking about how to make dinner taste good. Does your audience eat at McBurgers or the Gourmet French restaurant?
Know your audience and we can tell you how to make the dinner test good to them.
-
When I called up Sony Pro to report the but they told me they’d only just discovered the bug the week before (guess they never thought of actually TESTING to see if the ClipBrowser could handle MP4 sources). I tried to pin them to at least an approximate date but, like any good software developer, they wouldn’t commit. Given they’ve announced ClipBrowser 2 I would guess their intent is to get it out significantly before then. Unfortunately that’s not very accurate.
-
I’ve heard to optimal combination is to have firmware 1.05 and the do the backfocus routine in the maintenance menu. It really peeves me that both firmware update and backfocus really can and should be something the end user can do. Looking at the saw in the maintenance menu can also give you much better idea how the settings in the PPs are working.
-
DGFastchannel here in “the State” asks for 18mbps MPEG2 Program Streams for TV spots. Did they give you a data rate for H264? Apparently not. You might ask them if they have a minimum and maximum.
BTW I’m doing “digital signage” spots at the moment and the digital signage company hasn’t given me data rate specs either. I wonder if this is a new trend.
You could always “turn it up to 11” and see if their system blows up. I sent in an H264 encode at 35mbps (720p30 – they’re all HD) to see if I’ve pushed their limit.
-
I can see a reason for doing a final render of FX and titles in an uncompressed codec or other “higher” codec (Apple Pro Res). While it won’t improve the source files it can keep the titles and graphics from taking that “DV” codec hit.
-
I thought XL stood for the years in Roman Numerals before AutoDesk next updates the program.
It seems very few compression apps allow for adding VBI (Vertical Interval Blanking). The VBI is useful for those who add Sigma encoding as well as Closed Caption. I suspect this is why DG went to 512
-
Emailed to both of you.
-
emailed you the settings.
-
Interesting. You should contact the people who make Shotput ASAP. I can’t imagine though how a copy utility would impact BPAV but it may well be something about ShotPut and Transfer Tool 2.7 that don’t get along.
-
Default to MPEG 4 in Quicktime is 352×288 256kbps or something to that effect.
You need to define your target. What are you using this file for? Web viewing? How fast will be the typical targeted viewer’s Internet speed and computer type/age? Will they be on CableModem and have Quicktime 7 for example. If you have to decide all that before any setting can be determined as optimal.
An 7 year old computer with Windows 2000 on slow DSL in an office that blocks Quicktime will need something different than a 2 year old computer with CableModem and Quicktime 7. If you target the lowest common denominator (everyone) you will target fairly low data rate and codec.