sea3pea0 5 Posted August 16, 2016 Share Posted August 16, 2016 (edited) I use bit torrent sync to sync folders in my media browser library. The library monitor constantly records the changes of these files as they are modified by bit torrent sync (emby v 3.1.106.0). It would be nice if it would ignore those files. Also I noticed that if doing a library scan while .bts files are present they would get added into the library (emby v 3.0.6060). It would be nice if .bts files were also ignored while running a library scan. I know syncthing uses .sync as an extension, it would probably be good to have those ignored too if that's not already the case. Some logs here Edited August 16, 2016 by sea3pea0 Link to comment Share on other sites More sharing options...
Luke 36991 Posted August 16, 2016 Share Posted August 16, 2016 How do those get added to the library? We don't have anything that is looking for those extensions. I can update the library monitor. Link to comment Share on other sites More sharing options...
sea3pea0 5 Posted August 16, 2016 Author Share Posted August 16, 2016 It could have been a one time glitch of some sort or maybe something changed in the beta releases, since this only happened to me on 3.0.6060 and it only happened once that I've noticed. As far as the library monitor continuously reporting the changes to the .bts files, is this something that can be fixed without too much trouble? Also I am curious as to what kind of impact you think this might have on system resources other than there being many, many log entries? As I am running emby on a Synology DS 412+ with only 1gb ram and little processing power any little bit of spared resources helps Link to comment Share on other sites More sharing options...
Luke 36991 Posted August 17, 2016 Share Posted August 17, 2016 Yes it will be changed. How much stress it might be causing now depends on how active those other processes are. Link to comment Share on other sites More sharing options...
Solution solabc16 379 Posted September 9, 2016 Solution Share Posted September 9, 2016 This is now resolved in stable package release 3.0.7000.0-1 and beta package release 3.1.143.0-1-beta. - James Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now