Don't know if this issue is generic, ro specific to my monitor, but..

On my monitor (at least) the 'energy saver' setting in Blanker doesn't actually send the monitor into energy saver mode, it simply displays a black screen (and leaves the backlight lit).

My monitor is a Samsung Pebble 932MW using the DVI input from Mac-mini G4 1.5GHz with MorphOS 2.5.

Anyone else experience this?

[EDIT - Apple Keyboards suck]

[ Edited by boot_wb on 2010/6/18 19:04 ]

Yes, I have the same problem with my Mac mini 1.5GHz and DVI, but with VGA-cable it seems to work. Funnily my Mac mini 1.42GHz doesn't have the same problem, it works fine with same cables and monitors. So, I don't think it's monitor specific, but could it be 1.5GHz specific? Anyone else?

And for curiosity, if you have overlay graphics on screen, is it left visible when rest of the screen gets black (but not really blanked)? Like mplayer with overlay video driver in use and paused...

<!-- me flips back to ambient screen and does test -->

Yes, overlaid graphics do still stay on screen, at least in windowed mode.

I usually have mplayer running on its own public screen, and seldom pause video long enough for the monitor to go to sleep, so it's not something I would normally notice.

On a different note, I notice that the volume buttons on the (Cr)apple A1048 keyboards are now mapped to the global volume controls - nice! Not sure if the mapping is new, or just wasn't active for me before due to the lack of global volume control (thanks for that btw guys).

Hmm... it would be nice if that eject button also worked... (hint, hint!)
Would it take much work to extend the 'sample' capability of ambient's keyboard preferences to allow mapping of commands to media/extended keyboard function keys?
At the moment, neither 'eject' nor any volume control buttons are sampled.

[ Edited by boot_wb on 2010/6/18 19:25 ]

Hi,

my Samsung SyncMaster 2494HM also doesn't goes into energy saver mode.
(MacMini G4 1.5GHz)

Booting with MacOSX, the monitor goes into energy saver mode, so here it seems not be a hardware problem.