Good afternoon. I am hoping that I can explain the situation I am currently dealing with in TouchDesigner. I am currently working with the latest build (2023.12000) of the non-commercial 64-bit MacOS version of TouchDesigner on a 2021 MacBook Pro 16" with an M1 Max CPU.
I am using a replicator driven by a folder DAT to create a number of base comps containing scanned elements, one base comp per scan in the source folder. In each base comp is also a MovieFileIn Top that loads a a black and white image that is used as a matte to cut out the foreground of the scan from the background. The scans can be 1 of 6 different options so I have a script on the MovieFileIn DAT that selects the correct matte image as defined in the original folder DAT. The script is as follows:
Everything seems to work as expected when I switch into perform mode, but when I add an additional scan to the folder, some of the replicated base comps change to a different image in the aforementioned MovieFileIn DAT. It looks like the MovieFileIn source has switched from the above expression to a constant value which does not match. Any thoughts on why this might be happening? How might I resolve this issue?
Hello,
Its better if you post some element allowing to understand your problem.
Perhaps I have a solution for your problem.
When you change the folder content perhaps you have to force the choice of the video file with your python line.
In the model comp, i add a pulse element named Setfile and I link the corresponding parameter chop to a chop execute dat affecting the right file to the moviefilein.
In the Replicator callback, i would write:
c.par.Setfile.pulse()
And I am sure all the created moviefilein have the right file.
Jacques
Is your op(‘…/scansTable’) manually filled in or a Folder DAT? If the latter, the issue may be that since the DAT folder sorts out files alphabetically, the new scan you are adding to the folder changes the order of things, and hence your references are different in the movie players.
If that’s not the case. It is better if you post a simple example of this happening, either a quick screen recording, or a network, to better understand the issue.
I think Darien hit it on the nose! I was using a folder DAT and the new scans where not necessarily in line alphabetically so everything was shifting and perhaps that was breaking the links. I changed the sort order so that the newest scan was last, and I also used the replicator callbacks to assign the textures instead of scripting them inside the source component, as recommended by Peter Walker on Facebook, and everything is working as it should.