Brandon Allen

BrandonA

About Me

専門知識
Not Specified
Location
Not Specified
ウェブサイト

Connect

Recent Forum Posts

Image Magick not functioning 2020年5月28日20:22

Hi Akira,

In order to make things easier on Mac, I've added support for a PDG_IMAGEMAGICK_DIR variable. Instead of setting the PDG_IMAGEMAGICK variable, please set the PDG_IMAGEMAGICK_DIR variable to the location of your ImageMagick binary folder (e.g. ~/imagemagick/7.0.10-14/bin). This will allow the node to find the executables of all the various subcommands (convert, montage, etc.).

This fix will be available in the next Houdini daily build of 18.0 (18.0.481 or later).

Image Magick not functioning 2020年5月26日11:22

Hi Akira,

Glad you found a solution for now. The reason for this is that Imagemagick may be invoked in different ways depending on which installation of the program you are using.

For example, in some installations you call magickdirectly, and specify the subcommand as an argument:

magick montage
magick convert

In other installations, you call the subcommands directly:

montage
convert

I believe that some installations also support both. It looks like the first mode of operation is not being handled on MacOS (invoking the subcommand as an argument to magick. I will file a bug for this. I will also file a bug to update the node documentation with more clarification about the different ways that Imagemagick can be invoked.

Are you able to call the subcommands directly with your installation? If so, the easiest setup would be putting the Imagemagick binary folder on your system path.

Lastly, there will be some work done on the Imagemagick node to make this easier and more seamless for the user.

HDA processor parameter referencing 2020年5月15日13:10

You should be able to set “Create File Inputs” to an expression. E.g. if you have an attribute called “requires_inputs” you, should be able to set the “Create File inputs” parameter to “@requires_inputs” and HDA Processor will handle the rest.

1) This is possibly because the Python Script is adding attributes during the Cook step (guessing from the screenshot). Try setting the “Evaluate Script During” parameter to “Generate” on the Python Script node if it is not already set to that.

2) The HDA Processor service should be working. Can you send the errors as well as a screenshot of your service configuration in the PDG Service menu dialog?

3) This is a known issue with the expressions. I agree that at the minimum, all parameters should be accessible. I will make this change.

Built-in nodes for making it easier to work with attribute arrays is currently on our list of planned features.