FFMPeg Locking Files

[ftanner]

I think the ffmpeg.exe instances might be from generating thumbnail preview images, this is done for files so that when fast forwarding a preview of the video at that time is shown. Once the ffmpeg.exe instance is closed the server should no longer keep the file open, we will test here to see if we can reproduce the problem.

Another thing that I checked was to see if there were any "Processing playlist" items in the Mezzmo interface. I didn't see any.

[Peter]

I tried to reproduce the problem here by playing a file on the Roku then stopping it and going to the file on disk and moving it to another folder, the file was moved without any locking issues. Then I tried playing the file from the new location and then moving it back to the old folder and it was reported that the file was open in ffmpeg.exe and could not be moved but once ffmpeg.exe completed I could move the file.

[ftanner]

I tried to reproduce the problem here by playing a file on the Roku then stopping it and going to the file on disk and moving it to another folder, the file was moved without any locking issues. Then I tried playing the file from the new location and then moving it back to the old folder and it was reported that the file was open in ffmpeg.exe and could not be moved but once ffmpeg.exe completed I could move the file.

I couldn't move it after FFMPeg completed. Not sure what to tell you. I only know what I am experiencing. I even let it sit overnight in case something weird were happening and it STILL didn't move.. It still said it was in use by the Mezzmo Media Server service.

[Peter]

Did you play the file to the end or just try it as I did to play part of the file? MezzmoMediaServer.exe keeps the file open while the device is requesting bytes so possibly if it gets to the end something different is happening than if you stop it partway through.

[ftanner]

Did you play the file to the end or just try it as I did to play part of the file? MezzmoMediaServer.exe keeps the file open while the device is requesting bytes so possibly if it gets to the end something different is happening than if you stop it partway through.

I played them most of the way through, stopping just about the time that the credits came on.

[Peter]

Thanks, we will try this here to see if we can reproduce the problem. As a test could you please try playing a file for a few seconds then stop it and see if you can move the file on disk?

[ftanner]

Thanks, we will try this here to see if we can reproduce the problem. As a test could you please try playing a file for a few seconds then stop it and see if you can move the file on disk?

Played for 60 seconds and gave it a shot. No joy. Something interesting, I paid attention to it while it did it, is that it goes all of the way through the move cycle one time and the file shows up in the other location. When it goes through the "second cycle", which I am presuming is the delete from the original location, it fails and says "Try Again" or "Cancel". Try Again fails.