Page 1 of 1
Line 34292 Error
Posted: Tue Dec 17, 2019 7:02 pm
by Noqras
I saw a few other posts on an error similar to this, this is the "Array variable has incorrect number of subscripts or subscript dimension range exceeded" error that goes with a "Job aborted abnormally".
This may not even be a bug, may just be a safety, it looks like I really just exceeded the amount of processors allowed. This workflow has about 93-94 individual processors and after splitting the workflow into two separate ones, it starts picking media up from the watchfolder again.
Is there a known limit of processors? If I did actually exceed the number of processors allowed, is this limit necessary?
Re: Line 34292 Error
Posted: Tue Dec 17, 2019 8:28 pm
by admin
First, that is a crazy workflow!
Second, what is the version you're running? Check the help menu and select "About FFAStrans". I need the version number of FFAStrans.exe.
Thanks!
-steinar
Re: Line 34292 Error
Posted: Tue Dec 17, 2019 8:48 pm
by emcodem
Would you please export your workflow? i could use this for testing the new job details interface
Re: Line 34292 Error
Posted: Wed Dec 18, 2019 6:09 pm
by Noqras
Steinar, my man! Yeah it is a bit crazy and its not exactly symmetrical, I simplified the decision making yesterday though, my FFAStrans.exe version is 0.9.4.59.
emcodem wrote: ↑Tue Dec 17, 2019 8:48 pm
Would you please export your workflow? i could use this for testing the new job details interface
Absolutely, anything to help with that. One thing I like about Telestream Vantage is that you can see exactly what processor is running live in the GUI as the file goes through the workflow.
Here is the workflow that is currently not working for me unless I remove a few processors. I've also attached a version where I removed the section that just exported to Amberfin and I've simplified the conditional logic greatly.
Re: Line 34292 Error
Posted: Wed Dec 18, 2019 7:56 pm
by admin
Noqras, thank you for that workflow, it's great!
The bug was easy to fix but unfortunately, it will not be fixed in the current version. But you are right, there was a limit there but that was old legacy code not renewed. So this is now fixed for the next 1.0.0 bate and the limits are now gone. So thanks for reporting!
-steinar
Re: Line 34292 Error
Posted: Wed Dec 18, 2019 8:53 pm
by Noqras
Awesome! Perhaps I'll try the beta and do some testing.
Can't wait for the stable release, it'll be great!