Strange monitor behavior

My Apple menu has started listing everything twice:
Shutdown
Shutdown
Restart
Restart
Sleep
Sleep
Log out
Log out
And everything I select on the desktop has a great big rectangle around it. What's up?

Duh! It was universal access! Had speakers turned down so couldn't hear voice over. Must have inadvertantly turned on with +F5 shortcut.
I feel like a great big, Apple certified prat

Similar Messages

  • Strange ZWSREG behavior

    We are in the middle of a rollout of about 300 new machines. (used sysprep in the image) The first 100 are doing something strange. They boot up get renamed and join the windows domain with their new name, but register with ZEN as the randomly generated Microsoft name. (usually someting like N-398477634379d979) I deleted the workstation object, unreged and rereged the computer, but it always reregisters with the randomly generated name. What gives? I found a TID that said this was fixed by an update on the latest desktop agent, but that I could work around it by deleting the incorrectly named object and waiting for the machine to reboot, However it still registers with the wrong name. Any ideas? Thanks.
    J. Daniel Treadwell

    But these are new computers. They should not have image safe data yet. I tried it, but got the same result.
    Originally Posted by Craig Wilson
    Try running ZISWIN -R when you unregister.
    My guess is that it's pulling the old info from Image Safe Data.
    Craig Wilson - MCNE, MCSE, CCNA
    Novell Support Forums Volunteer Sysop
    Novell does not officially monitor these forums.
    Suggestions/Opinions/Statements made by me are solely my own.
    These thoughts may not be shared by either Novell or any rational human.
    "jtreadwell" <[email protected]> wrote in message
    news:[email protected]..
    >
    > We are in the middle of a rollout of about 300 new machines. (used
    > sysprep in the image) The first 100 are doing something strange. They
    > boot up get renamed and join the windows domain with their new name,
    > but register with ZEN as the randomly generated Microsoft name.
    > (usually someting like N-398477634379d979) I deleted the workstation
    > object, unreged and rereged the computer, but it always reregisters
    > with the randomly generated name. What gives? I found a TID that said
    > this was fixed by an update on the latest desktop agent, but that I
    > could work around it by deleting the incorrectly named object and
    > waiting for the machine to reboot, However it still registers with the
    > wrong name. Any ideas? Thanks.
    >
    >
    > J. Daniel Treadwell
    >
    >
    > --
    > jtreadwell
    > ------------------------------------------------------------------------
    > jtreadwell's Profile: NOVELL FORUMS - View Profile: jtreadwell
    > View this thread: Strange ZWSREG behavior - NOVELL FORUMS
    >

  • Capturing DVCAM in FCP 6.0.2 and encountering strange capture behavior

    I have FCP 6.0.2 and OSX 10.5.2 and QT 7.3.1. I have been capturing several DVCAM cassettes using my Sony DSR-20 deck. Although I have done this countless times before in earlier versions of FCP, I am encountering some strange repetitive behavior. I am capturing 30 minute clips one at a time. When I use batch capture it will cue the tape up properly to the in point...and then start capturing until it gets to about 10-12 minutes in, and then capture unexpectedly stops, no dialogue box, the tape rewinds and starts capturing again from the original in point. On this second capture, the tape sails past the 10 minute mark and keeps going to the end of the 30 minute clip. It then stops, gives me the dialogue box that it has successfully captured. And it has.
    But every DVCAM tape I captured today exhibited the same behavior. Capture would be successful until about about 10 minutes in, then FCP aborts (no dropped frame message, no dialogue box) rewinds the tape back to the in point, tries again, and this time succeeds with the second pass capturing the entire clip. Note at the 10 minute mark there is no scene change or no camera start/stop.
    Have other users experienced this issue? And if so, is there a workaround or a possible patch forthcoming from FCP?
    Many thanks,
    John

    Yes, each tape has an in and out point defined. In my 6 years of editing with Final Cut and DVCAM tapes I've never encountered this issue before in the capturing process until now. I will have to see in future weeks with other captures whether this is an on-going issue or not, but at least I can capture for now.

  • Bug in my code or strange memory behavior ?

    Hi, Guys !
    It's been a while since I post something in this forum - trying to use your help when it's really needed.
    So, here we go ...
    (we use Oracle 8.1.7 on Unix box and SQL * Plus 8.1.6)
    While back I wrote "core" PL/SQL package that resides in let's say DB1 database. It has RECORD_EXISTS_FNC function designed to dynamically check If the record exists in certain table/view. Assumptions are that you pass in :
    Table/View name, Column name, and unique numeric value (because by DBA rules all of our Tables have SEQUENCE as a Primary Key. And I plan soon to put in overloaded function to accept unique character value)
    Also every Table has SYS_TIME_STAMP and SYS_UPDATE_SEQuence columns that populated by Trigger before Insert/Update representing Last Update time_stamp
    and how many times record was updated within same second.
    (in case more than one User updates same record in same time - that was written before Oracle had more granular date/time). So function has SYS_TIME_STAMP and SYS_UPDATE_SEQUENCE parameters (optional) accordingly.
    And It looks something like :
    FUNCTION RECORD_EXISTS_FNC
    (iBV_NAME IN USER_VIEWS.VIEW_NAME%TYPE,
    iPK_FIELD IN USER_TAB_COLUMNS.COLUMN_NAME%TYPE,
    iPK_VALUE IN NUMBER,
    iSYS_TIME_STAMP IN DATE DEFAULT NULL,
    iSYS_UPDATE_SEQ IN NUMBER DEFAULT NULL) RETURN BOOLEAN IS
    TYPE REF_CUR IS REF CURSOR;
    CR REF_CUR;
    i PLS_INTEGER DEFAULT 0;
    vRESULT BOOLEAN DEFAULT FALSE;
    vQUERY USER_SOURCE.TEXT%TYPE;
    BEGIN
    vQUERY := 'SELECT 1 FROM ' || iBV_NAME || ' WHERE ' || iPK_FIELD || ' = ' || iPK_VALUE;
    IF iSYS_TIME_STAMP IS NOT NULL AND iSYS_UPDATE_SEQ IS NOT NULL THEN
    vQUERY := vQUERY || ' AND SYS_TIME_STAMP = TO_DATE (''' || iSYS_TIME_STAMP || ''')
    AND SYS_UPDATE_SEQ = ' || iSYS_UPDATE_SEQ;
    END IF;
    IF iBV_NAME IS NOT NULL AND
    iPK_FIELD IS NOT NULL AND
    iPK_VALUE IS NOT NULL THEN
    OPEN CR FOR vQUERY;
    FETCH CR INTO i;
    vRESULT := CR%FOUND;
    CLOSE CR;
    END IF;
    RETURN vRESULT;
    EXCEPTION
    WHEN OTHERS THEN
    IF CR%ISOPEN THEN
    CLOSE CR;
    END IF;
    INSERT_ERROR_LOG_PRC ('CORE_PKG', 'ORACLE', SQLCODE, SQLERRM, 'RECORD_EXISTS_FNC');
    RETURN vRESULT;
    END RECORD_EXISTS_FNC;
    So the problem is when I call this function from let's say
    database DB2 (via db remote link and synonym) and I know exactly that record does exists (because I am selecting those SYS fields before pass them in) - I get the correct result TRUE. The other programmer (Patrick) calls this function within same DB2 database, within same UserID/password (obviously different session), running exactly the same testing code and gets result FALSE (record doesn't exist, but it does !) He tried to Logoff/Login again several times within several days and try to run it and still was getting FALSE !
    I tried to Logoff/Login again and I was getting mostly TRUE and sometimes FALSE too !!!
    I thought may be It has something to do with REF CURSOR that I use to build SQL on the fly, so I changed to NDS
    using EXECUTE IMMEDIATE statement - nothing changed.
    vQUERY := 'SELECT COUNT (1) FROM ' || iBV_NAME || ' WHERE ' || iPK_FIELD || ' = ' || iPK_VALUE;
    IF iSYS_TIME_STAMP IS NOT NULL AND iSYS_UPDATE_SEQ IS NOT NULL THEN
    vQUERY := vQUERY || ' AND SYS_TIME_STAMP = TO_DATE (''' || iSYS_TIME_STAMP || ''') AND SYS_UPDATE_SEQ = ' || iSYS_UPDATE_SEQ;
    END IF;
    EXECUTE IMMEDIATE vQUERY INTO i;
    vRESULT := NOT (i = 0);
    RETURN vRESULT;
    Interesting note : when Patrick doesn't pass SYS parameters (Time_stamp, Update_sequence), or passes NULLs - function always finds the record ! (Statement 2 below)
    May be it has to do with the way TO_DATE () function gets parsed in that dynamic SQL - I don't know ...
    Here's the test code :
    SET SERVEROUTPUT ON;
    DECLARE
    SYS_TIME DATE;
    SYS_SEQ NUMBER;
    bEXISTS BOOLEAN DEFAULT FALSE;
    BEGIN
    SELECT SYS_TIME_STAMP, SYS_UPDATE_SEQ INTO SYS_TIME, SYS_SEQ FROM LOCATION_BV WHERE PK = 1;
    bEXISTS := CORE_PKG.RECORD_EXISTS_FNC ('LOCATION_BV','PK',1, SYS_TIME, SYS_SEQ); -- STATEMENT 1
    --bEXISTS := CORE_PKG.RECORD_EXISTS_FNC ('LOCATION_BV','PK',1, NULL, NULL);        -- STATEMENT 2
    IF bEXISTS THEN
    DBMS_OUTPUT.PUT_LINE ('TRUE');
    ELSE
    DBMS_OUTPUT.PUT_LINE ('FALSE');
    END IF;
    END;
    I asked our DBA, he has no clue about this strange inconsistent results.
    I debugged line by line, extracted that generated SQL and ran it in same account - works fine !
    Does anyone knows or have clues or can help what's going on ???
    I don't know If this is bug in my code or strange memory behavior ?
    (Please let me know If anything unclear)
    Thanx a lot for your help and time !
    Steve K.

    see your other thread
    Bug in my code or strange memory behavior ?

  • Strange Permissions Behavior with Public/Private Drop Box

    Strange Permissions Behavior with Non-Course Drop Box
    In an effort to promote iTunes U on campus this semester (and to get people working with audio and video more) we're having a contest in which people can submit personal or group audio/video projects.
    This being an iTunes promo, we intend for students to submit their contributions via a drop box.
    To that end, I began experimenting with drop boxes in iTunes U, which I haven't done much of previously. I've created a course called "iTunes U Drop Box Test" under "Campus Events". Within that, I have two tabs: "Featured Submissions" and "Dropbox". My goal with this drop box was to allow faculty, students and college folks the ability to use the drop box ("college" being a role I've defined for those who don't fit into the faculty/student roles).
    When I first started experimenting, access to the "iTunes U Drop Box Test" course looked like this:
    --- Credentials (System) ---
    Edit: Administrator@urn:mace:itunesu.com:sites:lafayette.edu
    Download: Authenticated@urn:mace:itunesu.com:sites:lafayette.edu
    Download: Unauthenticated@urn:mace:itunesu.com:sites:lafayette.edu
    Download: All@urn:mace:itunesu.com:sites:lafayette.edu
    --- Credentials ----
    Download: College@urn:mace:lafayette.edu
    Download: Instructor@urn:mace:lafayette.edu
    Download: Instructor@urn:mace:lafayette.edu:classes:${IDENTIFIER}
    Download: Student@urn:mace:lafayette.edu
    Download: Student@urn:mace:lafayette.edu:classes:${IDENTIFIER}
    For the "Featured" Submissions tab, I gave the non-system credentials the "download" right, and for the "Dropbox" tab I gave the non-system credentials the "dropbox" right.
    My understanding of this setup is that everyone should have had the ability to view the course and the contents of the "Featured Submissions" tab and that those in the College/Instructor/Student roles would be able to upload files via the "Dropbox" tab ... but not see the contents of said tab after the files were uploaded (aside from any files they uploaded themselves).
    This is not the behavior we saw however. While the College/Instructor/Student roles could upload files to the dropbox, everyone (including the unauthenticated public) was able to see all of the contents of the dropbox.
    The only way I could get this to work as advertised was to change all of the system credentials save the "Administrator" to "No Access":
    --- Credentials (System) ---
    Edit: Administrator@urn:mace:itunesu.com:sites:lafayette.edu
    No Access: Authenticated@urn:mace:itunesu.com:sites:lafayette.edu
    No Access: Unauthenticated@urn:mace:itunesu.com:sites:lafayette.edu
    No Access: All@urn:mace:itunesu.com:sites:lafayette.edu
    Once I did this, everything worked as advertised: College/Instructor/Student roles could upload tracks, and the "Dropbox" tab would only display tracks they uploaded.
    So my question is ... is this the correct behavior for the drop box? It looks like when the system credentials are in play, they're simply overriding whatever the normal "view" rule is for the drop box, which doesn't seem right.

    Your current configuration where things work as you wanted does seem correct to me. You are not using any System Credentials to accomplish the functionality and that's fine.
    Here's some more info to clarify how / why this is working for you and why you had to set "No Access" for the System Credentials:
    The System Credential "Authenticated@..." is going to get assigned to any user that goes through your transfer script. Even if you transfer script assigns no credentials to a user, upon entering iTunes U they will have at least 1 - the "Authenticated@..." credential. Therefore, unless you block access using "No Access", any user that passes through your transfer script is going to be able to access the area in question.
    When you change values for "Unauthenticated@..." or "All@..." you are defining what someone that DOES NOT pass through your transfer script can do. You want both of those to be "No Access" at the top level of your site if you do not want unauthenticated visitors.
    The distinction between "Unauthenticated" and "All" is that "All" applies to all users whether they pass through the transfer script or not.
    Here's another way to remember things:
    User passes through your transfer script, iTunes U automatically assigns:
    Authenticated@....
    All@....
    User does not pass through your transfer script and instead access your iTunes U site through derivable URL*, they get assigned:
    Unauthenticated@....
    All@....
    *The derivable URL for a site is: http://deimos.apple.com/WebObjects/Core.woa/Browse/site-domain-name
      Mac OS X (10.4.6)  

  • Strange XSLT Behavior: xsl:template match

    Hello I found the following strange XSLT behavior when using xsl:template. I only want to read the content of the element /Source/Surname/Details. Therefore I match this path using xsl:template match.
    What is strange that in the target message also the value of the Element LastName is written at the end. Please see example below. This is just a short example to point out the problem. I have a bigger message structure where I have to match a similar path. How can I avoid the the value of the FullDetails is just written at the end (not even beeing in an element)? I would have expected that the path is only matched once and the instructions then executed without <LastName> beeing even touched.I used XML Spy for this test.
    Here is an example:
    Source message:
    <?xml version="1.0" encoding="UTF-8"?>
    <Source>
         <Surname>
              <Details>MyFirstName</Details>
         </Surname>
         <LastName>
              <FullDetails> MyLastName </FullDetails>
         </LastName>
    </Source>
    XSLT
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
    <xsl:template match="/Source/Surname">
    <PORR>
    <Name><xsl:value-of select="Details"/></Name>
    </PORR>
    </xsl:template>
    </xsl:stylesheet>
    Target Message
    <?xml version="1.0" encoding="UTF-8"?>
    <PORR xmlns:fo="http://www.w3.org/1999/XSL/Format">
    <Name>MyFirstName</Name></PORR>MyLastName
    Edited by: Florian Guppenberger on Oct 8, 2009 4:35 AM
    Edited by: Florian Guppenberger on Oct 8, 2009 4:36 AM
    Edited by: Florian Guppenberger on Oct 8, 2009 4:36 AM
    Edited by: Florian Guppenberger on Oct 8, 2009 4:37 AM

    Hi,
    I am not sure why your XSLT behaving like that,please try this XSL,what i did chnages is Templete match /*,I given exact path in Value of select,.
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format">
    <xsl:template match="/*">
    <PORR>
    <Name><xsl:value-of select="/Source/Surname/Details"/></Name>
    </PORR>
    </xsl:template>
    </xsl:stylesheet>
    Regards,
    Raj

  • Strange typeover behavior in Newsfeeds

    I am getting this strange intermittent behavior when create a post in the Newsfeed.
    As you begin to type the text compress and it almost looks like the letters are typing over themselves
    The resulting text can be posted and looks fine when posted, it some times does throw an error but the error and type over don't seem connected
    It happens on all browser types and even phones and tablets

    Hi,
    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    Best Regards,
    Eric
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Trashed windowserver plist files, now monitor behavior is totally erratic

    Hello,
    I followed advice posted in another topic which suggested deleting the windowserver plist files to address erratic display behavior. If I remember correctly, I deleted four such files (sorry, didn't record the exact file names).
    Upon rebooting, the system created two new windowserver plist files
    com.apple.windowserver.plist
    com.apple.windowserver.0016cba959d1.plist
    The monitor behavior is now totally erratic. Specifically, anytime my Mini goes to sleep, it doesn't recognize the monitor when I wake it up. Screen is black with a "no signal" message generated by the monitor. I have to reboot several times, reset PRAM or reset the PMU to get the display back. No specific sequence of steps seems to do the trick, but I can get the Mini to recognize the display after several attempts with the above-mentioned approach.
    Here is the system set-up:
    Mini 1.83 GHz Intel Duo Core
    Viewsonic VX2245wm (the one with the built in ipod dock)
    Did I delete windowserver plist files that I should not have deleted? Any other thoughts on troubleshooting this?
    Thanks for any help.

    PS: I'm using MAC OS X 10.4.1
    Also, what originally prompted me to trash the plist files was that the display behavior became erratic following Apple updates a couple weeks ago.

  • Strange redraw behavior on second and third monitors

    I have a Lenovo T430 laptop (with the Nvidia Optimus hardware). With the default X configuration (i.e. no xorg.conf or any files in /etc/X11/xorg.conf.d/), the builtin monitor of my laptop works fine. However, I am not able to see the two monitors connected to my docking station with xrandr:
    Screen 0: minimum 8 x 8, current 1600 x 900, maximum 32767 x 32767
    LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
    1600x900 60.01*+ 40.00
    1024x768 60.00
    800x600 60.32 56.25
    640x480 59.94
    VGA1 disconnected (normal left inverted right x axis y axis)
    VIRTUAL1 disconnected (normal left inverted right x axis y axis)
    However, I just learned that I can use the --setprovideroutputsource option to get those monitors to show up in xrandr:
    [adavis@adavis-T430L ~]$ xrandr --listproviders
    Providers: number : 2
    Provider 0: id: 0xa2 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 3 associated providers: 0 name:Intel
    Provider 1: id: 0x66 cap: 0x7, Source Output, Sink Output, Source Offload crtcs: 2 outputs: 5 associated providers: 0 name:nouveau
    [adavis@adavis-T430L ~]$ xrandr --setprovideroutputsource nouveau Intel
    [adavis@adavis-T430L ~]$ xrandr
    Screen 0: minimum 8 x 8, current 1600 x 900, maximum 32767 x 32767
    LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
    1600x900 60.01*+ 40.00
    1024x768 60.00
    800x600 60.32 56.25
    640x480 59.94
    VGA1 disconnected (normal left inverted right x axis y axis)
    VIRTUAL1 disconnected (normal left inverted right x axis y axis)
    LVDS-1-2 disconnected (normal left inverted right x axis y axis)
    VGA-1-2 disconnected (normal left inverted right x axis y axis)
    DP-1-1 disconnected (normal left inverted right x axis y axis)
    DP-1-2 connected (normal left inverted right x axis y axis)
    1920x1080 60.00 +
    1600x1200 60.00
    1680x1050 59.88
    1280x1024 75.02 60.02
    1440x900 59.90
    1280x960 60.00
    1152x864 75.00
    1024x768 75.08 70.07 60.00
    832x624 74.55
    800x600 72.19 75.00 60.32 56.25
    640x480 75.00 72.81 66.67 60.00
    720x400 70.08
    DP-1-3 connected (normal left inverted right x axis y axis)
    1920x1080 60.00 +
    1600x1200 60.00
    1680x1050 59.88
    1280x1024 75.02 60.02
    1440x900 59.90
    1280x960 60.00
    1152x864 75.00
    1024x768 75.08 70.07 60.00
    832x624 74.55
    800x600 72.19 75.00 60.32 56.25
    640x480 75.00 72.81 66.67 60.00
    720x400 70.08
    1024x768 (0x71) 65.000MHz
    h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.36KHz
    v: height 768 start 771 end 777 total 806 clock 60.00Hz
    800x600 (0x75) 40.000MHz
    h: width 800 start 840 end 968 total 1056 skew 0 clock 37.88KHz
    v: height 600 start 601 end 605 total 628 clock 60.32Hz
    800x600 (0x76) 36.000MHz
    h: width 800 start 824 end 896 total 1024 skew 0 clock 35.16KHz
    v: height 600 start 601 end 603 total 625 clock 56.25Hz
    [adavis@adavis-T430L ~]$
    Then I can enable them:
    [adavis@adavis-T430L ~]$ xrandr --output DP-1-2 --auto --right-of LVDS1
    [adavis@adavis-T430L ~]$ xrandr --output DP-1-3 --auto --right-of DP-1-2
    [adavis@adavis-T430L ~]$
    Unfortunately, when I drag any windows onto the two additional monitors (the builtin laptop monitor works fine throughout all of this), I get some really weird redraw behavior: I have to scroll or resize a window to see the new output, moving windows leaves fragments of the window behind, I can mouse over anything to see the latest output in small, mouse-sized chunks.
    See this picture of my screen:  http://picpaste.com/E6sR62Ah.jpg
    What is this kind of Xserver artifact called (that might help my googling)? Any ideas how to fix this?
    Last edited by silpertan (2015-02-24 16:58:07)

    This usually happens when you edit using a delivery codec (H.264, mpeg2, etc). Are you capturing clips using FCP? Or are you using iMovie? Something else?
    Bear in mind that a TCP/IP connection is not reliable to edit with. The video is sent in packets, and a buffer cache is filled on the computer, but not from within FCP. FCP may not be able to retrieve the proper information in the proper order to display the video properly. Some get away with it, others don't. You may be in the latter category. Try dragging the clips to the host computer, or to an external hard drive, just for a test. (It's not a good idea to edit from a system drive, normally, but for purposes of this test, it'll be fine.)
    See if the problem persists when editing from a local drive.

  • Strange dual monitor behavior: mac pro + leopard + x1900xt + 2 dell 2001FPs

    I recently purchased a mac pro dual quad core with radeon x1900xt graphics card. Updated to 10.5.1. I have a dual monitor setup: 2 Dell 2001FPs connected to the x1900xt with dual-link DVI cables.
    Here's the problem:
    I want to use both monitors at their optimal resolution (1600x1200). I can get one monitor to run at 1600x1200 by changing the display preferences, but when I change the secondary monitor to something above 1280x1024, it goes dark, then doesn't come back on (the green light remains on, however). Occasionally while this is happening I will get a message on the black monitor telling me the computer is asleep. It obviously is not since I can see it is awake on the operating screen.
    Here's where it gets weird:
    I just found out that if I drag the mouse over into the darkened screen and then click a couple times, the monitor comes alive at the desired 1600x1200 resolution! If I restart from there, I get the primary monitor to come up upon startup, but I have to change the secondary monitor back down to 1280x1024, then back up to 1600x1200, then do the mystery clicking with the mouse!
    The problem occurs no matter which monitor is primary and no matter which slot is being used on the graphics card.
    To me this sounds like a driver problem, but I'm posting in the Mac Pro forum to see if any others have purchased the same configuration and have similar issues.
    Message was edited by: istra

    It appears I have solved my problem...for the time being.
    1. rechecked all connections, replaced cable on secondary monitor with new (no change in behavior)
    2. reviewed system log and saw this junk:
    {quote:title=system log}
    Dec 19 11:57:37 dhcp-xxx-xx-xxx-xxx [0x0-0x2f02f].com.apple.systempreferences[690]: objc[690]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Con trast.monitorPanel/Contents/MacOS/Contrast and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry.
    Dec 19 11:57:37 dhcp-xxx-xx-xxx-xxx [0x0-0x2f02f].com.apple.systempreferences[690]: objc[690]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT.
    Dec 19 11:57:37 dhcp-xxx-xx-xxx-xxx [0x0-0x2f02f].com.apple.systempreferences[690]: objc[690]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel.
    Dec 19 11:57:37 dhcp-xxx-xx-xxx-xxx [0x0-0x2f02f].com.apple.systempreferences[690]: objc[690]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch.
    Dec 19 11:57:37 dhcp-xxx-xx-xxx-xxx [0x0-0x2f02f].com.apple.systempreferences[690]: objc[690]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode.
    Dec 19 11:57:37 dhcp-xxx-xx-xxx-xxx [0x0-0x2f02f].com.apple.systempreferences[690]: objc[690]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization.
    Dec 19 11:57:37 dhcp-xxx-xx-xxx-xxx [0x0-0x2f02f].com.apple.systempreferences[690]: objc[690]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/TVO ptions.monitorPanel/Contents/MacOS/TVOptions. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/TVO ptions.monitorPanel/Contents/MacOS/TVOptions.{quote}
    The message above occurred each time I booted the mac pro and I think also when I changed resolutions on the monitors. This appeared to me to be a call to the specialized Apple Display extensions and preferences, not for non-apple displays.
    Resolution:
    I went into /System/Library/MonitorPanels/ and copied the AppleDisplay folder to the desktop and renamed it to XXXX.old. I deleted the AppleDisplay folder from its previous directory (I left behind the Arrange.monitorPanel, Display.monitorPanel, Profile.monitorPanel and VGADisplay.monitorPanel files). I then rebooted. No problems since. I can change resolutions all I want and my secondary monitor kicks right in, never staying black.
    Note: this seems to work for me because I am using Dell monitors on the mac pro with the x1900xt graphics card. I wouldn't do this if you have monitor trouble, especially if you have an Apple Display, as it seems these files are important for those.

  • Strange dual monitor behavior - ATI X1900 XT

    I have a Mac Pro w/ ATI X1900 XT. I replaced the GeForce 7300 GT that came w/ the pro with this X1900 XT as an upgrade from Apple, purchased after the initial system purchase.
    I have a 30" Cinema display and a 20" HP LP2065 LCD (very nice, LG/Philips S-IPS panel, just like the 30" ACD).
    http://www.blakespot.com/list/images/macprohp_applelcd.jpg
    I have some odd behavior on the HP secondary screen. I never sleep the Mac Pro, but do sleep its screens. When they wake, the ACD 30 lights up right away. The HP does sometimes - but about half the time it takes 2-5 minutes for it to light. The LED goes amber to green right away, but the screen is black (and unbacklit) for a few mins. Sometimes I see random blue lines across the blackish screen of the HP before it goes normal. Sometimes it lights fine but I see a "stuck" mouse pointer - either arrow or the spinning wheel - on that 2nd screen, but the REAL pointer that's tied to mouse control is on the ACD 30. Only when I move the mouse to push the real pointer to 2nd screen (HP) does the "stuck" pointer disappear.
    Not sure if this is a problem w/ the HP or if it's some odd ATI thing. I had a 20" ACD hooked up as a 2ndary, before going to the 20" HP, and it exhibited none of these issues.
    I am using the HP rotated, in portrait mode, as the X1900 drivers support this.
    Any thoughts? Thanks.
    blakespot

    I have a Mac Pro w/ ATI X1900 XT. I replaced the GeForce 7300 GT that came w/ the pro with this X1900 XT as an upgrade from Apple, purchased after the initial system purchase.
    I have a 30" Cinema display and a 20" HP LP2065 LCD (very nice, LG/Philips S-IPS panel, just like the 30" ACD).
    http://www.blakespot.com/list/images/macprohp_applelcd.jpg
    I have some odd behavior on the HP secondary screen. I never sleep the Mac Pro, but do sleep its screens. When they wake, the ACD 30 lights up right away. The HP does sometimes - but about half the time it takes 2-5 minutes for it to light. The LED goes amber to green right away, but the screen is black (and unbacklit) for a few mins. Sometimes I see random blue lines across the blackish screen of the HP before it goes normal. Sometimes it lights fine but I see a "stuck" mouse pointer - either arrow or the spinning wheel - on that 2nd screen, but the REAL pointer that's tied to mouse control is on the ACD 30. Only when I move the mouse to push the real pointer to 2nd screen (HP) does the "stuck" pointer disappear.
    Not sure if this is a problem w/ the HP or if it's some odd ATI thing. I had a 20" ACD hooked up as a 2ndary, before going to the 20" HP, and it exhibited none of these issues.
    I am using the HP rotated, in portrait mode, as the X1900 drivers support this.
    Any thoughts? Thanks.
    blakespot

  • Please help with strange monitor/Lightroom 4 interaction problem

    I bought a Dell Ultrasharp U3011 yesterday, and I'm now facing a very strange problem. It's sort of related to the common discussed issue of Lightroom's color management, but there is a twist here. I'll explain.
    The monitor I had been using (and still have) was a Samsung SyncMaster 244T. I had no problems at all with it.
    With the U3011, I've run into this problem:
    -When I view files in Lightroom 4, the colors are muted and contrast low. The same files seen in Xnview, ACDSee Pro (with the color management turned off), Digital Photo Professional (colorspace set to sRGB), are much more vivid. In Photoshop, if I use the default color setting, it looks muted like Lightroom (I'm guessing because Adobe products have default color profile set to ProPhoto RGB), but if I set the color profile to the monitor's profile, it becomes vivid and matches the other software I mentioned. If I use any other profile such as sRGB IEC81966-2.1, ProPhoto RGB, Adobe RGB, etc, it doesn't match the other software I mentioned. This is strange because the other ones match each other because they are set to sRGB, but in Photoshop, even if I set the color profile to sRGB, it still doesn't match.
    -In Lightroom 4, even if I use Soft Proofing, nothing changes. It's as if Soft Proofing is broken--it doesn't do anything, no matter what color profile I choose.
    -Now, here's the twist. I didn't have any of these problems when I use the 244T. This leads me to assume that the problem is how the U3011 is interacting with Lightroom. I did a quick comparison of opening up the same image on both monitors in ACDSee Pro, and they looked identical. (At this point, I had the U3011's preset set to sRGB. This is the only preset that makes the U3011 look identical to the 244T).
    Next, I did an experiment, and I was very surprised by what happened. This is what I did:
    With both monitors as a dual display setup, I turned on Before/After comparison in Lightroom (made sure both version had the same setting and look identical by copying the After's setting to Before). I then moved Lightroom's window so that one photo is seen on the U3011, and the other shows up on the 244T. And OMIGOD, they looked different! Why is this happening? I've already established that the same image looks identical on both monitors when viewed with ACDSee Pro, but in Lightroom, they looked different on each monitor.
    And then things got even more weird. When I dragged the Lightroom window fully to one monitor or the other, Lightroom actually started changing the colors right before my eyes as it responded to which monitor was displaying which photo! Lightroom was somehow interacting with the monitor in real-time. So if the Before looked muted on U3011 and the After looked vivid on the 244T, when I drag the whole window into 244T, the muted Before will stay muted for about a second or so, and then it'll suddenly change and become identical to After. And when I did the reverse (drag the window into U3011), the reverse also happened--the vivid After will stay vivid on U3011 for about a second or so, and then it would suddenly change and become muted. Lightroom was identifying each monitor's color profile setting and changing the images according to which monitor was doing the displaying, and when the images were split between the two monitors, Lightroom was slitting them into two different settings to match whichever monitor is displaying which side.
    So what the hell does that all mean, and what can I do to get Lightroom to display the photos so that they look the same as on all the other software I mentioned (so I don't have to play the guessing game of editing the images, export them out to other software to check how they turned out). Also, remember that I didn't have this problem with the 244T--Lightroom displayed the photos the same way as the other software I mentioned. The problem right now is that the U3011 is somehow causing Lightroom to display the photos differently, and no color profile presets in the OSD control can make them match.
    I need to solve this problem, or else my last resort would be to return the U3011 and try another brand/model and see if that helps.
    Any ideas?

    Yes, that's basically sensible advice you got there (but I was more succinct ).
    An important point that was mentioned over there is that you must not confuse document/source profile with monitor profile. They are both links in the color management chain, but they serve different purposes. The document profile defines the colors in a standard color space. The monitor profile describes the monitor's own native color space - its response to the RGB numbers it's fed. So one is translated into the other, by the application on the fly, through a normal profile conversion, and that way the colors appear on-screen as intended.
    If those two profiles/color spaces are roughly similar, as they would be in the case of an sRGB document displayed on a standard gamut display - then you can get by without color management. It won't look too far off. But a wide gamut monitor changes the rules, because its native color space is not similar to sRGB, it's much closer to Adobe RGB.
    Anyway, this is what color management is about. Any profile can be translated into any other. So in this context it doesn't really matter what color space the document is in - as long as you have a good monitor profile it will display correctly (within practical limitations). Lightroom is a sort of special case because its internal working color space is not one of the standard ones, instead it's a modified ProPhoto space with linear gamma. But the basic principle is exactly the same: source profile > monitor profile.
    Just to go a little more in-depth while I'm at it: When you calibrate a display you actually do two separate things. You first calibrate it to a more or less standardized response. But that's just a linear one-dimensional correction. It does nothing about how color is actually reproduced, how red is red for instance. The calibration is global and affects everything system-wide because it's read into the video card or monitor hardware.
    Then, once calibrated, a monitor profile is made. This is a full, complete and accurate description of the monitor's behavior, in three-dimensional color space. The precision level is much higher. This profile is used, by color managed applications like Lightroom and Photoshop, to display the image.
    Other applications that are not color managed will simply ignore this profile, and send the RGB numbers straight through to the display, unmodified. With a standard gamut monitor (and an sRGB document) the difference won't be too dramatic and you may not notice it unless you look closely. But a wide gamut monitor will make the difference jump out immediately.

  • Odd dual monitor behavior in Photoshop CC 2014 on Mavericks

    I'm seeing some strange issues with a dual monitor setup (monitor 1 is MacBook Pro screen, monitor 2 is an external monitor) in Photoshop CC 2014. I have images open on both screens. If I use the eyedropper to try to pick a color from an inactive image window on one screen, it won't pick up the color unless I click on the image to make it the active image. I don't remember this behavior on dual monitors before.
    I'm also seeing that if I switch from another application back to Photoshop and start painting or erasing, nothing happens in the active window. I have to re-switch applications and try again. Sometimes that works, other times it doesn't.
    On another occasion, I was working on one monitor. When I returned to the main monitor and tried to access an item in the Edit menu, all of the menus were empty and white.
    I can't identify if this is a Mac OS issue or an Adobe issue. I'm wondering if other people have been experiencing this behavior and if so, how to correct it.
    Thanks.

    Could be.  I tried restarting, closing and reopening Photoshop.  I just noticed this today, and I've been using CC 2014 since it came out.  I'm using it on a relatively new iMac, but I don't think it has happened before, though I could be wrong.  It's not the end of the world, but it is an annoyance.
    Thanks.

  • Strange window behavior with CS5

    I have begun experiencing strange behavior with PS CS5. I should begun with the machine configuration: 2.66GHz iMac (8,1) Intel Core Duo with 4GB RAM and OSX 10.6.6, Radeon HD 2600 Pro graphics card. The initial symptom showed up suddenly as an inability to display an image window; that is, I could open PS normally, everything would show up properly, but when I opened an image file of any sort, there would be no image window. Other cues indicated that the file was open; for example, the window menu would show it selected, and the layers palette would show the file's layers.
    It did not seem to matter what type of file was involved: PSD, JPG, TIF, whatever. Occasionally, this behavior would begin during a session. Sometimes it would happen right off the bat. Sometimes, stopping and restarting PS seemed to clean things up; other times, this had no effect. After messing around quite a bit with different permutations and combinations, all I could say was that the problem was random.
    I might add that I've had PS CS5 on this machine pretty much since it was announced, and had not had problems with it before. So this issue came along quite suddenly a couple of weeks ago. This was a little after I'd installed an update for Nik's Viveza 2; and I began to suspect that. Although why Viveza should do such a strange thing was odd, and Viveza was never part of the files I was experiencing issues with. Anyway, I went back to an earlier version of Viveza and the problem persisted.
    Since I run Time Machine, I also went back to versions of the entire PS folder from a month back, and found the same problem. Along the way, I experimented with the files I was using with PS CS4 & CS3, which I also have installed on this machine. These two versions of PS run perfectly well. At least the CS4 version has precisely the same plugins as the CS5 folder, and this seems to discount the potential problem with plugins.
    To be sure about CS5, I completely deactivated, deinstalled, and reinstalled it. The same issues occurred. Now, I have to admit that I let PS run its update process so that I brought it back to the most recent version in this step of my troubleshooting. So, I can't be certain that the issue isn't with some update of CS5.
    I might add that I have been running CS5 in 32-bit mode, for compatibility with certain plugins. This may or may not be an issue, since I have limited experience with running in 64-bit mode. At this point, I should add a bit more about the confusing behavior.
    While messing around with CS5, I also suspected the GPU support, since my problem had to do with windows. When the problem presents itself, the usual cycle through window views that you get by pressing the "F" key seems to get messed up. In particular, the "F" key doesn't work at all. Next, if you use the View menu to select different views, the full screen with menu bar view will often have garbled pixels, while the full screen view will show a blank grey screen. Then, cycling back to a window view will show a window with blank grey contents. This is interesting since the starting point was no window at all; but going into full screen and then back will produce a window with bogus contents.
    Now, the next strange thing, having to do with the GPU, is that CS5 often fails to recognize the Radeon HD 2600 card. Oddly enough, it did originally. And I had it running in Basic mode. However, CS4 does recognize the GPU; and I can set it in any variety of modes: Basic, Normal, and Advanced. This behavior is not consistent at all either; that is, while CS5 almost always now fails to detect the GPU, sometimes it does. As near as I can tell, this failure to detect the card does not depend upon whether I start CS5 in 32-bit or 64-bit mode. OTOH, CS4 always recognizes the GPU.
    Another form of this odd behavior arises if I start CS5 cold, and then just open a new blank window. This almost always works. I get a blank white window, and I can paint on it with a brush, etc. However, if I go ahead at this point and open a file, then the new file takes over the window; and there are no tabs. If I select the original new file, usually labelled "Untitled", the window bar will show the change of filename but the window's contents and the layers palette will continue to show the old file that I had opened. Cycling through views can sometimes get back to the new Untitled file, but just selecting file windows never works.
    Yet another aspect of this messed up window behavior is that the workspace bar, which shows the Bridge, MiniBridge and view icons on the upper left and the various workspace options and CS Live on the upper right, is present but blank. OTOH, the tool bar is always displayed correctly, as is the horizontal bar that shows the various tool options. Likewise, the palettes for the workspace such as layers, swatches, adjustments, and so on, are always correctly displayed on the left.
    My next steps in trying to figure this out will be to ensure that I am running the latest of all plugins so that I can get everything running in 64-bit mode and try this again. However, the single factor that seems consistent in this whole mess is that whenever I do find this odd behavior, the performance preferences window will indicate that CS5 is not detecting the GPU. Whenever this happens, if I open up CS4 and check the same performance preference in it, the GPU is detected. I can have the two preference windows side by side on the screen in fact, CS4 sees the GPU and CS5 does not. The counter-indication is that sometimes CS5 will work properly and the preferences window still shows that the GPU has not been detected. Having said that, I can add that if I have opened up CS5, and it has found the GPU, and I have set it into, say, Basic mode, and then later found CS5 messing up, and I go back and check the performance preferences again, the GPU has always been lost. So, CS5 can mess up windows with or without the GPU detected and active; but when if it started with the GPU present, it will show up as lost after the weird behavior starts.
    To add one more observation, I have had Macs and other computers with failing GPUs. This computer is showing none of the typical signs of that. Every other program seems to be working just fine, and I have a lot of these, many graphics intensive; e.g., Corel Painter 11, Parallels v6 running Windows 7, PS CS4, Lightroom v3, Aperture v3, and so on. It is just CS5 that is messing up.
    I could load up this message with screen shots of all this nonsense, but I'm not sure what that would add to the strange tale, other than I'm not pulling your legs. I am, however, pulling out my own hair.
    As I stated before, this began quite suddenly a couple of weeks ago, early Feb 2011. My best guess as to cause is some combination of incompatible updates between CS5, OSX, and maybe some plugin or other. I found unusual behavior with onOne's FocalPoint v2 last year after Apple updated GPU drivers in some OSX update, and cratered that program. It took onOne a month or two to fix that. I have CS5 on a laptop with the same OSX version, and on that I haven't seen these issues; but then, I haven't been using it as intensely over there. Also, that machine has different CPU and GPU models than this iMac.
    So, to the community: is anybody else starting to see this odd stuff? Am I alone?

    Here's the reason I say that the same plugins exist for both CS4 & CS5. Sometime last year, the internal hard drive on this computer died (as they so often do), and it was replaced under the Apple care warranty. As a consequence, I decided to rebuild the OS and applications from scratch and bring back my user files from backup. I among other things, I reinstalled all of CS4 as well as CS5 (and I had to put CS3 back too for reasons having to do with printing calibration images for Quad Tone RIP). Then, I went to reinstall the plugins that I needed. I use Nik Software, onOne, Portrait Professional and various Topaz plugins. To my recollection, most of these install in PS CS3, CS4, CS5, Aperture, and Lightroom. In short, it is not that I've copied or moved plugin folders from one application folder to another, just that the installers automatically detect the presence of the various applications and put the various plugins into each, as appropriate.
    The only 32-bit plugins that I have that don't fit into this category are from Vincent Versace. He provides special versions of certain Nik plugins (Tonal Contrast, Contrast Only, etc) that function with some Acme Educational extensions for performing B&W conversion, sharpening, blah blah blah. These plugins are only 32-bit and the extensions are only CS5 compatible. I've installed these ones only into CS5; so, you've got me. OTOH, I've had these from Vincent as soon as CS5 was available; and they've worked so far without problems. Perhaps I should just edit the extensions so I could use the latest plugins direct from Nik instead of the Versace special editions...
    I've checked fonts and repaired permissions. I am presently going through the rather tedious process of disabling plugins and extensions to see if anything yields consistent results. The rather random arrival of the strangeness makes ensuring that a change is really having an effect more difficult to validate, as you will appreciate.
    I apologize for my long-winded original post. I add all of the detail so that anyone who'd experienced similar strange behaviors might properly pattern-match what they were seeing. On the one hand, in finding the cause of a problem, you look for what's changed; and theoretically nothing is new. On the other hand, there's always so much changing behind the scenes with automatic updates of this, that, and the other thing that it's impossible to make the claim that nothing's new. 

  • CMYK images: strange monitor display & and printing

    I tried the way Pages 2 handles CMYK images today and found out some strange things.
    My problem: monitor display
    CMYK .jpg files are displayed inverted on screen like a negative - black is white and white is black. Layouting basicly rendered useless. Is there a work arround ?
    Solved: Printing
    For printing there are at least two ways to get a decent result. Here my findings:
    - Any color printers
    "Print - ColorSync - Color Conversion" set to "Standard" => CMYK images get converted to RGB
    "Print - ColorSync - Color Conversion" set to "Printer specific" => CMYK images stay in CMYK if printer is able to print CMYK
    - use "Save to PDF" within printing dialog
    Same as above, profiles tagged to images stay correct
    - Adobe Acrobat Distiller
    Same as above, but PDF looses recognizeable profile information. PDF workflow software does not recognize "SWOP" or "ISOcoated" by name but has "Embedded Adobe Postscript CRD Profile" instead which will create problems in workflow processing.
    - Exporting "File - Export - PDF"
    Profiles stay intact and are handled correctly.
    Cube, PB 17"   Mac OS X (10.4.7)  

    Thanks Noel for the reply. Hopefully  this will help.
    This is how the file should look like.
    This is how the file usually displays.
    Any help would be greatly appreciated.
    Regards,
    Ron Cecil

Maybe you are looking for