[Ed Dooley]

Is the 8800 either of these models? And if so, did you happen to look at NVidea’s site for an answer? And if so. did you find this? It doesn’t mention Quartz Extreme, but it does say 8800 and 23″ Cinema Display in the same sentence as “no display”.
Ed

Question: No display on Apple 23″ Cinema Display when connected to Geforce 8800GTX/8800GTS

Answer: NVIDIA has verified and fixed this problem through an update video BIOS firmware update. Since each video BIOS is custom made for the graphics card make and model, please contact the manufacturer of your Geforce 8800 graphics card to obtain a newer video BIOS version. You may find a list of some of our board partners contact information through the following URL:

https://www.nvidia.com/object/hardware_support.html

[Ed Dooley]

Not to take away from the other suggestions, they are all good, but Compressor using Frame Controls also works well, and you already have it. Do a search, it’s been discussed a bunch of times here.

Ed

[Ed Dooley]

Have you looked into Compressor or Nattress filters?
https://www.nattress.com/Products/standardsconversion/standardsconversion.htm
Ed

[Ed Dooley]

I meant to say .f4v instead of .m4v. But Adobe does say that Flash supports all of these variations of H.264:
F4V, MP4, M4A, MOV, MP4V, 3GP, 3G2
Ed

[Ed Dooley]

You’re working in NTSC? Then they’re rectangular pixels. Photoshop has a preset for NTSC so you can work in square pixel PS world and it adjusts for NTSC non-square pixels for you. You used to have to manually create stretched images to have a perfectly round circle on your video, but not anymore. DPI doesn’t mean anything in video, it’s the pixels that count. If you’re looking at NTSC video on a computer monitor, you’re seeing interlacing. You need to view on an interlaced video monitor. Having said that, if it looks good now, don’t mess with it. 🙂
Ed

[Dennis Dean] “Hi Ed, – viewing on a computer monitor, (in Final Cut) with everything rendered, as far as I know. In the interim, I’ve fixed the issue but not sure how. I created a new photoshop version of the logo from the original illustrator file – made certain I adjusted it for square pixels when I resized it – and added an alpha channel. I don’t think the first logo I was using was adjusted for square pixels nor did it have an alpha channel. I also created that file in significantly higher resolution, (600 dpi rather than 300 dpi which I usually use). The LiveType also became sharper – tho I didn’t touch that. I’m going to create another version and try some movement on the logo – and see how that works. Does anything in particular that I’ve described sound like the reason for the problem?
thanks”

[Ed Dooley]

That’s a good site with useful information. This one below should help you understand it better too. It’s a 5 page tutorial. One of the most important things is that that moov atom in a file is usually put at the end of the file. That forces the entire video to download before playing (it doesn’t affect streaming video, just progressive download). They have a few tools listed on page 2 that moves the moov atom to the header, so it will progressively download. Adobe says they’ll fix it in an update.

https://www.adobe.com/devnet/flashplayer/articles/hd_video_flash_player.html

Here’s another good basic how-to:
https://justin.everett-church.com/index.php/2007/12/06/working-with-h264-in-flash-player-concepts-101/

And some folks have been simply changing the tag from .mov to .M4V which can cause problems. I think it’s best to encode right to .m4v
Ed

[Ed Dooley]

What are you viewing it on, a video monitor or a computer monitor. Was the text rendered, or need to be rendered?
Ed

[Ed Dooley]

I try to avoid the trips out of FCP too. I still do all my “Ken Burns” moves in AE though. I’ve been using it for so long that it’s so much easier for me. I think the scaler’s better in AE anyway. If I spent more time doing it in FCP I guess I would get better. 🙂
I don’t purport to be a H.264/Flash wizard, but I have been playing with it. There have been some lively discussions here with walter and David (and others) about it.
Ed

[Ed Dooley]

The main thing is that H.264 doesn’t play well with FCP. It’s just like MPEG-2 and HDV in that it uses interframes, which makes FCP work harder. I’m sure it looks good, but overall it’s easier to edit QTs exported from FCP (if you have the storage).
Ed

[Ed Dooley]

Well, you didn’t suggest that she use Twixtor (or buy it), you said drop it in a 720P timeline and apply a deinterlacer. FCP has a built-in deinterlacer that throws away fields (Twixtor wasn’t mentioned, and she may not own it anyway). If she did as you suggested (add a deinterlacer) she would have thrown away half the fields and half the resolution. My opinion is that’s a bad thing. I also like Nattresses’ deinterlacer: https://www.nattress.com/Products/filmeffects/filmeffects.htm
Ed

[Rafael Amador] “[Ed Dooley] ” FCP. It does it in a fraction of the time because it’s just throwing away half the resolution”
Can you tell me which resolution are you throwing when working in 32b floating point?

[Ed Dooley] ” then Compressor (using Frame Controls) is the way to go from interlaced to Progressive,”
This I do it in FC with Twixtor that makes a better job, and faster, than Compressor.

FC (alone) can not beat Compressor when creating new pixels or in between frames, but this is not what we are talking about.
I’m tired of hearing FC can’t do this, FC can’t do that.
Try it.
Rafael
“