- Last post
- 11 Responses
I see they bypassed the yearly August/September upgrade, made it available this week and called it CC 2017.
Has anyone upgraded yet?
I'm on Mac Pro running 10.11.6, mostly concerned about After Effects and video work.
Just updated it this morning. So far no issues, but it's early days yet. My first impression is that ID seems a bit speedier.
I'm on a MacBook Pro (Retina, 15-inch, Late 2013) running 10.12.1, with 16 GB RAM at work.
- Nice. I have that laptop at home. How is Sierra? Any problems with that? I'm still on 10.10.CyBrainX
- I'm happy with Sierra, it's good and solid. So, assuming Adobe CC hasn't got any of its famous catastrophic bugs in it (ha!), this will be a good combo.Continuity
- perfect feedback, Continuity. :) I'm on the exact same setup... ...
*grabs balls... here we go... *clickPonyBoy
- Good luck!Continuity
Is it working ok with MacOS Sierra?
I'll skip this one and wait for CC 2020
Core i7-4790K @ 4.733 GHz | ASUS Z97-E/USB3.1 | 16GB DDR3-2148 MHz 9-10-10-29 @ 1.51v | Sapphire DUAL-X Radeon R9 280 @ 1100MHz/1575MHz | Samsung 850 EVO 250GB (Boot) | Intel 520 & 535 120 GB in RAID 0 | Corsair CX750M PSU | Windows 10 Pro 64-bit
Runs fine on my system - Bridge seems a *lot* faster. Coolorus, my one extension is broken but that always happens with updates - the dudes who make it are on point and normally have a fix within hours of the new CC being released.
The new PS 'New' dialogue box is horseradish though, clunky and awkward and totally made for touch devices - thankfully there is an option to retain the legacy new document window.
Updated OK so far with PS, AI use. However, for the first time ever After Effects real-time preview spinning busy cursor issues occurred; I've been running real-time for the past two releases just ducky (off a scratch SSD) though I hear others have had issues and this is the first AFX release that gives them realtime preview successfully. I'm on old and very hot-rodded hardware though.
My issue is well documented here: https://forums.adobe.com/thread/…
The timeline not as your last window fix is obnoxious, but really works.
("Hot-rodded" Mac Pro 2010 running Sierra 10.12.1 off PCIe SSD)
Has anyone been having these issues with Adobe Media Encoder?
It's slower than ever before. Sometimes it takes 20 seconds to add an After Effects comps to the Adobe Media Encoder cue. I'm not talking about very complex comps and I'm on a Mac Pro beast with 32 GB of RAM.
The size you can generate won't be full res unless you have your AE comp setting to be full. And if you try to change it in AME, it interpolates from low res.
- when the update rolled out, I didnt update because of the amount of plugins I use on current gigs, but then exporting via Media Encoder stopped workingmoldero
- I updated and it exports to Media encoder are faster than when it worked in '15moldero
- so you and I are getting the opposite effect here it seemsmoldero
- I'm on the mac trash can, you on mac or PC?moldero
- Mac Pro. trash can.CyBrainX
- yeah weird, did you try that customer support thing someone here mentioned where they log onto our system?moldero
- btw, on CC15 for me it always took between 10-30 seconds to export from AE to ME, but now its almost instant for me on CC17moldero
- if you find a fix ide love to hear it in case it starts doing that shit againmoldero
- I'm getting this too. Not with previous versionz.MrT
- Me too. I never had this problem in previous versions. Sometimes it would hang a little bit but not this bad.CyBrainX
I'm getting the playback beachball bug in After Effects. If I close the timeline panel and hit spacebar it plays back fine, it's a really dumb bug.
- I've had that bug for the past two major releases Was really hoping that would be fixed but guess not.fyoucher1
- I had never experienced it before, there's a whole bunch of threads about it on adobe.com - looks like it's a driver issue.zarkonite
- i never had thatmoldero
- It manifested for me with this version, never had it before. Decent fix is putting Render Queue tab at the bottom of your window layout.evilpeacock
- Yeah I just hit the shortcut for Render Queue so it covers up the timeline. The issue is with the timeline and screen refreshing.fyoucher1
- Well, supposedly there's a new update that came out this morning for AE2017 that fixes this. Can anyone confirm if this works?fyoucher1
updated. The 2 first start of Photoshop was a pain tho... suuuper slow, unworkable.. had to reboot my computer.
Now it work. Like i had to open the path first, now it slides well.
Just signed up for Adobe CC.
40% Black Friday Discount.
In almost twenty years of usage it's the first time I pay for it.
Feels weirdly like nothing special neither pissed off...nothing.
- I just recently started paying for it after being on CS5 for 8 years. Typekit makes it worth the $$$hotroddy
- 40% for one year?hotroddy
- yes, for one yearoey
- Also.. Dreamweaver was a pleasant surprise from cs5. Everything else is the same.hotroddy
- yes, typekit is goodGnash
- I'm shocked that everything isn't a pleasant surprise after skipping 5 versions.CyBrainX
- After 2 versions. I was on CS5.hotroddy
Does anyone know how to get the old f10 function from older versions of Photoshop to CC?
As you may recall - The f10 key would bring up all your open windows in a tile format. So you could easily scan through all your files. Almost like a rudimentary Bridge but for your open files.
*In cs3 all open files were 'floating windows'
*In cs5 all 'floating windows' would re-arrange to this tile format
But in CC there is no f10 key. I think it's reservered for an apple command rather than PS command.
Does anyone else know what I'm talking about?
> Arrange > Tile....Gnash
- not sure if it's tied to a keyGnash
- it's close but not the same. you can't jump in and out of files easily. I guess just something I have to relearn.hotroddy
- but thanks.. i will try to see if i can assign as keyboard shortcut.hotroddy
- a good analog is the 'mission control' feature that apple uses on os10hotroddy
- oh, I know what you mean. not sure what happened to itGnash