Directories of Image Sequences spreadable?

I have a main folder:
C:\Desktop\ImageSequences\

With these 4 folders within:

C:\Desktop\ImageSequences\1
C:\Desktop\ImageSequences\2
C:\Desktop\ImageSequences\3
C:\Desktop\ImageSequences\4\

In each folder is 25 .jpg images named 0001-0025

I’ve got a Dir node and a count node but I can’t seem to count directories?

I’m playing back the image sequences with picture stack which is working great.

What I want to do is arrange these image sequences in a 2 by 2 grid.

Ah okay, SubDir Node can help me with the first part.

So I think it’ll be something like this, I’m just having problems separating out by directories.

ImageSequenceGrid.v4p (19.4 kB)

PictureStack (EX9.Texture)'s Directory is spreadable. so you simply connect the output of SubDir (File) to it and then via the picturestacks Stack ID you address the stack/directory. ie. in your example simply connect to it a spread of:
0 1 2 3
to address the 4 stacks. see?

I get it, yeah that’s perfect, thanks very much for your help, really appreciate it :)

Sorry, one more question!

This is all working great, only problem is that I save over images in the directories as the patch is running, I then want these new images reloaded in the patch.

I try Update on the SubDir node, and the reset and reload pins on the PictureStack but it doesn’t seem to update to the new images that are in that folder unless I reload the patch or delete a link and relink.

Is it because it’s looking at the directory and seeing the same number of files and same names and so thinks it doesn’t need to rescan?

right. if you follow the Reload in the module you see it is only connected to the Dir (File) but not to the FileTexture (EX9.Texture)'s Reload. so the module won’t reload the files unless their names have changed (in which case the Dir would return the new filenames and the FileTexture would reload them automatically).

so you have 2 options:
*give them files new names
*connect the Reload also to the FileTexture inside the module. but in this case make sure to create a local copy (best using a different name) and not to modify the original

Excellent, I actually saved over the original module but made a back up just in case. It works perfectly, thanks very much for the help. Much appreciated.