If you put MPlayer in the fullscreen mode, it opens on its own screen, which is in the same resolution as your desktop and the image gets scaled by overlay so it doesn't make any extra cpu load. But as it's on its own screen, you can swap screens with command-m etc and let the mplayer be there on own screen without making things harder way. But when running it in windowed mode, I keep it on the Ambient screen...

In general, I like to have bigger apps on their own screens, especially if I want to run them fullscreen. Like OWB, Showcase, etc... if they have more of their own windows open, they stay cleanly on their own screen and you don't have to mess with them all on the Ambient screen. It's quicker to swap between programs that way. Also some legacy programs that don't use MUI (and MUI's way to minimize/iconify) it's better run them on their own screens IMHO. Like FinalWriter, Hollywood Designer, PPaint, ArtEffect, etc in my case.

And if a program doesn't benefit from enhanced mode effects, you can run them on non-enhanced screens and save some graphics memory by that. Non-enhanced screens also scroll their contents little quicker, so OWB etc can benefit that. But otherwise I usually keep screens in the same resolution and depth, unless some legacy program requires 8bit modes.


[ Edited by jPV 15.10.2019 - 21:44 ]