- 2-18-2020 1-54-39 PM.jpg (68.93 KiB) Viewed 4245 times
Output of one Encoder as input to another?
Output of one Encoder as input to another?
As the topic says, I want one encoder to complete, and then use THAT result as input to another encoder, but it appears to be using the same input file in all the encoders. Is this by design, or can I specify this behaviour somehow?
Re: Output of one Encoder as input to another?
Hi gdpodesta,
By design all encoders set the source variable for the next connected node(s). So if you connect an encoder to an encoder, the first will create the source for the second.
The source you're seeing in the monitor is the initially picked up or submitted source. It will never change but you have to see this as a "human identifier" for the job.
-steinar
By design all encoders set the source variable for the next connected node(s). So if you connect an encoder to an encoder, the first will create the source for the second.
The source you're seeing in the monitor is the initially picked up or submitted source. It will never change but you have to see this as a "human identifier" for the job.
-steinar
Re: Output of one Encoder as input to another?
Ah, so instead of my current Encoder1->Folder->Encoder2,
I should have 2 connections:
Encoder1--->Folder
---->Encoder2
Thank you good sir, just a shift in thinking.
I should have 2 connections:
Encoder1--->Folder
---->Encoder2
Thank you good sir, just a shift in thinking.