Frequent Buffering with 4K content

Help and Support Vero 4K / Vero 4K +
1

I am getting constant buffering with 4k content. Logs here: http://paste.osmc.tv/adazejawuj
I am running media via hanewin NFS via wired ethernet. I have attached my iperf results and I have tried using this for advancedsettings.xml:

adv

Example of a file that is stuttering here: http://paste.osmc.io/nubatojawo.coffee

Thanks guys

perf
perf942Ă—1001 16.4 KB

2

Try this instead:

	<cache>
		<memorysize>524880000</memorysize>
		<buffermode>1</buffermode>
	</cache>

(That’s just a snippit)

3 
Complete name                            : M:\XBMC\Movies\Goodfellas - 1990\Goodfellas.1990.UHD.BluRay.2160p.DTS-HD.MA.5.1.4K.HEVC
Format                                   : Matroska
Format version                           : Version 4 / Version 2
File size                                : 81.4 GiB
Duration                                 : 2 h 25 min
Overall bit rate                         : 80.2 Mb/s

Should be watchable over Wired.
An fstab mount will help you a lot I would suspect.

4

Hi,

Try removing:

<readfactor>5.0</readfactor>

From advancedsettings.xml, me & @dillthedog have found with recent testing readfactor hasn’t been working as expected.

Thanks Tom.

5

Changing to 5 did not help. Is it possible I didn’t create the XML file properly? I just right clicked “New” in winscp.

6

I’ve read that fstab helps, how exactly do I implement it?

7

No luck here as well. But thanks!

8

Post the complete contents of advancedsettings.xml, and make sure you use preformatted </>

9 
<advancedsettings>
<cache>
    <memorysize>900000000</memorysize> 
    <buffermode>1</buffermode>
    <readfactor>5.0</readfactor>
</cache>
</advancedsettings>
10

Well, you didn’t make the changes I suggested.

11

I tried every suggestion and combination of the memory size and readfactor in this thread. That is just what it is at the moment.

12

Did you reboot after making the changes?

Info about how to use NFS with fstab: Configuring fstab based NFS share mounts

13

Yes I rebooted everytime. I will look into fstab.

14

Depending on whether you’re using SMB or NFS shares, it’s either this article:

Configuring fstab based Samba share mounts

Or this one:

Configuring fstab based NFS share mounts

Those articles should get you going on the fstab front. No matter, if the problem should be resolved by adjusting advanced settings or not, fstab is always recommend as it gives you better througput and higher stability.

15

Thanks @bmillham and @Chillbo for the thread link. I see the example is for just one movies folder and one tv folder. I have several folders in my case:

I:\XBMC\Movies -public -readonly -name:Movies 192.168.2.20
I:\XBMC\TvShows -public -readonly -name:TV 192.168.2.20
J:\XBMC\Movies -public -readonly -name:Movies2 192.168.2.20
J:\XBMC\TV -public -readonly -name:TV2 192.168.2.20
K:\XBMC\Movies -public -readonly -name:Movies3 192.168.2.20
K:\XBMC\Test -public -readonly -name:Test 192.168.2.20
K:\XBMC\TV -public -readonly -name:TV3 192.168.2.20
L:\XBMC\Movies -public -readonly -name:Movies4 192.168.2.20
L:\XBMC\TV -public -readonly -name:TV4 192.168.2.20
E:\XBMC\TV -public -readonly -name:TV5 192.168.2.20
E:\XBMC\Movies -public -readonly -name:Movies5 192.168.2.20
E:\XBMC\Blair -public -readonly -name:Blair 192.168.2.20
M:\XBMC\TV -public -readonly -name:TV6 192.168.2.20
M:\XBMC\Movies -public -readonly -name:Movies6 192.168.2.20\

Do I just add multiple lines with the appropriate names?

16

Yes, each share needs a separate line and mountpoint.

17

Ok. Will this change all my file paths and need to readd media resulting in lost history for watched/unwatched?

18

Unfortunately, yes.

Edit: See next post. Sry :see_no_evil:

19

You could use path substitution to keep your watched status. What I’d suggest is just doing one share that has problem content on it for testing purposes.

20

Alright that kinda sucks but it will be for the better.