How to move .bif/nfo/png/jpg to Metadata folder.

[Guest]

Hey everyone, hoping someone can help me accomplish this. When I set up my libraries, I had the options checked for Metadata Readers: Nfo, Metadata Savers: Nfo, Save artwork into media folders, & Save video preview thumbnails into media folders. I now want to change this behavior so that the artwork and preview thumbnails are stored in the Metadata folder, and stop generating NFOs and let the data be stored in the database (I believe this is how this behaves?). I want only the media files to be stored in their folders with all other files/data stored in the metadata folder/databse.

After unchecking the above options, I went to each library and clicked "Refresh Metadata" in hopes that Emby would relocate the files to applicable locations, but it didn't behave that way. Could someone let me know what I'm doing wrong and how to accomplish what I want.

 

Thank you.

Edited January 8, 2024 by Shomesomesho

[Abobader 3464]

Hello Shomesomesho,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[rbjtech 5284]

Any reason why ?

People usually opt to go the other way - as saving the files locally (not with the media) means they cannot be easily tracked/modified.

Unless storage is an issue (unlikely as they are tiny files in comparison) then there is really nothing to be gained by saving them local - performance as an example is not improved as they are cached anyway.

If you did want to do it - then just delete the files (leaving just the media) - and emby will recognise this during a scan and re-create them locally for you.

Edited January 8, 2024 by rbjtech

[Luke 42081]

Hi, nothing in Emby will delete your existing nfo files. You will need to do that manually if that's what you want to do.

If you refresh metadata and check the box to replace existing images, then you should start to see images getting moved.

[Guest]

1 hour ago, rbjtech said:

Any reason why ?

People usually opt to go the other way - as saving the files locally (not with the media) means they cannot be easily tracked/modified.

Unless storage is an issue (unlikely as they are tiny files in comparison) then there is really nothing to be gained by saving them local - performance as an example is not improved as they are cached anyway.

If you did want to do it - then just delete the files (leaving just the media) - and emby will recognise this during a scan and re-create them locally for you.

Hey, thanks for the help. I run Emby on Unraid. The Emby install sits on an SSD while the media files are on conventional HHDs. I'm noticing that when users are browsing the library, it has to wake up the disks. This is sort of annoying and I'd like to allow the disks to remain spun down unless someone actually starts playing a file.

I know you said that the files are cached, but that confuses me as I've noticed a large difference in loading time for browsing library items that are sitting a SSD cache drive (yet to be moved onto the main HDDs) vs items on the main HDDs. I assumed this was to do with the NFO & pictures sittings on the faster cache vs the HDDs and Emby having to wait for the HDDs to spin up before it can load the library item. Am I misunderstanding something?

Specifically in regards to the .bif files, just to confirm, there is no way to have Emby move them into the Metadata folder automatically? I would like to avoid having to create over 70 GBs of .bif files again if I can, but I understand if it's the only way. Just want confirmation.

1 hour ago, Luke said:

Hi, nothing in Emby will delete your existing nfo files. You will need to do that manually if that's what you want to do.

If you refresh metadata and check the box to replace existing images, then you should start to see images getting moved.

Luke, thanks for your help. Could you confirm my last point above about .bif files?

Thanks again to both of you.

Edited January 8, 2024 by Shomesomesho

[rbjtech 5284]

Ah ha ok - now that I know that's the reason - it's worth doing a search as this questions has been asked, and 'answered' many times, but you are in for a world of disappointment as emby was never build with proper storage 'tiering' at it's heart - thus access to the media during routine scans and other system functions is a given - and by moving items you think are needed for just 'browsing' will wake disks, leaving you head scratching ...

It needs proper analysis tbh - I've yet to find anybody be 100% successful in this area.

On a personal note - Even though I cache all my non-media to nvme (using drivepooling software) - I leave my disks spinning 24x7 as the power/cost saved in not spinning them down, is saved in not having to replace them every couple of years due to wearing them out with constant heat cycles and spin up rotations which is when all the stress is put on the motors and electronics ... 

Lastly - there is no way to 'remap' any of the said files - incl bif - as a unique folder will be used if using local, and you will have no idea what that is.

[Luke 42081]

Quote

I know you said that the files are cached, but that confuses me as I've noticed a large difference in loading time for browsing library items that are sitting a SSD cache drive (yet to be moved onto the main HDDs) vs items on the main HDDs. I assumed this was to do with the NFO & pictures sittings on the faster cache vs the HDDs and Emby having to wait for the HDDs to spin up before it can load the library item. Am I misunderstanding something?

If you have images next to your media files, then no, Emby does not keep an extra copy of those internally. This could result in the spinning up that you're referring to when they are needed.

But stay tuned:

 

[Luke 42081]

Quote

Specifically in regards to the .bif files, just to confirm, there is no way to have Emby move them into the Metadata folder automatically? I would like to avoid having to create over 70 GBs of .bif files again if I can, but I understand if it's the only way. Just want confirmation.

Correct, there is currently no function to move the existing ones.

[Guest]

1 hour ago, rbjtech said:

On a personal note - Even though I cache all my non-media to nvme (using drivepooling software) - I leave my disks spinning 24x7 as the power/cost saved in not spinning them down, is saved in not having to replace them every couple of years due to wearing them out with constant heat cycles and spin up rotations which is when all the stress is put on the motors and electronics ...

Thank you for this. You sent me on a google adventure and I think I'll just leave my drives spun up all the time.

I'd like to understand something more clearly. When the options are unchecked for "Save artwork into media folders" where is Emby storing them? I thought it was the Metadata folder. Is this wrong? And with the "Cache Images Option" feature that Luke linked is coming in 4.8.0.67, how is that better than the Metadata folder?

1 hour ago, Luke said:

Correct, there is currently no function to move the existing ones.

Ok, thank you. I think I'll wait for that 4.8.0.67 release so I don't have to recreate all those files.

[Luke 42081]

Quote

When the options are unchecked for "Save artwork into media folders" where is Emby storing them? I thought it was the Metadata folder. Is this wrong?

Hi, does the help text underneath the option answer this?

[Guest]

2 minutes ago, Luke said:

Hi, does the help text underneath the option answer this?

No, it only says where it will be placed if it is checked. I'm asking where it is stored if it is unchecked. Apologies If I'm missing something.

[Luke 42081]

21 hours ago, Shomesomesho said:

No, it only says where it will be placed if it is checked. I'm asking where it is stored if it is unchecked. Apologies If I'm missing something.

OK the answer is it goes into the server's metadata folder. Thanks.

[Guest]

Just now, Luke said:

OK the answer is it goes into the server's metadata folder. Thanks.

Thank you Luke.

So on a setup that has the Metadata & Cache on the same machine as the Media drives, what is the benefit having the Artwork saved in the Cache folder instead of the Metadata folder?

[Luke 42081]

Just now, Shomesomesho said:

Thank you Luke.

So on a setup that has the Metadata & Cache on the same machine as the Media drives, what is the benefit having the Artwork saved in the Cache folder instead of the Metadata folder?

Well that is right there in the help text, no?

[Guest]

1 minute ago, Luke said:

Well that is right there in the help text, no?

Is that to say that the benefit is making the artwork easier to manage? There would be no performance gained? Just ease of backup and management? Apologies if my questioning sounds rude. It's not intended that way. I'm only trying to understand all the benefits of the new "Cache Images Option" feature.

[Luke 42081]

On 1/9/2024 at 2:13 PM, Shomesomesho said:

Is that to say that the benefit is making the artwork easier to manage? There would be no performance gained? Just ease of backup and management? Apologies if my questioning sounds rude. It's not intended that way. I'm only trying to understand all the benefits of the new "Cache Images Option" feature.

@Shomesomeshosorry. the main benefit of having artwork in media folders is more permanent storage next to the media files, easy ability edit outside of emby, etc. We'll look at improving the help text on that.