Auto-Organize Feature Request

[tvinhas 14]

Hi,

 

I really love the Auto-Organize feature of monitoring a directory for new shows, and than moving it to my chosen library.

 

My idea is to use it for recorded/downloaded shows from PlayOn, but in it's current form Emby will copy or move the file while it is still being downloaded.

It would be really nice if Emby could check if the file was still increasing in size before adding it to the library. You could add the file to some kind of queue once you find a new file, and check it again in 30 seconds to see if the file changed. If it did, keep the file in the queue until it doesn't see a change for a pre-determined amount of time.

 

Regards,

Thiago Vinhas

[Luke 37094]

Hi, thanks for the report. Yes this would be a nice enhancement.

[tvinhas 14]

@@Luke I just found out that this is not really necessary. At least when recording using PlayOn, the file is locked so Emby throws an exception like this:

2016-12-28 16:01:01.3295 Error App: Failed to move file from /dvr/PlayOn/Ray Donovan/Season 4/Ray Donovan - s04e05 - Get Even Before Leavin'.mp4 to /dvr/TV/Ray Donovan (2013)/Season 4/Ray Donovan - s04e05 - Get Even Before Leavin'.mp4: Lock violation on path
        *** Error Report ***
        Version: 3.1.265.0
        Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh
        Operating system: Unix 4.4.0.57
        64-Bit OS: True
        64-Bit Process: True
        Mono: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 28 20:49:26 UTC 2016)
        Processor count: 6
        Program data path: /var/lib/emby-server
        Application directory: /usr/lib/emby-server/bin
        System.IO.IOException: Lock violation on path
          at System.IO.File.Move (System.String sourceFileName, System.String destFileName) [0x00140] in <8f2c484307284b51944a1a13a14c0266>:0
          at Emby.Common.Implementations.IO.ManagedFileSystem.MoveFile (System.String source, System.String target) [0x00000] in <bef7798f4baf4a2cbd193bda78100cb9>:0
          at Emby.Server.Implementations.FileOrganization.EpisodeFileOrganizer.PerformFileSorting (MediaBrowser.Model.FileOrganization.TvFileOrganizationOptions options, MediaBrowser.Model.FileOrganization.FileOrganizationResult result) [0x00085] in <e9eeba7192ba4529aac9fe5fb4f73a8b>:0
        System.IO.IOException
          at System.IO.File.Move (System.String sourceFileName, System.String destFileName) [0x00140] in <8f2c484307284b51944a1a13a14c0266>:0
          at Emby.Common.Implementations.IO.ManagedFileSystem.MoveFile (System.String source, System.String target) [0x00000] in <bef7798f4baf4a2cbd193bda78100cb9>:0
          at Emby.Server.Implementations.FileOrganization.EpisodeFileOrganizer.PerformFileSorting (MediaBrowser.Model.FileOrganization.TvFileOrganizationOptions options, MediaBrowser.Model.FileOrganization.FileOrganizationResult result) [0x00085] in <e9eeba7192ba4529aac9fe5fb4f73a8b>:0

Maybe you could just treat this exception nicely.

[Luke 37094]

We do treat it nicely. It handles the error, logs it, and marches on. Later when the file is no longer locked it will work.