When it should do a dissolve between lower thirds, you have to use two lower thirds layers and to switch em in a z-pattern. See demo here:
Instead of Transition Placer + Placer use two lower thirds layers and variants in both of it.
No…you’re missing the point. If I have all my variants listed on my MIMORemote, I should be able to push any variant button and it should dissolve out the previous variant and dissolve in the new one.
You’re automation solution works fine for 5 variants. However, most of my shows have up to 75 variants. That’s a lot of additional automation.
It’s a pattern:
=> 1 appearance
while(on, sleep, off, sleep)
while(off, sleep, on, sleep)
=> last appearance
My “automation” was just to demonstrate the switching itself, not to show how you should program your script.
Write a script if you can, to automate it by yourself. Even to handle your Web Control Buttons. Maybe the cycleThroughVariats-Endpoint could bring you the clue.
Btw, if you just need it within WebControl, just switch the former variant off, when switching the next “on”.
At the buttons you’re able to configure multiple actions. But you still need two layers to do a dissolve.
Layer A (odd)
- Variant 1
- Variant 3
- Variant 5
…
Layer B (even)
- Variant 2
- Variant 4
- Variant 6
…
Any into any:
Use automation to load the content into a dynamic Variant of A, also in B. 
Another Option:
Use the layer thirds as a preset and modify it with Quartz Composer to your wishes. But as told: Variants are not Layers.
Unfortunately you’re still not following the real-world logic. I’ve been directing broadcast television since 1974 and my request is NOT unusual. But having to jump thru hoops to make the program do what its supposed to is unrealistic.
2 Likes
Yes, so use different layers to have a dissolve between lower third layers. Variants are not layers, so a dissolve between of 'em will never happen. For ease, I’d recommend to use two Layers. Push the content with a script into it.
By the way: My former post discribes several ways to fulfill your wish.
Finally, you could build your dynamic lower thirds by using other layers, like Static Text (without background or with background) and certain Pip window-Layers.
Important:
Variants of the same layer are not able to run the same time. Maybe you missed that point about the logic.
Maybe you’re planning your document the wrong way. 
@lorcott Here a demo. Without scripting, but it works. With scripting it would be dynamic and much easier, however:
Try it yourself:
You could try to do something with an ATEM-ME, but with mimoLive is something like this much easier.
Use layers, not variants:
This is like a button works: (Switch one LIVE and all others OFF)
Make for each layer a button:
Add as many buttons/layers you need to switch to whatever should be showen. Without scripting it’s lots to configure, but possible.
Just a hint:
If you really have more than 70 variants of a layer (or layers of the same “function”), it would be better for the performance of the whole system to work with scripts and two layers, which will be filled with content and switched on demand/keypress/buttonpress by/through a script. Plus: a 100%-the-same-time-transition is only possible if you use scripts.
If you also need something like this at the main program window, create layerSets instead of WebControl Buttons.
In lot’s of cases, mimoLive is an out-of-the-box-solution. In others it’s simply restricted by imagination and/or knowledge about the possibilities.
And finally, this isn’t a bug. Please close the thread, @stefan_boinx . Thanks a lot. 
Official statement: