Lights out N95!!

Hi everyone... I have a fully functioning n95, with the exception that there are no lights in the upper slider part.
have replaced ribbon flex cable as i thought this could be problem since the lights are out in upper keypad as well, but no luck! Any ideas as to what fault is would be appreciated. Thanks.

>On my system, "lights out" cycles the color of the background of the center panel, but has no effect on the appearance of the side panels. Is this normal behavior?
I've seen the same behavior on a dual-monitor configuration. Is that what you are running?
I run LR on my large display, with Windows desktop on a smaller display. I've seen some strange behavior that wasn't present in LR 1.0, but haven't had time to pin it all down yet. Regarding your question, if I move LR to the smaller display (i.e., like a one-monitor configuration) it works fine. Unfortunate....this all worked fine in LR 1.0.

Similar Messages

Dual Monitor + Lights Dim/Lights Out

Forgive me if this has already been discussed:
I have 3 monitors, two high resolution main monitors and a 21" Cintiq.
(My normal mode is to open PS on the Cintiq, put all menus on one of the high res monitors and use the other high res monitor for a larger view of the edits that are being made on the Cintiq.)
Lightroom is single monitor, and I can live with that for now but there is one feature - Lights Dim mode and Lights Out mode - that just plain does not work if I want to use the other monitors to open any other application. The monitors without Lightroom are also dimmed or blacked out, so the other application becomes useless.
Here's an example: If I'm running Lightroom on monitor 1 while also viewing one of the Luminous Landscape Lightroom Tutorials on monitor 2 I can't use the Lights Dim mode or Lights Out mode - it dims or blacks the video. Ouch! (Maybe there's a preference setting I haven't found yet?)

I don't think this is a bug. The whole point of the "Lights Out" feature is
to minimize and remove distractions while you are evaluating your images for
color, color casts and exposure. So, I am going to guess that Adobe feels
the other screens to also be a distraction. They could be right. However,
given that I figure a good number of people may not feel that way
(sometimes, not all of the time I am that way. Three monitors here by the
way) needs to add a preference setting that lets you decide which monitors
go "Lights Out" similar to the slide show playback monitor selection option.
Robert

Change the thin white border in lights-out mode?

It'd be nice if you could get rid of this border, or change it to grey or something... I couldn't find any way to adjust this, nor (surprisingly) much mention of it in this forum. Anyway, I find the bright white quite distracting.

I've just started using Lightroom, and whilst in general I really love it, I wasted about an hour looking for the preference to get rid of this garish thick white line in lights out mode.
In principle, lights-out mode is a brilliant way to review a photo without the noise of the interface.
However, I didn't take a photo of an incandescent rectangle, so why is this what I see in lights out mode - especially with darker shots?
I'd be just as miffed if you lined the edge of my picture with little yellow plastic ducks.
It is actually more offputting than the user interface. In the normal view, pictures are shown with a subtle shadow on a neutral grey.Why not use this by default?
If we are not to be able to choose how the edge is treated in lights out mode, then surely it's best to do nothing. I.e. just show the picture, but it would be better still if you could both choose the background picture and even how the edge is distinguished. E.g. 'don't show edge', 'show edge with shadow', 'show edge with line whose colour is ->(pick)' etc.
The other thing which would be good is if, in 'lights out mode', the image actually covered the available screen, or at least there was an option to zoom it to make the best use of the pixels available.
I signed up to this forum just to put this message up. If anyone else out there is irritated by this line, please add a message. Surely this matters to other people too?
please please please please please! (Is this helping?)

Lights-Out Management is not showing full status

Hi,
Since I upgraded my Intel XServe to Leopard, I don't get the full Lights-Out Management (LOM) status any more.
In Server Monitor it is only showing the status for:
- Power
- Temperature
- Blowers
- Security
Not the
- Info
- Memory
- Drives
- Network
Any idea what's wrong?
Thanks,
JO

http://discussions.apple.com/thread.jspa?threadID=1256863&tstart=0

Lightroom 5.2 and Mavericks Lights out bug with dual monitors

I installed OS X Mavericks on my iMac which has a second NEC display connected and that I use as my main display. When I activate "lights out/lights dim" pressing "L" on the keyboard my primary display (NEC) doesn't change at all but the secondary display (iMac) is the one that dims the lights on the interface. Makes no difference if I have the secondary display active as a second screen for Lightroom or not. Lights out/dimm dosen't work on my main interface display.
Anyone seeing this as well with their second display?

I am having the same issue and wondered what was the issue. Thank you for posting; now I remember Lightroom didn't start doing this until I updated to Mac OS Maverick. The only time I don't have that problem is when I physically disconnect my secondary display from my computer.

"lights out" effect on side panels?

On my system, "lights out" cycles the color of the background of the center panel, but has no effect on the appearance of the side panels. Is this normal behavior?

>On my system, "lights out" cycles the color of the background of the center panel, but has no effect on the appearance of the side panels. Is this normal behavior?
I've seen the same behavior on a dual-monitor configuration. Is that what you are running?
I run LR on my large display, with Windows desktop on a smaller display. I've seen some strange behavior that wasn't present in LR 1.0, but haven't had time to pin it all down yet. Regarding your question, if I move LR to the smaller display (i.e., like a one-monitor configuration) it works fine. Unfortunate....this all worked fine in LR 1.0.

How Do I Disable Lights Out Management (LOM)?

I was happily running 10.5 Server yesterday on my Intel XServe. The outside world was able to see my web server just fine.
I updated to 10.6 Server late last night and now my http service is not visible to the outside world (or local LAN for that matter).
Suspecting it has something to do with Lights Out Management (LOM).
How do I get LOM to turn loose of the local IP address of the ethernet interface?

What makes you think the LOM has anything to do with this?
There are about two million other things I'd check before I'd worry about the LOM. In fact I can't even think how the LOM could have have effect.
For a start have you verified the services are running? What do the logs say? Can you hit the web service from the machine itself? What about other services that should be running on the machine?
Have you checked the network configuration to make sure the server's IP address hasn't changed, that the default route is set correctly?
Then there are external factors to consider - maybe coincidences that occurred around the same time as your upgrade and may be masking the problem. Have you checked that your port forwarding is set correctly in your router? Are you sure your ISP hasn't started blocking port 80 traffic?

Lights out white border.

Hello I use the lights out function a lot when cropping images and I find the white border applied when in total black a huge help. I noticed it wasn’t there in this version and wanted to know if it was a preference setting or it was just removed. I have changed the lights out color to white which is nice but I would love to have that thin white border back for black backgrounds.

I have the exact same issue and mentioned it another thread here: http://forums.adobe.com/message/4129130#4129130
For me it is a huge loss. It helps for a number of reasons. Firstly, I like to snap in and out of Lights Out mode during editing to visualise the finished image without distraction. I also like to crop in lights out mode. While attempting to crop it is now much harder to locate the edge of the image under some circumstances. Additionally, it is very hard to discern where the image ends and the background lights out effect begins in images that have dark edges. It's 100% clear to me that this should be an option rather than a feature that is stripped out entirely.
As far as bugs go, I use lights out mode at least once per image during an edit. Often many times. Having used LR since release 1 I have never experienced an artifact left over by the lights out border. I'd very much like it back!

Asking for Lights out Management?

Running 10 iMacs & 10 Min Macs.
We can lock, restart, power off, control, all of that.
But as soon as we try to power on from shutdown, it comes up with ARD not active, and Lights out management not supported.
Obviously LOM has been discountinued with Xserve, but has it been integrated somewhere else?
I dont understand how it can be asking for LOM when it doesn't exist anymore.
Is there a solution to this? How can we power the mac's on using remote desktop?
And yes, before you ask, they are intel based.
Ross.

Hi
". . . but has it been integrated somewhere else?"
As of yet, no. It's not clear if Apple ever will? It has only ever been available on Intel XServes only.
"I dont understand how it can be asking for LOM when it doesn't exist anymore?"
It's not specifically asking for it as clearly LOM does exist but not on your hardware. ARD supports this feature if you're supporting hardware that does which can only be Intel XServe models.
"Is there a solution to this? How can we power the mac's on using remote desktop?"
Yes - you walk round to them and power them on. You can't use ARD to do this. You can however use ARD to send a terminal command that will set a power management schedule that goes some way in doing this for you. Mind you if you're having to go round to them all to switch them on you may as well apply the schedule settings locally. In an ideal world and assuming you have a mac server you can either define the settings you want in the build image you use to push out to rest or apply the settings using MCX.
Depending which method you use the Macs will have to be switched on at some point.
Questions specific to ARD are better asked in the dedicated ARD Forum here:
https://discussions.apple.com/community/servers_enterprise_software/apple_remote _desktop
HTH?
Tony

Lights Out Management...

Hi all,
I'm having troubles getting LOM to work on my new Intel XServe. During the Setup Assistant, without knowing anything about this feature, I happily skipped setting it up, thinking that it would be easy to enable it later (if deemed useful). The server is installed as a gateway (eth0 is WAN and eth1 is LAN), it is running local DNS, NAT, DHCP, Firewall and I can access the Server Admin and Workgroup Manager remotely using the domain name that points to the server.
Now when I go to the Server Monitor locally on the server and try to connect via. 127.0.0.1, it seems to connect briefly (i.e. the status lights at the bottom of the app change to green for a second), then the server listing itself disappears from the Server Monitor (i.e. the interface appears that I've never added a server). Now, if I try to add the server again (using the same local credentials), it says that that server has already been configured. The only way to remove this vanishing entry is to relaunch Server Monitor and delete the offending entry in the few seconds before it connects and vanishes again.
I've tried using the "Setup Local Server" menu option in the Server Monitor, but it's not clear to me what these values should be and everything that I've tried so far doesn't work. Should the port 1 have the same settings as my WAN port and port 2 the same as my LAN port?
Any help would be appreciated as guessing and testing isn't getting me too far and I'm concerned that by skipping the configuration of LOM in the Setup Assistant, I've made this impossible to turn on now.
Thanks for any suggestions,
Mike P

Thanks for this.
I've read that Apple doc already (to no avail), but thanks for the link anyways, others might find it useful.
Just so I understand your suggestion, when configuring Lights Out Management for LAN access, I should use Server Monitor -> Setup Local Server and change port 2 (I assume that port 2 would correspond to eth1 which is my LAN port distributing addresses in the 192.168.1.* range) by picking a valid IP within that range (e.g. 192.168.1.100), and filling in my subnet mask and router information (255.255.0.0 / 192.168.1.1 respectively)? This would then allow access to the server through Server Monitor while connected locally to the LAN via. 192.168.1.100?
Does this imply that for WAN access to Lights Out Management I would need my ISP to provide me with 2 static IP addresses (one for Lights Out and the other for web / internet services)?
Thanks again,
Mike P

Lights Out Management - Crashing / Resetting

It appears that Light-Out-Management is crashing, and I would like to know if there is a way to restart the LOM controller manually.
I have a Quad-Core Intel Xeon Xserve (XServe2,1).
- 2GB of memory (from factory)
- 80GB boot drive, 1TB drive modules in bays 2 and 3.
- 1 power supply
- no expansion cards
- connected to storage arrays via Firewire 800
- both ethernet ports are in use, 1 connected to the internal network via gigabit ethernet, the other to the fallback ISP
I have have configured Lights Out Management via Server Monitor. It typically works well, delivers information, sends notifications when needed. The lights-out management controller seems to crash or stop functioning regularly. I can only tell this has happened when I stop receiving notifications and the machine no longer appears in the Server Monitor list. The network connection to the machine is up and all other services seem to function normally. If I remote into the machine and do "Configure Local Machine" in Server Monitor, I get the marble of doom for about a minute, and when the Configure Local Machine interface does appear, all of the settings are zeroed out. (i.e. 0.0.0.0 for IP, subnet and router. username and password are blank.) Trying to re-enter the settings delivers an unhelpful error.
Restarting the machine does not help, when it reboots the LOM settings are still zeroed out. However if I shut down the machine and have the power disconnected for a short time (until the back panel lights go out) and then power up the machine, everything goes back to normal.
This is the only Intel Xserve in the rack, and the only one running 10.5. All the others are G5s running 10.4 or Ubuntu. Server Monitor runs well on the other OS X machines.

This problem has existed since the Intel Xserve was released. I haven't found a solution yet. The LOM usually comes back when I remove power from both power supplies for 15 seconds or so, but I'm not inclined to shut down my servers as frequently as the LOM quits.
It would be valuable for us if it worked, since its ipmi compliant.

Lights Out Management - not accessable outside subnet

Have a new out of the box XServe and have configured the Lights Out Management Card for one interface port. Works great locally and on the same subnet, however, outside the subnet can not connect to it. Server is in a layer 3 environment, does the Lights Out protocol use broadcast packets (as those could be what is being blocked).
Lights Out Port has IP, Subnet mask, and Gateway configured properly (double checked, and triple).
Thanks

i 'believe' LOM does not work outside the local subnet. annoyingly.
not even sure why.
[quote]Using Server Monitor
The Xserve comes with the Server Monitor application. You can find Server Monitor in
/Applications/Server/ and on the Admin Tools disc that comes with the Xserve. You can
use Server Monitor to:
Â Check the current status of the Xserve and its components, including
Â Drive module status
Â Power supply status and system internal voltages
Â Network interface status and activity level
Â Temperatures of critical internal components
Â Cooling fan status
Â Review basic Xserve information such as
Â Uptime
Â Mac OS X Server version running on the Xserve
Â Amount and type of memory installed in each slot
Â Model and capacity of each drive module
Â Shut down, start up, or restart the Xserve
Â Generate an Apple System Profiler report for the Xserve
Â Send email alerts in response to changes in the status of the Xserve
You can run Server Monitor on the Xserve or on any computer that can connect to the
same network. [/quote]
notice the last line....
if anyone figures anything out i'd be grateful. i thought i'd use the second enet int'fce and configure it for LOM, giving it a second WAN IP, but i abandoned that idea for some reason.. can't remember why that wasn't working....
also, this may help: http://www.afp548.com/article.php?story=20070211101829496
Message was edited by: dtich
Message was edited by: dtich

Feature Request: Lights Out Mode / tagging display.

Problem: "Lights out" mode hides tags - need to enable option to allow tags to be seen during lights out mode.
I love editing down photos to selects in lightroom, I love using the (L) LightsOut Mode to set the screen(s) to black.
however, when I do so, it hides tagging data as well. I would like an option (keyboard shortcut) to toggle the display of stars/flags/colors on and off.
Possible solutions:
Flags and stars are simple graphics that could appear over the image or beside/under it in tiny non distracting ways. colours could be the same or perhaps have the outer border turn to the selected colour.
ADDITIONALLY: I would love to see an option to "LIGHTS OUT" the second monitor indipendantly of the main. (this could be done in the second monitor drop down menu)

Originally Posted by Anarion
It's cool that these cards have headphone out but there's one rather large issue with how it that you can't use line out in headphone mode.
For example, if someone wants to use more powerful or better suited external headphone amp, he has to use already amped headphone out if he want best virtual surround/HRTF in games. The headphone out is slightly worse in quality too so it makes no sense to use it in above case.
Some headphones sound just too **** loud when plugged in the headphone amp so line out is only option. However, while that works just fine for normal stereo music, it is not optimal solution for games because the HRTF is way less accurate.
So, how about adding "Headphone mode" tick box for line out (or "Use line out plug instead" tick box in headphone mode)? It would solve various issues and fix one of the most annoying problem with Z/Zx/ZxR cards right now. It should be rather simple (i.e. same settings as headphone out but different output plug) thing yet would make massive difference in usability.
Hi Anarion,
I have relayed your product feature request to the designated department.
Will keep you informed for any updates on this thread, fingers crossed!
Cheers,
Philip-CL

X2100M2 Embedded LIghts Out Manager best practice

Hi guys,
I'm in worry about the best practice of configuring network interface on a X2100M2 Solaris 5.10 for the Embedded LIghts Out Manager. Hope you can help. I haven't find any documents of it which explain the best practice.
Here is the situation :
I've have 4 network interfaces but I only need two of them. So I decide to use the bge0 and the bge1 interfaces.
bge0 is the server interface with an IP with .157
bge1 is the ELOM interface with an IP with .156
In the past, it was the reverse : bge0 was the ELOM with .156 and bge1 was the network server int. with .157
Could you please guys let me know what is the best practice? Does the int.0 must be the server one? Is it possible to have network problem with this kind of configuration?
Thanks
Cheers,

hi guys,
No one have a clue? I've got some dukeDolars to offer...
Tks

Lights out - need black border for softproofing

The Lightroom 4 Beta has a white (and not black) background for previewing photos. In another discussion (Lights Out White Border) it was stated that this was intentional, not a bug. Many people requested the Black border be brought back, and the thread is "Assumed Answered". We are given the impression that White is what it will be!
In softproofing it is critical that we have a black screen in order to view the effects of Simulate Paper & Ink (Reference: Real World Color Management 2nd edition by Bruce Fraser)
Please bring back the Black Border! We NEED it!
Scott

SB Anderson wrote:
In softproofing it is critical that we have a black screen in order to view the effects of Simulate Paper & Ink (Reference: Real World Color Management 2nd edition by Bruce Fraser)
I think if Bruce we alive, he would actually change his mind about that...the reason he suggested a black screen was so you weren't influenced by the change from soft proofing off to soft proofing on in Photoshop. He suggested going to a black screen and hitting tab to hide Photoshop UI elements.
What the current soft proofing in Lightroom is doing is showing Paper White as the area surrounding the image area just as you would see in a final print. The LR UI is already dimmed down to not influence your view of the image. As a result, in Lightroom you really don't need (or want) a black screen.
Your eyes will use the paper white to adapt to the paper as the brightest area in your field of vision. This will allow you to better judge the relative brightness of your image. Give it a try...the soft proofing in Lightroom is, I think superior to soft proofing in Photoshop. New tools need new ways of using them.
BTW, Bruce was a good friend and partner in PixelGenius. I've also coauthored two books with him and have a real good idea of the way Bruce thought–and learned a lot from him and still do.

Lights out N95!!

Similar Messages

Maybe you are looking for