I'm not having these issues but this is entirely dependent on the response time capability of your server. The Fire vs. any of the other platforms shouldn't really make a difference as the bulk of the weight here is handled by the server.
I sent you the client log for a search for "hot fuzz". Before the search updates, search on FireTv was snappy with no issues.
- When searching via FireTv results return slowly and it eventually starts throwing volley errors.
- In the server logs I'm seeing a couple of interesting errors related to the display of search results:
System.IO.IOException: System.IO.IOException: The process cannot access the file 'M:\TV\Hot in Cleveland\Season 3\Hot in Cleveland - S03E14 - Hot & Heavy WEBDL-720p.nfo' because it is being used by another process at System.IO.FileStream.ValidateFileHandle(SafeFileHandle fileHandle)
- I checked and the file is accessable and readable by the account the service is running under
Emby theater and the web client both return results pretty much instantly. I also don't see server errors when searching via these clients. From what I can tell it seems to be resizing of images for display on the FireTv. In the UI it looks like once it hits this error on the server everything stops. The image for this episode isn't visible and there are no further results displayed. Full stack of an error below.
2019-06-06 09:16:22.598 Error ProviderManager: Error in metadata saver
*** Error Report ***
Command line: C:\Users\david\AppData\Roaming\Emby-Server\system\EmbyServer.dll -noautorunwebapp
Operating system: Microsoft Windows NT 6.2.9200.0
64-Bit OS: True
64-Bit Process: True
User Interactive: True
Processor count: 4
Program data path: C:\Users\david\AppData\Roaming\Emby-Server
Application directory: C:\Users\david\AppData\Roaming\Emby-Server\system
System.IO.IOException: System.IO.IOException: The process cannot access the file 'M:\TV\Hot in Cleveland\Season 3\Hot in Cleveland - S03E14 - Hot & Heavy WEBDL-720p.nfo' because it is being used by another process.
at System.IO.FileStream.ValidateFileHandle(SafeFileHandle fileHandle)
at System.IO.FileStream.CreateFileOpenHandle(FileMode mode, FileShare share, FileOptions options)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
at Emby.Server.Implementations.IO.ManagedFileSystem.GetFileStream(String path, FileOpenMode mode, FileAccessMode access, FileShareMode share, FileOpenOptions fileOpenOptions)
at Emby.Server.Implementations.IO.ManagedFileSystem.GetFileStream(String path, FileOpenMode mode, FileAccessMode access, FileShareMode share, Boolean isAsync)
at NfoMetadata.Savers.BaseNfoSaver.SaveToFile(Stream stream, String path)
at NfoMetadata.Savers.BaseNfoSaver.Save(BaseItem item, CancellationToken cancellationToken)
at MediaBrowser.Providers.Manager.ProviderManager.SaveMetadata(BaseItem item, LibraryOptions libraryOptions, ItemUpdateType updateType, IMetadataSaver savers, CancellationToken cancellationToken)
TargetSite: Microsoft.Win32.SafeHandles.SafeFileHandle ValidateFileHandle(Microsoft.Win32.SafeHandles.SafeFileHandle)