So i don't want emby jellyfin or other tools to write nfo-files all over the place or rename anything. I need to preserve the structure and names of my files and folders to some degree for archiving-and a lot of other reasons. I do this because i don't want any bug, user or coincidence to threatening me with the possibility of messing, deleting, renaming or restructuring my media-files/folders. Therefore i only mount my media-folders read-only for emby jellyfin, kodi and other tools. I don't want any tool than my file-manager and my brain to get in the way of my structure and naming-conventions. The idea about saving metadata with the mediafiles might seem appealing and easy first of all.but when you think about it its not that great at all. But in the end a migration/backup-process should be 100%, and not just 50-60%-ish.Īnd now comes the part about emby/jellyfin, that i completely dislike and reject: The structure of handling data and media. And i am fine with copying config files by hand, and running well documented pre-written SQL-queries etc etc. It's not just a single button-press and everything is magically done in 2 minutes. But from a users-perspective it should not be extremely more than: I mean, i can understand that from a programmers perspective a migration/backup-process is no simple task. When nothing besides the rootpath of my mediafiles and the paths to the config files have changed, i don't really understand nor can't i find good reasons why i should have to put my hardware, and my nerves to so much stress(io-workloads) re-indexing, re-downloading, re-editing and re-configuring the whole library when the data are already available somewhere (old machine). Manually edited, handcrafted movie-entries. This should not only include:įull cache(people,pictures,movieinfos,artistinfos) And with whole installation i mean whole. I for myself and i don't think i'm alone in this - need a proper way to backup and migrate a whole installation. And right now i don't know where to go or what to do to get this done. So, the whole migration-process took 4-5 hours by now and still isn't complete/finished and satisfying. And this is a huge bummer as i putted in A LOT OF TIME identifying the movies/videos/shows by hand while remaining their original filenames!(sometimes this is possible sometimes not) After the re-indexing scan of 1-2 hours, the files are there and users and everything else - but the manually edited, handcrafted movie-entries are ALL gone. I followed the instructions for a manual backup anyway and now i have a "partially" migrated/backed up new database. How can it be that a software like emby, so powerful and well written/supported, has no proper 100% backup/migration-process? To keep a permanent copy of metadata, we suggest enabling saving of local metadata to media folders. This will not backup library contents and metadata. I followed the instructions from was a little shocked when i read this in the documentation: So, as besides of the root-path from my mediafiles, nothing has changed and i thought: this won't be a big deal.just copying the database, correcting the rootpath for the mediafiles and boom it's done. So, i ditched Kodi for emby and never looked back.until now.I'm in a similar position as Kirk137 in his post like flort in this post to some hardware and software-changes, i'm in the process of having to migrate from a emby macOS installation to a Ubuntu-based Linux installation.Įven though my case is about macOS/Linux-migration, my problem is related with the general migration-process and metadata-management, and therefore belongs in the "general"-forum. But the overall feeling about emby jellyfin is just awesome! I mean, kodi gives me some more options and fine-control on how i want to structure my library where emby jellyfin is limiting me, and emby jellyfin has some little flaws here and there. The fact that i am here right now, writing this post about emby jellyfin is because: **i love it.**As a long time kodi-user i instantly fell in love with emby jellyfin the moment i installed it and started using it. I know i know, you devs of emby jellyfin have had discussions and thoughts about this topic enough i guess.But i want to ask you to maybe rethink one or two things about the structure of emby jellyfin.īut hold on, before you think: great, another non-programming average Joe who thinks he knows things better than we do. Let's talk about a real full migration and the separation of metadata and mediafiles.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |