Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

ModalAI Forum

  1. ModalAI Support Forum
  2. Ask your questions right here!
  3. voxl-streamer disconnecting live connection

voxl-streamer disconnecting live connection

Scheduled Pinned Locked Moved Ask your questions right here!
2 Posts 2 Posters 470 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J Offline
    J Offline
    jcai
    Contributor
    wrote on last edited by
    #1

    Unsure if the following is expected behaviour, but I doubt it is.

    Reproduce:

    • Start voxl-streamer listening to hires_front_small_encoded
    • Connect to the stream (e.g., ffplay -i rtsp://<voxl ip>:<port>/live)
    • Confirm that the stream looks good
    • Disconnect from the stream (CTRL-C the ffplay command)
    • Within 60 seconds, re-run the same ffplay command
    • Observe that the stream looks good but will freeze within 60 seconds (e.g., the command is restarted 15 seconds after initially closing the connection. The new stream will freeze after 45 seconds
    • Observe that voxl-streamer outputs Removed 1 sessions
    • Disconnect from the new stream (CTRL-C ffplay)
    • Observe that voxl-streamer outputs Removed 1 sessions again after 60 seconds

    Based on behaviour and source code, what I think is happening:
    When the first connection is closed, voxl-streamer detects this and decrements the number of clients. However, it takes 60 seconds for the gstreamer session to time out and close. During this time, if another client connects, there are now 2 gstreamer sessions and 1 voxl-streamer client. 60 seconds after the first connection is closed, the inactive gstreamer session is cleaned up. Since voxl-streamer doesn't know that this session was already inactive, when it closes, voxl-streamer decrements its number of clients even though the one client it has still has an active gstreamer session.

    Alex KushleyevA 1 Reply Last reply
    0
    • J jcai

      Unsure if the following is expected behaviour, but I doubt it is.

      Reproduce:

      • Start voxl-streamer listening to hires_front_small_encoded
      • Connect to the stream (e.g., ffplay -i rtsp://<voxl ip>:<port>/live)
      • Confirm that the stream looks good
      • Disconnect from the stream (CTRL-C the ffplay command)
      • Within 60 seconds, re-run the same ffplay command
      • Observe that the stream looks good but will freeze within 60 seconds (e.g., the command is restarted 15 seconds after initially closing the connection. The new stream will freeze after 45 seconds
      • Observe that voxl-streamer outputs Removed 1 sessions
      • Disconnect from the new stream (CTRL-C ffplay)
      • Observe that voxl-streamer outputs Removed 1 sessions again after 60 seconds

      Based on behaviour and source code, what I think is happening:
      When the first connection is closed, voxl-streamer detects this and decrements the number of clients. However, it takes 60 seconds for the gstreamer session to time out and close. During this time, if another client connects, there are now 2 gstreamer sessions and 1 voxl-streamer client. 60 seconds after the first connection is closed, the inactive gstreamer session is cleaned up. Since voxl-streamer doesn't know that this session was already inactive, when it closes, voxl-streamer decrements its number of clients even though the one client it has still has an active gstreamer session.

      Alex KushleyevA Offline
      Alex KushleyevA Offline
      Alex Kushleyev
      ModalAI Team
      wrote on last edited by
      #2

      @jcai, I just tested this. I do see that "Removed 1 sessions" message comes in after ~1 min after the first disconnect, but my second session is not interrupted when this happens.

      Please make sure you are using the latest version of voxl-streamer (you can try from nightly dev build). Also, something to double check, whether the two sessions are coming from the same or different port (maybe if you are using vpn or something, there new session starts from the same client port).

      Alex

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      ModalAI
      Categories Recent Tags ModalAI.com Docs
      © 2026 ModalAI® · Accelerating autonomy for smaller, smarter, safer drones · Powered by NodeBB
      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups