Another issue to consider is if you are viewing your output on a computer monitor, using quicktime to playback.
Media composer plays back fields in an interlaced project, Quicktime and some other players play back frames. therefore, when you view frame by frame, or park on a frame that is composed of 1 field of a previous frame and 1 field of a following frame you will see an interlaced frame, with the consequent tearing. Also, some systems can play with different field order than Media Composer, so you get artifacting from that.
I had a client that would complain about this...for broadcast, if you can link the file back into Media Composer and the fields are clean of frame blending, your OK, unless your final delivery is a file played back on computer. In that case you need to make different considerations, (such as using a 60p project).
I had a client that would complain about this...for broadcast, if you can link the file back into Media Composer and the fields are clean of frame blending, your OK, unless your final delivery is a file played back on computer. In that case you need to make different considerations, (such as using a 60p project).
Dave Hogan
Burbank, CA
On Wednesday, October 3, 2018 8:27 PM, "Mark Spano cutandcover@gmail.com [Avid-L2]" <Avid-L2@yahoogroups.com> wrote:
30p will result in a different pulldown (1:1:1:2).. It's not as nice to look at, compared to 30i (2:3).
On Wed, Oct 3, 2018 at 11:20 PM Shane Ross <shanerosseditor@yahoo.com> wrote:
If he makes the project 30p, no pulldown will be added. That's only added if he does 1080i60...interlaced 29.97.I haven't had ghosting with 30 in a 24 project.. Just stuttery frames. Yeah, don't blend anything
Shane
On Oct 3, 2018, at 8:05 PM, Mark Spano cutandcover@gmail.com [Avid-L2] <Avid-L2@yahoogroups.com> wrote:Any motion adapter set to Blended anything will "ghost". That's what
blending looks like. You need Both Fields. Bite the bullet, have it drop
those frames hard. There will be stuttering, but no ghosting.
You could move into a 30 frame project, and have the 23.98 clips get 2:3
pulldown added. That will be fine but you'll be at 30 fps and who knows if
you want to be there or can.
On Wed, Oct 3, 2018 at 10:10 PM Benjamin Hershleder Ben@ContactBen.com
[Avid-L2] <Avid-L2@yahoogroups.com> wrote:
>
>
>
>
> Hello big brains of the Avid-L2,
>
> I've been handed a situation where the client has a mixed frame rate
> situation. I've not had to deal with a mixed frame rate output in the past,
> so I wanted to see if my assumptions are correct, and if there are any
> suggestions to deal with the 'motion ghosting' issue/problem described
> below.
>
> *Project Info:*
> - HD 1920 x 1080
> - 23.976 fps
> - DNxHD175
> - The project is already edited
> - 50% of the short film's shots are 23.976fps, while the other 50% are at
> 30fps. The different fame rates are intercut.
> - Mac
> - MC version 8.something
> - Outputting from Avid to a QT with Animation codec (to get around the
> evil gamma shift). I tried several times with a QT Ref into Adobe Media
> Encoder, but AME didn't like it, and all I could get out of it was the
> audio.
>
> *Timeline Playback:*
> Playback of the short film inside of Media Composer looks fine. The 30fps
> shots show no issue (no motion ghosting), even though they are within a
> 23.976 project.
>
> *Output Issue / Problem (when output to QT):*
> As one would imagine, the footage shot at the project's frame rate
> (23.976) plays back just fine after output (since it matches the project's
> frame rate); but the 30fps footage now has ghosting on shots with motion.
> Obviously, this is due to the frame rate conversion (to be clear, all those
> clips have a 'Temporal' adapter on them and include Avid's 30fps notation
> on the clips in the sequence)
>
> *What I tested already (with no luck; all continued to produce 'ghosting'
> during motion):*
> 1 - Promoted one of 30fps clips to a Timewarp, and changed the render
> 'flavor.' It was originally Blended Interpolated, so I tried Blended VTR
> without success. I shied away from testing Fluid Motion because of the
> render time.
> 2 - I did a short video mixdown to DNxHD 175 of a few of the 30fps shots
> in the timeline, and then output that.
> 3 - I made a new Project that was 30fps, just as a test. As I thought, the
> 30fps shots played fine, while it was the 23.98 shots that now had the
> motion ghosting issue.
>
>
> *Questions:*
>
> 1 - Is there anything I can help them do *now* to reduce or eliminate the
> ghosting to the 30fps shots from within the original 23.976 project?
>
> 2 - Is there anything that could have been done after receiving the
> footage, and before beginning editing, that would have reduced or avoided
> this frame rate ghosting issue (e.g. processing the frame rate conversion
> during transcoding inside Avid, or outside in another app)?
>
> 3 - Anyone else found themselves in a similar situation? I just want to
> make sure I relate the situation well to the client before they go and
> murder the D.P. or the original editor.
>
>
> Thanks gang!
>
> Cheers,
> Benjamin
> ———
> Benjamin Hershleder
> ContactBen.com <http://ContactBen...com>
>  <http://tinyurl.com/avidmc-book>
>
>
>
>
>
>
>
> <http://tinyurl.com/avidmc-book>
> <http://tinyurl.com/avidmc-book>
>
>
[Non-text portions of this message have been removed]
__._,_.___
Posted by: Dave Hogan <mactvman@yahoo.com>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (5) |
Have you tried the highest rated email app?
With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app on the market. What are you waiting for? Now you can access all your inboxes (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 1000GB of free cloud storage.
this is the Avid-L2
SPONSORED LINKS
.
__,_._,___
No comments:
Post a Comment