Forum Replies Created

  • Stephane Labrie

    October 30, 2005 at 4:08 am in reply to: varicam workflow several questions

    Hi Anshul

    Before answering your question, keep in mind the following:
    -the camera can be set to 59.94 (for NTSC word) or 60.00 (for Pal world).
    -the camera shoot at any speed between 1 and 60 frames per second BUT the VTR always record 60 frames per second (the magic is in the shutter of the camera, not the VTR). I am not aware of a PAL-friendly 720p format (doing 50 instead of 60).
    -the camera only record in progressive mode.
    -each active frame is identified in the user bit.
    -you need a frame rate converter to get rid of the non active frames. Some NLE can also get rid of those frames at ingest time.

    Some answers:
    A- Each active frame has a bit enabled in the user bit, whatever 720/24/59.94 (that being 23.97) or 720/24/60.00 (that being 24).

    B- 25p/50i are almost the same, except for field motion (progressive vs interlaced). For video project, you could use 25p to get a film look. Video look would be emulated with 50p, converted to 25p (where each frame would become a field). Some NLE can do that field merge operation.

    C- the workflow would be: shoot at 720/25p, get a Panasonic frame rate converter to create 1080/25p and create new tapes. The downconvert to SD beta for offline. Conform with 1080/25p tapes and keep the 720/25p in your vault (just like you do with film negative reels).

    I recommand you to talk with your Panasonic reseller in India. You can also visit the Panasonic web site. Lof of data is available.

  • Stephane Labrie

    October 6, 2005 at 12:15 am in reply to: 24p help!

    Visit this link. It shows you how to use your varica footage and FCP.

    Small recap on Varicam format:
    -1280×720 / 8-bit 4:2:2 media on DVCPro HD tapes. 100mb/sec
    -the camera always record 60 progressive frames per second, whatever the shooting speed is ( from 4 to 60)
    -If you shoot at 24p, the material on tape is similar to film-to-tape xfer (2:3 pulldown). You need to remove the hybrid frames to wotk at 24p. The following web pages explain that.

    https://www.kenstone.net/fcp_homepage/dvcpro_hd_workflow_balis.html

    Other links:
    ftp://ftp.panasonic.com/pub/panasonic/drivers/pbts/papers/Overcrank-WP.pdf
    https://catalog2.panasonic.com/webapp/wcs/stores/servlet/ModelDetail?displayTab=R&storeId=11201&catalogId=13051&itemId=94208&catGroupId=14569&modelNo=AJ-HDC27H&surfModel=AJ-HDC27H
    https://www.jkor.com/peter/riddles.html
    http://www.24p.com

  • Stephane Labrie

    August 16, 2005 at 7:15 pm in reply to: File import stupid newbie question

    Many reasons:
    -encoding multiple file sequences take times (I’m looking to work with large image file) and it is an extra step.
    -I want the XML to point to the JPEG files and not to Quicktime movies
    -Other application can create one clip from a bunch of image files. I was sure that FCP could do that

    Thanks!

  • Stephane Labrie

    August 16, 2005 at 10:52 am in reply to: File import stupid newbie question

    Hi Simmie.

    I saw this option, but still, it does not help my main problem: I have to export an EDL or XML and I want the 100 frames to act as a single source clip with timcode & tape name.

    Thanks for your help guys. I`ll have to workaround it since FCP can`t do what I`d like to do.

  • Stephane Labrie

    August 15, 2005 at 6:56 pm in reply to: File import stupid newbie question

    Hi!

    Thanks for the answer. I’m looking to edit based on multiple image file sequences that will have a tape and timecode in a near future (I already have this data and want to put this in FCP for tracking and EDL purposes). So, I’d like not to encode a quicktime since I will loose the data about the jpeg files location AND will waste many hour of encoding.

    So, do I conclude that FCP can’t import a file sequence as a single clip just like Media100, Avid, etc do?

    Thanks!

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