[Jeff Brown]

A standard-def video DVD cannot have a data rate greater than about 9Gbps (that’s giga*bits*, not Bytes, per second) including audio. You have to reduce the data rate depending on the length of your program.

I don’t have a calculator for data rate, as my projects are all less than 20 minutes…

-jeff

[Jeff Brown]

Carly– just to reiterate: the key thing here that might be new to you is that you must create an MPEG-2 file for the video DVD. That’s how you fit long form stuff into a relatively small space, data-wise. Premiere can create this via Export: Adobe Media Encoder. Or, as Mike said, you can take a DV master (like your 60 GB file) into Encore, and Encore can do the authoring and encoding.

-jeff

[Jeff Brown]

QuickTime with the PNG codec is also lossless, but the (lossless) compression will produce smaller files. Just set quality to 100%.
I’d vote for QuickTime being more of a “universal” wrapper, but that’s not absolute.

-jeff

[Jeff Brown]

You can also check in Administrative Tools-Event Viewer; that just might specify what module caused the crash.
AC97 sound has been the culprit on one of my machines.

-jeff

[Jeff Brown]

I’d say the wide blanking is from an analog source, and part of the format. BetaSP perhaps?
Are you by any chance using the “reduce noise” filter? I find that kills Premiere pretty well, even on a fast machine.

-jeff

[Jeff Brown]

… and I’m in agreement with both of you. I do animation and post services, frequently for producer/editors. Some of them have done their own greenscreen keying, but I think they now realize that an acceptable key is different than a really good key. And a really good key takes the initial keying, frequently some roto, plus edge flashing, color suppression, and color correction. And that is best done in a compositing app.

Too bad though, that Keylight doesn’t work in Premiere. Reminds me I’ve been meaning to try it in Combustion (my tool of choice), because I’ve heard such good things about it.

Re: client demands for greenscreening– I’d offer it (even w/ the weather set) but remind them it’s a “premium” service. And charge accordingly.

-jeff

[Jeff Brown]

30P does not have pulldown, hence the “P” designation.
You would need 30i (officially, 59.94i) to use pulldown.

Or, make a custom setup that is 24P. (Which is probably 23.98P).

…and you thought digital was easier… ;>)

The following might help:
https://www.microsoft.com/windows/windowsmedia/howto/articles/UnderstandingHDFormats.aspx#theinfamoustable3

-jeff

[Jeff Brown]

You might also consider doing the titles in Photoshop. The last time I had a quantity of bullet point graphics to manage, it was much easier to do in Pshop than by using the title tool.
In either case, here’s what might help:

Create a folder for each language/region.
Keep the names of the graphics identical, use the folders to separate them. (title_a.psd is a different file in each folder)–
for example:

"project/english/title_a.psd"
"project/spanish/title_a.psd"
"project/danish/title_a.psd"

Make one more folder, we’ll call it “Current”.
Copy the first set of graphics to “Current.”
Do your edit using the graphics in the “Current” folder.
Then, to do a different version, copy a different set to the “Current” folder.

This does have the drawback of not having a Premiere project file for each language, but should “automate” the other part.

-jeff

[Jeff Brown]

But- aside from system sounds, there are sounds I use (Pandora, audio in Combustion, QuickTime) that play through the system device.
Hence my question…

-jeff

[Jeff Brown]

Best to know what your source footage really is. Could be that you are not seeing fields because it was originated on film.

But, for standard-def TV output, PAL and NTSC are both interlaced.

-jeff