HT202856 Mac Pro Late 2013 and Samsung 4k monitor problem

I have the new Samsung 28" 4k screen (U28D590D) and it has tearing along the right edge when used with displayport. Any way to fix that? I tried different cables (all DisplayPort 1.2 complient) to be sure and have narrowed the issue to the Mac Pro. The HDMI works fine tho only @30hz so is a bit laggy in normal interaction. There is no way to turn on Multi-stream as indicated and I hope it isnt that this screen will never work.

nMP(late 2013) can't change graphic card...
I also have a problem when using the AMD card on My Mac Pro (Mid2012) OSX 10.9.3,
however, Windows(Bootcamp) OR with Nvidia GTX 760 4K 60hz OSX, Windows both working very well.
Probably... AMD OSX driver issue..

Similar Messages

  • Mac Pro (late 2013) Philips 288p 4K Monitor Issues

    I have just bought a philips 4k monitor 288p for my Mac pro and I have quite a few issues, does anyone know of a firmware upgrade to the graphics card that will solve these ?
    Issues-
    Crashes on boot up when connect to monitor
    Using monitor is slow i.e. mouse seems to jump a bit, text takes longer to type etc.
    When in 'about this mac' it shows the monitor is running at 7350 x 4500 which is mental
    I have connected via Display port to mini display port and mini display port to dual link Dvi adaptor, both have the same issues.
    Any fixes would be most welcome.
    Thanks

    It sounds like the monitor is not correctly identifying itself to the Mac. Try Page 15 of:
    Mac Pro Late 2013 and Samsung 4k monitor problem
    First try resetting the SMC and PRAM
    Intel-based Macs: Resetting the System Management Controller (SMC)
    About NVRAM and PRAM
    You will only get 4K at 60 Hz via display port/mini display port.
    Are you using a display port 1.2 cable?
    Your monitor supports 1.2
    http://www.usa.philips.com/c-p/288P6LJEB_27/brilliance-4k-ultra-hd-led-backlit-m onitor/specifications

  • Why isn't Photoshop fully optimized for the Mac Pro (Late 2013), and when will this happen?

    On the new Mac Pro (late 2013):
    Currently, Photoshop CC 2014 seems to lag behind iMacs and Macbook Pros (even older ones) for some tasks.
    I assume that this issue is related to either multi-core processing but seems more likely to be a problem with the ATI GPUs not being optimized as the Nvidia GPUs are.
    Why is this the case, and when will this be addressed?
    Any feedback from Adobe official would be appreciated.
    Thanks

    jameskachan wrote:
    …The obvious reason [sic] seems to suggest…
    That's what it suggests to you, in the limited scope of your vision and knowledge, and without your having provided detailed specs about your hardware.
    Due to the current unavailability of clairvoyants and mind-readers in the forum, we respectfully request you supply sensible, complete details.
    We don't even know what your specific issues are, and for all we know you may be running the pathetic, buggy Yosemite OS—which Apple is giving away for free.
    In this case, you have been enormously fortunate in that you received a reply from none other than Gµrµ Chris Cox, a top Adobe engineer who has been writing Photoshop code since the last millennium.
    It's hight time you drop the attitude and avoid further embarrassing yourself in a public forum.  Just my two cents.

  • Cannot connect between a Mac Pro (late 2013) and a MBP and vice versa

    Cannot connect to Macbook Pro from Mac Pro late 2013. I have tried via ethernet and wifi. I can screen share either way. I have tried to connect to other MBP's on the same network with no luck. I try and connect as a registered user, as I usually do, with no luck. When I enter the Username and then Password the box vibrates as if the details are incorrect, they are definitely correct however.
    I have no firewall on. Both devices are using the most recent OS.
    Thanks in advance
    Jeff

    Hi Grant, Here is the Console system log. Tried to connect to Macbook Pro at 15:46:30
    Mar 22 15:44:28 Jeffs-Mac-Pro com.apple.xpc.launchd[1] (com.apple.preference.datetime.remoteservice[744]): Service exited due to signal: Killed: 9
    Mar 22 15:44:38 Jeffs-Mac-Pro kernel[0]: hfs: mounted Time Machine Backups on device disk2s2
    Mar 22 15:44:40 Jeffs-Mac-Pro com.apple.backupd[736]: Disk image /Volumes/Data/Jeff’s Mac Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
    Mar 22 15:44:40 Jeffs-Mac-Pro mds[35]: (Volume.Error:880) Root store set to FSOnly with matching create! (loaded:1)
    Mar 22 15:44:41 Jeffs-Mac-Pro com.apple.backupd[736]: Backing up to /dev/disk2s2: /Volumes/Time Machine Backups/Backups.backupdb
    Mar 22 15:45:27 Jeffs-Mac-Pro com.apple.backupd[736]: Will copy (72.8 MB) from Jeff Mac Pro HD
    Mar 22 15:45:27 Jeffs-Mac-Pro com.apple.backupd[736]: Found 973 files (72.8 MB) needing backup
    Mar 22 15:45:27 Jeffs-Mac-Pro com.apple.backupd[736]: 1.56 GB required (including padding), 232.28 GB available
    Mar 22 15:45:48 Jeffs-Mac-Pro NetAuthSysAgent[773]: NAHSelectionAcquireCredential complete: iakerb A88A5E19-89A1-8FEF-EE42-8F065FC94669 - ***@mac.com: GSSCred: 0x7ffa296262f0 <MC: iakerb com.apple.idms.appleid.prd.4f7466316e4d737570647351515953457261382b32773d3d@WEL LKNOWN:COM.APPLE.LKDC>
    Mar 22 15:46:41 Jeffs-Mac-Pro NetAuthSysAgent[773]: NAHSelectionAcquireCredential complete: iakerb A88A5E19-89A1-8FEF-EE42-8F065FC94669 - ***@mac.com: GSSCred: 0x7ffa29432780 <MC: iakerb com.apple.idms.appleid.prd.4f7466316e4d737570647351515953457261382b32773d3d@WEL LKNOWN:COM.APPLE.LKDC>
    Mar 22 15:47:04 Jeffs-Mac-Pro Console[781]: Failed to connect (_consoleX) outlet from (NSApplication) to (ConsoleX): missing setter or instance variable
    Mar 22 15:47:17 Jeffs-Mac-Pro com.apple.xpc.launchd[1] (com.apple.PubSub.Agent[784]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.pubsub.ipc
    Mar 22 15:47:17 Jeffs-Mac-Pro com.apple.xpc.launchd[1] (com.apple.PubSub.Agent[784]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.pubsub.notification
    Mar 22 15:47:36 Jeffs-Mac-Pro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): The _DirtyJetsamMemoryLimit key is not available on this platform.
    Mar 22 15:47:56 Jeffs-Mac-Pro Dock[286]: void CGSShmemReleaseMappedMemory(CGSShmemID): failed to find shmem ID 787.

  • New Mac Pro (Late 2013) and Motion

    Although Final Cut Pro is optimized for the new Mac Pro (Late 2013), the current Motion 5.1 apparently is not.  Even when turning the render settings down, the playback of a complex motion sequence within Motion was extremely choppy.  When exporting to a ProRes file, only four to six of the available 12 threads ony my 6-core system were being only partially utilized.   I have 64 GB RAM and dual D700s with nothing else running, so system resources are plentiful.  Any suggestions out there?  Hopefully there will be an update to bring it up to speed.

    The sequence I am rendering in Motion is definately complicated, with about 100 differencet images on a moving wall with reflections and multiple other effects.  This definitely pushes the system alot but I was able to use the same sequence on a very old Mac Pro (2006) and a i7 Hackintosh with an Apple 5870 card overclocked to 4 GHz without this severe stuttering on playback within Motion.  There is no shortage of memory on the new Mac Pro with 64 GB RAM and D700s with 6 GB VRAM, running all files on the main internal SSD.  Very strange.

  • New Mac Pro (Late 2013) and CC 2014

    Ok, I've been working on one of the new Mac Pro's from late 2013 and using CC 2013 with R3D footage quite successfully (though without great debayering performance on the R3D - I know it's supposed to be improved in CC 2014).
    I'm running 10.9.2 Mac OSX.
    When football season here in the states starts in two weeks, I will have a VERY deadline intensive 30 minute television show that I have to turn around from Saturday night at 2am until 8am Sunday morning.
    I have purchased CC 2014, but have read in the past few weeks about the headaches the combination of OS 10.9.3 (and .4) and CC 20014 have caused.
    My question is, where do we stand with those issues, and what would the community / Adobe moderators say about me heading up to the latest OS and CC 2014 under these circumstances? Thanks so much for the insight everyone.
    Banks

    jameskachan wrote:
    …The obvious reason [sic] seems to suggest…
    That's what it suggests to you, in the limited scope of your vision and knowledge, and without your having provided detailed specs about your hardware.
    Due to the current unavailability of clairvoyants and mind-readers in the forum, we respectfully request you supply sensible, complete details.
    We don't even know what your specific issues are, and for all we know you may be running the pathetic, buggy Yosemite OS—which Apple is giving away for free.
    In this case, you have been enormously fortunate in that you received a reply from none other than Gµrµ Chris Cox, a top Adobe engineer who has been writing Photoshop code since the last millennium.
    It's hight time you drop the attitude and avoid further embarrassing yourself in a public forum.  Just my two cents.

  • Mac pro (late 2013), Dell UP2414Q and windows8.1 bootcamp

    I bought mac pro (late 2013) and Dell UP2414Q.
    Monitor is set on DP1.2 and works normally in OS X. I get 4K@60Hz, I can switch to lower resolutions like 1920x1080 and it works.
    Then I Installed windwos 8.1 which I need for some testing and I have aproblem here:
    When DP 1.2 is enabled, and I switch to 1920x1080 resolution, I get 2 pictures on screen squeezed together - totally useless and I can't work on that.
    If I disable DP 1.2 and revert on monitor to DP 1.1 it works normally. But I switch to 4K with only DP1.1 enabled I can get only 30Hz out.
    As it seems under OS X I can use any resolution with DP 1.2 enabled, but not in windows 8.1 via bootcamp.
    I would really really love to get this working, I tried next things, but nothing worked:
    -update bootcamp support
    -update AMD gpu drivers from their web page
    I already wrote on Dell forum and I got redirected here on apple forums.

    which model  rMBP 13"  or rMBP 15"
    the 13 will support it with the latest intel drivers.
    the 15 will support it with the latest nvidia drivers.
    i have both models and both are working correctly.

  • Mac Pro (Late 2013), Photoshop CC stamp tools and Yosemite Problems

    Lately when I'm using the the stamp tool in Photoshop CC after a few clicks I hear a short "click click" out of the Mac Pro Late 2013 when then goes on to freeze
    my keyboard and basically makes it useless. I then have to save the photo by clicking in the menu bar, restart the computer which clears the problem. I'm using a Wacom Intuos Pro and thought it could the problem but I tried it also with a normal usb mouth clicking on an image and get the same results. What is this "click click" noise because as soon as I hear that I know that the Mac Pro is going to freeze.........anyone else having any Photoshop problems?

    I've not tried exporting with Premiere but with After Effects on my identical Mac Pro also using istat menus, I rarely if ever see the 2nd GPU spin up. I'm exporting right now for example and:
    makes me wonder if this is infact an issue with Istat menus or if the 2nd gpu really isnt being utilized.

  • Mac Pro late 2013 mouse and keyboard

    Today I receive my new Mac Pro late 2013. With my big surprise is without mouse and keyboard.
    Which keyboard and mouse I have to buy?
    Cable or wireless?
    How and where connect?
    I also see in the online store there is only cable keyboard USB 2 but the Mac Pro have only USB 3 ports.
    Please help me. I'm very frustrated. I have this new fantastic computer  front me and I can't do nothing.
    I look every where but I not find any information about.

    You can use wireless keyboard and mouse.
    http://store.apple.com/us/product/MC184D/B/apple-wireless-keyboard?fnode=56
    http://store.apple.com/us/product/MB829LL/A/apple-magic-mouse?fnode=56

  • HT6099 why does the mac pro (late 2013) only support up to 60Hz at 1080p? TV screens are pretty much all 120Hz. So much for future proof.

    why does the mac pro (late 2013) only support up to 60Hz at 1080p? TV screens are pretty much all >120Hz. So much for future proof.

    http://en.wikipedia.org/wiki/4K_resolution
    http://en.wikipedia.org/wiki/4K_UHD
    http://www.techradar.com/news/home-cinema/high-definition/4k-tv-resolution-what- you-need-to-know-1048954
    Need More Pixels? Samsung’s 2014 UHD TVs Ship This Month
    Wall Street Journal · 2 hours ago
    Samsung’s 2014 lineup of Ultra High-Definition (aka 4K) TVs are on the way, and thanks to UHD content deals struck with Fox and Paramount—not to mention the…
    Focusing on TVs and 1080p and 60Hz isn't the question, or the 'future'

  • My Mac Pro late 2013 hangs at 18 minutes left on update to Yosemite.

    I Attempted to update my Mac Pro late 2013 to Yosemite after it was released today through the Apple Store. Unfortunatly after several hours and many auto restarts it hung at 18 minutes to go.
    THe Mac is backed up on an Airport 4, but is there any other way and how do I get to the backup?
    Thanks for any help.

    Try resetting the SMC and NVRAM
    Intel-based Macs: Resetting the System Management Controller (SMC)
    About NVRAM and PRAM
    Next note the time of text problem and then after reboot open the Console app and look for log entries at that time. Post suspicious ones here

  • Premiere Pro CC crashing on brand new Mac Pro (late 2013)

    Such a big disappointment, yesterday our brand new Mac Pro (Late 2013) with OS X version 10.10.2 was installed and Premiere Pro CC is constantly crashing. One of the problems is that when I open a brand new project and before I add any content to a new sequence I just want to position the video track higher so I can see more audio tracks, the program crashed. I did it several times (new projects, new sequences) every time the same crashing program.
    Deinstalled Premiere Pro and reinstalled it again, but no luck.
    Tomorrow I created a whole new account with administrator rights on the Mac, the issue as described above was gone but at some point in time the program crashed again, and when I reopen the project, with two sequences open (one with footage and one empty) and I want to close the empty one, Premiere is crashing again. So I can't continue my work on this project and need to start over again....
    This is the error report that I'm getting....
    I hope somebody can help me on this because it's very frustrating...
    Thanks in advance

    Hi tschreiber10,
    Thanks for posting on Adobe forums,
    Please follow this document http://helpx.adobe.com/creative-cloud/kb/ame-premiere-crash-launch-export.html
    Regards,
    Sandeep

  • Can iMac 27 late 2009 enter TDM connected to a Mac Pro late 2013?

    I'm trying to get an iMac 27 late 2009 to enter target display mode when connected to a Mac Pro late 2013.
    I tried with Apple's Thunderbolt cable and pressing Command + F2 on the iMac did nothing.
    So I bought a Mini DisplayPort cable, and now Command + F2 makes the iMac's screen turn black for a second and then back.
    After rebooting, before logging in, if I press Command + F2 it actually works for about 2 seconds and then back to the iMac's screen. After this, if I keep trying it just flashes black.
    So, my question is, has anyone managed to connect this two devices?
    Should I buy another cable? Format the iMac? Any suggestions?
    Thanks for the help.
    OS X Mavericks 10.9.4 on both machines.

    Thanks for your help.
    I don't know what more I can add to the initial post.
    The second Mini DisplayPort cable that I tried is Belkin, I don't think there are better cables for this, since Apple is not selling it anymore.
    I did mentioned that if I restart the iMac, before logging in with any user, pressing command + F2 or simply connecting the cable will actually work, it shows up as a second display on the Mac Pro, I can move the mouse pointer on the iMac. But after about 2 seconds the iMac exits Target Display Mode, and after this pressing Command + F2 will only turn iMac's monitor black for about a second and not entering TDM anymore.
    I even checked the firmware versions and both are up to date according to this.

  • USB Card Reader not recognized on new Mac Pro (late 2013)

    My Sony USB multi-card reader (model: MRW62E), which I use for SD cards mostly, works on my MacBook Pro (Retina, Mid 2012), my new iMac, and my old Mac Pro (2009), via the USB ports, but is unrecognized entirely on my new Mac Pro (late 2013). All machines are running OS X Yosemite 10.10.2. Neither the card reader, nor the cards appear at all in FCP, image capture, apple system profiler, the desktop, or disk utility. I cannot find any drivers online addressing the issue, including Sony's website.
    Perhaps an additional update for increased compatibility vis-a-vis the new Mac Pro would do the trick...

    Does the reader show up under USB in System Report?
    If the reader is working properly both the reader and an inserted card will show up.

  • After Effects is NOT using the full Twelve GB of memory on my Mac Pro late 2013 dual video cards

    I would like to know if there is a reason why AE CC12 and CC13 (2014) is not using the full amount of video card memory on my MP late 2013. It's six GB per freaking card I invested in and its not accessing it.
    Is there a work around this issue?

    Why shouldn't it. When I upgraded to this new Mac Pro late 2013 with its dual video cards. Premier turned into a blasting fast editor. I no longer need to render my edited cuts and the scrubbing of preview and timeline footage is phenomenal. The only performance boost I've seen in AE with this new system is in rendering and I can't even say its double as fast in comparison to Premier or Encoder and its an 8-Core system with 32GB of ram. Everything else is flying.
    So again to answer your why should it. I rebuttal with "Why shouldn't it". The other two mentioned programs are using GPU resources to improve performance why is AE so behind the curve.
    I'm not the only one asking why. I was in the audience at a Dmala meeting here in LA with Todd Kopriva and Al Mooney previewing AE and Premier 2014.
    People kept asking Todd about performance boost in between questions about new features. Todd finally just asked what do you prefer a couple of new features or performance boost. Everyone wanted performance boost over new features. If you think I'm making this up go ask Todd Kopriva.

Maybe you are looking for