[Alan Okey]

Conduit Live does exactly what you need:

https://www.dvgarage.com/prod/prod.php?prod=conduit2

[Alan Okey]

Storage and Data Rates for Uncompressed SD / HD Video

525 NTSC uncompressed:
8 bit @ 720 x 486 @ 29.97fps = 20 MB per/sec, or 70 GB per/hr.
10 bit @ 720 x 486 @ 29.97fps = 27 MB per/sec, or 94 GB per/hr.

625 PAL uncompressed:
8 bit @ 720 x 576 @ 25fps = 20 MB per/sec, or 70 GB per/hr.
10 bit @ 720 x 576 @ 25fps = 26 MB per/sec, or 93 GB per/hr.

720p HDTV uncompressed:
8 bit @ 1280 x 720 @ 59.94fps = 105 MB per/sec, or 370 GB per/hr.
10 bit @ 1280 x 720 @ 59.94fps = 140 MB per/sec, or 494 GB per/hr.

1080i and 1080p HDTV uncompressed:
8 bit @ 1920 x 1080 @ 24fps = 95 MB per/sec, or 334 GB per/hr.
10 bit @ 1920 x 1080 @ 24fps = 127 MB per/sec, or 445 GB per/hr.

8 bit @ 1920 x 1080 @ 25fps = 99 MB per/sec, or 348 GB per/hr.
10 bit @ 1920 x 1080 @ 25fps = 132 MB per/sec, or 463 GB per/hr.

8 bit @ 1920 x 1080 @ 29.97fps = 119 MB per/sec, or 417 GB per/hr.
10 bit @ 1920 x 1080 @ 29.97fps = 158 MB per/sec, or 556 GB per/hr.

1080i and 1080p HDTV RGB (4:4:4) uncompressed:
10 bit @ 1280 x 720p @ 60fps = 211 per/sec, or 742 GB per/hr.
10 bit @ 1920 x 1080 @ 24PsF = 190 per/sec, or 667 GB per/hr.
10 bit @ 1920 x 1080 @ 50i = 198 per/sec, or 695 GB per/hr.
10 bit @ 1920 x 1080 @ 60i = 237 per/sec, or 834 GB per/hr.

[Alan Okey]

The compressor/limiter filter is designed for this function. Compressors reduce dynamic range (the difference between the loudest and softest portions of audio) by a specified ratio. Start with a fairly low ratio like 1.5:1 or 2:1, perhaps even as high as 4:1 and set the threshold to -60dB. Too high of a ratio is undesirable, as it boosts the noise floor and can make audio sound unnaturally processed and lifeless.

Adjust the final audio gain level so that peak level is around -12 on FCP’s level meters. Consult the TV station to which you’re delivering the final output for specs on required average and peak audio levels.

[Alan Okey]

There’s no danger of Apple dropping nVidia graphics, especially the discrete graphics. What’s at issue here is the nVidia chipsets. Intel is claiming that nVidia doesn’t have the right to produce chipsets compatible with its newest line of CPUs, something nVidia disputes.

In a nutshell, Intel is running scared because of technologies like OpenCL that threaten to make the CPU less dominant in the overall architecture of personal computers. GPU technology has evolved at a much more rapid pace than that of CPUs, and APIs like OpenCL are trying to take advantage of the extra horsepower. As one of nVidia’s co-founders recently put it, what’s really happening here is a battle for the soul of the PC.

[Alan Okey]

[walter biscardi] “People who live by the rumor sites are disappointed 95% of the time when whatever is “supposed” to be coming out doesn’t. “

But Walter, you missed the most important part of the rumor (lost in translation)!

Everyone gets a free puppy!

[Alan Okey]

[Dave LaRonde] “Give ’em an mpeg2 program stream. You can do it in Compressor. Telestream is a lot better than Compressor at this sort of thing: much better quality, much higher bitrate. “

Telestream can do 4:2:2 chroma in MPEG-2, which Compressor cannot. Some stations (i.e. DG Fastchannel) won’t accept 4:2:0 MPEG-2 program streams, only 4:2:2.

[Alan Okey]

[Mark Suszko] “And the old saying goes:

“Build a man a fire, you keep him warm for a night.
SET a man on fire; you keep him warm his whole life:””

I just read this. Thanks, you’re responsible for me snarfing soda through my nose.

I’m definitely going to steal this for future use.

😉

[Alan Okey]

In general, a station should provide you with the required specs, and you need to do what it takes to meet them. Request a spec sheet from the station.

I recently had a client who was given the option to submit MPEG-2 spots instead of Beta/DigiBeta, but Compressor was unable to crete files with the proper specs required by the station. Telestream Episode was recommended to me as an application that can create files with the requested specs.

[Alan Okey]

You mentioned that the video is for internet use, yet you specified 4:3 NTSC, which is technically 720×486 nonsquare pixels @ 29.97fps interlaced. Do you simply mean that you’d like the video to be 640×480 square pixels @ 29.97fps progressive, which is a more appropriate way to deliver SD over the web?

In either case, please, please, please tell us that you shot progressive HD and not interlaced. Please. This will make an absolute world of difference as to the level of quality you can expect when downscaling. If you haven’t yet shot the video, use 1080p30 or 720p30. Avoid 1080i60 like the plague. You could get by with 720p60, but there’s no need to shoot 60p for the web as you’d just be throwing out half of the frames anyway.

[Alan Okey]

Your source footage is terrible, therefore the results are guaranteed to be disappointing. If a good key was important to the client, they should have shot the talent against a proper green screen (not blue) using a proper format (not DV). I’m frankly surprised that your key looks as good as it does given the source material. Nice work.