0

LED Screen - RGB Full Range

Hello, 

I've got an issue with my XC4055 and my LED Screen. I don't manage to change the rgb range to full range. So my black content is display dark gray.

I've tried using this https://github.com/brightsign/video-mode-plugin/blob/master/SetMultiScreensVideoMode.brs video mode plugin. It does change the resolution, color space and framerate but not the rgb range. ("1920x1080x60p:rgb:fullrange")

I've also tried with a Script Plugin (https://github.com/brightsign/BrightAuthor-Plugins/tree/master/Set-Video-Mode) using the SetMode function (https://brightsign.atlassian.net/wiki/spaces/DOC/pages/370672969/roVideoMode#SetMode(mode-As-String)-As-Boolean-%5BinlineExtension%5D ). Here the issue is a bit different, the setMode function seems to work but triggers an application restart, causing the presentation's default VideoMode settings to reapply.

The documentation is not really clear to me and there is not a single example of the changing the rgb range somewhere (just custom resolution and color space).

PS : I am using BA connected :) 

Thank you by advance for your help ! 

3 comments

  • 0
    Avatar
    Guillaume Neyret

    But the videomode seems to have been changed when using the Video Mode Plugin; 
    But the LED Screen stay exactly the same

  • 0
    Avatar
    Vijayan T

    I used SetSingleScreenVideoMode.brs, it works fine for me. I am seeing deep black. no more gray.

    Function SetVideoMode(videoModeInputs, bsp) As String

      print "video mode plugin, Series 4 or earlier: SetVideoMode()"
      ' Example: manage the options of a supported video mode
      ' See options you can set - https://brightsign.atlassian.net/wiki/spaces/DOC/pages/370672969/roVideoMode#roVideoMode-SetMode(modeAsString)AsBooleansetmode
      ' return "1920x1080x60p:rgb:fullrange"

      ' Example: set the video mode to be a custom mode.
      ' Custom Modelines allow the player to play back video modes that are not natively supported in BrightAuthor:connected or BrightAuthor's Video Resolution
      ' down and not listed under https://brightsign.atlassian.net/wiki/spaces/DOC/pages/370676833/Supported+Video+Modes.
      ' These are considered, "custom".
      ' The following code block is a example of and how to generate or grab the modeline - https://brightsign.atlassian.net/wiki/spaces/DOC/pages/420217686/Applying+a+Custom+Resolution
      vm = CreateObject("roVideoMode")
      vm.SetCustomModeline("Modeline 1440x1920x50p 151.83 1440 1490 1510 1554  1920 1935 1939 1954  -hsync -vsync")
      ' return "custom"
      return "1920x1080x60p:rgb:fullrange"

    End Function

  • 0
    Avatar
    Guillaume Neyret

    Hello, 

    @Vijayan T, I’ve just seen your reply. Thank you, but your plugin only works with Series 4 players with a single video output, so it won’t work with Series 5 players.

    Two years ago, I managed to work around this issue using a NovaStar H9 LED processor, which can convert a limited-range RGB input to full range. However, I’m now working with an older LED processor (MCTRL660) and a BrightSign XC2055 player.

    I tried using the SetMultiScreens plugin from BrightSign’s GitHub repository: https://github.com/brightsign/video-mode-plugin/blob/master/SetMultiScreensVideoMode.brs. using 

    vm = CreateObject("roVideoMode")
    sm = vm.GetScreenModes()
    sm[0].video_mode = "1920x1080x50p:rgb:fullrange"
    vm.SetScreenModes(sm)

    However, this doesn’t resolve the issue.

    I also checked the video mode of each output using a script plugin to confirm that full range was applied. The result confirms that it is. Here is the video mode output one minute after reboot:

    name: HDMI-1
    video_mode: 1920x1080x50p:rgb:fullrange

    I can also see the video mode change in the DWS logs, but the issue remains on the LED screen, even with this setting applied.

    But with this modified, I can see the change on the LED screen. 

    For comparison, the LED screen displays correctly when using a Windows PC configured for full-range RGB.

    I’d like to use Series 5 players for a range of LED screen projects, but this issue is making me increasingly concerned about their suitability for this use case.

    Has anyone encountered this issue or found a solution?

Please sign in to leave a comment.