Is the Nx Cloud up? Visit our Status Page for the current health and performance of the Nx Cloud.

Status Page

Comments

7 comments

Date Votes
  • Andrey Terentyev
    • Network Optix team

    Hi,

    As the tutorial states

    It is important to understand a few limitations:

    • The video will work only if the browser can reach the system. If you are using your server’s IP address - the video will not be accessible outside of the local network.
    • If you embed the video on the secure website (using HTTPS) - requests might not work, because the browser doesn’t trust the server’s self-signed certificate.
    • The browser may have a limit of 5-7 connections per domain.
    0
  • Jean-Gregoire Kherian

    Hi Andrey, 

    Thanks, yes, i ve seen those limitations. 

    However, I m connecting to the server through the cloud, so 1 and 2 were not an issue.

    As for the last point, I understand this as a given client browser can only make 5-7 connections, so in practive could only fetch max 5-7 video in parallel. This is not an issue for my case where i only request one video. 

    But what would be the limit on the number for simultaneous distinct clients, if that makes sense?

    0
  • Jaemyn Kinney

    Do you mean to ask if there is a limitation on unique browser clients pulling streams?

    At the end of the day the NX web portal would likely use the same API you are using now to view so the same limitation would probably apply

    Though I would bet that limitation is based on server upload capability, cloud proxy capability in NX and browsers.

    I'll compare to software clients. I had this when I sold a system to an end user once.

    We set it up owner can see all cameras and manage users.

    People in departments get theirs. At that poi t it is expected that all 8 can run at once.

    Owner ends up giving everyone full access. Their stream all cameras because they can, jumps from one screen with 48 and 7 or so with 3 each to 8 with 48 and some have cameras set to 5 hours back on a constant playback and no sync.

    We didn't factor for that... They said we promised 8 connections. We started specifying a count of unique streams based on this instance. This is of course an extreme example.

    TL;DR
    Your max is your bottleneck and you can only control the server components and internet speeds. Rest is based on management of streams/access.

    Granted I don't work for NX so there may be some inside knowledge I'm missing.

    0
  • Jean-Gregoire Kherian

    yes indeed, asking about unique browser clients pulling streams.

    didn t fully get the case you described, but was it ~8 people and 6 cameras, yielding up to 48 parallel connections with all users viewing all feeds in parallel? in which case i guess you may hit either a given camera limit, or the overall available bandwidth limit?

    but going back a step, probably video streaming 101 question:

    If i have one camera with a video stream uploading at 1mbps and 3 remote client browser connecting to that video stream, does it mean that the camera is now uploading at 3 * 1 = 3 mbps with 3 parallel connection? or is it still only 1mbps from the camera to a server that then distributes this stream to all remote client browser, each one downloading at 1mbps. 

    when testing,  I have an nx server on my local netowrk, and it s connected to this nxvms cloud. 
    Does the nxvms cloud do this job of distributing the stream to remote clients? or would i need a separate cloud server for this? or alternatively should I use a 3rd party service ?

    0
  • Jaemyn Kinney

    I'm an access control support guy for my day job but I have an installer background.

    I was more or less saying 'depends' with a really long example.
    In my case we didn't build the server to run 48 live streams and about 20 odd playback streams at random intervals so of course it hit a resource issue.

    There are things like multicast or anything fancy that could be in the back end I dont know of. NX needs to answer that.

    What I was trying to do was give you an idea of what was in your control here so you could ensure that is factored in :)

    My best guess is that you are essentially proxying through NX cloud, not it running as a 'server' I could be very wrong here though, so here's hoping Andrey corrects me if I am.

    Until you hear from NX the play it safe approach is the worst case scenario so maybe just treat it like seperate software or web connections streaming

    0
  • Jaemyn Kinney

    Oh, third party service or make your own middleware API wouldn't be an awfull idea. Your web clients could 'subscribe' to a stream on your API and if that count is more than 1 it pulls the stream from NX.

    Don't know how.youd handle the NX operator permission side though.

    0
  • Jean-Gregoire Kherian

    yes let s see. thanks for the replies anyhow :-)
    basically wondering if i need something like this in between to be able to serve a large (ish) number of remote browser clients:
    https://www.ipcamlive.com/howdoesitwork



    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post