Forum Replies Created

Page 2 of 3
  • Tim Snider

    July 18, 2007 at 10:33 pm in reply to: Animation codec / ProRes render problem

    Interlacing isn’t a problem here.

  • Tim Snider

    July 18, 2007 at 5:49 pm in reply to: Animation codec / ProRes render problem

    We’re viewing the image on the Panasonic BT-LH2600 hi def broadcast monitor.

  • Tim Snider

    July 18, 2007 at 5:02 pm in reply to: Animation codec / ProRes render problem

    Correction:

    I meant to say “…NOT in the final render in the timeline” in that last post.

  • Tim Snider

    July 18, 2007 at 4:49 pm in reply to: Animation codec / ProRes render problem

    Pulldown typically refers to 3:2 pulldown. Frame rate is 23.98 in and out in my case. But if you mean color difference between 4:4:4 and 4:2:2, I’m not sure.

    It’s strange to me that the Animation codec looks good in the viewer and in the final render in the timeline.

    Any clues?

  • Thanks, Walter. I have found that when capturing 60fps material via the Kona 2 using a capture preset of “AJA Kona 2: 720p 23.98…”, the clips are set to the desired 23.98 frame rate so I can immediately see the slow-mo effect of overcranking. Is there no way to get around the timecode issue? Using the Frame Rate Converter is ok, but certainly slows down the workflow to have to address individual clips. Any ideas?

    Thanks again.
    Tim
    Deja View Media, Inc.
    http://www.dejaviewmedia.com

  • Tim Snider

    September 3, 2006 at 10:51 am in reply to: smoothing out motion track

    Folks,

    I’m working with “beak” on this project and I thought I’d add a bit of clarification to the problem. The footage we are using with motion tracker was shot with an SDX900 in 24p. We set tracking points on a smartphone screen and did some OTS (over-the-shoulder) shots of the person using it. We now need to replace the screen contents with a composite animation in AE.

    We’ve told AE to interpret the footage as 24p and used the “Guess 3:2 Pulldown”. When the footage plays in the 29.97 timeline, it appears to play fine. When we motion track the same footage and then use that data to place our composite, the edges of the overlayed composited image seem to jitter a bit compared to the 24p footage. The tracking just doesn’t appear to be smooth.

    Has anyone had any experience motion tracking 24p footage in AE and encountered the same problem?

    Thanks!
    Tim

    Tim Snider
    Deja View Media, Inc.

  • Tim Snider

    December 5, 2005 at 5:42 pm in reply to: Panasonic DVCPRO Deck

    I too am wondering if this can be done. I can’t find anything in the manual that would indicate that it’s possible.

    Tim Snider
    Deja View Media, Inc.

  • Tim Snider

    November 29, 2005 at 5:40 am in reply to: Sending feedback for 720p uncompressed captures

    Walter, I just let them hear from me. Hope this helps. This was the first time I upconverted from DVCPRO50 to DVCPRO HD 720p and immediately experienced the problem. I came to the COW and fortunately found your thread.
    Thanks.

    Keep us posted if you hear from Apple on this.

    Tim

    Tim Snider
    Deja View Media, Inc.

  • Tim Snider

    October 19, 2005 at 10:52 pm in reply to: DVCAM for broadcast SD television. Opinions please.

    Thanks for the input. I’ll ask the distributor who feeds it to the various PBS affiliates if it’s analog or digital. I can’t do anything about that, I know. However, editing in 8-bit uncompressed will help.

    Thanks again.
    Tim

  • Tim Snider

    October 19, 2005 at 10:50 pm in reply to: DVCAM for broadcast SD television. Opinions please.

    Thanks for the reply. As I suspected, I should’ve captured 8-bit uncompressed via SDI through my AJA KONA 2. I never really saw a degradation of the production in my studio. But I’m monitoring via YUV component out from the deck. I’ll make sure that if I use DVCAM in the future to capture via SDI, edit in 8-bit, then finish YUV to the Betacam deck.

    Thanks again.
    Tim

Page 2 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy