[SOLVED] Error on Populate Variables (1.0.0)

[ThomasM]

Hi all,

Maybe I misunderstood something, but...

I migrated from 9.4.x to 1.0.0 a few days ago. The workflows seem to work but not all: Everything looked good so far, but by testing a complex workflow I got error:

in "Populate Variables"-Node
I try to set my %i_seitennummer%-Variable to either 0 or 3 (zero or three; one (1) and two (2) are also possible). I only populate with integer numbers, not words, for sure!

The outcome is always an error in the FFAStrans-monitor (Process exited with error code: 1). I tried to delete and re-programm this node but with the same qutcome.

Any ideas?

[admin]

Hi Thomas,

I'm sorry about the delayed reply but your post was a bit lost on the radar. Although I have found a minor bug regarding variables, I'm not sure it will actually affect your workflow. I would like you to update to the 1.0.0.1 bug fix patch, run your workflow and see if all is ok... Ok?

-steinar

[ThomasM]

Hi Steinar,

thanks for your reply. As I am not in the Studio for a few days now, I try to describe the things that I did until yesterday evening:

The first thing that is questionable is the fact that the StatusMonitor puts out an Error 1 on that "PopulateVariables"-Node. I mean - how can a population of an integer Variable put out an error?

I then tried to make the Variable a string ( %s_seitennummer%). Same error.

Then I tried to update to 1.0.0.1. In that Workflow in question the same error occurs.

The next thing was to strip the workflow down to only a MonitorNode -> PopulateVariablesNode -> CreateTextfileNode. The latter works properly.

This brings me to the assumption, that the previous or the following Node of my questionable Workflow, or the VariableName does make some trouble ( %i_seitennummer% ).

I do have to test my other Workflows as well. I have some other UserVariables in other Workflows also on different machines all updated to 1.0.0. now and it all seems to work. So this special Workflow does make the trouble.

A short description:
The Workflow in question is aimed at sorting and transcoding digitized Videotapes with up to 6 AudioTracks and single / double-Sided-Media (Video2000). To distinguish the different formats the Filenames are set as follows:

(examples)
VHSFA1234INV9876_TC.mov or BETASSPFA1234INV9876_TC.mov both can have up to four audio-Tracks (two LNG, two AFM) and two TimeCode-Tracks (LTC and VITC converted to LTC).
UmaticFA1234INV9876_TC.mov is 1 AudioTrack and 1 TC-Track
V2000FA1234INV9876_Seite1.mov is Side one of Video2000-Tape with two AudioTracks.

So the Filename is analysed with some CommandNodes. The outcome is the ArchiveName ( e.g. "VHSFA1234INV9876" from "VHSFA1234INV9876_TC"), the presence of TimeCode (_TC -> TC-Variable) and if it is Video2000 ( (Seite1 from V2000FA1234INV9876_Seite1).

I will try to do some more testing on Wednesday.

So long,
tom

[momocampo]

Hello Tom,

Well, I saw your workflow and I think we can say it is quite big So, in my opinion, you don't have choice, you need to test your wf step by step. You can add generate text node after each populated variable to check if the variable is reliable. You use this populated variable to altered the following of your workflow so if the variable is no ok , paf!
Other way to be sure where is the error is to install the Encodem's webinterface and see exactly where is the error. The new version is really good to se e log's details.
Anyway, I will try to "dig"your workflow next week, I hope find where is the problem but we will find

CHeers.

Benjamin

[admin]

Hi tom,

I think I have found the cause of your bug. Could you please replace the existing \Processors\processors.a3x with the one attached and see if your workflows now works as expected?

-steinar

[ThomasM]

Hi Benjamin,
Hi steinar,

@benjamin - yes, i will try the web-interface as well. Thanks for this tip!
@steinar - great, i try to get to the Studio today or tomorrow for testing the fix.

I soon come back for a Report.

Regards,
Tom

[ThomasM]

Hi Steinar,

Now it´s running!

Thanks!

all the best,
tom

[admin]

Great, thanks!

-steinar