Re: [Avid-L2] Europe here calling: p50 -> p25 - i25

Hm.

I'm in a p50 timeline, recreating the edits (from whatever source, PGM live or Audio) - we might and surely will end up  with edits which are at "." instead of ":". If we would transfer this to Color and export from there into i25 wen will end up at these particular point ("." vs":") with intra-frame.

Avid itself can not grab, once switched from 50 to 25 Editing Timebase, the real edit point, because it's intra-frame?

So, the progressive is fine, however: going p50 to p25 with the goal in mind: i25 - > my thoughts are the edits have to be on ":" and shall not be on "."

I appreciate your input - but it's complicated!

Jochen "Jo" Hermann

filter Media Postproduction

Salzburg, Austria

On 7. Oct 2021, at 02:37, Knut A. Helgeland via groups.io <kahelia=me.com@groups.io> wrote:

Wrong. Your source is progressive and your edit is progressive all the way, until you master it into an interlaced format. The interlacing will use whatever full frames you give it, and divide them into half frames according to export spec.

K

On 7 Oct 2021, at 02:33, Jo's Mailinglists <lists@filter-media.net> wrote:

Correct:

Source is progressive, p50

Editing in p50 will result in edits in odd frame numbers. If we are pruning p50 into i25 we are, technically, merging two frame into two fields. I.e.: Frame :00 and frame :01 into interlaces 1. field :00 and second field : 01.

So, if there is an edit not on :00 or :02 or …  any even number: we will end up with intraframe, mid-field edits.

Wrong?

Jochen "Jo" Hermann

filter Media Postproduction

Salzburg, Austria

On 7. Oct 2021, at 02:25, Knut A. Helgeland via groups.io <kahelia=me.com@groups.io> wrote:

No, don't worry about fields, your source is progressive - the field encoding happens on final export to the i25 format.

K

On 7 Oct 2021, at 02:15, Jo's Mailinglists <lists@filter-media.net> wrote:

OBvan-recordings (2 Shows) @ UHDp50, one of the final outputs has to be 1080i25 (frameblending p50->i25 will do the trick).

However, I guess: we have to make sure all edits are done on the first "field", the even frame in the 50 raster (:00, :02, : 04, …)

Right?