URGENT!!! - Message "VIDEO: NDI: CANNOT KEEP LATENCY"

Bugs NDI

 

Hi, I have this message on Aximmetry, I am not sure how to solve it. Please can you help me?


   pizurnia

 
Profile Image
ahmed ahmed
  -  

I suggest that you try to lower NDI video resolution /frame.

Also you can also try to increase Aximmetry latency above 8 frames


 
Profile Image
TwentyStudios
  -  

Does your NDI signal have the same frame rate as your Aximmetry project?

I think it’s probably a network issue. Try using the NDI Monitor app from NDI tools on your Aximmetry computer and check if you’re getting smooth, steady video there.

 
Profile Image
mleobet
  -  

the same problem here =(

 
Profile Image
Zoltan@Aximmetry
  -  

Hi all,

Have you tried
- increasing the latency as Ahmed suggested
- and/or set the correct frame rate both for NDI input and Preferences / Rendering?


 
Profile Image
TwentyStudios
  -  

We’re having this issue as well under specific circumstances. For us, it occurs when using the NDI Tools Scan Converter (now called NDI Screen Capture). The scan converter seems to drop the frame rate dynamically when there is no activity on the screen. We’ve set the frame rate to match the one used in Aximmetry. 

The same screen capture source works perfectly in our Tricaster. In fact, we have to funnel the screen capture through the Tricaster to Aximmetry to make it work reliably. With all the reports here and on Facebook/Discord, I think it’s safe to say that something isn’t working correctly with the NDI handling in Aximmetry.

 
Profile Image
markusnygard_yle
  -  

Have you tried to use OBS as screencapture to NDI-software.
In many cases OBS works better than NDI Tools (especially considering audio-capturing) 

 
Profile Image
TwentyStudios
  -  

We get the same results with the vMix Screen Capture, but haven’t tried the one from OBS yet.

 
Profile Image
Zoltan@Aximmetry
  -  

Hi all,

TwentyStudios: we were not aware of such a frame dropping behaviour of some NDI sources, thank you for the hint!

Aximmetry's NDI handling is only "incorrect" in a sense that it expects frames coming exactly at the designated frame rate as with any other video sources. What we can do is skipping this check (as probably all other mentioned software do) and that will "fix" the problem.
It will be done in the next release.

 
Profile Image
Motionworx
  -  

Hi.

We're having the same issue. We're providing Aximmetry with a fixed 30p stream. It runs smoothly and works fine on all other capturing software. I've set the NDI settings in Aximmetry to capture 30p. I've changes the frame rate of the project to 30p and increased the latency as per Ahmed's suggestion. I've tried 1080p, 720p and even 480p. No change. Keep getting the same "Can't keep latency" message. We have a project coming up on Monday and have no choice but to sacrifice one of our HDMI Billboards. So we have to drop a camera due to the Unreal virtual camera 3 billboard limit. It's a massive problem to be honest - please try and fix the issues in the next update or at least increase the unreal cam templates to 4 or 5 billboards, then we can use that as a comfortable workaround.

A little off topic, but another potential feature update: We've noticed that Aximmetry doesn't support RTMPS either for streaming purposes. (Only RTMP). Vimeo, for example, only supports RTMPS. Can RTMPS support be included in the next update?

Thanks.

 
Profile Image
Zoltan@Aximmetry
  -  

Hi,

Thank you for the suggestions.
We're working both on the NDI issue and on the expanding the number of billboards.

We'll check RTMPS as well, thank you for reporting this issue!

 
Profile Image
Motionworx
  -  

Hi @Zoltan,

Any update on this? We still cannot use a NDI feed. We still continuously get "Can't keep latency" error regardless of what resolution and framerate we set it to. All other software accepts the NDI input just fine. We're on version 2021.2.2 Studio Edition.

 
Profile Image
TwentyStudios
  -  

@Motionworx: You know that you can turn the “Can’t keep latency” notifications, right? The problem is most likely present in all software, but they will just quietly drop frames without any warning. You will get the same results in Aximmetry if you switch to “Last Frame” instead.

 
Profile Image
Motionworx
  -  

@TwentyStudios: Thanks for the tip. We're still battling with this though. Aximmetry seems to sporadically decide when it allows the NDI and when not. If I set Aximmetry to show "Last Frame" instead of "Message" as per your suggestion, it shows a blank screen. Last week, when doing the exact same thing, it worked perfectly. This week, nothing changed on our side, but doesn't work. It's baffling. When I open NDI Tools' "Studio Monitor" I get all of the NDI feeds perfectly. All the other software picks it up without issues so I have no idea what I'm doing wrong when it comes to Aximmetry and NDI's. Any other tips that you can suggest? Thanks in advance.

 
Profile Image
Motionworx
  -  

@TwentyStudios: Just got it working again when I changed the NDI frame rate from AUTO to a fixed 30p in Device Mapper. (Although it worked last time on AUTO). Anyway - now I must just ensure that I never shut the computers off ever again so that it keeps working. :-) Thanks again for the help.

 
Profile Image
Darren Levine
  -  

@zoltan@aximmetry

Any update on this issue? on the latest release im testing 3 ndi feeds from one source, and getting various results of "no input" or cannot keep latency, which last a few seconds before reestablishing the feed, i've set the framerates manually to match, and our network is only 30% saturated.

 
Profile Image
TwentyStudios
  -  

@Darren Levine: What NDI sources are you using? We’ve had zero issues lately with vMix and Tricaster as NDI sources I  Aximmetry. NDI screen capture on lower end machines still drop frames now and then, but that’s a problem on the capture side and not with Aximmetry.

You can easily get rid of the message, at least. Just change to Last Frame in the preferences.

 
Profile Image
Motionworx
  -  

@Darren Levine: We resolved this problem by resetting the NDI frame rate in Device Mapper while the project is open. We experienced the same issue with our 2nd monitor as output monitor - it's as if those first settings that pop up when you run Aximmetry serve no purpose. Our workaround was to open Aximmetry, just hit "OK" with all of those settings, load the project, open "Video Outputs", reselect our 2nd display as the output monitor (#2), then it works instantly. Same goes for the NDI source. First load your project, open Device Mapper, reset the frame rate to AUTO or 30p or whatever you have it set to, and then, like magic, it works instantly. Hope this is helpful to you.

 
Profile Image
HumanContact
  -  

Hello, I wanted to weigh in here as I was previously suffering from this issue as well.

Despite a 10G network and no other major network traffic I was continually seeing regular dropped frames, enough that it was noticeable in the final product. Ultimately what I realized was the hardware that was sending the NDI streams, despite new and fairly competent i7 laptops were struggling to keep up even with something like static PowerPoint slides. 

As it turns out, swapping out to different systems and even in some cases less powerful systems, seems to have solved the issue completely. I've had zero dropped frames. In the end, everyone has a different setup so it's hard to say exactly what is causing each issue but don't discount, testing and re-testing your setup to find potential weak points. For me, I'm also beginning to look into hardware NDI encoders for mission critical feeds. 

 
Profile Image
Eifert@Aximmetry
  -  

Hi,

RTMPS support has been added to Aximmetry in version 2021.2.1:
Added support for RTMPS (secure RTMP) to re-enable using Facebook, Vimeo etc. Live.
https://aximmetry.com/learn/software-version-history/#software-additions

Warmest regards,