4K-Movie jerks and bumbs as hell from fileserver

i have a Windows2019 File-Server (not streaming-Server, just a Fileserver).
If i open a “big” 4k-movie via the Vero 4K and play the movie it jerks as hell, very 10-15 seconds the screen turns black, sounds stops.
If i play this same move via a usb-stick direct from the TV there are no problems.
Here her codec:
MPEG-H Part2/HEVC (H.265)
Rate 23.976

network connection 1 GB

May the kind of share (NFS) be a point?
Smaller 2k-movies does not make the problems from the server.

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • reboot the OSMC device twice(!)

  • reproduce the issue

  • upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

  • publish the provided URL from the log set upload, here

Thanks for your understanding. We hope that we can help you get up and running again shortly.

OSMC skin screenshot:

after the 2x restart and starting the moveiu again, the problems where not that strong. but the moive was not played thats smooth so you can i watch nice. it twicht a lot, or jerk - no sound dropout this time. but not “viewable”.
Log is uploaded at https://paste.osmc.tv/iyasirulit

Other Question: I try to use SMB instead of NFS share. But if i look down at service, theres some strange “)” stuff and i cannot use the normal remote to change the settings. How to fix this?

The remote issue is a known issue and should be fixed shortly in the next update.

Do you have a 4k TV? Because your TV/AVR is not reporting 4k capabilities.

Your Kodi Logs where not included which is also quite strange.

Kodi Log error

Also you might want to check your network with iperf3

but how to remove the wrong data that may disturb my share-settings?

You could change the skin temporarily.

Heres the IPREF-Result:

osmc@vero:~$ iperf3 -R -c
Connecting to host, port 5201
Reverse mode, remote host is sending
[ 5] local port 38886 connected to port 5201
[ ID] Interval Transfer Bitrate
[ 5] 0.00-1.00 sec 104 MBytes 872 Mbits/sec
[ 5] 1.00-2.00 sec 111 MBytes 930 Mbits/sec
[ 5] 2.00-3.00 sec 111 MBytes 934 Mbits/sec
[ 5] 3.00-4.00 sec 111 MBytes 930 Mbits/sec
[ 5] 4.00-5.00 sec 110 MBytes 922 Mbits/sec
[ 5] 5.00-6.00 sec 111 MBytes 931 Mbits/sec
[ 5] 6.00-7.00 sec 111 MBytes 932 Mbits/sec
[ 5] 7.00-8.00 sec 111 MBytes 934 Mbits/sec
[ 5] 8.00-9.00 sec 112 MBytes 935 Mbits/sec
[ 5] 9.00-10.00 sec 111 MBytes 933 Mbits/sec

[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.00 sec 1.08 GBytes 926 Mbits/sec sender
[ 5] 0.00-10.00 sec 1.08 GBytes 925 Mbits/sec receiver

iperf Done.

i post the Ipref-result lower in this thread.

That looks good (might want also to check without -R if it is in the 9xx Mbit region).

How about the TV? Is it a 4k TV? As mentioned the TV/AVR isn’t reporting 4k capability.
Also I am still concerned that your kodi.log seems not to work.

The TV is a brand new 65er LG 4K.
The AV-Receiver is an older Model Onkyo TX-NR616.
Ifound this in the description of it:
The TX-NR616 offers full 4K upscaling (4096 × 2160) from standard video sources such as 480i/p, 720p and 1080i/p. Interlaced progressive conversion and scaling are the product of Marvell’s high quality Qdeo technology. Qdeo is a versatile video processor that uses special algorithms to remove video signal noise and artifacts such as aliasing effects. This means your Blu-ray Discs and DVDs will be played back in greater detail than ever before on a compatible widescreen – almost cinema-like.
Note: 4K video playback requires a 4K compatible TV. HDMI switching is not supported on 4K content from source devices.

First, figure out why your logs have no kodi.log file.
It is located in the /home/osmc/.kodi/temp directory.
It should have the following permissions
Owner -write, Owner - read, Group -read, Others -read
(Aka 644)

Second, figure out why no 4K resolutions are detected.
I would bypass the AVR and connect directly to the display. Reboot, then check the kodi.log file.

Third, disable any upscaling in the AVR. Let the new display handle it…it is 10 years newer.

1 Like

Well this doesn’t indicate if it actually supports 4k inputs and if so which formats.

As @Wheelz wrote suggest to connect the Vero directly to the TV and see if the problem is gone by that.
But also need to figure out where the kodi.log error comes from.

Let us know if you need more help to investigate.

strange thing for me was in 1st line, that the problem changed as i reset the vero device.