XDCAM processor with opAtom and cyrillic filenames
XDCAM processor with opAtom and cyrillic filenames
Hello!
I found an issue with XDCAM processor as I think. Workflow is simple: Folder-> XDCAM->Folder
XDCAM processor is tuned up to generate Avid project structure. If source filename is cyrillic with spaces or without it - all of output structure files will have zero sizes.
XDCAM without disabled "Avid check" works well.
I found an issue with XDCAM processor as I think. Workflow is simple: Folder-> XDCAM->Folder
XDCAM processor is tuned up to generate Avid project structure. If source filename is cyrillic with spaces or without it - all of output structure files will have zero sizes.
XDCAM without disabled "Avid check" works well.
Re: XDCAM processor with opAtom and cyrillic filenames
Hi 3dsasha,
First, what FFAStrans version are you working on? Second, can you send the logs for the job? Right-click the on the job in the status monitor and select "Open log folder...". Zip the contents and send.
-steinar
First, what FFAStrans version are you working on? Second, can you send the logs for the job? Right-click the on the job in the status monitor and select "Open log folder...". Zip the contents and send.
-steinar
Re: XDCAM processor with opAtom and cyrillic filenames
I used latest ffastrans 1.2.0.0. Attachment applied.
- Attachments
-
- joblog.zip
- (10.98 KiB) Downloaded 309 times
Re: XDCAM processor with opAtom and cyrillic filenames
Hi 3dsasha,
I'm having trouble recreating the issue. Using 1.2.0 and the same file name as your original "руссиан тест.mxf" the workflow you sent has no problem delivering the 5 avid files. Also, FFAStrans has been much tested with all sorts of uncommon characters and the cyrillic is not special in that regard.
What OS are you running FFAStrans on?
-steinar
I'm having trouble recreating the issue. Using 1.2.0 and the same file name as your original "руссиан тест.mxf" the workflow you sent has no problem delivering the 5 avid files. Also, FFAStrans has been much tested with all sorts of uncommon characters and the cyrillic is not special in that regard.
What OS are you running FFAStrans on?
-steinar
Re: XDCAM processor with opAtom and cyrillic filenames
I reproduce it on my home PC. OS - Windows 10 Pro x64 2004 19041.1052. At office I have other Windows 10 Pro x64, exact version I'll know at workday.
After some tests I understood - changing setting "Clip name" from %s_original_name% to fixed non-cyrillic string solves zero size problem.
After some tests I understood - changing setting "Clip name" from %s_original_name% to fixed non-cyrillic string solves zero size problem.
Re: XDCAM processor with opAtom and cyrillic filenames
OK, this is strange!
Can you please open the workflow properties and go to "Maintainance" and check "Keep job work folders on completion", then run a small job. When finished use the status monitor and select "Open work folder..." on the job. Zip the contents and send. If it's too large you can try and upload to https://drive.google.com/drive/folders/ ... Drj4RH126U or use WeTransfer or any other sharing service.
Thanks!
-steinar
Can you please open the workflow properties and go to "Maintainance" and check "Keep job work folders on completion", then run a small job. When finished use the status monitor and select "Open work folder..." on the job. Zip the contents and send. If it's too large you can try and upload to https://drive.google.com/drive/folders/ ... Drj4RH126U or use WeTransfer or any other sharing service.
Thanks!
-steinar
Re: XDCAM processor with opAtom and cyrillic filenames
Thanks, and I'm sorry but I will also have to ask you to post the content in the processors\db\configs\host directory. There should be some .json files with the name of your computer. You can also send it in private post to admin if you like.
-steinar
-steinar
Re: XDCAM processor with opAtom and cyrillic filenames
Json is attached
- Attachments
-
- EDIT5.json
- (654 Bytes) Downloaded 329 times
Re: XDCAM processor with opAtom and cyrillic filenames
Thanks! I've been able to recreate the problem and working on a fix. Thanks for reporting!
-steinar
-steinar