[SOLVED] Get Errors on AVIsynth-Nodes

Questions and answers on how to get the most out of FFAStrans
ThomasM
Site Admin
Posts: 231
Joined: Wed Feb 22, 2017 6:36 am

Re: Get Errors on AVIsynth-Nodes

Post by ThomasM »

Hi emcodem,

thank zou for pointing that out. In the end I got everything running now. I had another issue, where in the "FIND_assumefps_"-node the command

%comspec% /c
"FOR /f "tokens=2 delims==" %f in
('findstr "AssumeOriginalFPS" "%s_original_path%\%s_original_name%.LOG"') DO
ECHO %f > "%s_original_path%\%s_archnumber%\FPS.fps""

gives me not only the number but also a carriage return, which leads to errors in the following script-nodes.

My working Workflow now is attached. If anyone is interested I can explain what it really is intended for. In short:

I create a Scanfile.AVI and a Scanfile.LOG on another machine. Scanfile is actually a Unique Identifier in the form of 16FA2345INV5678 where the first 16 determines the format 16 mm Film-stock. Other formats are N8 (regular-8), S8 (super-8) and 95 (9,5mm Pathe). the .LOG has information on Assumed filmspeed in FPS. This is only important for the person who gave us the Film, because we are always working on a 25 fps framebase.

So - the Workflow encodes the avi to ProRes. This proRes is the production-copy for e.g. NLE. The Prores is then encoded to MP4 on 25 FPS for research. These three (.avi, .mov, .mp4) all go to the MAM-System. The all get MD5 checksum and FFprobe-metadata-logs.

The last branch is for encoding a "customers-copy"where the frame is cropped and resized to Full-HD 4:3 and speed-down to a more common framerate for old film-stock.

If all encodings are ready, the whole Folder will be copyed to the MAM-Watchfolder. The MAM then automatically extracts the logs for archiving all that stuff (without the Änsichtskopie"for the customer...).

so long,
thanks for the support,

tom
Attachments
Full_Scanner_Workflow_Stumm.xml
(102.14 KiB) Downloaded 322 times
Post Reply