Transcoding problem
Re: Transcoding problem #161
Posted 13 April 2014 - 09:23
<p><span style="font-size:18px;"><span style="font-family:'lucida sans unicode', 'lucida grande', sans-serif;"><strong>Vu+ SOLO</strong></span></span>
Re: Transcoding problem #162
Posted 13 April 2014 - 09:30
HTTP/1.0 400 Bad request: ClientSocket: peer connection timeoutThx, this is an error message I can check.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
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: Transcoding problem #163
Re: Transcoding problem #164
Posted 13 April 2014 - 14:12
Read back before asking questions, that would help a lot.
The plugin is removed because it allowed you to change settings that crashed the transcoding engine. For now, use the config file. A new plugin is being worked on.
We're (Erik that is) are completely rewriting the stream and transcoding handling, to make it generic for all boxes, and to make it a lot more stable than the VU junk.
But that doesn't happen overnight. If you can't live with an instable situation every now and then, don't update to the bleeding edge, but only update when you know it is stable (and if not, revert to your backup).
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Transcoding problem #165
Posted 13 April 2014 - 14:21
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
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: Transcoding problem #166
Re: Transcoding problem #167
Posted 13 April 2014 - 14:27
This message means no http line was received within 5 seconds after opening the connection. Which is to be expected when you start up a telnet connection, so this is not a real error.
HTTP/1.0 400 Bad request: ClientSocket: peer connection timeoutThx, this is an error message I can check.
Can please do the following:
-> reboot the receiver (necessary for a clean dmesg output)
killall streamproxy
streamproxy -f
the streamproxy will run in the foreground now and log some things.
Now fire up the transcoding client device and after a complete run, copy all of the logging and paste it here. Also paste the output of dmesg please.
I am very curious why it works over here and not on your receiver.
Edited by Erik Slagter, 13 April 2014 - 14:28.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
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: Transcoding problem #168
Posted 13 April 2014 - 14:28
If you read some of the pages of this topic, you will have all of your answers.It is a pity that you solved for all as it will be better and removed a plug-in.
With lack of authorization on a stream? Why it doesn't work?
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
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: Transcoding problem #169
Re: Transcoding problem #170
Posted 13 April 2014 - 14:29
If you read some of the pages of this topic, you will have all of your answers.It is a pity that you solved for all as it will be better and removed a plug-in.
With lack of authorization on a stream? Why it doesn't work?
Edited by Erik Slagter, 13 April 2014 - 14:29.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
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: Transcoding problem #171
Posted 13 April 2014 - 14:33
This message means no http line was received within 5 seconds after opening the connection. Which is to be expected when you start up a telnet connection, so this is not a real error.
HTTP/1.0 400 Bad request: ClientSocket: peer connection timeoutThx, this is an error message I can check.
Can please do the following:
-> reboot the receiver (necessary for a clean dmesg output)
killall streamproxy
streamproxy -f
the streamproxy will run in the foreground now and log some things.
Now fire up the transcoding client device and after a complete run, copy all of the logging and paste it here. Also paste the output of dmesg please.
I am very curious why it works over here and not on your receiver.
well its working now lol looks like killall streamproxy fixed it
<p><span style="font-size:18px;"><span style="font-family:'lucida sans unicode', 'lucida grande', sans-serif;"><strong>Vu+ SOLO</strong></span></span>
Re: Transcoding problem #172
Re: Transcoding problem #173
Posted 13 April 2014 - 14:36
the solo2 totally froze now
root@vusolo2:~# killall streamproxy
root@vusolo2:~# streamproxy -f> 8002 -> transcode,5> 8003 -> transcode,6streamproxy: accept new connection on port 8002, default action: transcode, fd 7ClientSocket: no authorisation received from clientstreamproxy: accept new connection on port 8002, default action: transcode, fd 7ClientSocket: authentication: root,openpliClientSocket: header[Authorization]: "Basic cm9vdDp4Ym"ClientSocket: header[Connection]: "close"ClientSocket: header[Host]: "vusolo2.local:8002"ClientSocket: header[Icy-MetaData]: "1"ClientSocket: header[Range]: "bytes=0-"ClientSocket: header[User-Agent]: "VLC/2.1.1 LibVLC/2.1.1"ClientSocket: url: /1:0:1:2020:430:1:C00000:0:0:0:ClientSocket: parameter[] = "/1:0:1:2020:430:1:C00000:0:0:0:"Service: create service: 1:0:1:2020:430:1:C00000:0:0:0ClientSocket: default live requestClientSocket: transcoding serviceLiveTranscoding: 1:0:1:2020:430:1:C00000:0:0:0WebifRequest: send request to webif: "GET /web/stream?StreamService=1:0:1:2020:430:1:C00000:0:0:0 HTTP/1.0Authorization: Basic cm9vdDp4Ym"LiveTranscoding: pid[audio] = 6cLiveTranscoding: pid[audio-1] = 6dLiveTranscoding: pid[pat] = 0LiveTranscoding: pid[pcr] = 19aLiveTranscoding: pid[pmt] = 191LiveTranscoding: pid[subtitle] = 1b9LiveTranscoding: pid[subtitle-1] = 1b9LiveTranscoding: pid[text] = 1b9LiveTranscoding: pid[video] = 19aEncoder: open encoder /dev/bcm_enc0Encoder::setprop: cannot open property /proc/stb/encoder/0/display_format, system error: No such file or directoryEncoder::setprop: cannot open property /proc/stb/encoder/0/profile, system error: No such file or directoryEncoder::setprop: cannot open property /proc/stb/encoder/0/level, system error: No such file or directoryEncoder::setprop: cannot open property /proc/stb/encoder/0/gop_frameb, system error: No such file or directoryLiveTranscoding: encoder pid[audio] = 6c, system error: No such file or directoryLiveTranscoding: encoder pid[pat] = 0, system error: No such file or directoryLiveTranscoding: encoder pid[pmt] = 191, system error: No such file or directoryLiveTranscoding: encoder pid[video] = 19a, system error: No such file or directoryDemuxer: ioctl demuxer ADD PID: audio -> 0x6c, system error: No such file or directoryDemuxer: ioctl demuxer ADD PID: pmt -> 0x191, system error: No such file or directoryDemuxer: ioctl demuxer ADD PID: video -> 0x19a, system error: No such file or directoryLiveTranscoding: state init -> starting, system error: No such file or directoryLiveTranscoding: state starting -> running, system error: No such file or directory
Edited by taboune, 13 April 2014 - 14:39.
<p><span style="font-size:18px;"><span style="font-family:'lucida sans unicode', 'lucida grande', sans-serif;"><strong>Vu+ SOLO</strong></span></span>
Re: Transcoding problem #174
Posted 13 April 2014 - 14:36
If you read some of the pages of this topic, you will have all of your answers.It is a pity that you solved for all as it will be better and removed a plug-in.
With lack of authorization on a stream? Why it doesn't work?
Edited by Erik Slagter, 13 April 2014 - 14:37.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
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: Transcoding problem #175
Posted 13 April 2014 - 14:41
Encoder::setprop: cannot open property /proc/stb/encoder/0/display_format, system error: No such file or directory Encoder::setprop: cannot open property /proc/stb/encoder/0/profile, system error: No such file or directory Encoder::setprop: cannot open property /proc/stb/encoder/0/level, system error: No such file or directory Encoder::setprop: cannot open property /proc/stb/encoder/0/gop_frameb, system error: No such file or directoryThese are all errors.
Are you on a solo2 or on a duo2?
Can you please do this?
ls /proc/stb/encoder
ls /proc/stb/encoder/0
ls /proc/stb/encoder/1
The only way I can explain this could happen is that the transcoding engine already crashed at this point. The dmesg will show a lot of barf in that case (including null pointer/page references etc.)
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
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: Transcoding problem #176
Posted 13 April 2014 - 14:43
openpli 4 vusolo2 vusolo2 login: root Password:xxxxx root@vusolo2:~# ls /proc/stb/encoder 0 enable enable_choices root@vusolo2:~# ls /proc/stb/encoder/0 audio_pid demux framerate_choices pmt_pid bitrate framerate pcr_pid video_pid root@vusolo2:~# ls /proc/stb/encoder/1 ls: /proc/stb/encoder/1: No such file or directory
<p><span style="font-size:18px;"><span style="font-family:'lucida sans unicode', 'lucida grande', sans-serif;"><strong>Vu+ SOLO</strong></span></span>
Re: Transcoding problem #177
Posted 13 April 2014 - 14:44
The solo2 totally froze now
Yeah, that's the marvellous quality of the drivers of VU+.
Somehow you're doing "something" that upsets the drivers up to a point they stop trancoding and also crash the kernel at some point
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
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: Transcoding problem #178
Posted 13 April 2014 - 14:45
I did not test on the solo2 (yet). I guess the proc files are being written with values that upset the driver (but are good on vuduo2). I will test (and try to come with a workaround) for the solo2 one of the next days.
Edited by Erik Slagter, 13 April 2014 - 14:46.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
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: Transcoding problem #179
Re: Transcoding problem #180
Posted 13 April 2014 - 19:49
But it was working with the same settings ahhhhhhhhhhhh this is annoying
You can surely say that.
It appears that the solo2's driver is of even worse quality that we're used to on VU+ products.
This is what's going on:
When the streamproxy get's a request, it tries the encoders one-by-one to find a non-busy one. On the solo2 this will always be /dev/bcm_enc0, on the duo2 it can be either /dev/bcm_enc0 or /dev/bcm_enc1, depening whether the first is already being used.
Until today I had no exceptions for the solo2 and the duo2, both were treated the same. Which should be ok, solo2 has one encoder, duo2 has two and that's it. Also the duo2 has some extra encoding options, which would be tried to get set on the solo2 but fail (with a warning, you've seen it), no problem. The options would be set after opening the encoder device. That is only then we know which encoder is used, so which /proc/stb/encoder[0-1] directory to use.
It now appears the solo2 does not tolerate that. Anything you write (or read!) in this directory while the encoder is open, will crash (sigsegfault) the userspace application. So I made a workaround for the solo2 to only open /dev/bcm_enc0, to assume the encoder is always "0" and to set the bitrate (the only feasable option on the solo2) BEFORE the encoder is opened. That should prevent the crash. BUT in testing what model the streamproxy is running on, I used an access call (that is "open" without actually open the file, it only checks it's presence) on /dev/bcm_enc1 (which is not present on the solo2). Now to my amazing this also crashes! I have now made a workaround upon the workaround (scan the whole directory instead) and this seems to work.
So... I guess the solo2 now works again. Yes it's ugly. Try tomorrow.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
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.
21 user(s) are reading this topic
0 members, 21 guests, 0 anonymous users