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

nvmpi decoder fails with some RTSP streams #113

Open
w3sip opened this issue Apr 12, 2022 · 5 comments
Open

nvmpi decoder fails with some RTSP streams #113

w3sip opened this issue Apr 12, 2022 · 5 comments

Comments

@w3sip
Copy link

w3sip commented Apr 12, 2022

Trying to use nvmpi with ffmpeg 4.2 -- using commit 3dff99c3c2ef280209244d9bae5771997d4aa770 from this repository.

It seems to be very finicky with the bitstream it attempts to consume. For example:

ffmpeg/bin/ffmpeg -c:v h264_nvmpi -i rtsp://127.0.0.1/short.mkv -f null - - this command fails to decode RTSP stream served by live555 (frames are never generated)

The stream is fine (a different decoder is able to process it):

ffmpeg/bin/ffmpeg -c:v h264 -i rtsp://127.0.0.1/short.mkv -f null - - this command decodes it without issue

The problem isn't exclusive to live555 (we've seen it fail with ffmpeg-served video, albeit not as often), but this is the easiest way to reproduce the problem.

I'm attaching
live555.zip

Just running ./live555MediaServer & and one of the commands above should reproduce the issue.

@aimaicai
Copy link

I've the same problem: if I connect to a rtsp stream from a live camera is all ok, but if I connect to a rtsp media server streaming a video in loop it doesn't work: no frame are decoded. I'm using ffmpeg 4.2 and rtsp-simple-server (https://github.com/aler9/rtsp-simple-server) as server.
If I launch ffmpeg with the debug loglevel I see this output repeatedly coming till I ctrl-c:

cur_dts is invalid st:0 (0) [init:0 i_done:0 finish:0] (this is harmless if it occurs once at the start per stream)

Thanks for the awesome project.

@w3sip
Copy link
Author

w3sip commented Apr 14, 2022

The problem seems to be not with this wrapper, but the actual nvidia implementation. I'm seeing the same behavior if running with nvidia-supplied ffmpeg on Jetson. Tracking it here - https://forums.developer.nvidia.com/t/nvmpi-decoder-doesnt-work/210993/7

@grantthomas
Copy link

Can you elaborate on 'nvidia-supplied ffmpeg on Jetson' ?
From what I've understood, the entire reason why jetson-ffmpeg exists is because nvidia doesn't provide or support ffmpeg with hardware acceleration.

@grantthomas
Copy link

Interesting, thank you for the link @w3sip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants