Nx Meta: Lower resolution stream from the server for plug-in?

Comments

5 comments

  • Avatar
    Sergey Yuldashev

    Hi Jason,

    I really don't know your current environment. But let's assume you're dealing with a regular camera integrated into Nx.
    In this case you'll definitely see something like this in the GUI:

    Both camera streams are configurable with API calls:

    ec2/saveCameraUserAttributes
    or
    ec2/saveCameraUserAttributesList

    To get options for framerate and resolution you need to check through response for:

    ec2/getCamerasEx
    or
    ec2/getCameraUserAttributesList

    If you're using not the camera but generic RTSP/HTTP/UDP streams, there won't be options to change FPS/resolution though.

     

    By default Media Server uses Primary stream but the thing is that usually Server selects profiles for Primary stream with much higher resolution options that you need.

    But there is a way to force Media Server use Secondary stream for analysis:

    1. Create directory:
      Linux: /etc/nx_ini
      Windows: C:\Windows\System32\config\systemprofile\AppData\Local\nx_ini
    2. Navigate to that directory and create file nx_vms_server.ini
    3. Restart Media Server process to load nx_vms_server.ini
    4. In that ini file find string analyzeSecondaryStream=0 and change value to 1
    5. Restart Media Server to apply changes

    Please take into account that "nx_vms_server.ini" method was designed for experimental purposes only. It should never be applied at the production/end-users environments.

    Settings changes introduced with its modification will very likely be lost on the upgrade. Also Quality Assurance procedures cover only "default" state of the nx_vms_server.ini. So any modification makes your system less stable.

    1
    Comment actions Permalink
  • Avatar
    Roman Inflianskas

    It would be great if the plugin could choose per stream per camera.

    0
    Comment actions Permalink
  • Avatar
    Jason Shim

    As Sergey pointed out that this feature is experimental, this feauture was removed at 4.0.0.29228 while the previous one supported at 4.0.0.28728.

     

    As Roman pointed out, I'd also like the pluin could specify per stream per camera. As we see the recent higher resolution trend such as 4K is consuming all of CPU time in trying to decode where we don't need such high resolution.

    1
    Comment actions Permalink
  • Avatar
    Sergey Yuldashev

    Hi Jason!
    Actually it was not removed but rather just moved.

    Settings that previously were stored in "mediaserver.ini" file are now read by server from file "nx_vms_server.ini". My initial message was corrected.
    But the good point is that while all of this is experimental and even is still in beta - we can't guarantee the stable work.

    0
    Comment actions Permalink
  • Avatar
    Jason Shim

    Thanks. It is now populated.

    0
    Comment actions Permalink

Please sign in to leave a comment.