Page 1 of 1
RESIZE node produces incomplete AVS
Posted: Thu Sep 15, 2016 10:57 am
by kibi
In the last version 0.7.6.1 RESIZE node generates AviSynth script without the last string
That's why any workflow with RESIZE stops with an error:
Resize@xxx: AviSynth script did not return a clip
Re: RESIZE node produces incomplete AVS
Posted: Thu Sep 15, 2016 1:31 pm
by admin
Oh but that's weird! Just did a simple with various resize settings and I cannot recreate the issue. Can you please send me you workflow so I can investigate?
-steinar
Re: RESIZE node produces incomplete AVS
Posted: Tue Sep 20, 2016 3:07 pm
by kibi
Re: RESIZE node produces incomplete AVS
Posted: Tue Sep 20, 2016 5:42 pm
by admin
Hi,
When I import your workflow the custom avisynth node holding the "Sharpen"-template is empty, thereby causing the exact same error you posted. Can you please check if the "Sharpen" step is valid in your copy of the workflow?
-steinar
Re: RESIZE node produces incomplete AVS
Posted: Wed Sep 21, 2016 10:20 am
by kibi
At my side "Sharpen" node has the following content:
Code: Select all
# Variables:
#
# m_clip = The last returned AviSynth media
#
# Do NOT change any of the following variables!!!
# _ffas_video = <original video>
# _ffas_audio = <original audio>
# _ffas_height = <source height>
# _ffas_width = <source width>
# _m_clip_a_channels = <total channels>
# _ffas_work_fdr = Working folder for the workflow
#
m_clip = m_clip.Sharpen(.30)
# The following MUST be the last line of your script
Return m_clip
I used "File/Export Workflow" function, may be it has missed some ini files.
Re: RESIZE node produces incomplete AVS
Posted: Wed Sep 21, 2016 11:18 am
by admin
Hm, if I copy your script into the Sharpen node everything works perfectly. No errors. There must be something wrong with that particular node.
Can you please locate the following file: FFAStrans\Processors\templates\.avs_custom\5368617270656E.ini
It SHOULD be your "Sharpen"-template. If it's not there but you still see it in your node then there is a bug. Because the error you're seeing is exactly the same as I see when the Sharpen-node is empty.
If you DO locate the file can you please send it to me? Also, can you try and create a new template with a different name but with the same script?
-steinar
Re: RESIZE node produces incomplete AVS
Posted: Wed Sep 21, 2016 2:55 pm
by kibi
The content of the file is:
Code: Select all
[template]
name=Sharpen
text_data=0x48B1002320566172696162806C65733A0D0A23002000206D5F636C69700900093D20546865206C00617374207265747500726E6564204176690053796E7468206D650864696104C0446F204E004F54206368616E67006520616E79206F660420740076666F6C6C6F4077696E67207605C82104212101C65F66666173805F766964656F200068003C6F726967696E61146C2002123E07226175641C696F0A2102110821686569086768740122736F757218636520031008217769643C74680820020F031F03EB5F61025F015E6E656C73203DE0203C746F74804485080924806F726B5F66647280250E570005016C007164657220A8666F72827877000B668079E100600D0A0D0A032F80290304002E5368617270656EA0282E333029810F2302B10107934D55535420626543022502BC6C696E6581A67901006D20736372697074180D0A5282C684D30D0A
Re: RESIZE node produces incomplete AVS
Posted: Wed Sep 21, 2016 3:06 pm
by kibi
I have replaced Custom Avisynth Node with the new one and have made new template with the same code. And it has started to work normally.
Maybe it was the bug of migration from 0.7.5 to 0.7.6 (or to 0.7.6.1). The workflow had stopped working after the software upgrade. I definitely didn't touch the workflow.
Re: RESIZE node produces incomplete AVS
Posted: Thu Sep 22, 2016 11:39 am
by admin
It's hard to say what the cause was. The method for dealing with templates has changed much from 0.7.5 to 0.7.6 so it's not far fetched to say that it's a bug but at this time I cannot figure out what it is. Also, your template file seem to be ok. I've tried to export and import another workflow with the template and it works like it's supposed to. Do you have similar issues with other workflows?
-steinar
Re: RESIZE node produces incomplete AVS
Posted: Fri Sep 23, 2016 9:43 am
by kibi
No, I have not. It was the only workflow with Custom AviSynth. If you can not reproduce it in 0.7.6, then it's for sure the migration issue.