I am aware of this bug. It is caused by changed behaviour in jAlbum 28. You must use an earlier version of jAlbum.
This is the current state of Mirage:
- Mirage 10.1 is complete, but requires more testing. This fixes 10 bugs and has 8 enhancements. This is compatible with jAlbum versions 11.6.17 to 27.0.9.
- Mirage 11 is in progress. This is a complete rewrite. It will be responsive. It requires jAlbum 27.
- I previously decided not to release 10.1, but when I realized that 11 could not support old versions of jAlbum, I changed my mind. 10.1 is the final version that works with old versions of jAlbum.
A fix for the bug that you reported would be complicated. I don't want to put a lot of effort into fixing it in 10.1. This bug does not affect 11 because the failing Java code has been removed.