693 replies to this topic

[Erik Slagter]

So thats all i know about this. I hope it gets soon fixed anyway ... Thank you

Please read some of the other pages of this topic. Sometimes the transition to our new package fails and you need to clean some old things up, which iirc, I have described earlier.

[qnopli]

So thats all i know about this. I hope it gets soon fixed anyway ... Thank you

Please read some of the other pages of this topic. Sometimes the transition to our new package fails and you need to clean some old things up, which iirc, I have described earlier.

I already did the mentioned methods but it didn't helped yet. 

[Erik Slagter]

I can't find it atm, maybe it's in another topic.

 

Follow these steps to complete the transition or re-flash (if that's easier) with an image from tomorrow onwards!

 

Ignore any error, just proceed.

 

It's safest to copy and past these lines:

 

opkg remove enigma2-transtreamproxy-util

opkg remove enigma2-plugin-systemplugins-transcodingsetup

opkg remove vuplus-livestreamproxy

opkg remove vuplus-filestreamproxy

opkg remove vuplus-transcoding

opkg remove streamproxy

rm /etc/init.d/vuplus-transcoding.sh /etc/init.d/transcoding.sh /etc/enigma2/streamproxy.conf

 

Also check the file /etc/inetd.conf, if there are lines containing "livestreamproxy" or "filestreamproxy" remove them.

Then type

killall -HUP inetd

(or reboot).

 

Then type:

 

opkg update

opkg install streamproxy

 

Afterwards you should see this when you do netstat -lptn:

 

root@duo:~# netstat -lptn Active Internet connections (only servers) Proto Recv-Q Send-Q Local

Address           Foreign Address         State       PID/Program name    tcp        0      0

0.0.0.0:16000           0.0.0.0:*               LISTEN      423/CCcam tcp        0      0

0.0.0.0:12000           0.0.0.0:*               LISTEN      423/CCcam tcp        0      0

0.0.0.0:8001            0.0.0.0:*               LISTEN      433/enigma2 tcp        0      0

0.0.0.0:16001           0.0.0.0:*               LISTEN      423/CCcam tcp        0      0

0.0.0.0:21              0.0.0.0:*               LISTEN      388/inetd tcp        0      0

0.0.0.0:22              0.0.0.0:*               LISTEN      364/dropbear tcp        0      0

0.0.0.0:23              0.0.0.0:*               LISTEN      388/inetd tcp        0      0

:::8002                 :::*                    LISTEN      614/streamproxy tcp        0      0

:::8003                 :::*                    LISTEN      614/streamproxy tcp        0      0

:::80                   :::*                    LISTEN      433/enigma2 tcp        0      0

:::22                   :::*                    LISTEN      364/dropbear

Edited by Erik Slagter, 17 April 2014 - 21:25.

[qnopli]

OK - it's working now. I forgot to remove the 8002 port line from inetd.conf.

 

(but quality of stream now really sux)

[Erik Slagter]

This has been mentioned as well.

 

Edit the file /etc/enigma2/streamproxy.conf and change the bitrate (kbps). 1000 seems to be a reasonable default, you can also use -1 for max quality.

[delavega]

working now after updating but for how long?

[Erik Slagter]

I guess one day, better save the ipk so you can downgrade!

[delavega]

lol k

[pli1928]

Wow, it is working again.

 

Does anybody know why recorded files above the 2GB are not transcoded and streamable?

I got the error message:

 

streamproxy: exception: MpegTS::MpegTS: cannot open file

streamproxy: system error: Value too large for defined data type

[Erik Slagter]

I do not know but I will find out...

 

Maybe the file needs to be opened as O_LARGEFILE. I already use lseek64 so that's not the problem.

 

I'll be back.

[Erik Slagter]

Yeah fixed now (I believe), but in another way (autotools). Tomorrow new package.

[Erik Slagter]

Additional to the comment I made about the solo2's bitrate: it does seem the solo2 actually can go above 500 kbps, but 50% of the sessions will fail then (audio only). If you're okay with that, you actually can set the bitrate to above 500 kbps.

[Robinson]

Additional to the comment I made about the solo2's bitrate: it does seem the solo2 actually can go above 500 kbps, but 50% of the sessions will fail then (audio only). If you're okay with that, you actually can set the bitrate to above 500 kbps.

Is that unfixable? Driver-related?

[Erik Slagter]

Additional to the comment I made about the solo2's bitrate: it does seem the solo2 actually can go above 500 kbps, but 50% of the sessions will fail then (audio only). If you're okay with that, you actually can set the bitrate to above 500 kbps.

Is that unfixable? Driver-related?

It could be fixed by VU+

[pablocool]

Hi I'd like to ask how turn off streamproxy not uninstalling it. Most of the time I'd like it to be turned off how I did with transcoding plugin from menu. I had situations that unknown person from china connected my STB via internet and run transcoding. While I had turned on transmission plugin it caused higl load and STB freeze:

 

http://openpli.org/f...eezing +openpli

[Erik Slagter]

If you experience this, then you have a completely different problem.

Edited by Erik Slagter, 19 April 2014 - 18:28.

[SpaceRat]

If you experience this, then you have completely different problem.

Really?

[Erik Slagter]

So I assume you agree?

[SpaceRat]

So I assume you agree?

Not even close.

I love it when the whole world accesses my box.

Honestly:
It really amuses me that pablocool doesn't actually seem to have the slightest problem with the fact that the whole world can access his box, as long as it doesn't freeze ...

[Erik Slagter]

It's more interesting that this user really isn't the only one.