66LUX 6 Posted October 11, 2024 Posted October 11, 2024 Hi all. In the past, I was able to look in the respective movie's folder and see image files and a .nfo file with xml data regarding the film. This still exists in my movie folders for titles that were added a long time ago. Anything recent has a .nfo file, a fanart.jpg file and a clearlogo.png file with the media file, but the strange thing is that these additional files are zero bytes in size. They contain nothing. I have the box ticked in library settings to save artwork into the media folders, but I don't know why the created files are empty. I'm able to easily see all of the posters, synopsis, etc when viewing the client. It isn't causing me any problems, but it's been handy in the past to look at the nfo file if Emby misreads the title and assigns the wrong metadata to the film. I understand there's an "identify" option, but I'd have to find the incorrectly identified item from a long list in order to use it.
Carlo 4560 Posted October 11, 2024 Posted October 11, 2024 Hi, These should be in subdirectories located in the paths you added to each library.
66LUX 6 Posted October 11, 2024 Author Posted October 11, 2024 3 hours ago, Carlo said: Hi, These should be in subdirectories located in the paths you added to each library. Do you mean these directories should have been created by Emby, or is that something I should've created myself? I've been using Emby for a lot of years, starting with Windows and now on the NAS and I've never seen subdirectories under the media folders.
66LUX 6 Posted October 12, 2024 Author Posted October 12, 2024 (edited) I thought I had the answer for a second there. Looking at the Wiki, there's mention of the Synology permissions. "System internal user" didn't have read/write permissions, so I enabled it. Copied a new media file to the shared folder, scanned the media library and there's still nothing in the folder other than the video file. Logfile shows this error: 2024-10-12 10:29:13.010 Error ProviderManager: Error saving to smb://192.168.1.19/video/Films/Beetlejuice Beetlejuice (2024)/clearlogo.png. Create Handle Failed: Films\Beetlejuice Beetlejuice (2024). NTStatus: FILE_DOES_NOT_EXIST. embyserver.txt Edited October 12, 2024 by 66LUX
Carlo 4560 Posted October 12, 2024 Posted October 12, 2024 Did you enter the SMB share directly in the library setup? If so, this likely won't work. Instead, try using Synology File Manage creating a remote share mounted to your file system. You can then set permissions on this share and then add this mount to an Emby Library.
66LUX 6 Posted October 12, 2024 Author Posted October 12, 2024 6 hours ago, Carlo said: Did you enter the SMB share directly in the library setup? If so, this likely won't work. Instead, try using Synology File Manage creating a remote share mounted to your file system. You can then set permissions on this share and then add this mount to an Emby Library. I have no idea what you're trying to tell me, but I'll see if I can figure it out. Network admin isn't my strong point.
Carlo 4560 Posted October 13, 2024 Posted October 13, 2024 Please upload a screen shot of the library configuration showing all folders paths. Thanks, Carlo
66LUX 6 Posted October 13, 2024 Author Posted October 13, 2024 20 hours ago, Carlo said: Please upload a screen shot of the library configuration showing all folders paths. Hi Carlo. Sorry for the slow response. Busy day yesterday. I very much appreciate your help. Screenshot attached. I created a new shared folder with Synology File Station and called it "Videos" (as opposed to the old "Video"). Gave Emby read/write permissions in System Internal User and Local Users. I created a new library and called it "Test Films". As you can see, this new path is displayed differently in the library view, with smb and the slashes the other way around. I don't know why, because I don't think I did anything differently (although the older libraries have been there for a long time). I put a couple of media folders in that shared folder. Ran the Scan Media Library scheduled task. Both movies now show up in Emby client with the correct information, but the media folders themselves only contain the media video file. No other files in the folder. The log still shows the FILE_DOES_NOT_EXIST error Pardon my ignorance, but it seems that the GET function is finding the correct image file. The file listed actually exists on the web. Is the server supposed to "save as" a friendly name like "clearlogo.png? Is the issue that the file is not being created, or is the issue that it isn't being moved to my media folder? TIA embyserver (1).txt
Carlo 4560 Posted October 14, 2024 Posted October 14, 2024 Check the configuration of the library you just setup. You'll see options to read/write NFO files as well as saving images to the media folder.
Carlo 4560 Posted October 14, 2024 Posted October 14, 2024 Looking at your logs it appears you are still using SMB for Test Films. 2024-10-13 09:35:59.518 Info Server: http/1.1 POST http://192.168.1.19:8096/emby/Library/VirtualFolders?collectionType=movies&refreshLibrary=true&name=Test Films&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=9515d3bc-258c-4565-b80d-66506f8538aa&X-Emby-Client-Version=4.8.8.0&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/129.0.0.0 Safari/537.36 2024-10-13 09:35:59.759 Info App: Creating folder in database Films - smb://192.168.1.19/Videos/Films 2024-10-13 09:35:59.774 Info App: Created folder in database Films 64866 - smb://192.168.1.19/Videos/Films 2024-10-13 09:35:59.789 Info Server: http/1.1 Response 204 to host1. Time: 271ms. POST http://192.168.1.19:8096/emby/Library/VirtualFolders?collectionType=movies&refreshLibrary=true&name=Test Films&X-Emby-Client=Emby Web&X-Emby-Device-Name=Chrome Windows&X-Emby-Device-Id=9515d3bc-258c-4565-b80d-66506f8538aa&X-Emby-Client-Version=4.8.8.0&X-Emby-Token=x_secret1_x&X-Emby-Language=en-gb&reqformat=json 2024-10-13 09:35:59.793 Info TaskManager: Attempting to cancel Scheduled Task Scan media library 2024-10-13 09:35:59.793 Info TaskManager: Queueing task RefreshMediaLibraryTask 2024-10-13 09:36:00.010 Error ProviderManager: Error in metadata saver *** Error Report *** Version: 4.8.8.0 Command line: /volume1/@appstore/EmbyServer/system/EmbyServer.dll -programdata /var/packages/EmbyServer/var -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -nolocalportconfig -ignore_vaapi_enabled_flag -pidfile /var/packages/EmbyServer/var/EmbyServer.pid -defaultdirectory /volume1/Public -updatepackage emby-server-synology7_{version}_x86_64.spk -noautorunwebapp Operating system: Linux version 3.10.108 (root@build8) (gcc version 8.5.0 (GCC) ) #42962 SMP Fri Mar 24 12:30:20 CST 2023 Framework: .NET 6.0.25 OS/Process: x64/x64 Runtime: volume1/@appstore/EmbyServer/system/System.Private.CoreLib.dll Processor count: 4 Data path: /var/packages/EmbyServer/var Application path: /volume1/@appstore/EmbyServer/system System.IO.IOException: System.IO.IOException: Create Handle Failed: Films\Kenny Everett's Naughty Bits (1989). NTStatus: FILE_DOES_NOT_EXIST at EzSmb.Transports.Shares.Handlers.Bases.HandlerBase..ctor(SmbType smbType, ISMBFileStore store, String path, HandleType handleType, NodeType nodeType, HandleArgs args) at EzSmb.Transports.Shares.Smb2Share.GetHandler(String path, HandleType handleType, NodeType nodeType, HandleArgs args) at EzSmb.Transports.Shares.Bases.ShareBase.CreateFolder(Node node, String folderName) at EzSmb.Node.CreateFolder(String folderName, String relatedPath) at Emby.Server.Implementations.IO.SmbFileSystem.CreateDirectory(String path) at NfoMetadata.Savers.BaseNfoSaver.SaveToFile(Stream stream, String path, LibraryOptions libraryOptions, CancellationToken cancellationToken) at NfoMetadata.Savers.BaseNfoSaver.Save(BaseItem item, LibraryOptions libraryOptions, CancellationToken cancellationToken) at Emby.Providers.Manager.ProviderManager.SaveMetadata(BaseItem item, LibraryOptions libraryOptions, ItemUpdateType updateType, IMetadataSaver[] savers, CancellationToken cancellationToken) Source: Emby.Server.Implementations TargetSite: Void .ctor(EzSmb.Params.Enums.SmbType, SMBLibrary.Client.ISMBFileStore, System.String, EzSmb.Transports.Shares.Handlers.Enums.HandleType, EzSmb.NodeType, EzSmb.Transports.Shares.Handlers.HandleArgs)
Happy2Play 9780 Posted October 14, 2024 Posted October 14, 2024 (edited) Isn't this just Emby choking on the smb paths for metadata and images? 2024-10-13 09:04:53.754 Info MediaProbeManager: ProcessRun 'ffprobe' Execute: /var/packages/EmbyServer/target/bin/ffprobe -i "http://127.0.0.1:8096/Items/File?Id=smb%3A%2F%2F192.168.1.19%2Fvideo%2FFilms%2FThe+Wolverine+(2013)%2FThe+Wolverine+(2013).mkv" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data 2024-10-13 09:04:56.730 Error ProviderManager: Error in metadata saver *** Error Report *** Version: 4.8.8.0 Command line: /volume1/@appstore/EmbyServer/system/EmbyServer.dll -programdata /var/packages/EmbyServer/var -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -nolocalportconfig -ignore_vaapi_enabled_flag -pidfile /var/packages/EmbyServer/var/EmbyServer.pid -defaultdirectory /volume1/Public -updatepackage emby-server-synology7_{version}_x86_64.spk -noautorunwebapp Operating system: Linux version 3.10.108 (root@build8) (gcc version 8.5.0 (GCC) ) #42962 SMP Fri Mar 24 12:30:20 CST 2023 Framework: .NET 6.0.25 OS/Process: x64/x64 Runtime: volume1/@appstore/EmbyServer/system/System.Private.CoreLib.dll Processor count: 4 Data path: /var/packages/EmbyServer/var Application path: /volume1/@appstore/EmbyServer/system System.IO.IOException: System.IO.IOException: Create Handle Failed: Films\The Wolverine (2013). NTStatus: FILE_DOES_NOT_EXIST at EzSmb.Transports.Shares.Handlers.Bases.HandlerBase..ctor(SmbType smbType, ISMBFileStore store, String path, HandleType handleType, NodeType nodeType, HandleArgs args) at EzSmb.Transports.Shares.Smb2Share.GetHandler(String path, HandleType handleType, NodeType nodeType, HandleArgs args) at EzSmb.Transports.Shares.Bases.ShareBase.CreateFolder(Node node, String folderName) at EzSmb.Node.CreateFolder(String folderName, String relatedPath) at Emby.Server.Implementations.IO.SmbFileSystem.CreateDirectory(String path) at NfoMetadata.Savers.BaseNfoSaver.SaveToFile(Stream stream, String path, LibraryOptions libraryOptions, CancellationToken cancellationToken) at NfoMetadata.Savers.BaseNfoSaver.Save(BaseItem item, LibraryOptions libraryOptions, CancellationToken cancellationToken) at Emby.Providers.Manager.ProviderManager.SaveMetadata(BaseItem item, LibraryOptions libraryOptions, ItemUpdateType updateType, IMetadataSaver[] savers, CancellationToken cancellationToken) Source: Emby.Server.Implementations TargetSite: Void .ctor(EzSmb.Params.Enums.SmbType, SMBLibrary.Client.ISMBFileStore, System.String, EzSmb.Transports.Shares.Handlers.Enums.HandleType, EzSmb.NodeType, EzSmb.Transports.Shares.Handlers.HandleArgs) As all the other libraries are not SMB paths. Devs recommend mounting to local path. Edited October 14, 2024 by Happy2Play 1
66LUX 6 Posted October 14, 2024 Author Posted October 14, 2024 6 hours ago, Carlo said: Check the configuration of the library you just setup. You'll see options to read/write NFO files as well as saving images to the media folder. I have the save to media folders option ticked.
66LUX 6 Posted October 14, 2024 Author Posted October 14, 2024 6 hours ago, Happy2Play said: Isn't this just Emby choking on the smb paths for metadata and images? 2024-10-13 09:04:53.754 Info MediaProbeManager: ProcessRun 'ffprobe' Execute: /var/packages/EmbyServer/target/bin/ffprobe -i "http://127.0.0.1:8096/Items/File?Id=smb%3A%2F%2F192.168.1.19%2Fvideo%2FFilms%2FThe+Wolverine+(2013)%2FThe+Wolverine+(2013).mkv" -threads 0 -v info -print_format json -show_streams -show_chapters -show_format -show_data 2024-10-13 09:04:56.730 Error ProviderManager: Error in metadata saver *** Error Report *** Version: 4.8.8.0 Command line: /volume1/@appstore/EmbyServer/system/EmbyServer.dll -programdata /var/packages/EmbyServer/var -ffdetect /var/packages/EmbyServer/target/bin/ffdetect -ffmpeg /var/packages/EmbyServer/target/bin/ffmpeg -ffprobe /var/packages/EmbyServer/target/bin/ffprobe -nolocalportconfig -ignore_vaapi_enabled_flag -pidfile /var/packages/EmbyServer/var/EmbyServer.pid -defaultdirectory /volume1/Public -updatepackage emby-server-synology7_{version}_x86_64.spk -noautorunwebapp Operating system: Linux version 3.10.108 (root@build8) (gcc version 8.5.0 (GCC) ) #42962 SMP Fri Mar 24 12:30:20 CST 2023 Framework: .NET 6.0.25 OS/Process: x64/x64 Runtime: volume1/@appstore/EmbyServer/system/System.Private.CoreLib.dll Processor count: 4 Data path: /var/packages/EmbyServer/var Application path: /volume1/@appstore/EmbyServer/system System.IO.IOException: System.IO.IOException: Create Handle Failed: Films\The Wolverine (2013). NTStatus: FILE_DOES_NOT_EXIST at EzSmb.Transports.Shares.Handlers.Bases.HandlerBase..ctor(SmbType smbType, ISMBFileStore store, String path, HandleType handleType, NodeType nodeType, HandleArgs args) at EzSmb.Transports.Shares.Smb2Share.GetHandler(String path, HandleType handleType, NodeType nodeType, HandleArgs args) at EzSmb.Transports.Shares.Bases.ShareBase.CreateFolder(Node node, String folderName) at EzSmb.Node.CreateFolder(String folderName, String relatedPath) at Emby.Server.Implementations.IO.SmbFileSystem.CreateDirectory(String path) at NfoMetadata.Savers.BaseNfoSaver.SaveToFile(Stream stream, String path, LibraryOptions libraryOptions, CancellationToken cancellationToken) at NfoMetadata.Savers.BaseNfoSaver.Save(BaseItem item, LibraryOptions libraryOptions, CancellationToken cancellationToken) at Emby.Providers.Manager.ProviderManager.SaveMetadata(BaseItem item, LibraryOptions libraryOptions, ItemUpdateType updateType, IMetadataSaver[] savers, CancellationToken cancellationToken) Source: Emby.Server.Implementations TargetSite: Void .ctor(EzSmb.Params.Enums.SmbType, SMBLibrary.Client.ISMBFileStore, System.String, EzSmb.Transports.Shares.Handlers.Enums.HandleType, EzSmb.NodeType, EzSmb.Transports.Shares.Handlers.HandleArgs) As all the other libraries are not SMB paths. Devs recommend mounting to local path. Sorry, I don't know what you mean by "local path". Do you mean "/volume1/Videos/Films" instead of "smb://192.168.1.19/Videos/Films"? I've just changed it to "/volume1/Videos/Films" and running a scan. I'll update once done. Thanks.
seanbuff 1315 Posted October 14, 2024 Posted October 14, 2024 9 minutes ago, 66LUX said: Sorry, I don't know what you mean by "local path". Do you mean "/volume1/Videos/Films" instead of "smb://192.168.1.19/Videos/Films"? Correct, that's what is meant. Let us know how it goes.
66LUX 6 Posted October 15, 2024 Author Posted October 15, 2024 So I ran the media scan after changing the naming convention. The .nfo files are now being created and contain data, so that's a win. Strange thing is that I'd swear the SMB format was a requirement to make it all work in the past, but maybe I'm thinking of something else. Anyway, next thing was that the artwork wasn't saved into the same folder, even though I have that option checked. Once I viewed the individual film on the client side, it populated the images into the corresponding folder. Awesome result. Thank you all very much for your help with this. I'll edit the folder paths on my other media folders correctly now.
Happy2Play 9780 Posted October 15, 2024 Posted October 15, 2024 13 minutes ago, 66LUX said: Anyway, next thing was that the artwork wasn't saved into the same folder, even though I have that option checked. Once I viewed the individual film on the client side, it populated the images into the corresponding folder. Yes the "download in advance option will apply to media image otherwise the will be gotten on demand via navigation. enable show advances settings per library config. 1
66LUX 6 Posted October 16, 2024 Author Posted October 16, 2024 It all appears to be working as it should. I don't know what happened. It seems to have only started when I moved the drives to a new NAS. All good now. Thanks everyone for your help. 1 2
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now