-
-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Blank screen on broadcast from Popos 22.04 to Macos, Playback freezes on the Popos #957
Comments
Couple of things I've tried, I tried building the obs-ndi from the source and replaced the obs-plugin with the .so generated from the build with the command When I run obs from the console I can see no errors
I was able to capture this error message but not sure if its related to ndi plugin
|
What version of ffmpeg is installed? |
Also try:
|
@paulpv Thank you. I am running ffmpeg version 4.4.4
This is the main issue I am having, when I play the video from the other device, only 1 frame is played and it just gets stuck. So I think maybe the issue is with the encoders and decoders. What version of ffmpeg am I supposed to have? |
How did you install OBS and obs-ndi? |
I installed obs via the apt repo. And obs ndi first with the .deb package. But, I 've also built the obs and obs-ndi package myself to test if it worked on the latest version.
Another method:
|
Operating System Version
Popos 22.04
OBS Version
30.0.2
NDI Tools Version
SDK Version 5.6
Describe the bug
So, I've been trying to make the obs-ndi work on the pop os 22.04. Installed runtime, installed the obs-ndi and broadcasted the screen by making creating an output. But when I try to play the source from the NDI monitor or obs ndi on my mac, all I see is blank screen. When I try to play the braodcast from the NDI-HX camera or the macos in the obs-ndi by adding new source, it plays couple frames and just gets stuck.
I have tried everything, but couldn't make it work for the life of me. :(
Steps to reproduce
Expected behavior
No response
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: