Loading rgba_dry error

Hello :)

I am trying to load an rgba_dry layer but I always get an error from Motion IO.

I tried with the LOAD event in a json file and I also tried with the command line flag -batch-in-rgba_dry.

Here is the error:

I tried providing the path in many ways (absolute, relative, forward slashes, back slashes, no spaces, etc), but I never get a success.

I am able to use the LOAD_MASK event however. So I think that the way I provide paths is ok...

I am now wondering if the file needs to be formated in a specific way?

Any ideas on what could be my issue? (FYI: I am on Windows 11, Motion IO 7.2.2)

Thanks in advance!

Hi @9cLL3xn0xqGS,

The error message means that the file doesn't exist.

Could you please try to use the filename's absolute path? When you use a relative path, e.g. 'Original_MG.png', you need to run Motion IO in the folder where the file is located. When you use an absolute path, e.g. 'C:/Data/Original_MG.png', you can run Motion IO from any folder and it should still be able to locate the file.

Hi Michal,

Thank you so much for your answer :)

I have done some more testing and I finally had a success case. Here are my conclusions:

• The paths can be absolute or relative, they both work (if Motion IO is started in appropriate folder as you mentionned).
• The paths need to use forward slashes. Backslashes (Windows' default) will escape characters and will be problematic.
• The rgba file must be saved as an "exr" file. I didn't have success with other formats like "png" and "tiff".
• The rgba file must have an Alpha channel (just rgb channels will not work, it needs rgba).
• The rgba file must be of the same size and proportions as the canvas, otherwise it will not load the image correctly.

These are not big issues once we know about them, but maybe some of those limitations could be fixed in future versions?

In the hopes that this information can help :)

Thanks again!

Thanks for the summary, @9cLL3xn0xqGS!

In the next 7.2.3 release imported images are scaled automatically to the canvas size.

I've added your comments about relative paths and forward slashes to the Motion IO doc.

We indeed have a bug in Motion IO causing failure importing other than exr images. We've added it to our task list. Thanks, we didn't know about it.

Awesome!

Thank you!