Not yet I’m afraid.
Do you know if it worked on 3.14 OK?
Sam
Can you double check that?
Because we have 1 by default, which should cover network filesystems (see https://kodi.wiki/view/Advancedsettings.xml).
So the behaviour for network filesystems will be unchanged.
Edit: if you are playing from local filesystems only, the change you made will absolutely make no difference.
Sam
Looking in to this, you might’ve just improved playback by reducing the default buffering size (to effectively 0). That obviously won’t be effective across network boundaries.
You could try something more sensible, such as:
<cache>
<buffermode>1</buffermode>
<memorysize>201326592</memorysize>
<readfactor>5.0</readfactor>
</cache>
We’re working on improving these values internally.
Sam
As i understand by default there is no advanced settings. I created one for photosettings. And now this is added.
buffermode
Choose what to buffer:
0) Buffer all internet filesystems (like "2" but additionally also ftp, webdav, etc.) (default)
1) Buffer all filesystems (including local)
2) Only buffer true internet filesystems (streams) (http, https, etc.)
3) No buffer
4) Buffer all network filesystems (incl. smb, nfs, etc.) -->
So 1 is default set somewhere else i guess. I’ll adjust It.
Edit: @sam_nazarko
https://paste.osmc.tv/obumilesun (No logging enabled).
- Changed 4 into 1, buffering a lot.
- Added the other proposed setting, buffering a lot.
- Changed 1 into 4, buffering gone.
- Removed other setting, just buffermode only 4, no buffering.
From my perspective there seems to be a difference between 1 and 4. Without 4 it plays with buffering and with 4 it plays smootly. But I’m not sure why, cause 1 should do the same, unless…
My config is synology 4+II nas with 1 gb network adapter, attached to non managed switch, gb connections and the vero is Wired only on the same switch. Having autofs enabled and mount via /mnt as all are nfs mounts.
Willing to test more, or add/change settings. I know you are busy working internally to improve. Just mentioned it, no problem for me if the jelly fish buffer, as the rest works very nice.
@sam_nazarko & co., I’ve still got a problem with a Kodi-level NFS video source dropping its connection. Typically I can browse into it, and start something playing, but then playback stops spontaneously, and then (for a while) I can’t even browse into the folder.
The same NFS export mounted via autofs doesn’t have that issue, so I don’t think it’s a server or network problem.
There is always a system defined advancedsettings
Ah, i didn’t know, i spoke about the .kodi/userdata version of advancedsettings.xml 
From your link to advancedsettings i clicked on cache settings and it gave this explanation.
As i read 1 is internet and local, but seems to exclude nfs etc, as added in 4. And that is what most is been used to connect. But again, i’m just a user in kodi, no experience then using it.
https://kodi.wiki/view/HOW-TO:Modify_the_video_cache
Choose what to buffer
This setting will force Kodi to use a cache for all video files, including local network, internet, and even the local hard drive. Default value is 0 and will only cache videos that use internet file paths/sources.
| 0 | Buffer all internet filesystems (like “2” but additionally also ftp, webdav, etc.) (default) |
|---|---|
| 1 | Buffer all filesystems, both internet and local |
| 2 | Only buffer true internet filesystems (streams) (http, etc.) |
| 3 | No buffer |
| 4 | All network filesystems (incl. smb, nfs, etc.) |
No worries, I don’t play those as much.
I got really no idea if it ran well with 3.14, most what I use has Dolby or DTS, but maybe other have videos with aac that could do a test.
I just know it plays well on my Shield, that is always the first thing I try when something doesn’t work.
It seems confusing, but 1 should be a superset of 4. I mean if it was otherwise then a bitmask would be used.
1 Like
It would be good to know if those files play under 3.14.
Meanwhile, I can just play any file with an AAC track and expect an issue?
Any mkv I could find with an AAC track gives this result.
Not to add, but to explain my view of buffering: it’s like the movie is moving forward, but is shows with hicks, skipping frameS, just to keep on going, it Just couldn’t play fluently. There are no circles or whatsoever.
Maybe it’s called differently🤓 but for now i’m happy with the results of the setting in case of jelly fish. For the rest I can’t identify other advances yet.
I checked a few more today, it is exactly every 26 seconds.
The only mkv with an AAC track that didn’t have the issue is an 480p one.
And also all 5.1 AAC tracks don’t have the issues.
Just to clear the understanding of this and the related discussion. Stock Kodi does not have an advancedsettings.xml file unless a user creates one. OSMC on both platforms (they are not the same) are configured with one in the system folder. You can actually see it in the logs below the entry…
Contents of special://xbmc/system/advancedsettings.xml
If you put one in your userdata folder that will load after, and on top of the one in the system folder and any tags in the userdata file that are the same as what is in the system folder file, those setting take precedence. So in this case your Vero system advancedsettings.xml contains…
<cache>
<buffermode>1</buffermode>
<memorysize>524880000</memorysize>
<readfactor>5.0</readfactor>
</cache>
So when you add in your userdata/advancedsettings.xml file…
<cache>
<buffermode>4</buffermode>
</cache>
The settings your actually using become…
<cache>
<buffermode>4</buffermode>
<memorysize>524880000</memorysize>
<readfactor>5.0</readfactor>
</cache>
I mention all this as it is important for finding optimal settings to realize exactly what settings your actually using.
As for the confusion of why you are getting different results between buffermode 1 and 4 that is because you are using a system mount. Kodi does not know that mount is coming from your network so it uses local media cache settings. By changing to buffermode 4 your mount no longer uses the cache settings defined above.
Thank you for your explanation, so due to system mount and that 4 “disables” the default cache settings, still the behavior seems to be better for that jelly fish 300 file. It is indeed confusing why without cache it have a better effect in my situation, you might think that cache is improving for performance.
My guess is that the cache is only beneficial if it is needed, otherwise it is probably needlessly adding overhead. There is probably not a simple answer to be had here as peoples setups vary wildly so different situations, different optimal settings. The question for us is if we found the optimal default settings to cover the most people, not so much a matter of are the default settings tweaked optimal for just a single situation. When these larger rips became common there were issues that people were having that the current settings seemed to overcome on the whole, but there may be some improvement to be had still… after a ton of tweaking and testing.
1 Like
Coming back to the missing channels in the 5 GHz band:
I set the country code in the firmware configuration file: /lib/firmware/config_43455c0.txt but this did not solve the issue (Vero4K does not see e.g. channel 112)
Is it a driver issue then?
I will look in to this today.
Just to confirm: configuring via CRDA fixes everything?
Sam
No, I have not found anything that solves the issue, neither configuring CRDA, “iw reg set” XX nor setting the country code in the firmware configuration file.
Thank you for locking into this.
HEADS UP for all 3D MVC users: there’s initial 3D subtitle depth support coming to a Vero 4k/4k+ near you!
This initial implementation supports only mkv files where the “3d-plane” tag is set in subtitle tracks. You can use e.g. mediainfo to check it out:
Text
ID : 3
ID in the original source medium : 4609 (0x1201)
Format : PGS
Codec ID : S_HDMV/PGS
Codec ID/Info : Picture based subtitle format used on BDs/HD-DVDs
Duration : 1h 12mn
Bit rate : 37.8 Kbps
Count of elements : 432
Stream size : 5.2 MiB (0%)
Language : English
Default : Yes
Forced : No
3d-plane : 21
Original source medium : Blu-ray
In this example the 3d-plane is 21. If there’s no such tag then a default “3d-plane” 0 will be used.
So what’s a “3d-plane”? A 3d-plane defines the set of depth values to be used for a specific subtitle track. Each subtitle track might have its own plane. The depth values are stored in the MVC video(!) stream, and these values are stored per frame. So the depth of a subtitle might change between subsequent frames.
ISOs are currently not supported, they will use (fall back to) plane 0. I’m still investigating how to get the correct plane values for ISOs.
Have fun 
!
2 Likes