No transperancy rendering 3d pdf on Mac Pro

I'm in a limbo between Apple and Adobe. Although I find it hard to believe that I am the only one who uses 3d pdf diligently and try to do it on a fullgrown Mac. It started when I took my previous MacPro (Mid 2010) in use almost 4 years ago. All 3d-pdfs I tried to render on the machine lacked transparency and materials. The same file on an iMac or a PC looked like I wanted. I complained but the great As blamed each other. And I gave up the fight.
I resently bought a new MacPro (late 2013), partly in the hope that I would get a video card that was supported by Adobe/Apple. But no. The same dreary rendering without material properties. On this machine, I have installed Windows 8.1 throuhg bootcamp. And when I run Reader on Windows my 3d-pdfs looks as I expect. The same machine, the same graphics card, the same file ...
Am I the onely one experiencing this problem? Can I do anything about it?

Ok my images are removed...
But I cant give it up yet. Am I the only one experiencing this problem??? Here are 2 shrunk images. First from Acrobat Reader running on Mac OS 10.92:
Then Acrobat Reader on the same Mac Pro (late 2013) running on Windows 8.1:
Notice the semi transparent ceiling and more vivid colors.
I have an old post regarding the same problem on my previous Mac Pro here: https://discussions.apple.com/thread/3311368
Please give me a response if you have seen this...

Similar Messages

Poor rendering of 3d pdf on Mac Pro

I'm in a limbo between Apple and Adobe. Although I find it hard to believe that I am the only one who uses 3d pdf diligently and try to do it on a fullgrown Mac. It started when I took my previous MacPro (Mid 2010) in use almost 4 years ago. All 3d-pdfs I tried to render on the machine lacked transparency and materials. The same file on an iMac or a PC looked like I wanted. I complained but the great As blamed each other. And I gave up the fight.
I resently bought a new MacPro (late 2013), partly in the hope that I would get a video card that was supported by Adobe/Apple. But no. The same dreary rendering without material properties. On this machine, I have installed Windows 8.1 throuhg bootcamp. And when I run Reader on Windows my 3d-pdfs looks as I expect. The same machine, the same graphics card, the same file ...
Am I the onely one experiencing this problem? Can I do anything about it?

Ok my images are removed...
But I cant give it up yet. Am I the only one experiencing this problem??? Here are 2 shrunk images. First from Acrobat Reader running on Mac OS 10.92:
Then Acrobat Reader on the same Mac Pro (late 2013) running on Windows 8.1:
Notice the semi transparent ceiling and more vivid colors.
I have an old post regarding the same problem on my previous Mac Pro here: https://discussions.apple.com/thread/3311368
Please give me a response if you have seen this...

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.

12 core Mac Pro does not improve render time over iMac quad core

I'm rendering the same composition independently on two computers and they are basically rendering at the same rate, which is slightly better than 1 frame per second.
The project settings and preferences are identical in each instance (with the exception of memory and multiprocessing, which I have experimented with ad nauseum). The composition includes no motion blur, no effects, just a couple of layers of chroma keyed .mov files (using keylight 2.0) and some still images. Neither machine is running any other applications, except occasionally Google Chrome, which seems to have no effect on performance.
Both systems are running the latest version of After Effects CC (2014) and using the Classic 3D renderer.
System 1 MAC PRO:
Mac Pro 12 core 2.7 GHz Intel Xeon E5
dual AMD FirePro 500D 3072 MB GPUs
32 GB RAM
OS X 10.9.4
System 2 iMAC:
iMac quad core 2.5 GHz Intel Core i5
AMD Radeon HD 6750M 512 MB GPU
8 GB RAM
OS X 10.9.3
As you can see, system 1 is vastly more powerful, and yet no combination of memory/multiprocessing settings can get the system to render faster than system 2.
It doesn't seem to matter how much or little RAM I reserve for other applications (I have settled on 4 GB), or the number of CPUs I reserve for After Effects. The one setting that has improved performance is turning OFF render multiple frames. And even then it only brings the performance of the Mac Pro up to par with the iMac. I have cleared my cache, rebooted the computer, and read everything I can find online regarding the optimization of render settings.
Here's a comparison of the respective CPU Loads:
iMac
Mac Pro
With such a low CPU load, After Effects is obviously not utilizing the resources available to it on the Mac Pro. What a waste.
Can anyone help?

There's plenty of debate about the new Mac Pro vs a kitted out iMac. Benchmarks show that some iMac After Effects processing can actually be faster than on a Mac Pro, depending on the content and some other factors. If you're using software that has been optimised for the Mac Pro's GPU-centric architecture, like Final Cut Pro X, you will see great benefits.
mac pro vs imac
In my own facility recently we opted out of purchasing Mac Pros this year, and bought top-end iMacs instead. The benefit to cost ratio simply didn't make sense for us right now. Mac Pros are awesome machines, but a significant component of their cost is the dual GPUs, which are simply no benefit to After Effects.
Reports say that the After Effects engineers are working on a major revamp of the After Effects processing system, so I'm betting you will realise far greater benefits from your Mac pro in coming AE versions. For now, you may continue to see performance that is not spectacularly better than a souped-up iMac, depending on the type of processing involved.
I've seen a few benchmarks that suggest the 8 core systems give better bang-for-buck than the 12 cores. Try reducing your processors to 8 in After Effects and see if it makes a difference. With 8 cores, allocate 3GB of RAM per core to leave some RAM for the OS.

Adobe After Effect CC 2014 on Mac Pro 2013 and Performance

Hi everyone.
I'm planning to jump from my Mac Mini 2011 to some Mac Pro (cylinder) - 4 core or maybe 6 core and I'd like to know from someone who got experience with Ae and rendering/previewing or how smooth work it is on Mac Pro? I can't find any detailed video about performance Adobe Ae+Pr on Mac Pro. Of course I saw a thousand of benchmarks with scores but that doesn't say anything to me. I need to know if those grands are very well spent. I'm quiet afraid of those RAM previewing. Also I saw nice video with man who showed fast rendering on Premiere on Mac Pro. Actually I haven't got any problem even on Mac Mini with premiere - everything was smooth, without lack, delays or something but when I sent some tracks to Ae for stabilising or changes and see the results back in Premiere was a nightmare.
I would like to know what is you opinion and experiences. Thank you very much.
PS: If the Ae will be like that as it is today I have no choice to start with the Final Cut Pro X + Motion

AE is almost all CPU and ram. Your ram preview time will be decided by those specs. The nMPro is not the current best solution for that since that is the previous Ivy-E Platform with DDR3. The X99 Is the current platform ie Haswell E which has DDR4 and the 8 Core CPU's. That would be the better way to go if AE and ram preview is your focus. How ever if you have to go mac then I would not suggest less than the 6 Core and 32GB of ram. The Dual GPU's have no impact on AE since the only acceleration is Ray Tracer and that is Nvidia only.
Eric
ADK

Which Mac Pro? More cores=slower speeds? And most of us know the speed matters or FPU for music and I don't understand the faster is for the least amount of procs. And while I get the whole rendering thing and why it makes sense.

Which Mac Pro? More cores=slower speeds? And most of us know the speed matters or FPU for music and I don't understand the faster is for the least amount of procs. And while I get the whole rendering thing and why it makes sense.
The above is what the bar says. It's been a while and wondered, maybe Apple changed the format for forums. Then got this nice big blank canvas to air my concerns. Went to school for Computer Science, BSEE, even worked at Analog Devices in Newton Massachusetts, where they make something for apple.
The bottom line is fast CPU = more FPU = more headroom and still can't figure out why the more cores= the slower it gets unless it's to get us in to a 6 core then come out with faster cores down the road or a newer Mac that uses the GPU. Also. Few. I'm the guy who said a few years ago Mac has an FCP that looks like iMovie on Steroids. Having said that I called the campus one day to ask them something and while I used to work for Apple, I think she thought I still did as she asked me, "HOW ARE THE 32 CORES/1DYE COMING ALONG? Not wanting to embarrass her I said fine, fine and then hung up. Makes the most sense as I never quite got the 2,6,12 cores when for years everything from memory to CPU's have been, in sets of 2 to the 2nd power. 2,4,8,16,32,64,120,256,512, 1024, 2048,4196,8192, 72,768. Wow. W-O-W and will be using whatever I get with Apollo Quad.
Peace to all and hope someone can point us in THE RIGHT DIRECTION. THANK YOU

Thanks for your reply via email/msg. He wrote:
If you are interested in the actual design data for the Xeon processor, go to the Intel site and the actual CPU part numbers are:
Xeon 4 core - E5.1620v2
Xeon 6 core - E5.1650v2
Xeon 8 core - E5.1680v2
Xeon 12 core - E5.2697v2
I read that the CPU is easy to swap out but am sure something goes wrong at a certain point - even if solderedon they make material to absorb the solder, making your work area VERY clean.
My Question now is this, get an 8 core, then replace with 2 3.7 QUAD CHIPS, what would happen?
I also noticed that the 8 core Mac Pro is 3.0 when in fact they do have a 3.4 8 core chip, so 2 =16? Or if correct, wouldn't you be able to replace a QUAD CHIP WITH THAT? I;M SURE THEY ARE UO TO SOMETHING AS 1) WE HAVE SEEN NO AUDIO FPU OR PERHAPS I SHOULD CHECK OUT PC MAKERS WINDOWS machines for Sisoft Sandra "B-E-N-C-H-M-A-R-K-S" -
SOMETHINGS UP AND AM SURE WE'LL ALL BE PLEASED, AS the mac pro was announced Last year, barely made the December mark, then pushed to January, then February and now April.
Would rather wait and have it done correct than released to early only to have it benchmarked in audio and found to be slower in a few areas- - - the logical part of my brain is wondering what else I would have to swap out as I am sure it would run, and fine for a while, then, poof....
PEACE===AM SURE APPLE WILL BLOW US AWAY - they have to figure out how to increase the power for 150 watts or make the GPU work which in regard to FPU, I thought was NVIDIA?

Why can't I print a pdf from my mac pro to my printer?

why can't I print a pdf from my mac pro to my printer?

Don't know! You'll have to give us more details of what's happening when you try. Can you print other documents OK? When you try to print, does the printer icon appear in the dock - click on it and see if there are any printer messages.
Matt

I installed CS6 on Mac Pro (10.9 software version). I don't see the Adobe PDF printer in the printer/fax section. I can not figure how to create the PDF Printer.

I can not figure how to create a Adobe PDF Printer. Normally when you install the package ( CS6 Standard for Mac Pro) the installer creates the PDF printer automatically. In the System Preferences under the Printer/Fax I don't see the PDF printer. How do you create the PDF printer.
Thanks,
Melanie

did you install acrobat x and does it work as expected?

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.

Mac Pro 3.1 eight core FCP 6 shows all 8 cores rendering??

I just got a Mac Pro early 2008 3.1 with eight cores...running Leopard 10.5.8 I've read on this forum at times that FCP does not use more than 4 cores when rendering. But when I render 1080p pro res 442 in FCP 6 all eight cores run up over 90%, and it does indeed render almost three times as fast as my Power Mac g5 Quad. So I'm just curious why FCP is actually using all 8 cores. Any help is appreciated, as always.

Fay Krause wrote:
... I've read on this forum at times that FCP does not use more than 4 cores when rendering....
You are confusing cores with RAM.
FCP is a 32bit app. This means it can not make use of more than 4 GB of Ram (2.5 GB for the program and 1.5 for the frameworks).
FCP will use all the cores in a machine, how MUCH they are used, depends on a lot of factors - including the version of OSX you are runnning.
10.6.8 (snow leop) has a full 64 bit mode that will do a better job of allocating system resources to 32 bit tasks than 10.5. I ran 10.6.8 set to boot into 64 bit mode along with FCP 7 for a long time with great performance. If I hadn't needed 10.8 for other software, I'd still be running 10.6.8.
Best,
x

Why mac pro 2013 not supporting illustrator GPU rendering

Here, all nvidia cards supporting this:
http://helpx.adobe.com/illustrator/kb/gpu-performance-preview-improvements.html
now I'm thinking, that buying the new mac pro 2013 maybe wasn't the best idea... Apple put in AMD GPu's, that is fine by me, but come on, give us some more support for them! Normal windows PC (for 800€) with nvidia GPU is faster at rendering in Illustrator, than my workstation mac (3500+€)! Really? O.o
And story doesn't end here. I was reading one article about GPU usage in this new mac pro and then I tested it myself. Only one GPU is used and the other is barely touched! And this goes for Maya, photoshop, illustrator and other adobe programs. I was shocked, that I discovered I have one GPU to warm up my room and only one actually doing all the work.
Ok I understand, that also software developers needs to support stuff and write their software to actually use GPU's, but adobe creative suite is one of examples, where software is actually capable of using GPU via openCL and in some cases even CUDA from nvidia.
And there is one more thing: new mac pro, has 2 identical AMD GPU's inside, which can work in crossfire configuration under windows in bootcamp, but not in OS X. Sometimes I even play some games on my mac and sometimes I'm testing them (I'm artist, but I also like to develop and test some games in my free time) and it's kinda a shame, that I can run games with better performance under windows in bootcamp.
When I bought this computer I thought this is going to rock and sweep up with all my previous machines. Well in practice it is much of unused potential and great room warmer. It's kinda sad, that on my girlfriend's PC I can play games with better frames and details on GF 660GTX than on my mac pro... I know I know, mac's aren't for gaming, but hey, sometimes it is good to get my mind on rest and blow up some enemies!
I'm not saying mac pro isn't great product, which is (very great). But support to use all computer capabilities is very limited and Apple should kick developers in their back side and push them to start developing things to use GPU's more.
I'm also not expecting Apple to jump on their feet and fix problems overnight. No, just start thinking of adding more support and things that would make our computers much more used and not only good decoration on desk. First would be a good steep adding crossfire support to OS X. That might even help at rendering some 3D scenes?
Next step would probably be better cooperation with software developers, like Adobe , Autodesk,... If adobe made good support for GPU rendering in Illustrator, aim that we get that support soon as well. I'm sometimes having a lot of paths and objects and rendering goes pretty slow then.
I'm also thinking about that AMD choice Apple made wasn't so good when you see that Nvidia puts much more effort into supporting more and more stuff, while AMD is sitting idle not even updating their drivers anymore.
Oh and one more thing: Can we please, please, please, please, preeeeeetty please get 10-bit output support on OS X? It's kinda sad, having good mac workstation with 10-bit capable monitor (dell UP2414Q) and no support for it, while other PC workstations all support it... Photoshop is working much better on OS X and here I have much better integration and everything and I really love working in Photoshop running on OS X, but some basic things are missing and I'm really asking myself sometimes: was that good decision? Photoshop was first written for macs and in 2014 there is much better support for adobe software on windows than on OS X. Where went wrong?
Don't take me wrong and think I'm just ranting here without any good reason, but think: buying very expensive computer that is supposed to make creative work easy and painless is actually just on paper. In reality computer potential is pretty much unused and that makes me thinking if I would be much better buying iMac instead of mac pro...
TL;DR: I wish for some more support from Apple for their new expensive mac pro's 2013. They are great piece of equipment, but equivalent PC's running windows are surpassing them in this department, specially when GPU's are involved. Now I would like to point this out to Apple, so I don't know where to write so they will read so I first wrote that here. I hope someone from Apple reads this and give us some feedback on those missing things or maybe I get direction where to write to Apple so I get maybe some response from them(?):
-not enough GPU support for creative software (adobe suite, autodesk,...) - nvidia + windows offering much more for less money?
-no crossfire support on OS X. Any particular reason for that?
-no 10-bit support for 10-bit displays. Why not? Hardware is capable, why software isn't?
-lack of openCL software out there. Apple isn't doing much to get more support or developers just too lazy to put more effort into this? GPGPU isn't the future as some companies are trying to convince us?

Grant Bennet-Alder wrote:
All displays are supported by one GPU -- the display GPU. The second GPU is reserved for un-interrupted GPU computing and has no Display output Hardware.
Anandtech has a discussion of this in his review of the late 2013 Mac Pro.
Under OS X the situation is a bit more complicated. There is no system-wide CrossFire X equivalent that will automatically split up rendering tasks across both GPUs.
By default, one GPU is setup for display duties while the other is used exclusively for GPU compute workloads. GPUs are notoriously bad at context switching, which can severely limit compute performance if the GPU also has to deal with the rendering workloads associated with display in a modern OS. NVIDIA sought to address a similar problem with their Maximus technology, combining Quadro and Tesla cards into a single system for display and compute.
from section 9:
http://www.anandtech.com/show/7603/mac-pro-review-late-2013/9
Another problem here: on windows bootcamp crossfire IS working, but not in OS X. As I wrote, sometimes it would be better to get more rendering power than computing power (actually at current state of GPU computing software, computing GPU isn't working very much if at all). It would be nice to have an option to switch on and off crossfire so we could use more rendering power when needed.
Also not all people are doing video rendering on their computers. What about 3D modelling and 2D work in photosohp? And maybe people like me are occasionally wish to play some games on their mac?
You linked me GPU usage from one program (probably adobe after effects or premiere pro or apple final cut X?), that is probably one of the only pieces of software that actually uses both GPU's under OS X. I made same experiment with software I use and I even tested some software I don't use but it is advertised it is "optimized" for mac pro like pixelmator.
And guess what? Second GPU is 99% time idle. Even when some stuff is using openCL in Photoshop, stuff is still computed on rendering GPU and not on computing one, which makes computing GPU just a good room warmer as I wrote before. Wouldn't be better to at least use second GPU for something than heating air?

I have the current Mac Pro the entry level with the default specification and i feel some slow performance when applying after effects on my videos using final cut pro and also rendering a video takes long time ? what upgrades do you guys suggest?

i have the current Mac Pro the entry level with the default configuration and i feel lack of performance when applying after effects on my videos using final cut pro and also rendering a video takes long time ? what upgrades do you guys suggest i could do on my Mac Pro ?

256GB SSD it shipped with will run low and one of the things to watch.
Default memory is 12GB also something to think about.
D500 and FCP-X 10.1+
http://macperformanceguide.com/index_topics.html#MacPro2013Performance
Five models of 2013 Mac Pro running Resolve, FCPX, After Effects, Photoshop, and Aperture

After Effects CC 12.2 Crashes While Rendering on New Mac Pro

I have been working on a new project in AE 12.2 on my New Mac Pro. The project file runs a little slugish while I'm working. I am using Trapcode Lux, Optical Flares and a lot of expressions. When I go to render the file 1/4 of the way in my whole computer freezes and I need to force it to shutdown and restart. No error report is created I don't think.

Optical Flares is GPU dependent, which can play havoc when rendering using multiprocessing.
Try rendering with multiprocessing turned off.
If that doesn't work, try temporarily removing Optical Flares from the AE Plugins folder and restarting AE, then render. This will force a render with no Optical Flares included.

"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).

Apple Mac Pro online work PDF damage, cant recongnize file??

Hi Everyone, I recently brought a Apple Mac Pro for work, i do a lot of documentation online, i can't seem to open any documents to edit, i tried downloading Adobe Reader, I have been constantly searching for solutions and i'm pulling my hair out. i'm not the best and extremely new to the Mac pro world but, can anyone please assist??

http://www.macworld.com/article/2045686/editing-and-annotating-pdf-files-with-pr eview.html
http://lifehacker.com/5841747/the-best-pdf-viewereditor-for-mac
http://www.wikihow.com/Create-Pdf-on-Mac-in-6-Different-Ways

No transperancy rendering 3d pdf on Mac Pro

Similar Messages

Maybe you are looking for