Jump to content


jpl

Member Since 1 Nov 2014
Offline Last Active 19 Apr 2015 19:05
-----

Posts I've Made

In Topic: Transcoding problem

5 November 2014 - 23:16

As you've shown you have no interest in learning anything from anything other than Windows, I have assumed your preference would be the same.

 

Wrong, my friend, on two accounts: Firstly, I don't need to learn anything about Windows. Secondly, the Linux "community" attitude means I have to learn what is required on my own. Which I will. 

 

So thanks for your "kind" offer, but don't bother. If you could learn, it means I can learn it also, only 10 times better! :)

 

BTW: It wasn't me who launched the derogative comments on Linux, it was SpaceRat...not that it matters. Linux community has again opened it so warm and welcoming bosom in all matters! 


In Topic: Transcoding problem

3 November 2014 - 21:49

And now everything is working just fine, the way I want it to work. With the "Great Help of the Linux community"...give me a friggin break...


In Topic: Transcoding problem

3 November 2014 - 21:43

Sorry, but I did find the reason for inetd listening and occupying port 8002. It was in inetd.conf (don't you just like Lunix and Unix with conf files all over the place! compare that to the Windows registry which is so simple in comparison) but didn't bother to post it. Here is the offender:

 

"8002 stream tcp nowait root /usr/bin/transtreamproxy transtreamproxy"

 

Commented out with a #, reboot and one can use 8002 for the streamproxy process, or any other free port, at will.

 

Eric, if I had an IT technician, even suggesting to solve every problem by wiping everything all the time, instead of doing real troubleshooting - and solving the problem, I would fire him faster than you can say "get out of here". Reflashing/reinstalling or whatever, did you learn anything? BTW, if you even paid half an ear of your precious time, I started this post by saying that I DID just that! With a fresh image, latest build!

 

Jeez...Linux boffins...'nuff said...


In Topic: Transcoding problem

2 November 2014 - 11:55

Update: vu+ player app still reprts that it can't find support for the API, so changing video quality on the fly or in the settings doesn't work.

 

Does anybody know what the command would be to add support for the API - without updating the whole image, please?


In Topic: Transcoding problem

2 November 2014 - 11:31

I finally solved it myself.

 

For the benefit of those having problems with the transcoding, here is what I did, step-by-step:

 

1. Logged on to the box with telnet

2. Ran the command "opkg update vuplus-transcoding"

3. Ran the command "opkg install vuplus-transcoding -force-reinstall" (would maybe have worked without -force-reinstall)

4. Ran the command "/etc/init.d/streamproxy.sh stop" - shell reported that no such process was running

5. Ran the command "/etc/init.d/streamproxy.sh start" - shell reported process started

5. Ran "netstat -p tcp -a -n" and noticed that the process inetd was listening on port 8002, not streamproxy

6. Edited /etc/enigma2/streamproxy.conf and changed the listening ports to 8004 and 8005

7. Ran the command "/etc/init.d/streamproxy.sh start" again

8. Ran "netstat -p tcp -a -n" and now the process streamproxy was listening on ports 8004 and 8005

9. Changed the configuration in Vu+ player on my phone and pad to use port 8004

10. Transcoding is working again.

11. Made a full system backup.

 

Summary of problem: for some reason there seems to be a conflict in the configuration where inetd listens on port 8002. Since this process starts before streamproxy, the latter process can not start since the port is already taken.

 

See? Was it so difficult to write instructions/solution for other people to use? I don't think so...