Rendering slowed to a grinding halt CS6 on brand new mac pro...

Unbelievably and excruciatingly painful slow rendering in AE CS6 on a brand new Mac Pro.
My Pro:
3.5 Ghz 6-core Intel Xeon E5
32 GB 1867 MHz DDR3 ECC
AMD FirePro D700 6144MB
OSX 10.9.2
1) Internal 500GB SSD - (using 90gb for AE media cache)
External Thunderbolt drives:
2) 2 TB WD Black Caviar - (hosting all project assets)
3) 2 TB WD Black Caviar - (rendering destination)
Running After Effects CS6
The footage in my comp is just a bunch of illustrator files, and shape layers. There are 2 videos, but removing them does not improve the rendering. All the illustrator files are RGB. I am using effects on layers, but nothing out of the ordinary, a few displacement maps, some grain (non animated), some distort mesh (pre-rendering the distort mesh helped a little, but pretty sure there is something REALLY wrong here)
When its rendering, and I look at Activity Monitor, 85% of the CPU is still idle! I'm using Rendering Multiple Frames... 6 Cores for AE - 4 for others. 3GB for AE.
Of the 32gb RAM saving 4 for others applications.
For 25 seconds of footage, the task bar says something like 6 hours to render... and then it doesn't even finish. Even pre-rendering the distort mesh in a 4 layer pre-comp, for 25 seconds, took 25 minutes.
Someone please help, I'm not sure whats going on, but something is horribly wrong.

Not new to AE. Was rendering with animation codec, and have also tried using pro res 4444 to see if it will help.
comp size 1920 x 1080 @ 60fps
Turned off RMFS - and while this helps with the RAM preview (also setting the RAM preview to skip 1)
I was able to render using pro res 4444 @ 50% resolution @ 50% frame rate @ draft quality in 11 min (25 seconds) after pre-rendering 2 pre-comps.
Which is much better, but really don't understand why it could be taking so long.
I want to be able to RAM preview @ 60 fps - but every time RMFS is turned on it throws errors like "AE needs 2 or more playback frames" and I've also seen the error about it skipping frames and to allocate more memory to background processes. But no other programs running...
And I made a mistake: 12 cores, 8 for AE and 4 for other apps is what I had RMFS set to.

Similar Messages

The internet very very slow and drop in my brand new Mac pro OS X 10.8.3 any help!

I bought new Mac pro with Retina display (OS X 10.8.3) , I am suing Wifi and the Internet very slow and drop most of the time compare to my other Mac OS X10.7.4! any advice. Thank you

Pete
If multiple people are seeing the same problems after making the same changes it is hard to believe that each problem is fundamentally different. To say that a change is specific to a single configuration implies that every computer and every operating system installation are different. This is not rational. Treating each problem individually fixes one problem. Finding the root cause fixes all the problems. I am familiar with finding root cause of communication systems - in particular mission critical spacecraft command and telemetry links. That experience teaches me to break the problem into pieces. My troubleshooting indicates a very high packet loss between my computer and my wireless router. In the exact same configuration with with two other devices i see negligible packet losses. i can go outside my home network and see the same ping and traceroute evidence in comparing the devices. That rules out my ISP, my email provider and pretty much isolates the problem to the router Mac link. Is this thinking flawed? Can you suggest additional tests I can run to further isolate the dropped packet problem? Further, no hardware has changed in my configuration. The only change is the upgrade to 10.8.3.
In posting to other threads I am trying to find if there is evidence of the same problem and to determine if there is any other way to gather evidence, and perhaps suggest ideas that folks might double check their fixes. In doing so you aggregate the problem and not decimate it. The problem in this thread may not be solved if a packet loss is still present. I am seeing packet losses as high as 60%; an iPad at the same location is seeing less than 0.1%. The network connection will work with high packet losses. You know that is what TCP/IP does but why accept 20%, 10% or 5% packet loss if you know it should be much less than 1%. The problem can only be determined if it is tested.
I have created my own thread - I linked to it.
If you prefer to not allow comments on closed threads I would suggest closing the threads to editing. In the future I will link from my thread to the solved one however if my thread finds a better solution there will be no way of pointing from the closed thread to a better solution.
My apologies for attempting to perform a methodical root cause analysis.
Mike

PP CC 2014 Gets Extremely slow the larger my project gets on a new Mac Pro

My editing team and I have 3 of the new mac pro 3.7 GHZ Quad Core with 12 GB Ram, OSX10.9.3. We edit a TV show and the longer the timeline gets the slower PP gets. The problem is gradual, but by the time I get a timeline that is over 10 minutes long PP becomes very slow and unresponsive. Once my show reaches the 30 minute mark it's extremely slow. The main problem is with playback. I hit play and it takes anywhere from 10 to 20 seconds or more to even start playing. I'm editing footage from a Sony FS 700 and a Sony PXW-Z100, 1080i footage with no effects. Color correction and audio mixing is painfully slow once my timeline is complete. We converted from FCP7 and never had this problem with that program on the same computers. This problem is the same on all 3 computers so this can't be an isolated issue with just one computer.

Hi GW,
GWVideo wrote:
My editing team and I have 3 of the new mac pro 3.7 GHZ Quad Core with 12 GB Ram, OSX10.9.3. We edit a TV show and the longer the timeline gets the slower PP gets.
Sorry about that. You say you work in a team environment. Are you with CC for Teams or do each of you have individual licenses?
Do you work with networked drives? How does the project work if media is on local drives?
Do you have a deep organization system where the media is in a folder inside a folder, inside a folder, etc.? What happens if you simplify naming conventions and folder organization?
Do you use long names for your clips and sequences? What happens if you try shorter clips names and sequences.
Do you store the preview files and media cache database locally and on a fast drive? If not, move these files to a local drive.
Does the audio sample rate match sequence settings precisely? Mismatched settings can cause performance issues.
Do you use the Warp Stabilizer effect liberally? The project can bloat if too many Warp Stabilizer effects are added.
Is the project file migrated from an earlier version of Premiere Pro? Never update a project file to a new version of Premiere Pro. Remain on the current version until that project is complete.
If so, any or all of these items could be the root cause(s) of the problem for poor performance. Do some tests and post back about your findings.
Thanks,
Kevin

Brand new Mac Pro slowing down

I have a brand new mac-pro (8 core 2.8ghz,6gb 1x350/2x500gbhd)10.5.5.I have only put about 60gb on start up disk and 200gb on my HD 1.I already get the spinning ball when i open up some app's and to send a email (say 10 words nothing else)takes 10-15 secs to send,my broadband is up to 10mb.This is connected cable no wifi.I also have to quit force programs (they just freeze)and then it doesn;t quit force, can't do nothing.I HAXE ONLY USED THIS 4 TIMES.

The hatter,
Thank you for the history of the posts here.
I might add, Dano, your experience is actually quite unusual. In fact your mileage can be much worse on a PC. Viruses can wipe out ALL your data in an instant on a PC, while not on a Mac. Mac users at worse if there is something unstable usually only lose data if there is some hardware or software issue. So backing up your data is a prerequisite for owning any kind of computer.
Your experience with numerous spinning beachballs usually is indicative of faulty RAM, an overfull hard drive (which you obviously don't have), a directory issue* (which may happen if you don't know how to shut down your machine, or are using the wrong utilities to diagnose your machine), or some other hardware problem that can be sometimes diagnosed via the hardware test discs that came with your machine as indicated here:
http://docs.info.apple.com/article.html?artnum=303081
That lack of an error does not mean your RAM is healthy, it merely means the error is undetectable.
Secondly, if your version of Protools is too old, it will not run on a Mac Pro natively, so you have to make sure you are using the latest Protools. If your plugins are too old the same issue.
Third, if your software won't download fully, it usually is an indication that either your network is not setup properly, or your network preferences in your Mac is not setup properly. Some have found that by increasing the MTU they can make the networking work more smoothly. Some have found that by using an Open DNS they have less issues, as described on http://www.opendns.org/
So before you blame stuff on Apple lets get to the bottom of what's wrong with your machine.
- * Links to my pages may give me compensation.
Message was edited by: a brody

Adobe Bridge CC very slow on New Mac Pro

Im running both Bridge CC (6.1.0.115) and CS6 on my New Mac Pro
the Bridge CC is obviously slower than Bridge CS6.
CC also very easy to get the spinning ball every click on Bridge CC, very annoying.
Also Im using Dell 4K monitor, If I load monitor size preview will be really slow, even on the New Mac Pro. is there any way We can set a specific size of the preview? which can speedup the preview loading

If you go to the menu File > Project Settings > General and set the Renderer to Software Only, any change?
MtD

Premiere Pro CC continuous crash and extremely slow renders on a new Mac Pro.

Hello,
recently we changed our editing machines with the new Mac Pro with this configuration:
- CPU 3,5 GHz 6 core Intel Xeon E5
- 32 GB RAM
- 2x AMD FirePro D700 6 GB
we work on a server connected to the Mac Pro in Dual Ethernet configuration.
The rendering of a sequence at 1920x1080 with 3 video tracks (video footage converted at ProRes 422 LT, a title on a linked After Effects Comp and a PSD graphic overlay of a small logo) of the length of about 3 minutes it takes about 4 hour... when it doesn't crash.
When it crash, usually when i simply scroll the timeline, i receive an error message very long (if you want I can send you a rtf file about it, it's too long to paste it here).
These are my system information:
- Premiere Pro CC 8.2.0 (65)
- I've installed every updates available at this time
- OS X Yosemite 10.10.2
Thank you very much in advance, and sorry for my bad english.

Thanks Andrea for your assistance in reporting that additional information. You have come across an intermittent bug which has been reported by other users with no reliable repro steps for us to follow in house. So it appears to be mainly system specific, but we're not even sure which sorts of systems demonstrate it yet.
One other thing to try is clearing your media cache files (from preferences > media panel). In the meantime,e the best thing to do is make sure you submit those crash logs to adobe whenever you get them. This helps us identify common thread among various users who may be experiencing the same problem. Also, if you have time, please file a bug report describing the steps that caused the issue in your case: http://adobe.ly/ReportBug
Please be as specific as possible when describing your steps. Without a repeatable case, a bug like this is very, very difficult to fix. Thanks again for your support.
To work around the sloe render for AE comp problem, please try right clicking on the comp in the timeline and then choose the "Render and Replace" command to transcode it out to a more easily handled format. This should help a lot with your performance slowness, and you will still have the ability to restore the original comp files if needed.

"I've made a huge mistake." The laments of a new mac pro and ridiculously slow AE renders

I just purchased the late 2013 model of the Mac Pro with the following specs:
Processor: 3.5 GHz 6-Core Intel Xeon E5
Memory: 12 GB
Graphics: AMD FirePro D700
It barely squeaks out a faster render than my early 2008 Mac Pro (which has the following specs):
Processor: 2 x 3.2 Ghz Quad Core Intel Xeon
Memory: 16 GB
Graphics: NVIDIA GeForce 8800 GT
I obviously did NOT configure my new Mac Pro with the best features for AE CC. I still have time to return the machine, and try again. I would appreciate advice from someone who can ID where I went wrong - and direct me toward a machine that will churn out faster renders. Thanks so much!

Sorry, I'm out of the loop on the newer chipsets so would have to defer to others in that respect. There's a lot of reading to be done on multicore rendering in after effects; but you're best off running some test renders to see if its helping or hindering your comps and then base your decision for number of cores vs core speed on that. Either way multicore rendering does require a lot of RAM. You should be getting OK render speeds if you're not using the ray trace renderer, certainly should beat out the old box, that might be something to look into.
I can't advise using those thunderbolt pcie chasis to add an nvidia card to the new mac pro trash can; the sonnet ones we bought have been finicky with our AJA cards and I can only imagine a full graphics card under load being worse performance wise.
I built my hack a few years back on an ivy bridge i7 with 32 GB of ram. They have some newer guides for hardware choices and methods at http://www.tonymacx86.com/home.php
Although my build has been extremely stable, I will caution that putting together a hackintosh can be quite a pain even if you're an experienced system builder / knowledgable with *nix. If Windows is an option that can be considered, I've heard good things about the HP Z series workstations but Quadro cards seem overpriced IMO compared to the Geforce series for the cuda cores / ram size (though purists will surely encourage you not to go the budget route).

New Mac Pro (late 2013) crashes / freezes while rendering or editing in Premiere Pro CC

We recently purchased a new Mac Pro desktop (Late 2013, 16GB memory, D700 Graphic Card, 2.7 GHz -12 Core, OSX 10.9.3) and we are running Adobe CC on it. When using Premiere Pro CC (7.2.2) I am having major issues while rendering and editing. About 50% of the time when I try to render it starts off real fast then just freezes. This happens in Premiere and Media Encoder. Sometimes I can just Force Quit Premiere or Media Encoder and other times I have to do a hard restart on the entire computer because the entire computer freezes. The computer will also occasionally freeze whenever doing simple editing or stacking layers. The computer will also just decide to suddenly stop and restart when editing or doing simple tasks like browsing the web. Additionally there has been several times if the render does finish, the final video will have digital glitches throughout the video. I have to redo the render once or twice and it will finally be fine. This all is happening several times a day. This never happened on our previous Mac Pro, but we were not running Mavericks. I used Migration Assistant to transfer from old computer to new computer. So I don't know if this is an a problem with the actual Mac Pro, Mavericks, graphic card or Adobe? But right now I am very frustrated as you can imaging spending all this money for a computer that has been giving us more issues than our previous computer. Any help would be greatly appreciated!

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. All it does is to collect information about the state of the computer. That information goes nowhere unless you choose to share it. However, you should be cautious about running any kind of program (not just a shell script) at the behest of a stranger. If you have doubts, search this site for other discussions in which this procedure has been followed without any report of ill effects. If you can't satisfy yourself that the instructions are safe, don't follow them. Ask for other options.
Here's a summary of what you need to do, if you choose to proceed:
☞ Copy a line of text in this window to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
The sequence is: copy, paste, wait, paste again. You don't need to copy a second time. Details follow.
4. You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode, under the conditions in which the problem is reproduced. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
5. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
6. The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, though you may not see all of it in the browser window, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
Triple-click anywhere in the line of text below on this page to select it:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/libexec;clear;cd;p=(Software Hardware Memory Diagnostics Power FireWire Thunderbolt USB Fonts 51 4 1000 25 5120 KiB/s 1024 85 \\b%% 20480 1 MB/s 25000 ports 'com.autodesk.AutoCad com.evenflow.dropbox com.google.GoogleDrive' DYLD_INSERT_LIBRARIES\ DYLD_LIBRARY_PATH -86 ` route -n get default|awk '/e:/{print $2}' ` 25 N\\/A down up 102400 25600 recvfrom sendto CFBundleIdentifier 25 25 25 1000 MB );N5=${#p[@]};p[N5]=` networksetup -listnetworkserviceorder|awk ' NR>1 { sub(/^$[0-9]+$ /,"");n=$0;getline;} $NF=="'${p[26]}')" { sub(/.$/,"",$NF);print n;exit;} ' `;f=('\n%s: %s\n' '\n%s\n\n%s\n' '\nRAM details\n%s\n' %s\ %s '%s\n\t(%s)\n' );S0() { echo ' { q=$NF+0;$NF="";u=$(NF-1);$(NF-1)="";gsub(/^ +| +$/,"");if(q>='${p[$1]}') printf("%s (UID %s) is using %s '${p[$2]}'",$0,u,q);} ';};s=(' /^ *$|CSConfigDot/d;s/^ */ /;s/[-0-9A-Fa-f]{22,}/UUID/g;s/(ochat)\.[^.]+(\..+)/\1\2/;/Shared/!s/\/Users\/[^/]+/~/g ' ' s/^ +//;5p;6p;8p;12p;' ' {sub(/^ +/,"")};NR==6;NR==13&&$2<'${p[10]} ' 1s/://;3,6d;/[my].+:/d;s/^ {4}//;H;${ g;s/\n$//;/s: [^EO]|x([^08]|02[^F]|8[^0])/p;} ' ' 5h;6{ H;g;/P/!p;} ' ' ($1~/^Cy/&&$3>'${p[11]}')||($1~/^Cond/&&$2!~/^N/) ' ' /:$/{ N;/:.+:/d;s/ *://;b0'$'\n'' };/^ *(V.+ [0N]|Man).+ /{ s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;};$b0'$'\n'' d;:0'$'\n'' x;s/\n\n//;/Apple[ ,]|Intel|SMSC/d;s/\n.*//;/\)$/p;' ' s/^.*C/C/;H;${ g;/No th|pms/!p;} ' '/= [^GO]/p' '{$1=""};1' ' /Of/!{ s/^.+is |\.//g;p;} ' ' $0&&!/ / { n++;print;} END { if(n<200) print "com.apple.";} ' ' $3~/[0-9]:[0-9]{2}$/ { gsub(/:[0-9:a-f]{14}/,"");} { print|"tail -n'${p[12]}'";} ' ' NR==2&&$4<='${p[13]}' { print $4;} ' ' END { $2/=256;if($2>='${p[15]}') print int($2) } ' ' NR!=13{next};{sub(/[+-]$/,"",$NF)};'"`S0 21 22`" 'NR!=2{next}'"`S0 37 17`" ' NR!=5||$8!~/[RW]/{next};{ $(NF-1)=$1;$NF=int($NF/10000000);for(i=1;i<=3;i++){$i="";$(NF-1-i)="";};};'"`S0 19 20`" 's:^:/:p' '/\.kext\/(Contents\/)?Info\.plist$/p' 's/^.{52}(.+) <.+/\1/p' ' /Launch[AD].+\.plist$/ { n++;print;} END { if(n<200) print "/System/";} ' '/\.xpc\/(Contents\/)?Info\.plist$/p' ' NR>1&&!/0x|\.[0-9]+$|com\.apple\.launchctl\.(Aqua|Background|System)$/ { print $3;} ' ' /\.(framew|lproj)|\):/d;/plist:|:.+(Mach|scrip)/s/:[^:]+//p ' '/root/p' ' !/\/Contents\/.+\/Contents|Applic|Autom|Frameworks/&&/Lib.+\/Info.plist$/ { n++;print;} END { if(n<1000) print "/System/";} ' '/^\/usr\/lib\/.+dylib$/p' ' /Temp|emac/d;/(etc|Preferences)\//s/^\.\/[^/]+//p;' ' /\/(Contents\/.+\/Contents|Frameworks)\/|\.wdgt\/.+\.[bw]/d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| ","||kMDItem'${p[35]}'=");sub("^.."," ") };1 ' p '{print $3"\t"$1}' 's/\'$'\t''.+//p' 's/1/On/p' '/Prox.+: [^0]/p' '$2>'${p[9]}'{$2=$2-1;print}' ' BEGIN { i="'${p[26]}'";M1='${p[16]}';M2='${p[18]}';M3='${p[31]}';M4='${p[32]}';} !/^A/ { next;} /%/ { getline;if($5<M1) a="user "$2"%, system "$4"%";} /disk0/&&$4>M2 { b=$3" ops/s, "$4" blocks/s";} $2==i { if(c) { d=$3+$4+$5+$6;next;};if($4>M3||$6>M4) c=int($4/1024)" in, "int($6/1024)" out";} END { if(a) print "CPU: "a;if(b) print "I/O: "b;if(c) print "Net: "c" (KiB/s)";if(d) print "Net errors: "d" packets/s";} ' ' /r\[0\] /&&$NF!~/^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./ { print $NF;exit;} ' ' !/^T/ { printf "(static)";exit;} ' '/apsd|OpenD/!s/:.+//p' ' (/k:/&&$3!~/(255\.){3}0/ )||(/v6:/&&$2!~/A/ ) ' ' $1~"lR"&&$2<='${p[25]}';$1~"li"&&$3!~"wpa2";' ' BEGIN { FS=":";} { n=split($3,a,".");sub(/_2[01].+/,"",$3);print $2" "$3" "a[n]" "$1;b=b$1;} END { if(b) print("\n\t* Code injection");} ' ' NR!=4{next} {$NF/=10240} '"`S0 27 14`" ' END { if($3~/[0-9]/)print$3;} ' ' BEGIN { L='${p[36]}';} !/^[[:space:]]*(#.*)?$/ { l++;if(l<=L) f=f"\n "$0;} END { F=FILENAME;if(!F) exit;if(!f) f="\n [N/A]";"file -b "F|getline T;if(T!~/^(AS.+ (En.+ )?text$|POSIX sh.+ text ex)/) F=F" ("T")";printf("\nContents of %s\n%s\n",F,f);if(l>L) printf("\n ...and %s more line(s)\n",l-L);} ' ' BEGIN{FS="= "} /Path/{print $2} ' ' /^ +B/{ s/.+= |(-[0-9]+)?\.s.+//g;p;} ' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' / /{$0="'"${p[28]}"'"};1;' '/ en/!s/\.//p' ' NR!=13{next};{sub(/[+-M]$/,"",$NF)};'"`S0 39 40`" ' $10~/$L/&&$9!~"localhost" { sub(/.+:/,"",$9);print $1": "$9;} ' '/^ +r/s/.+"(.+)".+/\1/p' 's/(.+\.wdgt)\/(Contents\/)?Info\.plist$/\1/p' 's/^.+\/(.+)\.wdgt$/\1/p' );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps sudo\ crontab sudo\ iotop top pkgutil PlistBuddy whoami cksum kextstat launchctl sudo\ launchctl crontab 'sudo defaults read' stat lsbom mdfind ' for i in ${p[24]};do ${c1[18]} ${c2[27]} $i;done;' defaults\ read scutil sudo\ dtrace sudo\ profiles sed\ -En awk /S*/*/P*/*/*/C*/*/airport networksetup mdutil sudo\ lsof test );c2=(com.apple.loginwindow\ LoginHook '-c Print /L*/P*/loginw*' '-c Print L*/P*/*loginit*' '-c Print L*/Saf*/*/E*.plist' '~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' '-c Print\ :'${p[35]}' 2>&1' '-c Print\ :Label 2>&1' '{/,}L*/{Con,Pref}* -type f ! -size 0 -name *.plist -exec plutil -s {} \;' "-f'%N: %l' Desktop L*/Keyc*" therm sysload boot-args status " -F '\$Time \$Message' -k Sender kernel -k Message Req 'Beac|caug|dead[^bl]|FAIL|GPU |hfs: Ru|inval|jnl:|last value [1-9]|n Cause: -|NVDA$|pagin|proc: t|Roamed|rror|ssert|Thrott|tim(ed? ?|ing )o|WARN' -k Message Rne 'Goog|ksadm|SMC:' -o -k Sender fseventsd -k Message Req 'SL' " '-du -n DEV -n EDEV 1 10' 'acrx -o comm,ruid,%cpu' '-t1 10 1' '-f -pfc /var/db/r*/com.apple.*.{BS,Bas,Es,OSXU,Rem,up}*.bom' '{/,}L*/Lo*/Diag* -type f -regex .\*[cgh] ! -name *ag \( -exec grep -lq "^Thread c" {} \; -exec printf \* \; -o -true $ -execdir stat -f:%Sc:%N -t%F {} \;|sort -t: -k2 |tail -n'${p[38]} '-L {/{S*/,},}L*/Lau* -type f' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,E}* {/,}L*/{A*d,Ca*/*/Ex,Compon,Ex,In,iTu,Keyb,Mail/B,P*P,Qu*T,Scripti,Sec,Servi,Spo,Widg}* -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto,{cron,fs}tab,hosts,[lps]*.conf,pam.d,ssh{,d}_config,*.local} {,/usr/local}/etc/periodic/*/* /L*/P*{,/*}/com.a*.{Bo,sec*.ap}* .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers -getinfo\ "${p[N5]}" -P -m\ / '' -n1 '-R -l1 -n1 -o prt -stats command,uid,prt' '--regexp --only-files --files com.apple.pkg.*|sort|uniq' -kl -l -s\ / '-R -l1 -n1 -o mem -stats command,uid,mem' -i4TCP:0-1023 com.apple.dashboard\ layer-gadgets '-d /L*/Mana*/$USER&&echo On' );N1=${#c2[@]};for j in {0..8};do c2[N1+j]=SP${p[j]}DataType;done;N2=${#c2[@]};for j in 0 1;do c2[N2+j]="-n ' syscall::'${p[33+j]}':return { @out[execname,uid]=sum(arg0) } tick-10sec { trunc(@out,1);exit(0);} '";done;l=(Restricted\ files Hidden\ apps 'Elapsed time (s)' POST Battery Safari\ extensions Bad\ plists 'High file counts' User Heat System\ load boot\ args FileVault Diagnostic\ reports Log 'Free space (MiB)' 'Swap (MiB)' Activity 'CPU per process' Login\ hook 'I/O per process' Mach\ ports kexts Daemons Agents launchd Startup\ items Admin\ access Root\ access Bundles dylibs Apps Font\ issues Inserted\ dylibs Firewall Proxies DNS TCP/IP Wi-Fi Profiles Root\ crontab User\ crontab 'Global login items' 'User login items' Spotlight Memory Listeners Widgets Parental\ Controls );N3=${#l[@]};for i in 0 1 2;do l[N3+i]=${p[5+i]};done;N4=${#l[@]};for j in 0 1;do l[N4+j]="Current ${p[29+j]}stream data";done;A0() { id -G|grep -qw 80;v[1]=$?;((v[1]==0))&&sudo true;v[2]=$?;v[3]=`date +%s`;clear >&-;date '+Start time: %T %D%n';};for i in 0 1;do eval ' A'$((1+i))'() { v=` eval "${c1[$1]} ${c2[$2]}"|'${c1[30+i]}' "${s[$3]}" `;[[ "$v" ]];};A'$((3+i))'() { v=` while read i;do [[ "$i" ]]&&eval "${c1[$1]} ${c2[$2]}" \"$i\"|'${c1[30+i]}' "${s[$3]}";done<<<"${v[$4]}" `;[[ "$v" ]];};A'$((5+i))'() { v=` while read i;do '${c1[30+i]}' "${s[$1]}" "$i";done<<<"${v[$2]}" `;[[ "$v" ]];};';done;A7(){ v=$((`date +%s`-v[3]));};B2(){ v[$1]="$v";};for i in 0 1;do eval ' B'$i'() { v=;((v['$((i+1))']==0))||{ v=No;false;};};B'$((3+i))'() { v[$2]=`'${c1[30+i]}' "${s[$3]}"<<<"${v[$1]}"`;} ';done;B5(){ v[$1]="${v[$1]}"$'\n'"${v[$2]}";};B6() { v=` paste -d: <(printf "${v[$1]}") <(printf "${v[$2]}")|awk -F: ' {printf("'"${f[$3]}"'",$1,$2)} ' `;};B7(){ v=`grep -Fv "${v[$1]}"<<<"$v"`;};C0(){ [[ "$v" ]]&&echo "$v";};C1() { [[ "$v" ]]&&printf "${f[$1]}" "${l[$2]}" "$v";};C2() { v=`echo $v`;[[ "$v" != 0 ]]&&C1 0 $1;};C3() { v=`sed -E "$s"<<<"$v"`&&C1 1 $1;};for i in 1 2;do for j in 2 3;do eval D$i$j'(){ A'$i' $1 $2 $3; C'$j' $4;};';done;done;{ A0;A2 0 $((N1+1)) 2;C0;A1 0 $N1 1;C0;B0;C2 27;B0&&! B1&&C2 28;D12 15 37 25 8;A1 0 $((N1+2)) 3;C0;D13 0 $((N1+3)) 4 3;D23 0 $((N1+4)) 5 4;for i in 0 1 2;do D13 0 $((N1+5+i)) 6 $((N3+i));done;D13 1 10 7 9;D13 1 11 8 10;D22 2 12 9 11;D12 3 13 10 12;D23 4 19 44 13;D23 5 14 12 14;D22 6 36 13 15;D22 7 37 14 16;D23 8 15 38 17;D22 9 16 16 18;B1&&{ D22 11 17 17 20;for i in 0 1;do D22 28 $((N2+i)) 45 $((N4+i));done;};D22 12 44 54 45;D22 12 39 15 21;A1 13 40 18;B2 4;B3 4 0 19;A3 14 6 32 0;B4 0 5 11;A1 17 41 20;B7 5;C3 22;B4 4 6 21;A3 14 7 32 6;B4 0 7 11;B3 4 0 22;A3 14 6 32 0;B4 0 8 11;B5 7 8;B1&&{ A2 19 26 23;B7 7;C3 23;};A2 18 26 23;B7 7;C3 24;A2 4 20 21;B7 6;B2 9;A4 14 7 52 9;B2 10;B6 9 10 4;C3 25;D13 4 21 24 26;B4 4 12 26;B3 4 13 27;A1 4 22 29;B7 12;B2 14;A4 14 6 52 14;B2 15;B6 14 15 4;B3 0 0 30;C3 29;A1 4 23 27;B7 13;C3 30;D13 24 24 32 31;D13 25 37 32 33;A1 23 18 28;B2 16;A2 16 25 33;B7 16;B3 0 0 34;B2 21;A6 47 21&&C0;B1&&{ D13 21 0 32 19;D13 10 42 32 40;D22 29 35 46 39;};D23 14 1 48 42;D12 34 43 53 44;D22 0 $((N1+8)) 51 32;D13 4 8 41 6;D12 26 28 35 34;D13 27 29 36 35;A2 27 32 39&&{ B2 19;A2 33 33 40;B2 20;B6 19 20 3;};C2 36;D23 33 34 42 37;B1&&D23 35 45 55 46;D23 32 31 43 38;D12 36 47 32 48;D13 20 42 32 41;D23 14 2 48 43;D13 4 5 32 1;D22 4 4 50 0;D13 14 3 49 5;B3 4 22 57;A1 26 46 56;B7 22;B3 0 0 58;C3 47;D23 22 9 37 7;A7;C2 2;} 2>/dev/null|pbcopy;exit 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
7. Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Click anywhere in the Terminal window and paste by pressing command-V. The text you pasted should vanish immediately. If it doesn't, press the return key.
8. If you see an error message in the Terminal window such as "syntax error," enter
exec bash
and press return. Then paste the script again.
9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important. If you don't know the password, or if you prefer not to enter it, press the key combination control-C or just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, there will be nothing in the Terminal window and no indication of progress. Wait for the line
[Process completed]
to appear. If you don't see it within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report the results. No harm will be done.
11. When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with "Model Identifier." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
12. When you post the results, you might see the message, "You have included content in your post that is not permitted." It means that the forum software has misidentified something in the post as a violation of the rules. If that happens, please post the test results on Pastebin, then post a link here to the page you created.
Note: This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
Copyright © 2014 by Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

WHY AFTER EFFECTS STILLS SO SLOW IN THE NEW MAC PRO?

I have the new mac pro with this settings:
3 GHz 8-Core Intel Xeon E5
64 GB 1867 MHz DDR3 ECC
AMD FirePro D700 6144 MB
Software OS X 10.9.2
And the AE performs slower than in my old mac pro. I have set the preferences as seen on all those tutorials on this site, I have an SSD external disc for cache files, memory and multiprocessing settings correctly...and previews are very very slow, and I can not even render a single comp without waiting 10 minutes. I am very disappointed and frustrated with this situation...
Am I missing something?

I don't understand why it's even up to the user to figure out what settings are best. Isn't the application in a vastly superior position to know what its resource constraints are at any given moment? Instead I have to try rendering a couple of comps, kill the render, fix the render queue since AE STILL doesn't offer a graceful way to quit and resume renders.
I have to say that one of the attributes of AE that consistently disappoints me is multiprocessing and its accompanying memory management policies. I regularly produce hundreds of network graphics at a go, and I can never reap any benefit from multiprocessing, because AE has to load the entire project into each core, instead of just loading the comps it needs to render at any given time. Similarly, a project that requires 400 heavily-automated versions (a regular occurrence for some of my Latin America clients, where graphics have to be versioned for multiple feeds and languages) can simply choke AE. If it could load this stuff into memory on-the-fly (or at least offload some of it when memory gets tight), this wouldn't be a problem, and I sincerely doubt the performance would be worse than it is now. This is on a previous-gen Mac Pro with 48 GB RAM, so, while not strictly state-of-the-art, it's no slouch.
Heck, even opening some of these projects just to browse their contents is a painful 30-minute process, as AE apparently has to not only load everything into memory before I can even do anything, but, judging by how it hangs for many minutes at 99% on the progress bar, it also seems to be evaluating all the expressions in all the hundreds of comps (presumably so it can render the project thumbnails). And yes, I've tried splitting the projects up, but this leads to its own complications, particularly when revisions come in a week or two later.
I don't want any of this to sound overly negative, since I know AE has a small team and this sort of stuff isn't trivial to implement. I do appreciate this application and all it does, particularly for me creatively and professionally. I just get a bit tired of seeing new releases come every year and this stuff seems to go unaddressed.

I just brought a brand new Macbook pro retina display, when i connect it to my apple tv through airplay its too slow and when it try to play a movie apply tv is always a minute or 2 behind. How can i fix this?

I just brought a brand new Macbook pro retina display, when i connect it to my apple tv through airplay its too slow and when it try to play a movie apply tv is always a minute or 2 behind. How can i fix this?

Hello HanaAmer1,
We've an article which provides troubleshooting steps that can help get AirPlay workign correctly.
iTunes: Troubleshooting AirPlay and AirPlay Mirroring
http://support.apple.com/kb/TS5209
Cheers,
Allen

I am having a problem with very slow start up after expanding RAM on my 2009 Mac Pro.

I am having a problem with very slow start up after expanding RAM on my 2009 Mac Pro (8 Core 2.93GHz). When I run the Mac Pro with 2 x 2Gb RAM it takes 4 seconds before the gray screen, chime and spinning wheel appear.However when I expand the RAM to 20GB the grey screen and chimes appear after a long 20+ second black screen.
The RAM modules are paored 2 x 4GB Crucial CT51272BA1339.M18FMR and 6 x 2GB SAMSUNG M391B5673FH0-CH9, all DDR3 ECC.
Reading articles on the internet, I thought it may be damaged RAM modules, but I have completed memtest and all are okay. I have tried changing the pairs around and if I use any paired 2 modules the Mac Pro starts normally, only when I try running more than 2 modules the delayed start up happens. (black screen 20 Seconds)
I also have tried PRAM and SMU resets after changing the RAM setups, and the issues always occurs when I have more than 2 modules. As you can see I have 6 SAMSUNG modules and even with identical modules the issue happens, when increasing the RAM to more than 2 modules.
The Mac Pro runs fine after the start up screen and can see all the modules, but has anyone else come across this issue, or have any ideas as to why my Mac Pro is taking 20 seconds to start up with 20 GB RAM?

Hi there. Thanks for your comments.
I have tried all the different combinations of RAM setup, and as stated in my initial topic, the Mac Pro boot up time only slows when I have more that 2 modules. Where I place these does not seem to make a difference.
I have taken the Mac Pro to an Apple Reseller technician yesterday and they where not able to find any RAM errors. Apparently the boot up time is within Apple's acceptable parameters for this set up.
Could anyone that is running a Mac Pro 2009 with more that 4 modules of RAM, please let me know if the boot up time is normal. ( the time it takes from pressing the power button to seeing the gray screen around 16 - 20 seconds)
Or is anyone else having the same issues?
thanks for your responce

I bought a brand new Mac 27" desktop that came loaded with Adobe CS6. Everything worked like a charm until the hard drive, 1Tb, developed a bad sector and the Apple Store reinstalled a new one as I had extended warranty with them. The recycled the drive i

I bought a brand new Mac 27" desktop that came loaded with Adobe CS6. Everything worked like a charm until the hard drive, 1Tb, developed a bad sector and the Apple Store reinstalled a new one as I had extended warranty with them. They recycled the drive immediately (like a fool I didn't ask for it back to get the data off it.) But luckily I have all my data on CrashPlan. I downloaded it and it worked great except I downloaded it to the desktop and not the original location so it got squirrely. I also have an external 1.5Tb drive that I wanted to make bootable so I installed Mavericks 10.9.3 . I then went ahead and installed it on the newly installed drive too.
I think that because I have a new drive Adobe thinks I have a news computer. I bought the 27" Mac brand new from Ebay and it came loaded with software, including CS6. I have a serial number for CS6 but Adobe said it wasn't valid. (I have owned CS2, CS4 and now CS6 which came preloaded onto the Mac by the seller who told me that the software was registered to the Mac???
I am going to re-download the backup but this time to the original location (I still don't think it will work with Adobe. What can I do about this?
iMac 27-inch, Late 2012
Processor 3.2 GHz Intel Core i5
Memory 32 GB 1600 MHz DDR3
Graphics NVIDIA GeForce GTX 675MX 1024 MB
Software OS X 10.9.3 (13D65)@

You need to contact Adobe Support either by chat or via phone when you have serial number and activation issues.
Here is a link to a page with options to help make contact:
http://www.adobe.com/support/download-install/supportinfo/

ITunes downloads fast on old Mac mini but slow on brand new Macbook Pro on the same WiFi network?

Hi all,
I have an old Mac mini that's from around 2008 and runs on Snow Leopard. I also have a brand new Macbook Pro with retina display that's running Mountain Lion. Both running iTunes 10.6.3.
I never noticed anything wrong with my MBP's connection speed until last night when I downloaded a free TV episode from iTunes. The download speed varied between 20KB/s and 40KB/s and it took me 7 to 8 hours to download a single episode. I checked my internet connection but there was nothing wrong with it, SpeedTest.net told me I had a download speed of 94MB/s and upload speed of 80MB/s, it was only iTunes that was unbearably slow.
Today I was browsing iTunes again and was planning to buy some movies, but again it took forever for the trailers to download. So I fired up my Mac mini just to see if it would be just as slow. Turned out my Mac mini could download the same trailers from iTunes at a much higher speed than my MBP (around 3MB/s on the ones I tested).
So what gives? They are on the same Wifi network provided by an Airport Extreme, and although my iPhone and iPad are also connected to it, no one else is doing any heavy duty downloading.
Thanks in advance!
Keywords: iTunes download speed, slow iTunes downloads, different connection speeds on different Macs, slow iTunes connection, iTunes takes a long time to download

It's possible the DNS setting your ISP is using are interfering. Although your PC works OK Macs can be sensitive to DNS settings. Here is a MacWorld DNS Troubleshooting article that explains the issue and below is how to fix it.
1. System preferences
2. Network
3. Click Advanced
4. Click DNS tab
5. Click + sign
6. Add 208.67.222.222
7. Click + sign
8. Add 208.67.220.220
9. Click OK.
10. Exit System Preferences
11. Try out your MBP and report what happened.
Roger

How do I re-install Adobe CS6 on a new mac with no disc drive?

How do I re-install Adobe CS6 on a new mac with no disc drive?

Downloads available:
Suites and Programs: CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4 | CS3
Acrobat: XI, X | 9,8 | 9 standard
Premiere Elements: 12 | 11, 10 | 9, 8, 7
Photoshop Elements: 12 | 11, 10 | 9,8,7
Lightroom: 5.6| 5 | 4 | 3
Captivate: 8 | 7 | 6 | 5
Contribute: CS5 | CS4, CS3
Download and installation help for Adobe links
Download and installation help for Prodesigntools links are listed on most linked pages. They are critical; especially steps 1, 2 and 3. If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.

Render times very slow on new Mac Pro and Premiere CC

Hi there
I have a brand spanking new Mac Pro (specs below) working off a G Studio r 24 TB array. Rendering anything in Premiere is taking an age (2 minutes timeline is taking 30 minutes). I am cutting 4k Sony F5 footage (XAVC). I have done tests with 1080 material and this doesn't make any difference.
I have spoken to Adobe support and reset permissions plus all the basic workarounds suggested: but there has been no improvement. I was due a call back but have not heard anything.
Can anyone suggest a solution - i have several important deadlines coming up, and can't really deal with the downtime.
I understand 3rd party apps take longer, but even with PP effects, rendering is taking way too long: especially with a super fast system like this.
Regards
Louis
YOSEMITE 10.10.3
Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: 8-Core Intel Xeon E5
Processor Speed: 3 GHz
Number of Processors: 1
Total Number of Cores: 8
L2 Cache (per Core): 256 KB
L3 Cache: 25 MB
Memory: 64 GB
Boot ROM Version: MP61.0116.B11
SMC Version (system): 2.20f18
Illumination Version: 1.4a6
Serial Number (system): F5KPD0DDF694
Hardware UUID: 8975F4BE-0140-583C-9615-E3BD60BEC8F2

If you go to the menu File > Project Settings > General and set the Renderer to Software Only, any change?
MtD

Rendering slowed to a grinding halt CS6 on brand new mac pro...

Similar Messages

Maybe you are looking for