Is it possible to scan a library without adding any artwork

[Pog22 52]

Hear me out. I have my Emby running in docker on a dedi server with 160TB of cloud media mounted as read only. I'd like to use the plugins that give TV series themes but they will not work on this instance of Emby. It's not possible to change the mount to write as I'm using Plexdrive which has been flawless for years and doesn't support write.

 

My plan is to run a second Emby server using a writeable mount just for the purpose of these plugins but I'd like to minimise the scan time by customising it and not adding any artwork to speed up the scan. Any tips, ideas, input appreciated!

Edited February 2, 2021 by Pog22

[Carlo 4561]

No way to do this I can think of from inside Emby with a read only drive.

HOWEVER, you could shut down PlexDrive, fireup rclone (using same drive letter/paths) and run the theme plugins manually once every so often.

Then switch back to PlexDrive after this is complete.

[Pog22 52]

4 hours ago, cayars said:

No way to do this I can think of from inside Emby with a read only drive.

HOWEVER, you could shut down PlexDrive, fireup rclone (using same drive letter/paths) and run the theme plugins manually once every so often.

Then switch back to PlexDrive after this is complete.

 

Thanks for your input!

Yeah but I already have a read and write rclone mount at a different path that I use for sonarr and radarr. I was going to use this different path to another Emby instance and let it scan the library. With 160TB this could take a week with artwork, hence me trying to minimise to just metadata.

Edited February 3, 2021 by Pog22

[rbjtech 5284]

I'm not 100% of your intention here - but with any library you can simply turn off elements (or all..) of the metadata providers and/or image providers and no metadata will be gathered for that item.  If you previously wrote the metadata/images to the shares, then that is all that will be used - it will not attempt to update/write to that share.

I'm not sure if that helps you ?

Goto Library > Advanced > Then remove everything except NFO reader - ie only read what is there, do not add/update.

 

Edited February 3, 2021 by rbjtech

[Pog22 52]

1 hour ago, rbjtech said:

I'm not 100% of your intention here - but with any library you can simply turn off elements (or all..) of the metadata providers and/or image providers and no metadata will be gathered for that item.  If you previously wrote the metadata/images to the shares, then that is all that will be used - it will not attempt to update/write to that share.

I'm not sure if that helps you ?

Goto Library > Advanced > Then remove everything except NFO reader - ie only read what is there, do not add/update.

 

Hi, thanks, that's exactly what I was looking for, I wasn't aware of having that much control. An nfo will need to be created during a scan as they're not next to the media because Emby cannot write there.

 

My next question, can I use my Emby premiere key on a second Emby instance to run this plug-in

 

[rbjtech 5284]

If the 2nd instance is related directly to the first (in your case it uses the same source media), then I believe you are not breeching any of the license T&C's at all.

@ebr should be able to confirm this as this is just my personal viewpoint.

 

[pwhodges 2014]

My understanding is that you can use your premiere key on as many servers as you choose to run yourself - however, there is only one count of clients, regardless of which server they connect to.

Paul

[Carlo 4561]

1 hour ago, Pog22 said:

My next question, can I use my Emby premiere key on a second Emby instance to run this plug-in

Yes, this is not a problem at all.

5 minutes ago, pwhodges said:

My understanding is that you can use your premiere key on as many servers as you choose to run yourself - however, there is only one count of clients, regardless of which server they connect to.

Paul

Correct, the license count is unique devices per license key. The same 5 devices hitting your main, beta and "util server" is still just 5 licenses not 15.

[Pog22 52]

Perfect folks, I have a new docker instance ready to spin up to get this going. 

[Carlo 4561]

1 hour ago, Pog22 said:

Hi, thanks, that's exactly what I was looking for, I wasn't aware of having that much control. An nfo will need to be created during a scan as they're not next to the media because Emby cannot write there.

Question for you.  How good are you at scripting?
Do you know how to walk a path programmatically and create new files?

An advanced technique you could use.

If so you could mimic your good drive on the local file system but instead of creating mp4, mkv files just create strm files (dummy files that don't even have to point to the media). You could skip the graphic files as.

If you can do this then you can have a second Emby server scan those in and run the theme plugins against this "stub" folder structure.
When complete you can copy back the theme files to google.

But a second Emby server with the same paths and write access would just be so much cleaner and easier!!!

[Pog22 52]

I'm already at 53% TV library scanned on a new Emby instance 

 

Thanks for your help though. I had considered a few different options but thought a second instance of Emby on the Dedi server would be the cleanest since I already had a read write mount.