Project

General

Profile

Bug #4856

Pipe with ts input only in mpeg2

Added by Mytril Goldhand almost 7 years ago. Updated almost 7 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2018-01-14
Due date:
% Done:

0%

Estimated time:
Found in version:
4.2.5
Affected Versions:

Description

Hi guys,

i'm experimenting with the pipe feature to create my own channel. But i have found a problem with the pipe input.

If you have a mux with "pipe:///usr/bin/ffmpeg -re -loglevel fatal - i inputfile.mkv -flags +global_header -c copy -tune zerolatency -f mpegts pipe:1" as url. "inputfile.mkv" can only be a mpeg2 video stream. If it is an h264 or MPEG-4 stream, then it leads to a problem. If you start the channel, you can only hear the audio. If you than restart the channel you can watch and hear all normally. If you wait 10 Minutes or so without watching, the same problems start again.

Files

noVideoThenVideo.txt (31.6 KB) noVideoThenVideo.txt Debug log Mytril Goldhand, 2018-01-14 19:05

History

#2

Updated by Jaroslav Kysela almost 7 years ago

Make sure that your source stream has I (intra) frames at least every 3 seconds. From stats, this file is not ideal for streaming.

#3

Updated by Mytril Goldhand almost 7 years ago

Thank you for your advice.
Now i could fix the problem with h264.

For all who use ffmpeg and x264. -g 70 sets the maximum time between iframes to enarly 3 minutes (3 x 23,97 fps = 71,91) (3 x 25 fps = 75)

Can be closed.

#4

Updated by Mark Clarkstone almost 7 years ago

  • Status changed from New to Invalid

Closing as requested.

Also available in: Atom PDF