Login at Kodi Home

**fritsch** · 2024-10-12, 15:38

Yeah - had a brief look: https://github.com/fritsch/xbmc/commits/cache3/ - as always got stuck with RAW first ;-). Only real change for IEC - use plain averaging, not weighted anymore. Reason - we assume that we are on "average right", not on weighted average.

APIPerfi · 2024-10-13, 03:57

Thanks for all of the helpful information jogal, I'll make sure to keep it in mind!

Just to clarify my thought process, I essentially want to factory reset my Shield with its current 9.1.1 firmware and only update to the 9.2.0 hotfix in the event that the reset has no positive effect.

In my head, by doing this order of operations, I'm not needlessly introducing any additional variables into the already existent problem.

As far as losing my settings and Kodi config, those aren't too much of a concern to me as settings can be remembered and Kodi config can be backed up fairly easily as you've already mentioned.

The biggest unavoidable (to my knowledge) hurdle is rebuilding my sizable library again from scratch, as the ID associated with my HDD will change with the reset.

Audiomixer

The 9.1.1+ hotfix image was released over a year ago and was known as 9.2.0 and is superseded (no longer available) by Image 2 which was released Oct 8, 2024 and is known as 9.1.2. Install with peace of mind as i have it on 3 shield 2019 pro. It improves on the first image of the hotfix in stability which was more stable than the public release of 9.1.1.
Resetting a shield with the hotfix will result in a clean slate of the hotfix image. 9.1.2 pre reset = 9.1.2 post reset. Disney+ will install.

https://www.nvidia.com/en-us/geforce/for...fix-image/

On edit: My shields connected to 1gig ethernet to synology nas and full audio capable AVRs using passthrough. I have one of the three installs of kodi 21.1 using the pm4k plex addon and non exhibit frame droppage with high bitrate material.

APIPerfi · 2024-10-15, 21:07

Finally factory reset my Shield, but it unfortunately did not help with the frame drops.

After seeing the frame drops still, I went as far as installing a custom launcher and disabling the stock launcher and TV recommendations through adb, still no luck.

I am still noticing nvphsd as a top process in adb. Does anyone know what the significance of this process is, and or the likelihood that it's causing frame drops?

Thank you all again for the continued support, I really appreciate it. At this point, I can't think of anything else to do and don't have the infrastructure or budget to adopt a local network storage solution.

Frankly I'm a little burnt out and frustrated with the problem as a whole.

**Hitcher** · 2024-10-15, 21:49

(2024-10-15, 21:07)APIPerfi Wrote: Thank you all again for the continued support, I really appreciate it. At this point, I can't think of anything else to do and don't have the infrastructure or budget to adopt a local network storage solution.

Does your router have a USB slot you could plug it into?

APIPerfi · 2024-10-15, 22:32

My router does, yes. I have tried to use this method in the past, but it too has its fair share of cumbersome issues due to the way my internet is set up and the nature of my external HDD.

I could give it another stab, but it's not on the top of my list. Regardless, thank you for the suggestion Hitcher!

Jimdr6 · 2024-10-28, 10:47

For last 3 years (kodi v20) I did have the same problem (stuttering and drop frame on my 2017 nvidia pro- Lg c1 ).
Nothing solved the problem except someone here suggested me to install kodi FOO and actually worked perfect without drops.
But after kodi v 21 I stopped using FOO. I started have stuttering again so never used again 4K movies and watched only everything in 1080.

Last week I upgraded my internet line to fiber to the home 100. (I leave in Greece).
I notice huge different on my speed and ping. Now I can play any 4K movie even with HDR without any frame drop or stuttering.
So definitely on Nvidia shield pro, 4K hdr etc has to do with the line.

izprtxqkft · 2024-10-28, 18:12

disclaimer for anyone that finds this thread in the future

'internet speed' should have no impact on Kodi's operation on any device unless files are being played from the 'internet'
kodi is geared towards 'local' file playback which then only depends on the 'local' network (LAN) speeds

reports of the issue being fixed by upgrading internet speeds may not reflect conditions which are based on LAN
and may be anecdotal due to replacement of LAN equipment when the internet was upgraded, modems for example which are dual purpose routers

(i see no logs to determine any final causes or corrections)

APIPerfi · 2024-11-15, 23:37

Hello everyone, OP here.

I just wanted to provide a quick update and some new findings for anyone in the future that may deem them helpful. Happy to report that the issue is more or less fixed (fingers crossed)!

I'm still using an external HDD directly connected via USB to my Shield TV Pro on 9.1.1 firmware. For perspective, I'll give a rundown of all the steps it took to get here, eliminating placebo along the way.

1. Factory reset Shield with fresh Kodi 21.1 install (no change)
2. Custom launcher [FLauncher] + Disabled com.google.android.tvlauncher & com.google.android.tvrecommendations (no change)
3. Replaced Shield Power Adapter (no change)
4. Replaced all relevant cables, including USB and HDMI (no change)
5. Disabled Settings/System > Audio > Send low volume noise which is enabled by default in Kodi (solution)

Since changing this one setting, I have had completely uninterrupted smooth playback, regardless of file size, avg bitrate, resolution, cropping, etc.

It's also worth mentioning that I'm still using the Arctic Zephyr Reloaded skin with all of my original library configs, and am getting flawless playback.

These steps could have a compounding effect in the grand scheme of things, but I'm betting that the "Send low volume noise" was the primary culprit as it was an instant night and day difference when I disabled it.

Hopefully my findings can help someone with a similar issue, and thank you to everyone who offered me help throughout my troubleshooting!

**fritsch** · 2024-11-16, 08:24

What do you use for "Keep Audio alive"?

APIPerfi · 2024-11-17, 03:46

(2024-11-16, 08:24)fritsch Wrote: What do you use for "Keep Audio alive"?

The default "1 minute" setting.

**fritsch**

The difference here is from a systematic pov, concerning audio engine sadly nothing. First when you do passthrough: noise is not generated and never send to a sink. This setting therefore does then nothing in passthrough case.

If you use PCM, the only difference is that heat up and keep alive is one time noise other time zeroes. Same buffers, same sizes.

So if your issue is inside passthrough there would be a programming bug to affect this as here mid play only iec pause bursts are created.

If you can, please capture another debug log with audio component enabled and low noise enabled.

APIPerfi · 2024-11-18, 09:05

If it's all the same to you fritsch, considering my setup is finally working properly I'd rather not continue to tinker and test.

In the event that the problem begins to regress again, I'll certainly consider creating this debug log.