Is 1080psf export possible from Premiere or AME?

Forum|Forum|14 years ago
October 18, 2011
2 replies
22039 views

I'm exporting individual clips of EX-1 XDcam from a sequence, one clip at a time so I can also apply some level correction to the export. It is 23.967 psf at origin from the camera. I am exporting to ProRes HQ 23.967 1080p as reported by Premiere Pro 5.5.1. The time line is AJA 23.98 1080psf. The problem is that the exports are turning out to be true 1080p, not psf as the original. I'm using the clips in another program that does not create a 1080p timeline, Media 100 Suite 2.1 (latest version, came with the AJA 1080 LHi OEM board I'm using). Bottom line, is there a way to get Premiere or AME to export a true 1080psf ProRes file? Psf is preferred in many applications. I don't see any mode select for psf, even though I am in a 1080psf timeline.

This topic has been closed for replies.

Correct answer DMHP

I do know that ProRes allows PsF as an option. Here is a grab from Final Cut. There are many other ProRes PsF options.

Figured it out. There is a popup in the export window Codec settings. One of the options is "Interlaced". Check that and it turns exports a PsF progressive clip. That is the way Media 100 sees it, and it shows up on all the monitors in Source and Program windows. Yay! Thanks everyone.

T

tvamsterdam

Participant

After hours of searching in Premiere Pro (and the forum topics) I have found the solution for old DV SD footage edited in 1080p: export to AVI in DV Widescreen with upper field and the double interlace lines problem is solved. After that blow up the footage again and you have an HD movie without the lines, as it should be...

E

excited_Genie16B8

Legend

I recall using Media 100. My question to you is why would you prefer this over the vastly superior Premiere Pro? Why not just edit the media right there in PP, instead of adding an effect and exporting to edit in another NLE?

D

DMHPAuthor

Inspiring

The project is already started in Media 100 Suite 2.1. It must have been a long time since you've used Media 100. Other than the fact that it won't playback until media is converted to ProRes, I prefer the simple, quick interface to any other. But the biggest reason is stability on the Mac. Media 100 Suite 2.1 is solid as a rock. I have a new Mac Pro with GTX 285 NVidia Card 24 Gb RAM, fast RAID, and I still find unexpected crashes in 5.5.1. That and the fact that 5.5.1 broke Nikon D7000 support, the main reason I wanted to get into Premiere in the first place. There is a lot of D7000 footage in this project, so I am going back and forth between 5.0.4 (which supports it) and 5.5.1 (which doesn't). But these things are not why I posted. Just wanted to find out why Premiere is taking 1080psf footage from my EX-1 on a 1080psf AJA timeline and exporting it as 1080p. It is giving me problems that I wouldn't have if it stayed in psf. Is there any way to over-ride this behavior and get 23.98 psf out? I see settings in interpret footage. Saw an article in Pro Video Coalition that extolled the fact that it automatically interprets psf as p in 5.5.1. Does this mean I should be doing my exports in 5.0.4 to get more control over interpretation, or is there an interpretation setting I can change in 5.5.1?

Don't get me wrong, I really enjoy using Premiere, I love the fact that you don't have to convert to get playback of my EX-1 footage, even though my D7000 doesn't work presently. I intend to use it for all of my titling and color correction. Maybe I'll give the next project when I am not under a lot of time pressure to Premiere. Hopefully they fix Nikon support before I have to pay a third time for 6.0. Media 100 will take the 1080p on the timeline, it just won't playback in the source window on my external monitors when the project setting is psf, and all timelines at 23.98 1080 are psf. I really don't want to edit a 30 minute documentary without source window playback.

Thanks in advance for any help with this.

D

DMHPAuthor

Inspiring

Colin Brougham wrote:
Wikipedia lists the XDCAM formats as using PsF.
No, it doesn't.

"PsF became a means of initial image acquisition in professional Sony video cameras. It is employed in HDCAM and XDCAM video cameras..."

http://en.wikipedia.org/wiki/Progressive_segmented_Frame

Did no modifications, selected "Interlaced" in the "Codec Settings" Buttton. It comes up with the popups already set to "Automatic" and "Top field first". Left "Enable chroma filterin (no "g" for some reason) unchecked. So not so simple really, and no documentation I could find. Glad it was just the one check. Also on import to the Media 100, it wants full 0-255 color space for proper rendition. Also on Media 100 import window, leave the "Import Media to the Media Standard and Codec" unchecked. This would do a recompression of the material to the current project standard, even if it is already the same. With these Premiere export Codec settings , and proper settings on output, it quick imported to Media 100 and came in as the native EX-1 type 23.967 PsF. Worked fine on all AJA monitor outputs, SDI 23.98 PsF and 720x486 29.97 component SD. Thanks again.

It is in this Color Correction Mode of Premiere 5.5.1 Mac that I am getting most of my crashes. It also happens in effects mode as well. When I am working on a sequence applying RGB Curves or Fast Color Corrector to get Luma and contrast to broadcast safe, someties it will just begin playing clips or a timeline that isn't in the front or even active. Often it happens when I play back the active front sequence and it just starts playing another sequence or clip (not even in the same Bin, necessarily) audio only, so it is hard to tell where it is coming from. When this happens, nothing in the program is active or changeable. You can click away on anything and nothing will stop the phantom playback. Sometimes it allows you to save the project and all the windows close, but the program is still open and you must do a "Force Quit" to actually get the computer back. A reopen of the program and everything is fine until a few clips/sequences later (can be a while sometimes) it will do it again. Think there is a bug here, as 5.5.1 was a clean install, etc. Will probably start a new thread about this, and copy this last paragraph. Where is the best place to report this behavior directly?

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded