HI! first thankyou for this amazing tool! already having alot of fun. I looked thru the forum to see if i could find this issue but i didn't see anything...
The issue i'm having is that i've made a simple folder Monitor --> mp4 --> folder delivery. The folder being watched has 3 mov files:
No matter what i do, Oreo_Swing_edit_v002.mov will not be picked up. if i look in the folder, "Processors\.cache\wfs\20160901130448\mons\20160901-131141-526-43A156ED4703", I can see the .txt files for the two that were correctly transcoded, and then a subfolder "i" that has a .txt file for the one thats not being picked up. No matter what i do i cant seem to get the folder monitor to pick up all 3 files. The contents of the .txt file in the "i" folder ends with retries=61 and that seems to be climbing...
if i manually submit the file to the workflow its processed without any trouble. Not sure what this could be. any thoughts?
thankyou kindly,
doug
the mov file in question was open by artists using quicktime player....
once they all closed out then the folder monitor picked up the file. if its possible to work around this issue within FFAStrans somehow that would be very very helpful.
Hi doug, thank you for using FFAStrans and welcome to the forum!
I have tried to recreate the issue by opening a QuickTime file using both PC and Mac, and with different kinds of network share. You might have a different network setup than I have available cause the monitor picks up the file no matter what. The monitor tries to figure out if the file is available for reading but maybe the method used to check this is too strict. I will have a close look at it but it's a bit difficult when I'm not able to recreate the issue.
The main reason for this issue is because I want to make sure FFAStrans does not pick up files that are being written. If it does, it might cause an incomplete transcoding, and we don't want that. But as I wrote, the method might be to strict and I want to find out what's actually going on. But because I'm not able to recreate the issue myself, I will send you a private patch that logs this particular issue. This will have no impact on your day-to-day transcoding but you will need to recreate the issue and send me log-files. I'll be back at you when I have the patch ready.
Just to be clear; some files are not picked up BEACUSE they are open in another program like QuickTime? Or are they not picked up at all even though the files are free? If it's the latter, then I have found a new bug that has been addressed in the upcoming 0.7.7 version. It sometimes caused FFAStrans to stop picking up files, and in some cases it simply would not start properly. Now, I'm not sure if this particular bug is what you have but I hope it's related.
There has been a lot of changes in 0.7.5 and 0.7.6 to how FFAStrans detects and picks up new files, so some issues was sort of expected. But the next release seem pretty reliable at this point.
At my site the files are not opened by any programs. The files are moved to the input directory very fast (AVS scripts are very light weght video files) and they shouldn't be blocked at any time. I have wrote batch script - a workaround for clearing FFASTrans directory:
echo ************** Clear jobs directory...
del F:\FFASTrans\Processors\.cache\monitor\jobs\*.ini 1>nul 2>nul
echo ************** Clear work media cache directory...
rmdir F:\FFASTrans\.work_media_cache /q /s
mkdir F:\FFASTrans\.work_media_cache
echo ************** Clear tickets directory...
del F:\FFASTrans\Processors\.cache\tickets\*.ini 1>nul 2>nul
echo ************** Clear workflow status directory...
rmdir F:\FFASTrans\Processors\.cache\wfs /q /s
mkdir F:\FFASTrans\Processors\.cache\wfs
The batch should be executed when there are no jobs under processing.
Disk F is not a local drive - it's mapped network drive. I suppose, sometimes it can be unavailable for a moment. And it could lead to mismatch in tickets/workflows ini files, for example orphan links.
I appear to be having the same issue with one of my folder monitors. It will work fine for 2 weeks then just stop picking up new files. It does detect the files as it creates a new .txt file for them in the C:\FFAStrans0.7.7_Win32\Processors\.cache\wfs\20160929172310\mons\20161129-131247-461-1F205F02F1C0\i folder but it never starts the workflow running on the file. Currently running 0.7.7 and had the same issue in 0.7.6.
