Question about realtime monitor on network shares

[AviatorBimmer 28]

When I had Emby running on my Synology 1019+, every time I added a movie or TV Show to a library, within minutes, if not seconds, I could see the library begin to add the movies and the little spinner show in the top right corner of the library with the percentage completed.

 

Last week I built a new PC better suited for Emby, deleted the Emby Server on the Synology and installed it on the Windows 10 PC.

 

I decided to not copy over any of the metadata and/cache and start from scratch.

 

Now that the server is running on the PC, I've noticed Real time monitoring is not working. I tripled checked to make sure it was enabled in the library's settings.

 

The only thing I can think of that could possibly have an impact, just thinking out loud here, is the fact that the actual media files are still on the NAS and not locally on the PC where the server is installed.

 

Could this cause an issue? Perhaps Windows 10 is not able to detect changes in the library files when they are hosted on another machine, being my Synology NAS in this case?

 

Every time I add new media files, I wait and wait and it never shows the new files automatically. I have to manually initiate a "Refresh Metadata" command so Emby kicks in and starts processing the new media files.

 

Any guidance would be greatly appreciated!

 

 

Sent from my iPhone using Tapatalk

[Luke 42086]

 

 

Perhaps Windows 10 is not able to detect changes in the library files when they are hosted on another machine, being my Synology NAS in this case?

Yes this is probably it.

[AviatorBimmer 28]

Yes this is probably it.

Dang, just what I feared.

 

So nothing can be done about it? Not something that can be implemented?

 

If not, no biggie. I'll just manually start the refresh metadata after adding media files, I'll definitely miss that feature though.

 

 

Sent from my iPhone using Tapatalk

[Luke 42086]

Emby Server is built with .NET Core, and our real-time monitor uses their FileSystemWatcher API, so whatever it supports is what we support as well.

 

I know that some network shares will work, but if you're running the server on windows then i imagine it is probably limited to other windows network shares.

[AviatorBimmer 28]

Emby Server is built with .NET Core, and our real-time monitor uses their FileSystemWatcher API, so whatever it supports is what we support as well.

 

I know that some network shares will work, but if you're running the server on windows then i imagine it is probably limited to other windows network shares.

Makes perfect sense.

 

I did some research on the FileSystemWatcher API and it seems that besides the local computer, it indeed can detect changes on remote computers and network drives:

 

 

 

I did remember that my library was setup using a network share instead:

 

 

 

This got me thinking.

 

I wonder if I map that drive so it has it's own drive letter, and set up the library using the mapped network drive instead. [emoji848]

 

Will it then be able to recognize it as a network drive and thus any changes to the files?

 

Only one way to find out...

 

 

Sent from my iPhone using Tapatalk

[Luke 42086]

Maybe, but i will guess no.

[Luke 42086]

And we don't recommend mapped network drives anyway because windows will disconnect them when idle, and then Emby Server will not be able to reach them anymore.

[AviatorBimmer 28]

Just tried it with a mapped network drive and it didn't work.

 

I'll just leave it with the share name as it was setup. I definitely don't want it disconnecting.

 

Thanks Luke, for being so helpful and patient as always!

 

 

Sent from my iPhone using Tapatalk

[AviatorBimmer 28]

@@Luke

 

I did find a "workaround" lol

 

I installed Radarr on my Synology and set it up so that it triggers a "Scan library files" event every time a new media file is added to the library. Works like a charm!

 

BTW, that Radarr is one amazing piece of software. Compliments Emby immensely.

 

 

Sent from my iPhone using Tapatalk

[Luke 42086]

Thanks for the feedback.

[muzicman0 84]

So I use a script to do various things when a file is added to a folder, and I use the same mechanism Emby does.  What it appears happens for me is that if I set say C:\TV to be monitored, anything written to C:\TV or C:\TV\Show_Name will work, but as soon as it is 2 folders deep (IE: C:\TV\Show_Name\Season 01), it won't work.  This is on both my QNAP and Synology drives.  It may have been 1 folder deep where it stopped working, but I don't think so.