and all runs very well including timeshift.
If you’re recording/timeshifting to a NAS, think about you’re creating 3 streams with it: One coming from the TVheadend server, one writing the timeshift to the NAS and another one reading timeshift from the NAS … and that with a 100 Mbit/s Ethernet interface of the Vero 4k. That could start to saturate the available bandwidth of the Vero 4K.
In addition some OSMC settings which seem to be important (to me):
Settings → Live TV → Playback → Fallback Frequence = 50 Hz (all DVB-C channels here are in 50 Hz)
Settings → Player → Video
-Adjust Display Refresh Rate = On Start/Stop (if set to ALWAYS the screensaver will not work anymore playing music)
-Sync Playback to Display = OFF (ON would deactivate audio passthrough)
-Allow Hardware Acceleration - amcodec = ON (default)
-Accelerate MPEG2 = always (default)
-Accelerate MPEG4 = HD and up (default)
-Accelerate H264 = always (default)
To make it more sick, with this configuration and used add-on setup of TVheadend and Tvheadend HTSP Client (PVR), sometimes video stutter starts if I DEACTIVATE the hardware acceleration (which also is more logical to me) but I haven’t invested time to find out what are the circumstances for this behaviour.
Yes…, as I wrote a few comments before, the problem with TvHeadend is the timeshift and this problem is present on all my clients. The DVBViewer client has only a problem on the Vero4K so I think it depends to the Vero4K environment.
You wrote that your TvHeadend setup works as expected include timeshift but the difference between our setups is that my TvHeadend server runs on a seperate x86-64 Kubuntu system and not directly on the Vero4K.
May I ask you to change the thread title since it seems to be a specific dvbviewer plugin issue? The current title suggests a general 720p 50 Hz playback problem with the Vero 4k which was the reason I looked into this at all, thx. I keep my fingers crossed that you get some help for the DVBViewer.