Since {inputfilename} expression has no more used, I used @filename attribute instead, but I got only 2 types of filename pattern ... not file names(frame000001.jpeg, frame000002.jpeg, ...) but directory names(brimstone_images, stock_pictures). I also tried pythonscript node using below, still got same result.
Just checked this fast, as far as I understand you can use `@filename`. You have to use backticks to isolate the expression within a string parameter. @filename is automatically made by a file pattern TOP, so I assume you have something similar in your network. Alternatively `@pdg_input` gives you access to the implicit top attribute Input. Hope this helps you out Cheers!
Technical VFX artist @ Housemarque / Sony Interactive Entertainment
Here is whole capture. I set each parameters just like this tutorial, and changed only OutputFilePath item. Using @pdg_input instead of @filename, result changed a little but it is still incomplete.
also I tried each "Generate When" item "Automatic" to "Each Upstream Item is Cooked", got same result.
Reading the documentation for the imagemagick node (https://www.sidefx.com/docs/houdini/nodes/top/imagemagick.html [www.sidefx.com]) there seems to be an attribute called {inputfilepath} which you might be able to use. As you mentioned, the {inputfilename} seems to be gone. Alternatively, you can also use the @output_dirs attribute that should come from the file decompress node to point to a path and then use some globbing (for example *.png) to select all files and expand them to separate work items. You can then get the filename attribute correctly. For as far as I can read here, the instructions in the tutorial you are following do not accommodate for the removal of the {inputfilename} attribute, so I guess you have to dive a little deeper now By holding middle-mouse button on a work item you can easily inspect the attributes it holds and debug that way.
Technical VFX artist @ Housemarque / Sony Interactive Entertainment