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.

Sign up for GitHub

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

Jump to bottom

Invalid NAL units reported by ffmpeg #49

Closed
QuantumEntangledAndy opened this issue Jul 28, 2020 · 0 comments · Fixed by #50
Closed

Invalid NAL units reported by ffmpeg #49

QuantumEntangledAndy opened this issue Jul 28, 2020 · 0 comments · Fixed by #50
Labels
bug Something isn't working

Comments

@QuantumEntangledAndy
Copy link
Collaborator

QuantumEntangledAndy commented Jul 28, 2020 •
edited
Loading

Describe the bug
When using neolink with ffmpeg, ffmepg reports that it is recieving invalid NAL (h264) units.

To Reproduce
Start neolink with h264 stream and open with ffplay

Log will include items such as

[h264 @ 0x7f9866877c00] Invalid NAL unit 0, skipping.    0B f=0/0
[h264 @ 0x7f9866877c00] Invalid NAL unit 0, skipping.    0B f=0/0
[h264 @ 0x7f9866877c00] Invalid NAL unit 0, skipping.    0B f=0/0
[h264 @ 0x7f9866877c00] Invalid NAL unit 0, skipping.    0B f=0/0
[h264 @ 0x7f9866877c00] Invalid NAL unit 8, skipping.    0B f=0/0

Expected behavior
ffmpeg/ffplay to report a valid stream

Versions
Neolink version: head (95935d331b3c8b2de07a8d40ec7b9580a16424c7e)
Reolink camera model and firmware: E1

I think this is to do with the extra data that neolink sends along with the video such as the aac. Filtering this out may be sufficient.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Filter data sent to gsteamer using magic bytes QuantumEntangledAndy/neolink
1 participant
@QuantumEntangledAndy