XnView Software

My guess is that there's something going on with the M1 versions, Rosetta, or Big Sur; the latter might be corrected in the newest version of Mac OS. I'll keep this thread in my browser until this is resolved. I do have another Intel machine running Big Sur; so, I might have a look there to see if ...

How about this. Take the ORF file from the link.
Load it into the batch convert.
Apply many transformations, change them a lot, do it for some time. (20 minutes) It needs to redraw the file many times on each successive change.
Watch to see if you're having the memory creep up in activity monitor ...

I don't think it'll make much of a difference if I use the ORF files from the link or ORF files from my drive. The problem isn't really visible with 50 ORF files. It's more like 500 ORF files. Memory management is different on M1 machines. Are you using a M1 mac? Maybe that's it.

I can make a ...

Here are my setting > Formats:

I have:

XnView MP MacOSX
Version 0.99.1 64bits (Sep 23 2021)
Libformat version 7.95

I could not find "Load format settings".

Well, I have thousands of RAW files... which one? I really don't think it's a specific type of RAW file.

Anyway, here's a link to some RAW ORF files on dpreview:

https://www.dpreview.com/sample-galleries/2955274204/olympus-om-d-e-m1-mark-ii-iceland-sample-gallery/

Look on the right-hand side and ...

I just retested with multicore unselected and batch convert exhibited the same behavior. My thought is that somehow the loop is not clearing memory after each save. The end result is a memory creep that never clears unless xnview is closed. After converting enough files, OSX will prompt "Force quit ...

Hello Pierre,
I think this happens only with RAW files. I tried with only jpg and was unable to reproduce it (multicore selected).

Here are my exact settings for the RAW export:

There were multiple formats: ORF, RW2, jpg
Outputs were all jpg

Xnview was successful, just with a limited number of batch converts and I had to quit to liberate that memory.
I'm fairly confident you can recreate this on any M1 mac running Big Sur.

I should have added that it ended up using 34GB of memory and the ONLY way to lower the memory usage was to quit the app.

Upon performing a Batch Convert of some 500 images, I noticed excessive usage of memory. If I convert too many images, I eventually get a message asking to force quit an app to create more memory. Below is an screenshot of the memory usage:

Thank you Pierre for getting back to me. I've found a workaround by exporting the portrait ".ORF" files separately and then making a preset to rotate them... not ideal in that some end up upside-down. Thank you for your help. I love this program as it's just so powerful and unique.

After more research, it would seem ALL ".ORF" files (from Em1 ii, E-PL9, and E-P7 tested) batch export wrong when photo was taken in portrait. When converted to ".DNG" before export, they do fine. Is there some way to add this support?

I'm still having a problem with output rotation in a batch convert. My RAW Olympus E-M1 mark ii (.ORF) portrait photos are not rotating on batch convert to jpg. Not sure why. The photo displays fine everywhere EXCEPT on batch export (finder, inside xnview, etc.). I'm currently running the latest ...