693 replies to this topic

[macnuts]

First of all, many, many thanks for the transcoding rework.

 

I had the same problem as in post 631 above. Vu+Player 2.0, android device with 4.4.2, internal player. I've changed it to Dice Player (free at Google Play) and now transcoding plays OK. Hope it may help somebody.

 

BTW, at the same time I can use internal player on my another device (Samsung Galaxy Tab 3, android 4.3). It looks like the problem is outside OpenPLi then.

 

Regards.

Edited by macnuts, 9 June 2014 - 20:00.

[Erik Slagter]

This is exactly what I experience as well. Using the internal player works on some devices and doesn't on others. The device it doesn't work on is a CM11 device, so it's not exactly "factory default" The device it does work on is a CM10 device (also, not factory). I guess either Google or CM has broken something on the way. So if it doesn't work, the first step is to try an external player. I use vplayer which works great on all my devices.

[tilleke]

I can confirm what @macnuts and Erik said.

 

The Internal Player for transcoding in Vu+ Player has some problems running on some devices, especially Google-devices (Nexus-range) but mainly with KitKat (4.2.2). However, the problems is not appearing on all Google-devices - for some it works, on others it does not   . This is very much due to the implementation of the manufacturer of your Android-device and the code they are using for decoding. This may vary from device to device despite using the native Android video-object. However, as Erik suggested, you can use an external player which normally implements their own decoding based upon FFMPEG and thus bypasses the problem. Using an external player, you can still benefit from setting parameters within the app such as bitrate (in advanced settings in the app). As a sidenote, on my Nexus7, I had similar problems but resolved them with Erik's streamproxy while I continue having problems using the original transtreamproxy.

 

 

[pablocool]

Hi

 

I have a question. Why streamproxy ignores /etc/enigma2/streamproxy.conf ?

 

By default in conf file is

bitrate 500

resolution 480p

 

When I run VLC I see that resolution is 416x224. It is very low. I updated conf file to

bitrate 1500

resolution 720p

 

for a test. Then I performed

/etc/init.d/streamproxy stop

/etc/init.d/streamproxy start

 

But resolution is still 416x224 with poor quality. Even STB reboot is not helping. Running PS command I can see that for example oscam uses conf file

 

 

/usr/bin/oscam --config-dir /etc/tuxbox/config/oscam --daemon --pidfile /tmp/oscam.pid --restart 2 --utf8

 

streamproxy unfortunately not:

 

/usr/bin/streamproxy

 

How can I fix that? BR

[Erik Slagter]

That is because the solo2 (which you apparently use) only supports this resolution. The solo2 can only set the bitrate, no other setting. Also the configuration file is hardcoded into the source, there is no need to specify it.

[malakudi]

When we can expect for ET10000 to support transcoding?

[littlesat]

http://sourceforge.n...d112c973f632d7/

[SpaceRat]

I only had a quick look at that commit, but it seems to be yet another step back:

While Erik's proxy was capable of handling IPv6 and IPv4 (and E2s built in streaming was not), IPv6 support has now been entirely removed (unless the E2 socket class has been updated through a different commit).

So no streaming for customers of
- Unitymedia/KBW (UPC Germany)
- Glasfaser Deutschland
- M-Net
- ...

[littlesat]

Are they on ip6 only? And please note that Aachen and Koeln are not build on the same date...

But I do not see anything in that patch that removes ipv6?

Edited by littlesat, 15 June 2014 - 11:16.

[mirakels]

I only had a quick look at that commit, but it seems to be yet another step back:

While Erik's proxy was capable of handling IPv6 and IPv4 (and E2s built in streaming was not), IPv6 support has now been entirely removed (unless the E2 socket class has been updated through a different commit).

So no streaming for customers of
- Unitymedia/KBW (UPC Germany)
- Glasfaser Deutschland
- M-Net
- ...

Erik's code is still there so there shoudl be no issues.

This commit was additional for the xtrend encoder.

 

So it is a step forward but there might be more steps.

[SpaceRat]

Are they on ip6 only?

They are on DS-lite (Dual Stack lite = Full IPv6 but IPv4 Carrier-Grade-NAT only)

And please note that Aachen and Koeln are not build on the same date...
But I do not see anything in that patch that removes ipv6?

It comes through the back:

By using existing E2 socket code - which is outdated IPv4-only stuff - the limitation "IPv4 only" automatically applies to anything using it.
Erik's streamproxy used all new code, which was dual stack capable.

[WanWizard]

There is no excuse these days anymore to not have full IPv6 support. Especially if you have a product with a global audience.

 

So I'm sure this will be addressed.

[littlesat]

At least spacerat thanks for reporting...

[pablocool]

@Eric yes I ak using solo2. Is it hardware issue that resolution have to be hardcoded in program code? I am not sure but I recall that earlier plugin transcoding was capable of res change.

[Robinson]

Such low resolution may be OK for mobile devices but not for notebooks.

[Trial]

Hi,

Solo2 was never able to change resolution and bitrate max was 1MBit.

 

ciao

[pablocool]

Such low resolution may be OK for mobile devices but not for notebooks.

Exactly this is the case.

[Erik Slagter]

For the people complaining about the resolution on the solo2, please tell me where streamproxy should program the resolution:

root@solo:/proc/stb/encoder/0# ls
audio_pid          demux              framerate_choices  pmt_pid
bitrate            framerate          pcr_pid            video_pid

compared to the duo2:

root@duo:/proc/stb/encoder/0# ls
aspectratio             display_format          gop_framep_choices      profile
aspectratio_choices     display_format_choices  height                  profile_choices
audio_codec             framerate               interlaced              refreshrate
audio_codec_choices     framerate_choices       level                   video_codec
audio_pid               gop_frameb              level_choices           video_codec_choices
bitrate                 gop_frameb_choices      pcr_pid                 video_pid
demux                   gop_framep              pmt_pid                 width 

[pablocool]

For the people complaining about the resolution on the solo2, please tell me where streamproxy should program the resolution:

root@solo:/proc/stb/encoder/0# ls
audio_pid          demux              framerate_choices  pmt_pid
bitrate            framerate          pcr_pid            video_pid

compared to the duo2:

root@duo:/proc/stb/encoder/0# ls
aspectratio             display_format          gop_framep_choices      profile
aspectratio_choices     display_format_choices  height                  profile_choices
audio_codec             framerate               interlaced              refreshrate
audio_codec_choices     framerate_choices       level                   video_codec
audio_pid               gop_frameb              level_choices           video_codec_choices
bitrate                 gop_frameb_choices      pcr_pid                 video_pid
demux                   gop_framep              pmt_pid                 width 

This ends discussion:) So I guess I need duo2. Or maybe there is comparable ET STB supporting steamproxy and res change?

[WanWizard]

Not at the moment. There is transcoding support coming up for the ET 10K.