I gave up on MM2 last year because of how bad the transitions looked. Recently I had need of something like MM and decided to try again and had the same CPU load and terrible transitions until I found this thread.

With the latest Raspbian Stretch, MM2, and a downgrade of electron to 1.4.15 it works far better. Barely a spike on the CPU meter.

This thread is far too long. Considering the impact of this solution, it really should be in the FAQ on github. The only reason I even noticed this thread is due to the weekly Email summary.

I gave up on MM2 last year because of how bad the transitions looked. Recently I had need of something like MM and decided to try again and had the same CPU load and terrible transitions until I found this thread.

With the latest Raspbian Stretch, MM2, and a downgrade of electron to 1.4.15 it works far better. Barely a spike on the CPU meter.

This thread is far too long. Considering the impact of this solution, it really should be in the FAQ on github. The only reason I even noticed this thread is due to the weekly Email summary.

I’ve found that if I have multiple iFrames in one position, i.e. ‘top_left’ and fade one out completely then start the fade in on the next one, I get the fade in/out to work properly which is my desired outcome.

If I have single iFrames in the left and center and try to fade one out and the other in, it always pops in. That needs to be fixed but I couldn’t identify a cause.

I’ve been fighting with this as well. @tosti007 I noticed the same thing in the inspector. Still looking for a solution but digging into the guts of this thing is time consuming… I appreciate the test results, that saved me some time chasing ghosts.

// Show the desire modules
var showModules = MM.getModules().withClass(page);
for (i = 0; i < showModules.length; i += 1) {
    showModules[i].show(this.config.fadeTime);
}

If I figure it out I’ll post an update. I just wanted to let someone know that I’m experiencing the same issue.