535
Replies
genefama wrote:
Does any Mac user on this thread know whether or not we can grant open access to everything on our computers and to every non-existent "Guest User" under the sun and be free and clear of this nonsense?
For what it's worth: it may seem like "nonsense" to you, but file permissions are key to the UNIX underpinnings of OS X. It's one of the ways that UNIX (and therefore OS X) is so secure from things like general hacking, viruses, and what have you. I hate to say it, but you're not going to get "free and clear" of it unless you want to back-grade to OS 9. Which was a turd of an OS.
Now, why you have to keep correcting file permissions like that is an interesting mystery. Without seeing what's actually being corrected, I can't really tell you what or why. My strong suspicion, however, is that it has absolutely nothing at all to do with your Premiere Pro issues. In fact I'll bet a paycheck on it. 
jas
Regarding Mac Pro5,1: I had a very stable FCP, AE, PS CS5/6 station since mid-2010 (from 10.6 to 10.7.4). I updated software/repaired permissions regularly. I used Permission Manager, SuperDuper, and DiskWarrior to keep my ducks in a row. (see config below)
Unhappy with Apple's commitment to FCP/Pro users, I geared up for switching from FCP to PrP, specifically, I added a Nvidia Quadro 4000 Mac (which seemed like the most powerful card Adobe was recommending to take advantage of CS6 improvements). I also added a fast cache volume.
I decided to learn PrP by editing a DSLR project with it. (No recompress of h.264? Awesome!!, I thought). Though I had the latest Cuda drivers and Mac & Adobe updates, the day I started using PrP to edit, I got kernel panics, serious errors, and what I would later learn is a harmless/annoying line 87 error. (Thanks @benwinter!)
Phone calls with Adobe tech support: escalated to a higher tier. An employee who shall be referred to as "V" told me to try creating a new Admin account, and to email him the results. The results were: "serious error" in the first few minutes of use. I sent the update to V along with my crash report. He has not yet responded but has (or has allowed the system to) mark my case #0183359996 as "withdrawn" for some reason. But I digress! I have great news, keep reading!
@Jim Simon asked if I had tried simply wiping/rebuilding my system. I didn't have time in the middle of the project (and why would I have to wipe/rebuild a highly functional box?? Was this a wild goose chase??? What's the deal?? I'm on a deadline, waa waa!) I hobbled through the project by turning rendering from GPU to CPU, quitting PrP after it sent anything to another program, and incessantly clicking the error 87 dialogue until it disappeared for a while.
But as soon as my project was finished, I wiped/rebuilt my system. ALL CLEAR SO FAR! Thanks Jim!
My next steps are to back up my functional system and begin adding all of the things I need to really use it: Wacom diver, Epson Expression 10000 XL driver, GoPro CinePro codec etc...
In the age of the App Store, Apple makes a fresh install tricky. I have listed the obsessive steps I took to create a fully-fresh&functional edit system that dynamically links to AE and AU the way I always hoped it would. I will definitely update this post if I encounter kernel panics and serious errors as I incorporate the rest of my programs/peripherals.
Details:
1. Download Lion (again) from App Store and make a bootable install disc on an external FW drive using these fantastic instructions:
http://reviews.cnet.com/8301-13727_7-20080989-263/how-to-create-an-os-x-lion-installation-disc/
2. Boot from FW; Erase my system drive; Install 10.7; (note: no migration, no time machine, just a fresh install) restart
3. Upgrade to 10.7.4; restart
4. Download/instal latest Mac Cuda driver (4.2.10)
http://www.nvidia.com/object/cuda-mac-driver.html; restart
5. Give Admin Automatic login; un-require password for sleep and screensaver
6. Instal CS6: PrP, AE, AU, PS, AI, FL; I did NOT launch any of the applications.
7. Launched AAM Updates Notifier; downloaded/installed all updates; restart
8. Launched PrP; it asked me to (click to) install Java Runtime; I complied; PrP downloaded Java, installed it, then launched.
9. I made a new project:
10. General tab: I left everything as is -- Renderer is set to the default "Mercury playback...GPU" (come on Quadro 4000, I'm rooting for you!!);
11. Scratch Disc tab: I set all capture/cache directories to a folder within my dedicated CACHE volume; I set the proj file directory to a folder on my dedicated project and media drive.
12. Sequence Preset: DSLR 720p24 @23.976
13. It took five seconds to load the interface, so I quit and relaunched; much snappier results on the second launch.
14. Edited a project with various h.264s from Canon 5D & Canon 7D; no problem, works great!
15. Made a 1080p24 sequence. Warp stabilize a shaky shot in that? No problem! Load the result into my 720p24 sequence? Sure! I'll even "Scale to Frame Size" (NOTE: Though i love the one-stop scale feature -- I've notice a bug or bizarre interface choice at this point: I have 1080p footage in a 720p sequence, I can see the whole frame but the footage shows a scale of 100% in its effects control; the correct value is about 66.7%)
16. Highlighted all clips in sequence and initiated "Replace with After Effects Sequence"; It launched AE
17. AE Prefs; I left everything the same except -- I set all of my caches to a folder on my designated Cache drive. (Note: I point all disposable Adobe data to a folder called "CACHEs" in every App that gives me the choice on where to save temp stuff. Along with preferences, this folder gets emptied/trashed when things run-amok.)
18. Rotated, scaled, masked, vignetted and otherwise jacked around with footage in AE; was astounded to see near-instant update in PrP. Some clips had poor playback on first drag-through, but very quickly cached themselves and suddenly I was living the dream: not rendering in AE :)))
19. Sent sequence audio to AU; changed temp directory to designated cache volume/folder; it told me changes would take place after I restarted App, so I restarted and re-opened the XML PrP had previously sent to AU.
20. EQed and sent back to PrP; no problem!
21. Went back into AE; turned on raytracing, added some lights, shadows, bending... back in PrP things were a bit more sluggish on that clip as expected. (About the same as dragging through the AE timeline ) Rendered in PrP... Heard the Quadro fan kick in... Green lines, good playback...
CS 6 Production Premium | Mac OS 10.7.4 | MacPro5,1 | 32 GB Ram | PROJECT & MEDIA drive: Mercury Accelsior. Blackmagic Disk Speed Test: > 500 MB/s read/write | CACHE drive: Internal SATA Raid 0. Blackmagic Disk Speed Test: > 400 MB/s read/write | Nvidia Quadro 4000 Mac | CUDA Driver Version: 4.2.10 | GPU Driver Version: 1.3.4.0 (270.00.00f06) |
AdChoices