Jump to content


Photo

streamproxy and seeking in file


  • Please log in to reply
55 replies to this topic

#1 anudanan

  • Senior Member
  • 962 posts

+14
Neutral

Posted 12 January 2019 - 23:51

If I stream a movie with trancoding from the begin, it works fine. (the header[range]: "bytes=0" is seen in the message file

 

But if I seek to a positon > 0 in the file, transcoding doesn´t start. I´ve tested it with VLC and some apps. Without transcoding it works fine on the direct streamport

 

In the message log I see many busy informations from the broadcom chip. Is this a bug with seeking inside streamproxy?

 

 

 

Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: ClientSocket: header[accept-language]: "de"
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: ClientSocket: header[authorization]: "Basic cm9vdDptaXN0cjJkMg=="
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: ClientSocket: header[host]: "192.168.1.43:8013"
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: ClientSocket: header[range]: "bytes=741286680-"
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: ClientSocket: header[user-agent]: "VLC/3.0.4 LibVLC/3.0.4"
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: ClientSocket: url: /file?file=/hdd/movie/20190112%202154%20-%20SAT_1%20Gold%20HD%20-%201%201_2%20Ritter.ts&bitrate=1000000&width=720&height=576&aspectratio=2&interlaced=0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:  clientsocket: streaming parameters before defaults from config:
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     http_range = 741286680-
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject config default auth = true
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: accept config default bframes = 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: accept config default bitrate = 1000
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject config default foreground = false
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject config default group =
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: accept config default level = 3.1
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject config default listen:8002 = 1
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject config default listen:8013 = 1
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: accept config default profile = baseline
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: accept config default size = 576p
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject config default webifport = 80
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:  clientsocket: streaming parameters after defaults:
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     bframes = 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     bitrate = 1000
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     http_range = 741286680-
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     level = 3.1
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     profile = baseline
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     size = 576p
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: get parameter[aspectratio] = "2"
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject streaming specific param aspectratio = 2
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: get parameter[bitrate] = "1000000"
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: accept streaming specific param bitrate = 1000000
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: get parameter[file] = "/hdd/movie/20190112 2154 - SAT_1 Gold HD - 1 1_2 Ritter.ts"
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject streaming specific param file = /hdd/movie/20190112 2154 - SAT_1 Gold HD - 1 1_2 Ritter.ts
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: get parameter[height] = "576"
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: ClientSocket: Xtrend workaround active
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: accept streaming specific param size = 576p
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: get parameter[interlaced] = "0"
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject streaming specific param interlaced = 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: get parameter[width] = "720"
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject streaming specific param width = 720
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:  clientsocket: streaming parameters after url params:
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     bframes = 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     bitrate = 1000
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     http_range = 741286680-
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     level = 3.1
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     profile = baseline
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     size = 576p
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject default bitrate, it is already set to 1000
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject default size, it is already set to 576p
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject default profile, it is already set to baseline
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject default level, it is already set to 3.1
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: reject default bframes, it is already set to 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: clientsocket: accept default framerate = 30000
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:  clientsocket: streaming parameters after setting default params:
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     bframes = 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     bitrate = 1000
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     framerate = 30000
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     http_range = 741286680-
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     level = 3.1
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     profile = baseline
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy:     size = 576p
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: ClientSocket: file transcoding request
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: ClientSocket: transcoding service broadcom
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: MpegTS::init: file length: 4404 Mb
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 1: 1
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 1: 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 1: 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 1: 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 1: 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 1: 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 1: 5
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: FileTrancoding: streaming file: /hdd/movie/20190112 2154 - SAT_1 Gold HD - 1 1_2 Ritter.ts
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: FileTrancoding: byte_offset: 0 / 4618747904 (0 %)
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: FileTrancoding: pct_offset: 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: FileTrancoding: time_offset: 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: FileTranscodingBroadcom: performing http byte range seek
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: FileTranscodingBroadcom: file_offset: 741286680
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 0
Jan 12 23:36:23 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 1
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 2
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 3
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 4
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 5
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 6
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 7
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 8
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 9
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 10
Jan 12 23:36:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 11
Jan 12 23:36:25 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 12
Jan 12 23:36:25 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 12 23:36:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 13



Edited by anudanan, 12 January 2019 - 23:52.

Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: streamproxy and seeking in file #2 anudanan

  • Senior Member
  • 962 posts

+14
Neutral

Posted 13 January 2019 - 10:01

I´ve the feeling the problem may be that the first streaming connection is still open during the client makes the second connection with seeking to more than byte 0 comes up.

Sometimes it works with VLC; sometimes not.

 

With the dreamplayer APP it doesn´t work.


Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: streamproxy and seeking in file #3 Erik Slagter

  • PLi® Core member
  • 44,821 posts

+489
Excellent

Posted 13 January 2019 - 13:09

It indeed has to do with the encoders. I have not tested this with the Duo4k, but with other receivers, the encoder takes some time for the encoder to be released. This is all internal to the driver and kernel. So when a new request comes in, streamproxy keeps trying it for some time, but apparently not long enough for the duo4k. It's a PITA because sometimes the (first) encoder really is still in use, when you're setting up a second transcoding session, so we're never sure. That's why I can't make the timeout to be "forever". The other side of the issue is that http is stateless. If the seeking request could be done on the same/existing http connection, the whole encoding session would not need to be setup again (12 seconds....) and streamproxy could simply skip the input to the requested point.

 

If we could use an alternative, self designed protocol, it would be quite a bit simpeler, but then no player or app could use it.


Edited by Erik Slagter, 13 January 2019 - 13:10.

* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: streamproxy and seeking in file #4 anudanan

  • Senior Member
  • 962 posts

+14
Neutral

Posted 13 January 2019 - 13:48

The most bad thing from my point of view is that the streaming clients don´t close the tcp session before establishing a new one. I´ve made same traces with wireshark and on my routers and have seen, that the fist TCP session in aktiv but no ACKs are running. After some time (TCP timeout I think) there I see a Reset from the enigma box and if that came fast enough, than the second session runs but mostly not. I don´t know why the clients don´t close the first tcp session.

 

On my box I only have one encoder (uno4kse) so seeking is today not working with apps.

 

I think there is no chance to make a detection that the seeking connection comes from the same client in the same movie. If it possible streamproxy have a chance to kill the established TCP session and the encoder is faster free for the next session

 

Here I have a message log form a stream with dreamplayer. First from the beginning and then a seek which doens´t worl


Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: streamproxy: accept new connection on port 8013, default action: transcode, fd 7
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: ClientSocket: authentication: xxxx,xxxx
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: ClientSocket: header[accept]: "*/*"
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: ClientSocket: header[accept-language]: "en_US"
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: ClientSocket: header[authorization]: "Basic cm9vdDptaXN0cjJkMg=="
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: ClientSocket: header[host]: "gsf1200s.mooo.com:8013"
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: ClientSocket: header[range]: "bytes=0-"
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: ClientSocket: header[user-agent]: "VLC/3.0.4 LibVLC/3.0.4"
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: ClientSocket: url: /file?file=%2Fhdd%2Fmovie%2F20190113%200343%20-%20SAT_1%20HD%20-%20Troja.ts&bitrate=1000000&size=576p
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:  clientsocket: streaming parameters before defaults from config:
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     http_range = 0-
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: reject config default auth = true
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: accept config default bframes = 0
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: accept config default bitrate = 1000
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: reject config default foreground = false
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: reject config default group = 
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: accept config default level = 3.1
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: reject config default listen:8002 = 1
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: reject config default listen:8013 = 1
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: accept config default profile = baseline
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: accept config default size = 576p
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: reject config default webifport = 80
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:  clientsocket: streaming parameters after defaults:
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     bframes = 0
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     bitrate = 1000
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     http_range = 0-
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     level = 3.1
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     profile = baseline
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     size = 576p
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: get parameter[bitrate] = "1000000"
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: accept streaming specific param bitrate = 1000000
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: get parameter[file] = "/hdd/movie/20190113 0343 - SAT_1 HD - Troja.ts"
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: reject streaming specific param file = /hdd/movie/20190113 0343 - SAT_1 HD - Troja.ts
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: get parameter[size] = "576p"
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: accept streaming specific param size = 576p
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:  clientsocket: streaming parameters after url params:
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     bframes = 0
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     bitrate = 1000
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     http_range = 0-
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     level = 3.1
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     profile = baseline
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     size = 576p
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: reject default bitrate, it is already set to 1000
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: reject default size, it is already set to 576p
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: reject default profile, it is already set to baseline
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: reject default level, it is already set to 3.1
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: reject default bframes, it is already set to 0
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: clientsocket: accept default framerate = 30000
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:  clientsocket: streaming parameters after setting default params:
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     bframes = 0
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     bitrate = 1000
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     framerate = 30000
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     http_range = 0-
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     level = 3.1
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     profile = baseline
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy:     size = 576p
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: ClientSocket: file transcoding request
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: ClientSocket: transcoding service broadcom
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: MpegTS::init: file length: 9090 Mb
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 1: 6
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 2: 0
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 1: 5
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: FileTrancoding: streaming file: /hdd/movie/20190113 0343 - SAT_1 HD - Troja.ts
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: FileTrancoding: byte_offset: 0 / 9532424192 (0 %)
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: FileTrancoding: pct_offset: 0
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: FileTrancoding: time_offset: 0
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: FileTranscodingBroadcom: file_offset: 0
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: EncoderBroadcom: bcm_enc0 open
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: EncoderBroadcom: found streaming parameter == stb_feature: "bframes" [0]
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: setprop: gop_frameb=0
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: EncoderBroadcom: found streaming parameter == stb_feature: "bitrate" [1000]
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: setprop: bitrate=1000000
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: EncoderBroadcom: found streaming parameter == stb_feature: "framerate" [30000]
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: setprop: framerate=30000
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: EncoderBroadcom: no stb traits/feature entry for streaming parameter "http_range"
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: EncoderBroadcom: found streaming parameter == stb_feature: "level" [3.1]
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: setprop: level=3.1
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: EncoderBroadcom: found streaming parameter == stb_feature: "profile" [baseline]
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: setprop: profile=baseline
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: EncoderBroadcom: found streaming parameter == stb_feature: "size" [576p]
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: setprop: display_format=576p
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: pmt: 96
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: video: 255
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: audio: 259
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: start ioctl
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: FileTranscodingBroadcom: encoder pid[audio] = 103
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: FileTranscodingBroadcom: encoder pid[pmt] = 60
Jan 13 13:39:57 Schlafzimmer user.warn streamproxy: FileTranscodingBroadcom: encoder pid[video] = ff
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: streamproxy: accept new connection on port 8013, default action: transcode, fd 7
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: ClientSocket: authentication: rxxxx,xxxxx
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: ClientSocket: header[accept]: "*/*"
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: ClientSocket: header[accept-language]: "en_US"
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: ClientSocket: header[authorization]: "Basic cm9vdDptaXN0cjJkMg=="
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: ClientSocket: header[host]: "gsf1200s.mooo.com:8013"
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: ClientSocket: header[range]: "bytes=4289590772-"
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: ClientSocket: header[user-agent]: "VLC/3.0.4 LibVLC/3.0.4"
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: ClientSocket: url: /file?file=%2Fhdd%2Fmovie%2F20190113%200343%20-%20SAT_1%20HD%20-%20Troja.ts&bitrate=1000000&size=576p
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:  clientsocket: streaming parameters before defaults from config:
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     http_range = 4289590772-
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: reject config default auth = true
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: accept config default bframes = 0
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: accept config default bitrate = 1000
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: reject config default foreground = false
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: reject config default group = 
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: accept config default level = 3.1
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: reject config default listen:8002 = 1
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: reject config default listen:8013 = 1
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: accept config default profile = baseline
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: accept config default size = 576p
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: reject config default webifport = 80
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:  clientsocket: streaming parameters after defaults:
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     bframes = 0
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     bitrate = 1000
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     http_range = 4289590772-
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     level = 3.1
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     profile = baseline
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     size = 576p
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: get parameter[bitrate] = "1000000"
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: accept streaming specific param bitrate = 1000000
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: get parameter[file] = "/hdd/movie/20190113 0343 - SAT_1 HD - Troja.ts"
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: reject streaming specific param file = /hdd/movie/20190113 0343 - SAT_1 HD - Troja.ts
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: get parameter[size] = "576p"
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: accept streaming specific param size = 576p
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:  clientsocket: streaming parameters after url params:
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     bframes = 0
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     bitrate = 1000
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     http_range = 4289590772-
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     level = 3.1
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     profile = baseline
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     size = 576p
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: reject default bitrate, it is already set to 1000
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: reject default size, it is already set to 576p
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: reject default profile, it is already set to baseline
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: reject default level, it is already set to 3.1
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: reject default bframes, it is already set to 0
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: clientsocket: accept default framerate = 30000
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:  clientsocket: streaming parameters after setting default params:
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     bframes = 0
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     bitrate = 1000
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     framerate = 30000
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     http_range = 4289590772-
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     level = 3.1
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     profile = baseline
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy:     size = 576p
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: ClientSocket: file transcoding request
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: ClientSocket: transcoding service broadcom
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: MpegTS::init: file length: 9090 Mb
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 1: 6
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 1: 0
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: MpegTS::read_pmt: reserved 1: 3
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: FileTrancoding: streaming file: /hdd/movie/20190113 0343 - SAT_1 HD - Troja.ts
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: FileTrancoding: byte_offset: 0 / 9532424192 (0 %)
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: FileTrancoding: pct_offset: 0
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: FileTrancoding: time_offset: 0
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: FileTranscodingBroadcom: performing http byte range seek
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: FileTranscodingBroadcom: file_offset: 4289590772
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 0
Jan 13 13:40:23 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 1
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 2
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 3
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 4
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 5
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 6
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 7
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 8
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 9
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 10
Jan 13 13:40:24 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 11
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 12
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 13
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 14
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 15
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 16
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 17
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 18
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 19
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 20
Jan 13 13:40:25 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 21
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 22
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 23
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 24
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 25
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 26
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 27
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 28
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 29
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 30
Jan 13 13:40:26 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 31
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 32
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 33
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 34
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 35
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 36
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 37
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 38
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 39
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 40
Jan 13 13:40:27 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 41
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 42
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 43
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 44
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 45
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 46
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 47
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 48
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 49
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 50
Jan 13 13:40:28 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 51
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 52
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 53
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 54
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 55
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 56
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 57
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 58
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 59
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 60
Jan 13 13:40:29 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:30 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 61
Jan 13 13:40:30 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:30 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 62
Jan 13 13:40:30 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:30 Schlafzimmer user.warn streamproxy: EncoderBroadcom: waiting for encoder 0 to become available, attempt 63
Jan 13 13:40:30 Schlafzimmer user.warn streamproxy: system error: Device or resource busy
Jan 13 13:40:30 Schlafzimmer user.warn streamproxy: ClientSocket: trap: no encoders available (std::exception)
Jan 13 13:40:30 Schlafzimmer user.warn streamproxy: streamproxy: pid 22884 exited
Jan 13 13:40:30 Schlafzimmer user.warn streamproxy: FileTranscodingBroadcom: client hung up
Jan 13 13:40:30 Schlafzimmer user.warn streamproxy: FileTranscodingBroadcom: streaming ends, socket max queue fill: 45%
Jan 13 13:40:32 Schlafzimmer user.warn kernel: [1117263.560164] !!!^M[MENC]: TIMEOUT 0
Jan 13 13:40:32 Schlafzimmer user.warn kernel: [1117263.560164] 
Jan 13 13:40:32 Schlafzimmer user.warn streamproxy: FileTranscodingBroadcom: cleanup up
Jan 13 13:40:32 Schlafzimmer user.warn streamproxy: ClientSocket: file transcoding ends
Jan 13 13:40:32 Schlafzimmer user.warn streamproxy: streamproxy: pid 22879 exited 

Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: streamproxy and seeking in file #5 Erik Slagter

  • PLi® Core member
  • 44,821 posts

+489
Excellent

Posted 13 January 2019 - 14:08

There is another issue, like you, looks like it, already found out. Many clients setup more than one http connection to a server. They setup a new connection for a new request but leave the existing open for a next request ("http connection caching"). From the client's perspective, this is reasonable, but for the streamproxy, it's a disaster. This way the streamproxy never knows when the current streaming socket is done with and the transcoding should stop.

 

As said, the obvious solution would be to not use http for streaming, where the client sets ip only connection; data from server to client is current encoder output, data from client to server is commands to control the encoder. When the connection is closed, the session is aborted; it should normally not occur because the client should announce it's leaving.

 

If you can get an app developer willing to implement such a protocol, I'll make the streamproxy side. And then you'll have seemless and quick seeking in recordings.


* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: streamproxy and seeking in file #6 anudanan

  • Senior Member
  • 962 posts

+14
Neutral

Posted 13 January 2019 - 14:23

I don´t know many persons for programming or changing APPs.

 

I only have contact to the writer of tellymote for IOS but this APP is today not able to stream trancodes movies, only without trancoding. For LIVE TV tellymote supports trancoding.

 

He is very active in the VTI forum so I don´t know how he is interested to implement a better protocol together with openpli

 

But for the APPS dreamdroid or dreamplayer (android), which works normally very stable and are easy to use, I don´t have contact to the developer.


Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: streamproxy and seeking in file #7 Erik Slagter

  • PLi® Core member
  • 44,821 posts

+489
Excellent

Posted 14 January 2019 - 20:32

But at least you know now why this is working non-optimal.


* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: streamproxy and seeking in file #8 anudanan

  • Senior Member
  • 962 posts

+14
Neutral

Posted 14 January 2019 - 21:22

exactly, it is very clear now. Thanks for the very technical discussion


Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: streamproxy and seeking in file #9 Erik Slagter

  • PLi® Core member
  • 44,821 posts

+489
Excellent

Posted 15 January 2019 - 19:30

You never know if you're going to find an app developer that's willing to implement another protocol and then we can solve it :)


* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: streamproxy and seeking in file #10 anudanan

  • Senior Member
  • 962 posts

+14
Neutral

Posted 15 January 2019 - 19:41

I had contact to Christan Fees who hat written dreamplayer, but he have no time actually to do that

 

I also have writte a mail to the developer of dreamdroid, but until today I´ve no answer 


Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: streamproxy and seeking in file #11 Erik Slagter

  • PLi® Core member
  • 44,821 posts

+489
Excellent

Posted 16 January 2019 - 19:30

Yes, I have also a few requests with Christian Fees pending ;)


* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: streamproxy and seeking in file #12 anudanan

  • Senior Member
  • 962 posts

+14
Neutral

Posted 23 January 2019 - 19:33

Today I have made some prototyping codechanges to find a workaround for the seeking problem. Now my changed streamproxy parent process kills a streaming process, if the new requested file for transcoding has the same name as the file which is in transcoded steaming.The hw encoder is now earlier free and the new stream can start. I know that is not perfect because a second other client with the same requests file can kill the other steam but that is acceptable for me on my uno4kse, because I only have one encoder.

The code is not fine today but it works. I‘ve placed the fork later now in the clientstreaming.cpp because the parent must know the filename to store it for the later comparison .

Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: streamproxy and seeking in file #13 Erik Slagter

  • PLi® Core member
  • 44,821 posts

+489
Excellent

Posted 23 January 2019 - 19:37

I am always in a for POC ;)

 

I have though of a construction like this, but it's very difficult to implement in a way that always works.

 

Also you will that killing a streamproxy client process is dangerous; if the encoding buffer isn't emptied frequently when the encoder is still running, that will often lead to a driver crash.


Edited by Erik Slagter, 23 January 2019 - 19:38.

* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: streamproxy and seeking in file #14 anudanan

  • Senior Member
  • 962 posts

+14
Neutral

Posted 23 January 2019 - 19:47

So SIGTERM is better to send to the fork child and a signal handler for that musst read the buffer empty

Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: streamproxy and seeking in file #15 Erik Slagter

  • PLi® Core member
  • 44,821 posts

+489
Excellent

Posted 23 January 2019 - 20:00

That could be an option. The problem is that the signal interrupts the read and poll calls so may also cause problems. That could in itself be worked around I think. But I'd rather see a real IPC method where the new child signals all existing children it has a request to stream service x (where service can be something like 1:0:1:... or a file) and then waits for all children that are already streaming that service to properly flush and terminate. But that will take time, possibly a few seconds.

 

It would be even better to not kill or terminate the child but recycle it. At any moment we can close/shutdown the existing connection to the browser (or app, for the same), http should be able to handle that. Then we replace the http connection with the new connection. That way the new connection does not need to setup the encoding, which normally takes about 12 seconds and can simply do the seek and continue outputting to the encoder.

 

I will have to think about this for maybe nasty effects I don't think of right now.


* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: streamproxy and seeking in file #16 anudanan

  • Senior Member
  • 962 posts

+14
Neutral

Posted 23 January 2019 - 20:05

An interesting idea, thanks for sharing

Edited by anudanan, 23 January 2019 - 20:09.

Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: streamproxy and seeking in file #17 anudanan

  • Senior Member
  • 962 posts

+14
Neutral

Posted 23 January 2019 - 20:42

Do you think it es easy to give an old child process the access to the new connection socket. Maybe that is easier with thread because they have the same addressspace

Edited by anudanan, 23 January 2019 - 20:46.

Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: streamproxy and seeking in file #18 Erik Slagter

  • PLi® Core member
  • 44,821 posts

+489
Excellent

Posted 24 January 2019 - 17:33

Currently they're different processes, resulting from a fork(). It could be done using threads, I already thought about it when I originally designed it. Problem is that each thread will need for a part own storage (TLS - thread local storage). Most data is encapsulated in classes, so I'd have to come up with an alternative allocator for each class that uses TLS. It's all doable, but a fork() is so much simpeler.

 

Threads are best used when all or next to all data can be shared. That's not the case here.


Edited by Erik Slagter, 24 January 2019 - 17:34.

* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.

Re: streamproxy and seeking in file #19 anudanan

  • Senior Member
  • 962 posts

+14
Neutral

Posted 24 January 2019 - 22:51

Is it possible to transfer the new sockethandling structures to an old child process?  Currently is goes with the fork to the child. But how goes it to the child from the parent later when a next connection will come up?


Receiver:2 x Uno4k SE (PLI 7.0 rel), 1 x ET9200 (PLI 4.0), NAS: 2 x QNAP 410, TV: LG 50PS8000, LG 47LB570V, LG 42LM615S, Sound: Yamaha RX-v663, Teufel System 5 THX


Re: streamproxy and seeking in file #20 Erik Slagter

  • PLi® Core member
  • 44,821 posts

+489
Excellent

Posted 25 January 2019 - 19:17

That's something that is possible but needs good thinking.


* Wavefrontier T90 with 28E/23E/19E/13E/9E/4.8E/0.8W/5W via SCR switches 2 x 2 x 6 user bands
* Ziggo digital cable TV (FTA)
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users