Noticed stutter when playing a varierty of content, both TV and films so doesn’t seem related to frame rate. It seems more pronounced than the micro stutter that I experienced on the 4k+ for a time, lasting for maybe 1/2 a second
I do have whitelist set up. Same playing content from different drives, also.
Logs here: pending
I creates logs a lot faster on the V
Does that log set even contain you reproducing the issue? I wasn’t seeing any playback there and you seem to have a number of locations you play content from. Does local playback have this issue or only UPnP, Onedrive, an add-on, something else?
The support request guide outlines how to save the logs to disk so you can edit them and then how to upload after. Use that to take enough of the unimportant time period out so they are small enough to upload.
TBH I stopped looking as soon as I spotted you were low on memory as that is going to cause playback issues even though the playback itself isn’t the problem. The playback with the Vero’s default large cache settings is going to take up a chunk of memory and make the issue show up, but the issue is that something else is taking up more RAM than it should. You said it took a few days before you saw an issue. Just take a note of what memory is used on a fresh restart and then after a day or two to see what is growing. If it is Kodi and restarting it frees up the memory then you need to start looking at add-ons you’ve installed.
Just limit memory and cpu usage of each container.
In portainer you can easily do that by recreating the container and going into the runtime & ressources section and set max memory and cpu usage.
You can also limit the the whole docker setup with memory slice
Create a file to /etc/systemd/system/docker_limit.slice
Description=Slice that limits docker resources
CPUQuota=200% <-- cpu limit (each core is 100%, limit to 2 to keep the rest available to kodi)
MemoryLimit=2G <-- mem limit, keep 1.5g for kodi
Start unit: systemctl start docker_limit.slice
Restart Docker daemon: systemctl restart docker
Personnaly i would move all that stuff to a RPI or desktop machine with a stronger CPU.
The Vero CPU is not that powerful and can get easily overload with the parsing done by the *arr software.
Also yo can easily replace the *arr with flexget that can handle all that stuff.
Have a look at : [HowTo] Flexget, "the lazy couch" fully automated watching experience
Well, you said you don’t tend to have an issue until the system has been up for a number of days, correct? When it starts to have an issue and you ssh in what does CPU and RAM usage look like when it is actively playing poorly? This doesn’t occur with just certain types of files and if you reboot after the problem shows up the same file plays without issue, yes?