One thing I've found, (which might relate to your workflow attempts so far) is that the edited/locked/unrendered DV sequence, has to be dropped into the 8bit sequence for rendering/exporting. IOW, I can't export a DV sequence, then drop that in an 8bit sequence, because the disparity in scan lines between 720x480 vs 720x486 will 'tear' graphics apart...particularly text.
So I'm on the same page: I
shouldn't export a DV sequence (File>Export>Quicktime Movie>Self-contained movie) and suggest that he place it into a 720 x 486 Final Cut sequence? Or there will be "tearing" issues? (We're kind of seeing that with the Photo JPEG files)
Info to get more specific answers...like...
-how are these digital files expected to be delivered...tape? hard drives? ftp site? (we used to upload our DV shows by ftp, but the uncompressed 8bit are way to cumbersome, so we sneaker-net them on external harddrives).
We're trying to provide our video as digital files via a server/download rather than driving two miles to deliver it on a Beta tape. Since both organizations have FCP, we thought we could expedite-- and save gas, time, etc.-- by providing a serviceable digital file. The question here is: in what flavor?
-what format would be best for cross platforms...FCP/Avid/Premier/Vegas/Velocity/Edius..etc.
The cross platform format question is so they can post the resulting file to a web site so others can download it and use it as a source file. Of course, they'd like to provide in a good quality codec but need to consider bandwidth as well as quality. Their solution is the Photo JPEG approach-- I'm asking, +"Is there something else?"+
-what lenght are these clips expected to be...1min. / 1 hour / various
The length is under two minutes. Never more than that.
-who are the ultimate end users and how will the media be used
The ultimate end users are broadcast news stations and their affiliates. We surmise it won't be long before the satellite uplink delivery is no longer cost-effective and video news packages will be shared like photographs that users can download and use in their publications. But for right now, we're just trying to get our packages over to them and let them decide what flavor they want to serve.
-what additional compressions might take place throughout the pipeline...QT / WMV / Flash / RM
A station might download a segment, use some footage from it and post their resulting package from their web site. Or they could post the entire package as their own news story-- nobody has an issue with that as long as it's seen and used. They will post it as Flash video, as that's what I'm seeing a lot of news web sites using (CNN, NBC, Fox News, etc.)
-"IT / server folks" sounds to me, more like PC based systems...will this ultimately be web delivery / YouTube / output to tape / broadcast / projected in a theater...or other end deliverables.
The IT-server folks control the servers and are concerned about the bandwidth. A larger file equates into more demands on the bandwidth and they don't want the download delivery of a 2 minute package affecting the bandwidth of the server. The pipe is only so big, they say.
Ultimately the end deliverable(s) will often drive the workflow, so please clarify what you/your client are trying to accomplish.
The above describes what it is we're trying to do. We supply our local client with a finished product and they, as a gatekeeper, supply it to the broadcast audience. Their default delivery is a satellite uplink and they're alternatively providing these as on-demand web downloads. Since that delivery is Photo-JPEG, CCIR 601, it seems they're asking us to provide our videos already encoded in that flavor. What we're saying is, "We'll provide you the product as an export from Final Cut-to-Quicktime movie, and
you make the flavor you
want to provide it in."
THANKS for your helpful consideration!