Editing Collections is causing new folder and nfo to be created.

[briancameron 1]

If i manually edit metadata in a collection, it creates a new folder and a new collection.nfo file.

So for example.  If i edit Airplane Collection's metadata instead of editing the collection.nfo in "emby-server/metadata/collections/Airplane Collection" it create s a new folder at 'emby-server/metadata/collections/Airplane Collection-tmdb-91663' and a new collection.nfo within that folder.  It leaves all the images in the original folder, but if i edit an image the edited version appears in the new folder too.

If i delete the new collection, delete the folder in metadata, and refresh and rescan the whole library, it doesn't seem to see the original folder at all as if I try to go to the individual movies and add to a collection, it doesn't see the Airplane Collection at all.

Not sure if I have done something stupid in my settings, or if this is a bug.

I generally prefer to edit metadata manually or through Tiny Media Manager, but I am noticing that any changes made manually or in TMM to the collection nfo's are not being reflected in emby.  Even after a full library refresh, rescan, and reboot of server. It's as if it no longer sees the files, but yet is displaying all the data from them before I edit them....

If i manually refresh, or rescan any individual collection, even without changing anything it immediately creates a new folder with -tmdb-xxxxx after it with a new collection.nfo file.

I'm on 4.9.1.90

[GrimReaper 4739]

2 hours ago, briancameron said:

Not sure if I have done something stupid in my settings, or if this is a bug.

It's neither, based on discussion in another thread, that's just a new way of saving collections folders:

I'd assume you're just caught in the transition phase: any new auto-collection will automatically be saved as <collectionfoldername>-tmdbid, whereas any change to existing collections (manual edit, metadata refresh) will create additional -tmdbid folder. Over time, they should all get that suffix (based on changes/edits you make). 

[briancameron 1]

That is just a horrid choice of a change, and without any clear warning of the change, or choice to accept this new naming convention.

The ability to edit metadata in third party apps has just been ripped away, and i have to use scrapers I don't want to use through emby.  I have TMDB and the ability to save to nfo switched OFF in the collections library, and yet it is scraping tbdb and changing my nfos.  Awful.

I have multiple folders for the same film collection now, with some edits in one folder, and some in another.  Emby reading one, and not the other.  Tiny Media Manager for exmaple making changes in one folder and not the other.

Instead of a simple clear system where all collections were plainly named, we now have this mix of a system.  It's completely made a mess of my collection.  Really dissapointed.

[GrimReaper 4739]

19 minutes ago, briancameron said:

I have TMDB and the ability to save to nfo switched OFF in the collections library, and yet it is scraping tbdb and changing my nfos.

Yeah, collections management apparently still needs to be fleshed out, I've asked the Dev about NFO saving in another topic, still waiting for reply. 

And the worst offender of all: legacy/junk folders being left behind, during my tests I've created 5 of them for the same collection: each title change or ProviderID adding (where there was none) or replacing created another -tmdb-ID folder (containing respective collection.nfo with NFO saver disabled) while leaving previous ones in place. So: 1 collection in the UI - 5 folders under metadata\collections. I've stopped there as pattern was apparent. 

23 minutes ago, briancameron said:

Tiny Media Manager for exmaple making changes in one folder and not the other

I've already raised a ticket with TMM few days ago to address new naming scheme, it apparently will be, hopefully in near future. Until then, manual intervention will be required. 

[briancameron 1]

20 hours ago, GrimReaper said:

I've already raised a ticket with TMM few days ago to address new naming scheme, it apparently will be, hopefully in near future. Until then, manual intervention will be required. 

Yes. I noticed, which I’m grateful that you got there and explained the issue so well before me. 
 

In an ideal world I would just get collections out my head for a few weeks whilst TMM and Emby make changes. However with Emby scraping and saving even when switched off, I fear there may be quite a few unintentional folder creations and nfo confusions in that period even as I try to avoid doing anything. 

[GrimReaper 4739]

12 minutes ago, briancameron said:

In an ideal world I would just get collections out my head for a few weeks whilst TMM and Emby make changes. However with Emby scraping and saving even when switched off, I fear there may be quite a few unintentional folder creations and nfo confusions in that period even as I try to avoid doing anything.

There might be and unfortunately nothing you can do for now (except meticulously curating that manually on daily basis); I can only suggest what I did myself: make a backup copy of your MSIF that you'll update/re-write in proper format once TMM addresses the changes and revert/copy back afterwards.