Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stuttering #14

Open
oxovi opened this issue Oct 14, 2018 · 11 comments
Open

Stuttering #14

oxovi opened this issue Oct 14, 2018 · 11 comments

Comments

@oxovi
Copy link

oxovi commented Oct 14, 2018

I use Open ATV on vu+ zero and assume that this is the code that is running there.

My satip client is stuttering a lot. Other clients do not experience this problem (e.g. VLC).

Does it make sense to increase buffering somehow?

@perexg
Copy link
Contributor

perexg commented Oct 16, 2018

What is your server? If you're using minisatip and latest satipclient, you can enable the TCP transport mode (add tcpdata=1 to the end of vtuner.conf). Example config:

0=desc:minisatip,ipaddr:192.168.100.237,tuner_type:DVB-S,uuid:11223344-9999-0000-b7ae-0022b7f0056e,vtuner_type:satip_client,tcpdata:1

@oxovi
Copy link
Author

oxovi commented Oct 16, 2018

I use a Kathrein EXIP 414/E. I was not able to see if it supports TCP transport mode. It has nothing in the UI to enable it.
https://www.kathrein.de/en/sat/product/20510103/
Thanks for trying to help.

@perexg
Copy link
Contributor

perexg commented Oct 16, 2018

The TCP transport mode is not in the SAT>IP standard specification. I do not know if any official software in SAT>IP servers support this extension. The UDP protocol is unreliable, so if something is not tuned properly in the network stack, there might be some packet loss. The UDP buffer size is already set to 1MB in the satipclient code. I assume that your box is connected to the gigabit network, the SAT>IP through WIFI without TCP data transfer is really sub-optimal.

You may try to tune net.core.rmem_max kernel parameter (sysctl net.core.rmem_max), if it helps.

@oxovi
Copy link
Author

oxovi commented Oct 16, 2018

Thanks for the explanation. This is very interesting and rests my case.
I will play around with net.core.rmem_max and report back.
Unfortunately I need to use WiFi (5GHz) and I have tuned that as much as possible.

@perexg
Copy link
Contributor

perexg commented Oct 16, 2018

BTW: There is also another way to improve your setup. If you have a linux server connected directly to your SAT>IP server box, you may install minisatip server and use it as proxy for your enigma2 box (so Kathrein -> gigabit network UDP -> minisatip -> wifi TCP -> enigma2). The minisatip can be used also as a SAT>IP client - --satip-servers option. https://github.com/catalinii/minisatip

@oxovi
Copy link
Author

oxovi commented Oct 16, 2018

That is actually a real option. Thanks :-). I will see if a RPI3 can do the job.

@DocSnyd3r
Copy link

Hi works for me too. Raspberry 2 about 40% CPU when I stream 2 HD channel with TCP.

@DocSnyd3r
Copy link

Well still problems changed sysctl -w net.core.rmem_max=212992 coming from 163840. Running an VU+ zero 4k image...

@estimadarocha
Copy link

@perexg you still use sat>ip client on enigma? does it still work good with vtuner_type:satip_client,tcpdata:1 and optimized kernel parameters?

@perexg
Copy link
Contributor

perexg commented Nov 11, 2020

Yes, I don't have any problems with this configuration.

@estimadarocha
Copy link

estimadarocha commented Jan 9, 2022

@perexg sorry to ask again... i am running sat>ip client on a gbue4k pushing from satipaxe and using sat>ip vtuner i am always seeing buffered on satipaxe. if i use wget pushing from same device to same stb it don't buffer! any idea?

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants