Save 'Single Frame' dialog - `OpenEXR` support

Question

Save 'Single Frame' dialog - `OpenEXR` support

Closed this issue 3 months ago · 9 comments

nothing urgent, but I thought it's worth a report: When I try to save the current frame using the 'Single Frame' option, I always get the OpenEXR dialog afterwards, regardless of the file format I typed before. And more importantly, I get the following error message when saving the frame as OpenEXR: ERROR: [save] /Users/p2or/Desktop/test.exr: Unsupported video - Is this a bug or is it simply not supported?

MacOS 14.3, mrv2 64 bits - v1.0.2 - Built Jan 23 2024 03:36:21

Cheers,
Christian

Answer 1 · 2024-01-31T20:01:09.000Z

The dialog is normal. It appears for any format, but it should remain ghosted for any format that is not .exr.

The "unsupported video" is likely you trying to save a movie file as an EXR or some other RGB/A format. The movies are in YUV space that's why it reports unsupported video format. You can work around it if you select Show Annotations which will, besides saving annotations, capture each frame as RGBA and save it as such.

If that does not solve your issues, let me know.

Answer 2 · 2024-01-31T20:30:33.000Z

Hi @ggarra13,

thanks for your feedback.

The dialog is normal. It appears for any format, but it should remain ghosted for any format that is not .exr.

Yep, the OpenEXR options are greyed-out for all formats I tested. I'd expect some format related settings like in version 1 though - feel free to ignore.

The "unsupported video" is likely you trying to save a movie file as an EXR or some other RGB/A format.

Unfortunately, I get this error message when I try to save a single frame to EXR, although all other formats seem to work.

Cheers,
Christian

Answer 3 · 2024-01-31T20:50:20.000Z

Hi, @p2or

Unfortunately, I get this error message when I try to save a single frame to EXR, although all other formats seem to work.

I can confirm this as a bug. You can currently work around it if you select "Save Annotations" in the popup options.

Answer 4 · 2024-02-01T12:35:25.000Z

Find a fix in the beta directory of sourceforge at (without NDI or pyFLTK support):

https://sourceforge.net/projects/mrv2/files/beta/

There's also a beta for M1 machines (Darwin-arm64) which I would like you to test if you can and report if it is faster than the Intel version (Darwin-amd64).

Answer 5 · 2024-02-01T17:55:42.000Z

Hi @ggarra13,

thanks. I've just installed mrv2-beta-Darwin-amd64.dmg. When I try to save a single image as EXR, mrv2 unfortunately crashes immediately.

There's also a beta for M1 machines (Darwin-arm64) which I would like you to test if you can and report if it is faster than the Intel version (Darwin-amd64).

I am happy to help. Is there anything I should look out for? In general, it feels a little faster. I've also tried to save a single frame to EXR:

Does this help?

Cheers,
Christian

Answer 6 · 2024-02-02T17:12:17.000Z

Find the M1 (arm64) version without NDI support at:

https://sourceforge.net/projects/mrv2/files/beta/

It should also fix the EXR saving.

Answer 7 · 2024-02-04T23:51:24.000Z

v1.0.3 has been released with the fixes on both AMD64 and ARM64.

Answer 8 · 2024-02-05T13:29:03.000Z

Hi @ggarra13,

as of version 1.0.3, saving the frame as OpenEXR works as expected. Great, many thanks for your quick fix.

Re ARM performance: I have tested a 4k image sequence (OpenEXR) as well as regular 4k-Clips (.mp4) and there is no noticeable difference between the Arm64 and Amd64 version - both are a little jerky.

Does this help?

Cheers,
Christian

Answer 9 · 2024-02-05T17:56:53.000Z

Re ARM performance: I have tested a 4k image sequence (OpenEXR) as well as regular 4k-Clips (.mp4) and there is no noticeable difference between the Arm64 and Amd64 version - both are a little jerky.

Does this help?

Yes, that helps.