ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Doodle Labs + Low Latency on VTX

    VOXL 2
    2
    3
    56
    Loading More Posts
    • 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.
    • DemarconiusD
      Demarconius
      last edited by

      Hi Everybody.
      I'm trying to get a better understanding of how the Video encoding latency gets down to 15ms with Doodle Labs integration? I recognize these are two separate statements that are in the same paragraph so it may not be possible.
      Has there been any improvements to Doodle Labs Mini OEM getting a lower latency below 100ms? I'd love to test this out myself.
      57b0f9be-4710-4598-80cd-297c19ae39f0-image.png

      ModeratorM 1 Reply Last reply Reply Quote 0
      • ModeratorM
        Moderator ModalAI Team @Demarconius
        last edited by

        @Demarconius Yes, we can achieve ~50ms glass to glass using our VRX and voxl-vtx software service on the UAS-side.

        https://docs.modalai.com/vrx-ground-unit-developer-guide/#doodle-labs

        DemarconiusD 1 Reply Last reply Reply Quote 0
        • DemarconiusD
          Demarconius @Moderator
          last edited by

          @Moderator

          Thanks for the clarification on the ~50 ms glass-to-glass number.

          Trying to get a better understanding the performance envelope:
          1. Does the 50 ms include RF transport over Doodle, decode, and HDMI output latency, or is that measured only within the VOXL + VRX software stack?
          2. Was this measured in point-to-point mode or mesh routing mode?
          3. Can you expand on bitrate, resolution, and encoder settings were used (GOP structure, B-frames disabled, UDP vs RTSP)?
          4. Is MAVLink or other traffic running on the same link during that measurement?
          5. Do you have a latency breakdown per stage (encode / RF / decode / display)?

          Appreciate any information you can provide. I just want to make sure I can test and validate this effectively.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Powered by NodeBB | Contributors