Latest post Tue, Sep 12 2017 2:01 PM by DStone. 38 replies.
Page 2 of 3 (39 items) < Previous 1 2 3 Next >
Sort Posts: Previous Next
  • Mon, Aug 28 2017 7:02 PM In reply to

    • scocklin
    • Top 150 Contributor
    • Joined on Thu, Oct 13 2005
    • Maryland
    • Posts 597
    • Points 7,065

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    So I just checked those same A7s files in DaVinci Resolve, the linked files in Avid where reading TC starting at 00:00:00:00 in Resolve the source TC start reads 14:30:17:12, it looks like the source time code reads correctly in Resolve. I also check the file TC In After Effects and the source TC start also reads 14:30:17:12.

    HP Z800 2x 3.46GHz Hex Core X5690, 48GB Ram, Windows 10, Samsung SSD 850 Pro 512GB, Avid Mojo DX, Nvidia Quadro K4000, GTX 780, DeckLink SDI 4K, Avid... [view my complete system specs]
  • Mon, Aug 28 2017 7:43 PM In reply to

    • scocklin
    • Top 150 Contributor
    • Joined on Thu, Oct 13 2005
    • Maryland
    • Posts 597
    • Points 7,065

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    I did a frame count in Avid, Resolve and Convert V4.

    Avid Clip frames is 32891

    Resolve Clip End Frame=32891, Frames = 32892

    Convert V4 Frames = 32897

    HP Z800 2x 3.46GHz Hex Core X5690, 48GB Ram, Windows 10, Samsung SSD 850 Pro 512GB, Avid Mojo DX, Nvidia Quadro K4000, GTX 780, DeckLink SDI 4K, Avid... [view my complete system specs]
  • Mon, Aug 28 2017 9:15 PM In reply to

    • DStone
    • Top 50 Contributor
    • Joined on Fri, Nov 4 2005
    • Massachusetts
    • Posts 3,175
    • Points 41,155
    • Moderator: Media Composer Getting Started

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    Convert V4 is most definitely off the mark. I trust Resolve, and given the one frame off error, it's not just me.

    DIY quad core I7-4790K, 16Gb, NVidia GTX 970 4GB, Win 10 Pro, MC 8.7, MC 7.x [view my complete system specs]

    Dave S.

  • Mon, Aug 28 2017 9:34 PM In reply to

    • scocklin
    • Top 150 Contributor
    • Joined on Thu, Oct 13 2005
    • Maryland
    • Posts 597
    • Points 7,065

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    I have looked at the XAVC Long GOP compression map, it looks like the TC meta data is embeded on each frame I would assume with the audio.  And as I said I'm reading true time code in Resolve and AE.

    HP Z800 2x 3.46GHz Hex Core X5690, 48GB Ram, Windows 10, Samsung SSD 850 Pro 512GB, Avid Mojo DX, Nvidia Quadro K4000, GTX 780, DeckLink SDI 4K, Avid... [view my complete system specs]
  • Mon, Aug 28 2017 9:46 PM In reply to

    • DStone
    • Top 50 Contributor
    • Joined on Fri, Nov 4 2005
    • Massachusetts
    • Posts 3,175
    • Points 41,155
    • Moderator: Media Composer Getting Started

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    Just to throw it out there, select a clip, right-click and choose Modify->Modify Clip and change the time code to aux.

    DIY quad core I7-4790K, 16Gb, NVidia GTX 970 4GB, Win 10 Pro, MC 8.7, MC 7.x [view my complete system specs]

    Dave S.

  • Mon, Aug 28 2017 9:49 PM In reply to

    • DStone
    • Top 50 Contributor
    • Joined on Fri, Nov 4 2005
    • Massachusetts
    • Posts 3,175
    • Points 41,155
    • Moderator: Media Composer Getting Started

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    And while you're at it, go into the bin where the clips are and choose all of the aux TC columns. See if the timecode shows up in one of those.

    DIY quad core I7-4790K, 16Gb, NVidia GTX 970 4GB, Win 10 Pro, MC 8.7, MC 7.x [view my complete system specs]

    Dave S.

  • Mon, Aug 28 2017 9:59 PM In reply to

    • scocklin
    • Top 150 Contributor
    • Joined on Thu, Oct 13 2005
    • Maryland
    • Posts 597
    • Points 7,065

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    Tried it both ways and it still reads TC start 00:00:00:00

    HP Z800 2x 3.46GHz Hex Core X5690, 48GB Ram, Windows 10, Samsung SSD 850 Pro 512GB, Avid Mojo DX, Nvidia Quadro K4000, GTX 780, DeckLink SDI 4K, Avid... [view my complete system specs]
  • Mon, Aug 28 2017 11:28 PM In reply to

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    scocklin:

    I did a frame count in Avid, Resolve and Convert V4.

    Avid Clip frames is 32891

    Resolve Clip End Frame=32891, Frames = 32892

    Convert V4 Frames = 32897

    Possible explanation. The 1 frame could be the difference between how MC programmers and Resolve programmers determine the TC of the out frame ..... at the start of the next frame or the end of the last frame.

     

    Also
    "
    Convert V4 Frames = 32897"  Could this 6 frame difference actually vary with clip duration?.... As in the difference between DF and NDF count?

  • Tue, Aug 29 2017 12:16 AM In reply to

    • scocklin
    • Top 150 Contributor
    • Joined on Thu, Oct 13 2005
    • Maryland
    • Posts 597
    • Points 7,065

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    We can't read TC in Avid but can read it in Resolve, AE and Convert V4 so is this an Avid bug?

    HP Z800 2x 3.46GHz Hex Core X5690, 48GB Ram, Windows 10, Samsung SSD 850 Pro 512GB, Avid Mojo DX, Nvidia Quadro K4000, GTX 780, DeckLink SDI 4K, Avid... [view my complete system specs]
  • Tue, Aug 29 2017 1:10 AM In reply to

    • DStone
    • Top 50 Contributor
    • Joined on Fri, Nov 4 2005
    • Massachusetts
    • Posts 3,175
    • Points 41,155
    • Moderator: Media Composer Getting Started

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    Are you sue Convert is reading the timecode? I haven't checked, but it certain derives new timecode from the clip modification date. This means you  get freerun timecode for cameras that don't have timecode, but it wasn't created by the camera.

    DIY quad core I7-4790K, 16Gb, NVidia GTX 970 4GB, Win 10 Pro, MC 8.7, MC 7.x [view my complete system specs]

    Dave S.

  • Tue, Aug 29 2017 3:00 AM In reply to

    • dori_bashan
    • Top 150 Contributor
    • Joined on Thu, Oct 13 2005
    • ISRAEL
    • Posts 646
    • Points 7,975

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    I can confirm the TC issue.

    we tested the same XAVC S clips in MC 8.9.1, Sony Catalyst Browse, Resolve and SCRATCH.

    Only MC shows a start TC of 00:00:00:00... all other software shows the correct start TC.

     

    90x Media Composer, 8x Symphony Nitris, 8x ISIS 5000, ,6x Pro Tools, 4x Assimilate SCRATCH Systems- Opus Post Production, ISRAEL. [view my complete system specs]
  • Tue, Aug 29 2017 12:32 PM In reply to

    • DStone
    • Top 50 Contributor
    • Joined on Fri, Nov 4 2005
    • Massachusetts
    • Posts 3,175
    • Points 41,155
    • Moderator: Media Composer Getting Started

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    So I did a lot of research into this last night, and here's what I found. The AX100 (my camera) doesn't have timecode at all so I'm stuck on that one. The A7S/A7S ii have non-standard timecode. instead of a timecode track (which would have a track ID and be marked as timecode) it looks like the timecode is being stored in the meta data track for Real Time Meta Data (which is camera specific and can be anything the camera wants). Other things that can be in that track include things like focus setting, iris, etc. (anything that changes with time). Unfortunately, this is not a standardized format. It's also possible that the start time is being stored in the non-realtime meta data, and that the timecode is being derived from that + frame count but again if so then it's also proprietary to the camera.

    It's also possible that the metadata include MXF OP1a atoms and that a MXF decoder could figure out what was there, but that's for someone else to look at.

    The easiest thing to do would be for Avid to check with Sony and ask the question "Hey, where's the timecode coming from?"

    DIY quad core I7-4790K, 16Gb, NVidia GTX 970 4GB, Win 10 Pro, MC 8.7, MC 7.x [view my complete system specs]

    Dave S.

  • Tue, Aug 29 2017 12:37 PM In reply to

    • scocklin
    • Top 150 Contributor
    • Joined on Thu, Oct 13 2005
    • Maryland
    • Posts 597
    • Points 7,065

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    DStone:
    Are you sue Convert is reading the timecode? I haven't checked, but it certain derives new timecode from the clip modification date. This means you  get freerun timecode for cameras that don't have timecode, but it wasn't created by the camera.

     

    Just checked it again, the correct time code is showing in the burn in section;

     

    HP Z800 2x 3.46GHz Hex Core X5690, 48GB Ram, Windows 10, Samsung SSD 850 Pro 512GB, Avid Mojo DX, Nvidia Quadro K4000, GTX 780, DeckLink SDI 4K, Avid... [view my complete system specs]
  • Tue, Aug 29 2017 1:22 PM In reply to

    • scocklin
    • Top 150 Contributor
    • Joined on Thu, Oct 13 2005
    • Maryland
    • Posts 597
    • Points 7,065

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    DStone:

    It's also possible that the metadata include MXF OP1a atoms and that a MXF decoder could figure out what was there, but that's for someone else to look at.

    T

    From a Sony Tech newsletter by Hugo Gaggioni

    Figure 16. XAVC bit stream structure (example) 

    p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.5px Arial} span.s1 {font: 11.5px Tahoma}

    Sony has been adopting MXF OP1a from the 1st stage of file-based format in the professional domain, and has been continuously evolving it. MPEG-2 Long GOP implementation known as XDCAM or SMPTE-RDD9 has been widely adopted as HD file base format. XAVC adopts this well established and widely implemented MXF OP1a throughout the format, from HD to 4K, Intra and Long GOP. Moreover, multi-partition OP1a is being considered for edit-while-ingest type of application in the near future. 

    More on the XAVC codec;

    http://bento.cdn.pbs.org/hostedbento-prod/filer_public/2013/04/18/gaggioni_xavc-pbs-conf-2013-v05_1.pdf

    HP Z800 2x 3.46GHz Hex Core X5690, 48GB Ram, Windows 10, Samsung SSD 850 Pro 512GB, Avid Mojo DX, Nvidia Quadro K4000, GTX 780, DeckLink SDI 4K, Avid... [view my complete system specs]
  • Tue, Aug 29 2017 2:33 PM In reply to

    • DStone
    • Top 50 Contributor
    • Joined on Fri, Nov 4 2005
    • Massachusetts
    • Posts 3,175
    • Points 41,155
    • Moderator: Media Composer Getting Started

    Re: MC 8.9.1 XAVC-S support. Good, but lacking common metadata.

    Well that would explain the OP1a headers in the metadata. Now we just need someone to decode them.

    DIY quad core I7-4790K, 16Gb, NVidia GTX 970 4GB, Win 10 Pro, MC 8.7, MC 7.x [view my complete system specs]

    Dave S.

Page 2 of 3 (39 items) < Previous 1 2 3 Next >

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller