mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-24 07:30:57 +01:00
[Issue]: rtsp not working with tcp-only source (ffmpeg crash) #3757
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#3757
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MayeulC on GitHub (Apr 20, 2022).
Please describe your bug
I set up rtsp-simple-proxy to convert udp-only streams to tcp-only before forwarding to docker.
It looks like the ffmpeg command used by jellyfin doesn't work as-is (see ffmpeg logs):
However, in that part of the command:
I am not sure why both transport types would be specified
If I delete the
-rtsp_transport udppart, ffmpeg proceeds to decode as intended, and the video appears in the browser. It also works if I switch tcp and UDP around like so:Or if I remove transport options altogether:
rtsp-simple-server might make a good tool for a simple test case. I should note that before making it tcp-only, the first ffprobe failed due to a timeout (invoking it manually and forcing tcp works).
I suggest either swapping these arguments around, or getting rid of them. An alternative would be to call ffprobe in tcp-only, and continue with tcp if it works, or fall back to udp, as it seems tcp is preffered anyway.
Jellyfin Version
10.7.7
if other:
No response
Environment
Jellyfin logs
FFmpeg logs
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@MayeulC commented on GitHub (Aug 3, 2022):
I confirm that this was fixed. Somehow I didn't get a notification, and read it in the release notes. Thanks @thornbill !!!
Now it seems my streams only work while transcoding, I'll investigate.