[quote user="Job ter Burg"] Interesting, Michael Phillips writes on the Red forums : Avid only outputs PsF when in progressive projects. The 5.5 release has a console command to make it P to play nicer with monitors when using HDMI. [/quote] So that answers the question of whether or not Avid outputs a P or a PsF signal -- 5.5 will be able

[quote user="Job ter Burg"] [quote user="lalittle"]there doesn't seem to be any way of knowing if any given monitor can handle a PsF signal on ANY inputs before purchasing it[/quote]Go to a store? Ask for a demo unit? [/quote] We're talking about consumer electronics here, not pro monitors, which means a normal consumer electronics

[quote user="NubusAvid"] Remember that many HD televisions will accept an interlaced "aka Psf signal" via a component or RGB connection, indeed that is how I feed my Panasonic TH50-PF11 (as I cannot afford Job's HDSDI card for this model. This works perfectly with both the component input and the Dsub VGA type connector on this

[quote user="Job ter Burg"] Like I said, most of those don't support PsF. They won't understand the signal. A few will, apparently. I think Michael Phillips from Avid wrote here (in a 3D topic) that in Burlington, Avid has a consumer 3DTV with HDMI that accepts PsF. They simply took an Avid system to the local electronics store and

[quote user="Cagey"] [quote user="lalittle"]Based on what I've been reading, the point of creating PsF was not to save on bandwidth, but rather to continue to utilize existing equipment and media[/quote] Then why not support both? Surely they would if it were feasable, especially considering progressive's prevalance and rapid

I'm seeing this as well ever since installing Avid on a fresh system a couple weeks ago. So what's the official word on what to do? Is it recommended to just ignore it, or is it better to try one of the methods to prevent it from loading? Is there a fix in the works that will happen with a patch, or ??? I imagine that a lot more people are getting

[quote user="Cagey"] [quote user="lalittle"]I don't understand how this would save any bandwidth. It's still 23.976 fps of material displayed every second, so isn't the actual amount of image data per second the same?[/quote] Bandwidth is a measure of how big the chunks of data are that you are moving. The data rate is

[quote user="Cagey"] The same reason that NTSC is interlaced is why we have PsF. Take one 1080 progessive frame and split it into two interlaced frames of odd and even scan lines. Then display them as 1080i. You save in bandwidth requirements and even though it is not true 1080p it does not suffer from the same issues as 1080i because the

[quote user="Job ter Burg"] PsF is not the same as pulldown. Pulldown means adding fields and converting 23.976p to 59.98i. Maybe the AJA supports that (the Matrox does, AFAIK), maybe not. But PsF is just P-in-two-segments. It's the way all HD decks work as well. [/quote] Ah -- I see. I read somewhere that PsF was essentially the same

[quote user="Job ter Burg"] It has nothing to do with the media INSIDE the Avid. There are no PsF projects, there are just p-projects. It only has to do with the type of signal at the output side of the box. Most (consumer type) HDMI devices are not capable of handling a PsF signal, only P signals. [/quote] This is where I get a bit fuzzy