Verify the file reached the configured source
When a newly added video does not appear in Emby, begin with its actual location on the server. A file visible in your personal desktop account may have been copied to a different directory from the library’s configured root. Compare the complete server-side path privately before repeating client refreshes.
Check that the copy has finished and that the server process can read the file. Keep one known new item as the test. Avoid adding several renamed copies, because duplicate inputs make it harder to distinguish delayed discovery from a matching or grouping issue. Preserve the original filename and the time the transfer completed.
Inspect the affected library’s monitoring setting
Emby offers real-time monitoring for changes and additions, but its documentation limits that option to supported filesystems. A monitoring checkbox is therefore not proof that every mounted storage route will generate the same change notifications. Identify the actual filesystem and mount or share arrangement used by the affected library.
Open the library settings and inspect real-time monitoring. Emby’s guide calls for a server restart after changing the option. Treat that as a deliberate configuration change, record the previous state and use a normal server restart. Repeatedly restarting the television client does not apply a server-side monitoring change.
Compare monitoring with an explicit scan
Use the server’s ordinary library-scan route for the affected collection and inspect whether the known file appears. If a scan finds it while monitoring did not, retain that comparison. It narrows the case to detection timing or the storage notification route without proving a codec or metadata-provider problem.
If a scan also fails to find the file, inspect the configured root, server access and supported naming. If the entry appears under an unexpected title or version selector, record that result rather than reporting it as absent. Discovery and identification are different stages even when both affect the final library view.
Verify the client after server discovery
Once the item exists in the server library, open the same collection as the intended user in the client. Check access to that library and the client’s current view. A server administrator seeing an item does not prove a restricted viewer is allowed to see the same storage root.
Keep the final record small: source path, copy completion, monitoring state, scan result and viewer result. That sequence is more useful than a broad claim that automatic scanning never works. The expected outcome is a known discovery route for the actual storage system; it does not promise immediate notifications from every network filesystem.
Questions answered
Does real-time monitoring work identically on every storage path?
No. Emby documents it for supported filesystems. Verify the actual storage and compare with an explicit library scan.
What does it mean if a manual scan finds the new file?
It establishes that the scan can discover that file. Keep the monitoring and timing question separate from media playback or client library access.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.