Page 2 of 2 FirstFirst 12
Results 11 to 18 of 18
  1. Collapse Details
    #11
    Default
    Quote Originally Posted by Fohdeesha View Post
    No, rec.709 is the wider gamut color space that is specified for all HD video. All HD camcorders and dslrs use this colorspace internally when taking the sensors rgb output and encoding it to YUV for recording. rec.601 is the 30 year old, small gamut SD colorspace that was used when broadcasting sd footage over the air forever ago. Taking your gorgeous, wide color gamut rec.709 native mts footage and using this program to comperes that colorspace down to the 30 year old small gamut 601 is a horrible horrible thing to do. As for the banding/shadows, I'd look elsewhere for a solution. Those artifacts are in your original footage, the down conversion to a smaller gamut effects the bit depth among a slew of other things and its process of removing information it's hiding the banding/artifacts

    Refer to my post above in this thread Psynema, the gh2 records broadcast range. period. there is no information below 16 or above 235 to recover. I wish somebody would put that in a sticky.
    Then why does selecting broadcast range not make a difference in the footage I'm getting and full range does?


    Reply With Quote
     

  2. Collapse Details
    #12
    Senior Member Fohdeesha's Avatar
    Join Date
    Jul 2008
    Location
    Indianapolis, Indiana
    Posts
    827
    Default
    because like I've mentioned in literally 9000 other posts, when you select full range, it is taking the original 16-235 luma data and stretching it to fill a 0-255 container.
    (9:38:44 PM) ngubbet: ROYGBIV 4:4:4:4:4:4:4


    Reply With Quote
     

  3. Collapse Details
    #13
    Default
    Quote Originally Posted by Fohdeesha View Post
    because like I've mentioned in literally 9000 other posts, when you select full range, it is taking the original 16-235 luma data and stretching it to fill a 0-255 container.
    Yes EVERYONE understands THAT

    But there's no difference in curves using Broadcast Range vs. Log n ' Transfer.


    Reply With Quote
     

  4. Collapse Details
    #14
    Default
    Why is this program called 5DtoRGB when it has nothing to do with RGB? Everything about its features implies that it stays in YUV space... doesn't instill confidence.

    And the 'range' setting is just confusing terminology, does it refer to the source range or the target range? What matters is if there's a 0>16 transfer, 16>0 or none. Anything else is the software masking what it does with terminology. When encountering a new tool or workflow I just run it twice and pick the result that neither clips nor applies a double range compression.


    Reply With Quote
     

  5. Collapse Details
    #15
    Junior Member
    Join Date
    Sep 2012
    Posts
    1
    Default
    Ok, there must be something retarded I'm doing. On some of my videos, after I process them, I get this motion blur interlacing thing that makes the video look terrible. The MTS file looks fine but after I put it through 5DtoRGB, it looks like this. PLEASE HELP!!! Screen Shot 2012-09-09 at 11.59.50 AM.jpg


    Reply With Quote
     

  6. Collapse Details
    #16
    Default
    Quote Originally Posted by Fohdeesha View Post
    100% true, the gh2 writes to rec.709 complaint broadcast range h.264. blacks at 16 and whites at 235.
    Although the GH2's MTS files do comply with Rec. 709, they contain metadata flags that indicate full-swing 0-255 range, rather than the studio-swing 16-235 broadcast range. This can be confirmed in Adobe After Effects CS5.5, which unlike Premiere or FCP, can be run in ICC color-managed mode. When you set up an AE project to use a color managed profile, it will automatically identify the color space used in each imported video file. If both color spaces match, AE will import the file without remapping the colors. If the color spaces differ, AE will remap the file's color space to the project's color space.

    If you set your AE project's color space to HDTV (Rec. 709) 16-235, it will remap imported files that do not use the Rec. 709 studio-swing broadcast color space to limit their range of 8-bit color values to 16-235. Files that were recorded in studio-swing color space will be used as-is without remapping. When you import a GH2 MTS file, AE reports that its color space does not match, and remaps the file to the studio-swing 16-235 color space.

    If you set your AE project's color space to HDTV (Rec. 709), it will remap imported files that do not use the Rec. 709 full-swing color space to expand their range of 8-bit color values to 0-255. Files that were recorded in full-swing color space will be used as-is without remapping. When you import a GH2 MTS file, AE reports that its color space does match Rec. 709 full-swing, and the file is imported as-is without remapping.

    Here's a screen-grab from an AE project set up to use HDTV (Rec. 709) full-swing color space. The overlaid waveform monitor in the lower right corner shows that imported GH2 MTS file contains luma values that range over the entire full-swing color space.
    Attached Images Attached Images


    Reply With Quote
     

  7. Collapse Details
    #17
    Default
    All I know is it looks better in low lit wild/doc situations using full range, just less shadow noise and MUCH closer to the final grade. Slightly faded is easier to fix than horrendously crushed. Just an easier workflow if you do events.


    Reply With Quote
     

  8. Collapse Details
    #18
    Default
    Are many of the posts in this thread referring to a paid version of 5DtoRGB? I see references to "log transfer" and "chroma" settings which are not in the free Windows 64-bit version. Thanks.
    Last edited by GHKAM; 02-20-2013 at 08:00 AM.


    Reply With Quote
     

Page 2 of 2 FirstFirst 12

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
  •