693 replies to this topic

[Rob van der Does]

Knowing that it did work fine a short time ago, I flashed 28/5 PLi to see if I could replicate using the just updated Android VU-Player.
And indeed: all kinds of issues:
1- Sometimes the 'loading' screen starts flashing,
2- sometimes all goes well, but trying to change the bitrate of a transcoded stream the app tells me transcoding isn't supported,
3- sometimes only a white screen shows
4- sometimes nothing works at all.
This was with authentication set to off. If set to on transcoding doesn't work at all.

The above issues seem to be random.

[Erik Slagter]

Last change/update in the streamproxy is may 25.

[tilleke]

I will check the issue with Solo2 and Vu+ Player.

[Erik Slagter]

It might be an issue with setting the bitrate too high, somewhere above 500kbps (iirc) the driver starts to get flaky (working only every now and then and ultimately crash).

[колбаскин]

It might be an issue with setting the bitrate too high, somewhere above 500kbps (iirc) the driver starts to get flaky (working only every now and then and ultimately crash).

 

You try VU+Player on VU+ Solo2 with transcoding ?

 

You removed the plugin for change settings transcoding from image and now you can not change the settings in VU+ player on the phone

[Rob van der Does]

My first transcoded stream was fine. That was with the default bitrate 1mbs. I then changed to 500kbs and the trouble started. Rebooting the Solo2 and the app didn't change it for the better.
atm I'm trying to help Tilleke to debug this issue.

[Rob van der Does]

atm I'm trying to help Tilleke to debug this issue.

Done that. It looks like there is an issue with the (automated) starting of the stream proxy webserver.
Tilleke will contact Erik about this.

[tilleke]

I just tested Vu+ Player with a Solo2 using OpenPLI with the help of SatKiekerd.

 

It did not work in the beginning but then I realized that the process streamproxy was not running. I started it manually and everything worked just fine!

 

Erik: I have also noted that sometimes streamproxy does not start. A reboot fixes it. Could it be a problem with the "/etc/init.d"?

 

I did not test test streaming authentication but I guess it should work just fine.

[Erik Slagter]

It's more propable that the streamproxy does start indeed, but it stops for some reason. At that moment the syslog should give some information. I haven't seen it in some while.

[tilleke]

I checked this evening in LAN with my Solo2 flashed with OpenPLI of May 29, 2014 and Vu+ Player for Android (version 2.0) and everything worked great. 

I tried with and without streaming authentication. Everything fine also with Internal Player (and changing frequently bitrates from app).

 

One thing I suggest is that if you have JUST flashed the STB, then reboot it and the streamproxy works fine thereafter. In either case, I think a reboot after a flash is always a good idea.

 

You removed the plugin for change settings transcoding from image and now you can not change the settings in VU+ player on the phone

 

So based on my test earlier today in remote (thanks to @SatKiekerd for helping out) and my test this evening, Vu+ Player seems to work very well with OpenPLI and its streamproxy (including changing bitrates from app). Also the Duo2 is running well.

As suggested by me, try to reboot if you have just flashed the STB.

 

Hope this helps.

Edited by tilleke, 29 May 2014 - 23:21.

[Rob van der Does]

Well, this doesn't coincide my experience. Yesterday I flashed PLi twice, rebooted several times (warm and cold) and yet I couldn't get transcoding to work. That was also on my LAN and using the Android VU-Player.

Edited by SatKiekerd, 30 May 2014 - 05:24.

[Erik Slagter]

Okay SatKiekerd, then apparently some combination of factors gives problems and you're lucky Can you please enable syslog (either file or memory buffering), reboot, scan the syslog for streamproxy and post them here? Hope this gives some clue's.

[Erik Slagter]

@Tilleke, I think the VU+Player 2.0 is a nice piece of work, there is only one little problem I have, but that's very probable due to my hardware/firmware, starting a file stream may take ages to complete, but I found out that if I standby the device and wake it, it continues. That's really all. I can't remember having the problem with the tablet.

[колбаскин]

Vu+ Player seems to work very well with OpenPLI and its streamproxy (including changing bitrates from app). Also the Duo2 is running well.

In VU+ Duo2 with Vu+ Player transcoding not work in internal player

In VU+ Solo2 transcoding not work with all players

[tilleke]

Vu+ Player seems to work very well with OpenPLI and its streamproxy (including changing bitrates from app). Also the Duo2 is running well.

In VU+ Duo2 with Vu+ Player transcoding not work in internal player

In VU+ Solo2 transcoding not work with all players

 

Listen dude,

 

Statements like that is not of any use at all. If you don't describe your set up (device, Android OS-version and so forth), how you have set up everything, WAN or LAN, what you have tried and so on, there is no way I can help you. I am not going to consider your reports unless you tell me above information and all extra information which can be useful for understanding your problem. If you feel that your English is not good enough, then use Google translate. I don't have time to loose. 

Edited by tilleke, 30 May 2014 - 08:19.

[Rob van der Does]

@Tilleke, I think the VU+Player 2.0 is a nice piece of work, there is only one little problem I have, but that's very probable due to my hardware/firmware, starting a file stream may take ages to complete, but I found out that if I standby the device and wake it, it continues. That's really all. I can't remember having the problem with the tablet.

Is that using the DUO2 or the Solo2?
In my experience there's a huge difference between the results of the two boxes, in all images.
Also: do you use the internal Android player (as I did above; I forgot to mention that) or any other player?

[Rob van der Does]

Okay SatKiekerd, then apparently some combination of factors gives problems and you're lucky Can you please enable syslog (either file or memory buffering), reboot, scan the syslog for streamproxy and post them here? Hope this gives some clue's.

What 'syslog' do you require? An RS-232 log?

[Rob van der Does]

Hmm, tried the same today: worked fine, until I changed the bitrate several times. Then the flashing 'loading stream' was there again.

[Erik Slagter]

What 'syslog' do you require? An RS-232 log?

No, just syslog. It's not installed by default, you need to install busybox-syslog and configure it, but I'm pretty sure you can find out how

The other way is to kill streamproxy and run it in the foreground using the -f flag, but that won't help if the problem is that it won't start from boot.

Edited by Erik Slagter, 30 May 2014 - 16:03.

[Erik Slagter]

Hmm, tried the same today: worked fine, until I changed the bitrate several times. Then the flashing 'loading stream' was there again.

The streamproxy does not differentiate between solo2 and duo2. It tries to set all parameters and if it can't (because the /proc entries are missing), it just goes on.

So if there is a difference in operation between solo2 and duo2, it must be driver/hardware related. Which I am not surprised about actually, because the transcoding on the solo2 is really flakey.