Page 4 of 6 FirstFirst 123456 LastLast
Results 31 to 40 of 60
  1. Collapse Details
    #31
    Senior Member
    Join Date
    Jan 2016
    Posts
    171
    Default
    Quote Originally Posted by sunnyjimfilms View Post
    This has been fixed with FCPX update.
    Yep. Confirmed.

    Sidenote: .mxf wrapped prores is very cool.


    Reply With Quote
     

  2. Collapse Details
    #32
    Junior Member
    Join Date
    Nov 2016
    Posts
    14
    Default
    Hi balazer,

    Sorry for the elephant, wrong clip -that clip was not even Clog. Here is the correct clip - https://www.dropbox.com/s/0wa8p9ibga...CANON.MXF?dl=0

    As Sunnyjimfilms stated the shifting behaviour in FCPX is fixed with the latest update. However FCPX stil interpretes the C-log clips in what looks to be the "wrong gamma". See post #24 in this thread.


    1 out of 1 members found this post helpful.
    Reply With Quote
     

  3. Collapse Details
    #33
    Senior Member
    Join Date
    May 2006
    Location
    Syracuse, NY
    Posts
    335
    Default
    So this is NOT an issue on Premier Pro?


    Reply With Quote
     

  4. Collapse Details
    #34
    Senior Member
    Join Date
    Jan 2016
    Posts
    171
    Default
    Quote Originally Posted by Lkorver View Post
    So this is NOT an issue on Premier Pro?
    If by THIS you mean a brief Gamma shift of over exposure various C Log files when viewed in Premiere in Source and Program panels and also through an external reference monitor and waveform (through ScopeBox), then in my experience, no it's not an issue. One idea is to test and retest on your system and see what you come up with.

    As to the deeper discussion in this thread regarding data analysis and black level interpretation, that is beyond my understanding.


    Reply With Quote
     

  5. Collapse Details
    #35
    Senior Member
    Join Date
    Jun 2013
    Posts
    116
    Default
    yep its fixed since 10.3.2


    Reply With Quote
     

  6. Collapse Details
    #36
    Senior Member
    Join Date
    Jan 2011
    Posts
    174
    Default
    Quote Originally Posted by Alex P View Post
    Hi balazer,

    Sorry for the elephant, wrong clip -that clip was not even Clog. Here is the correct clip - https://www.dropbox.com/s/0wa8p9ibga...CANON.MXF?dl=0

    As Sunnyjimfilms stated the shifting behaviour in FCPX is fixed with the latest update. However FCPX stil interpretes the C-log clips in what looks to be the "wrong gamma". See post #24 in this thread.
    Thanks for sending the new clip.

    Glad about FCPX fixing the weird level shifting, but I did confirm that the C300 Mark II 1.0.6 firmware is setting the H.264 VUI video_full_range_flag erroneously. Your sample video uses SMPTE/legal/TV/video/BT.709 levels, not full range levels. All of the Canon Log clips are *supposed* to show the same levels across all cameras, video apps, and firmware versions, whether recorded internally or externally. This bug in firmware version 1.0.6 means levels will be different for internally recorded clips in apps that know how to read the flag. FCPX is affected, apparently. DaVinci Resolve on the PC is not affected. Externally recorded clips won't be affected, which is to say that internally and externally recorded clips from firmware 1.0.6 won't match each other in FCPX, which is obviously a bad thing.

    I will try to bring this bug to Canon's attention.


    Reply With Quote
     

  7. Collapse Details
    #37
    Senior Member AndreeOnline's Avatar
    Join Date
    Mar 2012
    Location
    Zürich
    Posts
    949
    Default
    Quote Originally Posted by balazer View Post
    …but I did confirm that the C300 Mark II 1.0.6 firmware is setting the H.264 VUI video_full_range_flag erroneously.
    It's not in error, Canon highlights the change in the firmware notes:

    Firmware Version 1.0.6.1.00 incorporates the following fixes and enhancements:
    1. Support for the OLED Electronic Viewfinder EVF-V70 *1 has been added.
    2. Shutter Angle Priority has been added. A constant shutter angle can now be maintained, regardless of any other camera settings being changed.
    3. Support for the WFT-E8 has been added.
    4. Zebra Range Expanded Below 65%.
    - The range of the Zebra 1 setting has been expanded to between 5% (±5%) and 95% (±5%) in steps of 5%.
    - The range of the Zebra 2 setting has been expanded to between 5% and 100% in steps of 5%.
    5. Built-in Mic Audio Off
    - The internal microphone on the camera body can now be turned off.
    6. In Browser Remote, the focus guide frame can now be displayed.
    7. 2K Crop Audio Recording
    - Audio can now be recorded when the camera is set in 2K crop mode.
    8. Support for CFast cards (VPG130) has been added. *2
    9. Support for peripheral illumination & chromatic aberration when the EF 24-105mm f/4L IS II USM lens is attached, has been added.
    10. Metadata related to the XF-AVC range has been corrected.
    - The range of Canon Log/Log2/Log3 has been corrected to full range.

    11. The quality of autofocus has been enhanced.
    12. The operation reliability after changing the recording mode has been enhanced.
    @andreemarkefors


    Reply With Quote
     

  8. Collapse Details
    #38
    Senior Member
    Join Date
    Jun 2012
    Location
    Cincinnati, Ohio USA
    Posts
    461
    Default
    Quote Originally Posted by Lkorver View Post
    So this is NOT an issue on Premier Pro?
    There is indeed some weirdness involving black levels and the rgb 444 modes in Premiere Pro: http://www.dvxuser.com/V6/showthread...irmware-update


    Reply With Quote
     

  9. Collapse Details
    #39
    Senior Member
    Join Date
    Jan 2011
    Posts
    174
    Default
    Quote Originally Posted by AndreeOnline View Post
    It's not in error, Canon highlights the change in the firmware notes:

    Firmware Version 1.0.6.1.00 incorporates the following fixes and enhancements:
    10. Metadata related to the XF-AVC range has been corrected.
    - The range of Canon Log/Log2/Log3 has been corrected to full range.
    They didn't correct it. They screwed it up. It was right before, and then they made it wrong in the 1.0.6 firmware.


    Reply With Quote
     

  10. Collapse Details
    #40
    Senior Member AndreeOnline's Avatar
    Join Date
    Mar 2012
    Location
    Zürich
    Posts
    949
    Default
    Quote Originally Posted by balazer View Post
    They didn't correct it. They screwed it up. It was right before, and then they made it wrong in the 1.0.6 firmware.
    From a perspective where 'full range' is wrong, you're right.

    I personally much prefer full range, but that is beside the point. What I'm saying is that when Canon explicitly says the change is deliberate and according to what they feel is right, then they didn't screw it up.
    @andreemarkefors


    Reply With Quote
     

Page 4 of 6 FirstFirst 123456 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •