Skip to content
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

V3.0.0-beta3 windows Nvidia nvenc broken #128

Closed
theofficialgman opened this issue Oct 16, 2022 · 3 comments · Fixed by #19
Closed

V3.0.0-beta3 windows Nvidia nvenc broken #128

theofficialgman opened this issue Oct 16, 2022 · 3 comments · Fixed by #19
Assignees
Labels
bug Something isn't working

Comments

@theofficialgman
Copy link

There is no output in the rtsp stream when the Nvidia nvenc encoder is selected in the streaming settings. This worked perfectly in 27.X and the older versions of the plugin.

X264 does still work in this new version on obs 28

@andrecaleffi
Copy link

same problem here

@sophy228
Copy link

sophy228 commented Feb 9, 2023

The issue is simple, the jim-nvenc get SPP header only after 1st encoded packet, but rtsp output just ask encoder for SPP infomation before that, so rtso create H264 source with empty SPP, than the rtsp client such as VLC report no SPP received ...

Hope author can fix such isse ..

@iamscottxu iamscottxu added the bug Something isn't working label Mar 14, 2023
iamscottxu added a commit that referenced this issue Mar 16, 2023
…ined when using the jim-nvenc encoder. (#128)

Signed-off-by: scottxu <[email protected]>
@iamscottxu iamscottxu self-assigned this Mar 20, 2023
@iamscottxu iamscottxu linked a pull request Mar 20, 2023 that will close this issue
@theofficialgman
Copy link
Author

Can confirm fixed and available in the latest beta release https://github.com/iamscottxu/obs-rtspserver/releases/tag/v3.1.0-beta1

This was referenced Dec 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants