legallink 187 Posted December 7, 2019 Posted December 7, 2019 For me, Emby creates teh appearance of a new library for each Camera Upload folder. Not sure if that's intended or not, even though I only create 1 library for it. 1
Luke 40082 Posted December 8, 2019 Posted December 8, 2019 Hi, what do you mean "for each Camera Upload folder' ?
legallink 187 Posted December 9, 2019 Author Posted December 9, 2019 Screen shots attached. The first photo is the Library setup: From there, you can then see in the Metadata Manager that there are 3 "Camera Upload" libraries. If you see in my folder hierarchy, there is 1 Camera Upload parent folder, and then 3 different subfolders (auto created as 1 for each device) Which results in a home screen with 3 "Camera Upload" libraries being displayed separately. They are not displayed as 1 library. Is it expected to create a library for each device separately? I would assume if you create 1 library at the parent level, it would show all camera uploads in 1 library, as that is how the system works for all other media types.
Luke 40082 Posted December 10, 2019 Posted December 10, 2019 Are they all displaying the same content?
legallink 187 Posted December 10, 2019 Author Posted December 10, 2019 Are they all displaying the same content? Yes. Each of the 3 displayed libraries shows all 3 sub folders (aka each devices uploaded photos), which is the expected behavior except for the creation of 3 libraries.
Luke 40082 Posted December 11, 2019 Posted December 11, 2019 Can you remove the extra libraries? After that, do they get recreated again?
FlyBoyML 1 Posted February 19, 2020 Posted February 19, 2020 I have the same issue. Everytime my phone uploads new photos, it creates 2 new "libraries" and displays a BUNCH of libraries on the home page. I also get a failed library scan. Attached are some photos and my logs.Could not find a part of the path '/home/emby/root/default/Camera Uploads1'.at System.IO.Enumeration.FileSystemEnumerator`1.CreateDirectoryHandle(String path, Boolean ignoreNotFound)at System.IO.Enumeration.FileSystemEnumerator`1..ctor(String directory, EnumerationOptions options)at System.IO.Enumeration.FileSystemEnumerable`1..ctor(String directory, FindTransform transform, EnumerationOptions options)at System.IO.Enumeration.FileSystemEnumerableFactory.FileSystemInfos(String directory, String expression, EnumerationOptions options)at System.IO.DirectoryInfo.InternalEnumerateInfos(String path, String searchPattern, SearchTarget searchTarget, EnumerationOptions options)at System.IO.DirectoryInfo.EnumerateFileSystemInfos(String searchPattern, SearchOption searchOption)at Emby.Server.Implementations.IO.ManagedFileSystem.GetFileSystemEntries(String path, Boolean recursive)at MediaBrowser.Controller.Providers.DirectoryService.GetFileSystemEntries(String path)at MediaBrowser.Controller.IO.FileData.GetFilteredFileSystemEntries(IDirectoryService directoryService, String path, IFileSystem fileSystem, IServerApplicationHost appHost, ILogger logger, ItemResolveArgs args, Int32 flattenFolderDepth, Boolean resolveShortcuts)at MediaBrowser.Controller.Entities.CollectionFolder.CreateResolveArgs(IDirectoryService directoryService)at MediaBrowser.Controller.Entities.CollectionFolder.FolderIdsRequireUpdating(Boolean updateValues)at MediaBrowser.Controller.Entities.CollectionFolder.RequiresRefresh()at MediaBrowser.Providers.Manager.MetadataService`2.RefreshMetadata(BaseItem item, MetadataRefreshOptions refreshOptions, CancellationToken cancellationToken)at MediaBrowser.Controller.Entities.BaseItem.RefreshMetadata(MetadataRefreshOptions options, CancellationToken cancellationToken)at Emby.Server.Implementations.Library.LibraryManager.ValidateTopLibraryFolders(CancellationToken cancellationToken)at Emby.Server.Implementations.Library.LibraryManager.PerformLibraryValidation(IProgress`1 progress, CancellationToken cancellationToken)at Emby.Server.Implementations.Library.LibraryManager.ValidateMediaLibraryInternal(IProgress`1 progress, CancellationToken cancellationToken)at Emby.Server.Implementations.ScheduledTasks.ScheduledTaskWorker.ExecuteInternal(TaskOptions options) EmbyLogs.txt
Luke 40082 Posted February 20, 2020 Posted February 20, 2020 Are you able to remove the extras from library setup?
FlyBoyML 1 Posted February 20, 2020 Posted February 20, 2020 (edited) I can remove them libraries, but it still keeps about 2-4 of the iterations on the home screen, even though there are none under Server/Library. I can also confirm that when I remove the libraries, it does remove the folder in .../root/default/ Everytime I remove them, it will be fine until A) my phone tries to upload a new photo B ) I trigger a library scan. I just did another library scan, and the result was five new libraries, with 4 iterations each on the homescreen. Edited February 20, 2020 by FlyBoyML
Luke 40082 Posted February 20, 2020 Posted February 20, 2020 Can you try just removing all but one and then run a full scan? Thanks.
FlyBoyML 1 Posted February 20, 2020 Posted February 20, 2020 I removed all but one. The result is that it fails the library scan:Could not find a part of the path '/home/emby/root/default/Camera Uploads1'.at System.IO.Enumeration.FileSystemEnumerator`1.CreateDirectoryHandle(String path, Boolean ignoreNotFound)
FlyBoyML 1 Posted February 20, 2020 Posted February 20, 2020 Also, of note, I am running Emby Server on an ASUSTOR nas. I have set a camera upload path and checked "create a subfolder for each device", but this problem occurs as well with the default storage location and the subfolder option unchecked.
FlyBoyML 1 Posted February 20, 2020 Posted February 20, 2020 Correct. I haven't changed or removed anything other than through the "Manage Emby Server" interface.
Luke 40082 Posted February 20, 2020 Posted February 20, 2020 I guess try creating that folder it was complaining about.
FlyBoyML 1 Posted February 20, 2020 Posted February 20, 2020 Okay. So I created a folder called "Camera Uploads" but i didn't create any xml files to go in it. Emby is now running a library scan, and looks like its working. However, this was after I deleted ALL libraries for camera uploads. What is telling emby to still look for that folder?
FlyBoyML 1 Posted February 20, 2020 Posted February 20, 2020 After creating that folder, Emby now shows a library called "Camera Uploads" but says 0 folders. And when I tried to upload a new photo from my phone, Emby created two new folders called "Camera Upload1" and "Camera Upload11", and now I have three libraries.
scotthews 1 Posted February 23, 2020 Posted February 23, 2020 I can confirm this is an issue. I turned on the Camera Upload from the android app which upload 400+ photos from my device. Afterwards I have around 12 Camera Upload Libraries created. Logged in as Admin and removed them all from the server, but now have 6 Camera Uploads libraries on my Home Page that won't go away. I originally had 12 Camera Uploads folders on my Home Page. After selecting all 12 and choosing to delete them, 6 disappeared, but the other 6 seem to be stuck there. My Emby home page is now a bit of a mess!
Luke 40082 Posted February 23, 2020 Posted February 23, 2020 We're looking into it. Thanks for reporting.
FlyBoyML 1 Posted March 13, 2020 Posted March 13, 2020 Is this issue resolved? It appears that the latest Android update included this fix.
Luke 40082 Posted March 13, 2020 Posted March 13, 2020 The problem is actually on the server, but thanks for the feedback. 1
spoopers 5 Posted July 4, 2020 Posted July 4, 2020 Having the same issue here, any sign of a fix?Sent from my ONEPLUS A3003 using Tapatalk
Luke 40082 Posted July 4, 2020 Posted July 4, 2020 We're looking into it. For now I would just remove the duplicates from emby library setup.
julespotvin 2 Posted August 14, 2020 Posted August 14, 2020 Sooooooo... any update? Same issue for me.
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