Thanks - I believe this latest approach is the closest to what users expect.

First, there's no reason to go back to jAlbum 19. That will have no effect on how an Animatics album displays itself. The jAlbum core doesn't produce a single line of HTML, CSS, or Javascript - that's all done by the skin. In short, you can update to jAlbum 38, but continue to use an older version of Animatics.

I just ran a quick test of Animatics, and the display of the Ken Burns effect is smooth as silk, and the images fit the browser window without issue. The image titles don't appear to be unusually large.

I think you may be running into a situation in which the browser is stubbornly using a cached version of the Javascript file that powers the album, and maybe even a cached version of the CSS file. Do some aggressive cache-clearing of your browser before concluding that there's a problem. A simple CTRL-F5 might not do the trick - you need to get into the browser settings and tell it to delete all cached images and files (you can leave everything else alone, like cookies, history, passwords, etc.).

I can't speak to your custom code, since I don't know what that consists of. But since there have been so many changes since Animatics 2.1.6, I'm not at all surprised that the custom code no longer works.

Does your result with the new version look the same as it does on my website surrealismus.org?

Exactly what you experienced with my settings happened to me as well after upgrading — both on my screen with different browsers and on my smartphone! The images no longer fit entirely into the browser window at the end, the Ken Burns effect runs very choppily, the image titles are far too large, and my custom HTML code stopped working. After reverting to jAlbum 19 Pro with Animatics 2.1.6, everything worked smoothly again, just as before.

And here's a movie of the show in my browser:

(screen video removed)

No choppiness, no overly-large titles, no images that don't fit (the full-sized original of the 1937 Delage isn't big enough to fill the screen, so of course the scaled image isn't large enough to do that, either).

Those would not be acceptable to me. Fortunately, I'm seeing neither of them.

I've given it the ultimate test, an album with only the original, full-sized, multi-megabyte images. Not even any scaling. They're typically around 4000x3000 px, and anywhere from 4MB to 7MB each. Viewing them in the U.S., on a 7-year-old desktop PC with an obsolete WiFi card, from the jAlbum AWS server (in Stockholm, I believe), I get no stuttering, no choppiness, no problems.

(test album deleted)

There's something wrong either with your computer or your internet connection. I can't diagnose them remotely. Best of luck.

I get a perfectly smooth, stutter-free show, on multiple platforms. But oddly, Firefox doesn't do well with it, whereas Brave and Chrome are fine. Firefox usually provides the best rendering of a site. Surprising.