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.

Similar Messages

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.

Can I set up a new Mac Pro late 2013 using a Wacom Cintique 13HD tablet as the default monitor? How would I install the driver software for the tablet?

Can I set up a new Mac Pro late 2013 using a Wacom Cintique 13HD tablet as the default monitor? How would I install the driver software for the tablet?

The wacom site will have the drivers for you.
http://us.wacom.com/en/support/drivers

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.

Running 4 screens as one with Mac Pro Late 2013

Hello there, got a Mac Pro late 2013 edition driving 4 60" 1080P screens in a 2x2 configuration. Trying to make those work as one 4k display. Was able to get it working to allow us to display a page across all 4 displays. But have not been able to get a video to display across all 4. Our current configuration has also been very finnicky and anytime we move the webpage around, it snaps the window to be full screen across the bottem two displays.
Anyone have any idea's as to how to make this work the way we are wanting to?

"Fullscreen" is a garbage feature ported from IOS and the iPhone, the land of tiny screens and one-at-a-time processing -- AVOID it at all costs.
This will work as long as you stretch a Window across multiple screens, and turn OFF all hints that you want multiple, independent screens.
This describes the new ways Mavericks tries to undercut the way it used to work:
OS X: Using Multiple Displays in Mavericks

Help! Multiple Displays not Working. (Mac Pro late 2013).

Hardware:
Late 2013 Mac Pro
Processor: 3.7 GHz Quad Core Intel Xeon E5
Memory: 12 GB 1867 MHz DDR ECC
Graphics: AMD FirePro D300 2048 M8
Software: OS X 10.9.2 (13C64)
Displays:
4 LG Electronics S-Class 25UM64-S 25-Inch Screen LED-Lit Monitor's
Display Connection:
6 Moshi Mini DisplayPort to HDMI Adapter (4K)
Issue:
First of all, thank you in advance for taking the time to help!
I just picked up this Mac Pro (as stated above) and I am having quite the time trying to get the monitors to display properly (or at all!)!
Everything is hooked up properly (i'd like to think so), i've run through most of the trouble shooting methods I can think of and have found online... and still, 2 of the 4 displays do not show! The Mac Pro is not recognizing two of them.
I was told that the MacPro could recognize up to 6 Mini DisplayPort to HDMI monitors, however, only 2 are working properly. Is it because of the Moshi Mini DisplayPort to HDMI adapters? Should I be running MDP to DP cables instead? The monitors support DisplayPort input's, however, they also allow for PIP hence the use of 6 MDP adapters to HDMI. (2 of the monitors are using the built in picture in picture split screen. So 2 HDMI inputs each).
Really pulling my hair on this one.. I figured it would be plug and play.. at least, that's how apple USED to be.
Any ideas?! Am I simply needing to use the MDP to DP cables instead of MDP to HDMI? Please help!
Thank you!

See:
Mac Pro (Late 2013): Using multiple displays - Apple Support
Can I connect more than 2 DVI or HDMI displays?
Mac Pro supports a total of two DVI or HDMI displays when connected via the built-in HDMI port or using the Apple Mini DisplayPort to DVI adapter. To connect additional DVI displays, use an active DVI adaptersuch as the Apple Mini DisplayPort to Dual-Link DVI adapter. You can connect up to six active adapter DVI displays. This requires a powered USB hub since Mac Pro offers four USB ports and you will need six to connect them all.
Thus, use a display port to mini display port cable

Cannot connect from Mac Pro late 2013 to Macbook Pro

Cannot connect from Mac Pro late 2013 to Macbook Pro . I have tried via ethernet and wifi. I can connect from the MBP to the Mac Pro but not vice versa. 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 not however.
Thanks in advance
Jeff

It is 'just not working' again.
To answer you question. Other sharing services work. I can connect as a guest. I can share screens. I cannot air drop.
I cannot connect either way now i.e. from Mac Pro to MBP and vice versa.
I cannot connect to my wife MBP either. My wife cannot connect to my Mac Pro.
It neither works with wifi or ethernet cable.
I can connect to my Time Capsule directly and Time Machine backups are working.
The passwords are 100% correct.
The Mac Pro is a late 2013. Does anyone else have a similar problem? I have never suffered this one before. Seriously effecting my workflow
Thanks

How can Mac Pro (late 2013) create a WiFi network for Mac Books to connect to internet?

I am moving my Mac-Pro (late 2013) to a garden office. I have an ethernet cable to connect it to the house network. I also have a Mac Book Air which will only connect to a network by WiFi. I can use this Mac-Pro to create a WiFi network and the MacBook can talk to the Mac Pro over this WiFi network. But the Mac Book does not see the local network let alone the Internet, both of which are seen on the Mac Pro.
Is there a way that I can connect the created WiFi network to one of the two Ethernet cards in the Mac Pro?
Or what?
Tim

I have half cracked it.
For some reason the first step it to turn internet sharing off.
Then internet sharing can be configured and the wireless network set up and given a password.
Then, and then only, turn internet sharing back on and turn WiFi ON. All this is on the Mac-Pro (late 2013).
Now the Mac Air sees the new network and can log on and connect to the WAN internet locations, at least via Safari.
BUT if I use Finder on the Air, it will connect to the Mac Pro but it will not display what is on its disc. Though I can do screen sharing. Odd.
Also Air-Drop has stopped working, so there is no means of transferring files between the Pro and the Air.
I am going away now for a few days and will revisit this on my return.
Thanks for your help.

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.

Mac Pro Late 2013 Cubase 8 Problems

Hello
I'm currently running Yosemite on the late 2013 Mac Pro.
I'm having major issues with Cubase 8.
When i select my Virus TI Channel, the whole program crashes. Sometimes it just randomly crashes.
Also, vst2 plugins are really laggy, and i can't figure out the problem, vst3 is fine. happens on 32bit and 64 bit version of cubase.
I tried reinstalling everything (including a clean OSX) but didn't help.
Back on mavericks i also had the VST2 laggy problem, but i had no problems with the virus ti at all.
I can't continue any of my projects now because it's just crashing when selecting the virus ti channel. (It does in empty projects aswel)
I tried different virus ti drivers, but that doesn't help at all. I know people that are using cubase 8 on yosemite with the virus and they have no problems, so i'm pretty sure it's not because of that.
Sometimes when i'm on skype for example, it freezes. when i quit it and try to reopen it the icon just keeps jumping in the dock. This also happened with chrome and twitter a few times, maybe the problems are connected with eachother? i don't know, just giving as much information as i can, because i really want this fixed. Cubase is showing crashlogs after it crashes but i can't figure out what it means.
Today i saw something in the crashlog about my graphicscard (2x AMD FirePro D300) could this mean something?
Anyone that could help me out here please? cause i've no idea what else to do.
Oh btw, i tried studio one aswel, the VST2 Lag problem is also happening in there.
My setup -
Mac Pro Late 2013
OSX Yosemite
12 GB Ram
Quad-Core Intel Xeon E5
2x AMD FirePro D300
Cubase 8
Virus TI Snow
MOTU 828 MK3 Hybrid
Greets!

I was using a hub, so I immediately removed that upon the first issues. But the USB has still frozen after the removal of the hub. The HD is a self powered G-Tech drive. I'll have to play around a bit more will all of your suggestions this weekend.
I woke up the computer just now to check the discussion, an am greeted with a notification from Mavericks that the "Disk Not Ejected Properly. (Eject disk before disconnecting or turning it off)" which the disk is still connected, and the usb seems to still work fine. In fact I was able to unplug the USB cable for the G-Tech HD, and then replug it in, everything reappeared fine. The USB bus was not frozen (this time).
But it's this kind of flakiness that has me coming and going. I haven't (yet) been able to identify whether the USB is the problem or the driver or a third thing I haven't figured out...

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

Similar Messages

Maybe you are looking for