160 replies to this topic

[mesho]

Hmmm..... On the mentioned website Solo2 supports also only linited Transcoding. I see no issues by my friends having Solo2. TranscodingSetup is installed and works fine.

[Dimitrij]

http://wiki.openpli.org/comparison

et8500 SoC bcm7429

root@et8500:~# cat /proc/stb/info/chipset
bcm7241
root@et8500:~#

[Rob van der Does]

You can't use transcoding on Solo SE.

According to http://www.vuplus-co...-for-you.18506/ you can.

[betacentauri]

That's new for me. I thought such a "little" box can't transcode.

[Rob van der Does]

Well, the SoC isn't little

[Rob van der Does]

That's new for me. I thought such a "little" box can't transcode.

Ahh, you meant to say that as even a huge box like the ET8000 can't transcode (in spite of the initil specs), the small Solo SE isn't supposed to be able to

[mesho]

 

You can't use transcoding on Solo SE.

According to http://www.vuplus-co...-for-you.18506/ you can.

According to mentioned website:
If you press the green button, and scroll though the plugins in the menu, you will find the Transcoding Setup, just press ok to select this plugin and then enable it. Once enabled, you can use the Transcoding function.

The problem is that in OpenPLi TranscodingSetup plugin can not be accessed to enable that. I get the green screen with "We are sorry. Your STB encountered a software problem , and need to be restarted. Component: TranscodingSetup." And Solo SE is rebooting. streamproxy.conf is missing in /etc/enigma2. Please find the screen attached.
Just to mention that streaming on Solo SE is not working regular way like on Solo2 but only by using pau plugin.

Attached Files

•  20151005_214624.jpg   257.06KB   6 downloads

Edited by mesho, 6 October 2015 - 21:49.

[Rob van der Does]

That's for the PLi-devs to answer. It looks like the PLi image for the SE doesn't support transcoding then. Other images do.

[Erik Slagter]

I don't think we ship the SoloSE's images with the (required) streamproxy. I was under the impression transcoding is not supported on SoloSE. Please post the output of this command and we will know:

 

ls -l /proc/stb/encoder

 

If that exposes a transcoding API, I can implement support for the SoloSE.

[mx3L]

root@vusolose:~# ls -l /proc/stb/encoder
dr-xr-xr-x    2 root     root             0 Oct  7 12:37 0
-rw-r--r--    1 root     root             0 Oct  7 12:37 enable
-r--r--r--    1 root     root             0 Oct  7 12:37 enable_choices

[Erik Slagter]

Actually I meant ls -R excuse. So at least there is support in the drivers and api.

 

Can someone please make a NEW topic, something like request for transcoding on SoloSE?

Edited by Erik Slagter, 7 October 2015 - 11:50.

[mesho]

It's done. New Topic "request for transcoding on SoloSE" is ready.

[Satpal]

Yesterday I tried for the first time to transcode a recording from the hdd in my home network with the default settings provided by the VU+ Player 2.2 after which the Solo2 didn't respond anymore. Next thing the box didn't fully boot anymore, I had to flash it.

 

Is it really possible to compromise the image so easily?

[Erik Slagter]

Crash it (from the drivers): yes, corrupt the image: no.

[Robinson]

What steps do I need to take to check why I have a problem with transcoding on my Solo2?

I understand I need to check if some binaries are running and if config files are OK? What are they?

What else do I need to check?

[Erik Slagter]

The easiest way to check:

 

- login to the receiver

- type killall streamproxy

- type streamproxy -f

- then try to do transcoding (from your computer, app, or whatever)

- post the output here (minus passwords)

- after done, type ^C

- type streamproxy

[Robinson]

What do you make of it?

root@vusolo2:~# killall streamproxy
killall: streamproxy: no process killed
root@vusolo2:~# streamproxy -f
Checking manufacturer/model: VU+/Solo2
Checking id: /proc/stb/info/model = dm8000
Checking id: /proc/stb/info/vumodel = solo2
model identified as: VU+ Solo2 (bcm7356)
streamproxy: config_map: auth = false/0
streamproxy: config_map: bframes = 0/0
streamproxy: config_map: bitrate = 500/500
streamproxy: config_map: foreground = true/1
streamproxy: config_map: group = /2142228444
streamproxy: config_map: level = 3.1/3
streamproxy: config_map: listen:8002 = 1/1
streamproxy: config_map: listen:8003 = 1/1
streamproxy: config_map: profile = baseline/0
streamproxy: config_map: size = 480p/480
streamproxy: config_map: webifport = 80/80
streamproxy: AcceptSocket: cannot bind accept socket (std::exception)
root@vusolo2:~#
root@vusolo2:~# streamproxy
root@vusolo2:~#

Anything I can do to remedy the issue?

[WanWizard]

check using ps if you really killed it. The error suggests the port is already bound to something.

[Erik Slagter]

In anyway "something" is already listening on port 8002 or 8003. Can it be that you didn't flash for a loooong time? Use netstat -lptn to find out who's guilty.

[Robinson]

Can it be that you didn't flash for a loooong time?

 Yes. It's true.