New Mac Pro 2.66 Ghz Nehalem Quad and FCP and Compressor

When something goes well for a change it deserves its rightful place in the posts of this discussion forum. I just completed my hook-up and an initial test on my new Nehalem quad Mac Pro, and I must say that once in a while things do work out.
1. The noise level is non-existant. I literally had to check to make sure that the unit was on. This in comparision to my G5 which sounds like the SST on take off. I might now actually hear the audio on my video monitor.
2. The speed is INCREDIBLE! Prior to shutdown, I ran a test by sending an hour's worth of mixed XDCAM EX/HDV footage to Compressor on my G5. At the highest quality 2 hour setting for DVD encoding (double pass) it took the G5 12.5 hours to encode. Running the same clip through the same version of Compressor in the Mac Pro took approximately 45 minutes. This roughly translates into a 16.5X increase in speed over my dual 2.5 Ghz processor G5. I'M SOLD! And for now, the Honeymoon continues.
The only drawback (besides the price) is that I had to buy a $100 adapter/power supply to enable my old 25" Cinema screen run on the new video card.
Thanks
fastfreddy

Mac Pro 1,1 (all Mac Pro models come with Xeon).
What matters is cleaning the X1900 of dust and from clogging intake and exhaust - every three months.
Run Apple Hardware Test from your OEM DVD.
Install SmcFanControl 2.x and keep the fans rpm to 800-900 instead of 499-599 base as minimum at least.
Monitor temperatures with Hardware Monitor or similar.
Have you been looking to see in System Profile: Memory if there are any errors?
Normally, clone backup update weekly and running Disk Warrior at the same time should be done to spot disk directory and file system problems before they get worse. Or any time your system freezes.
Freeze... and what you have 90% of the time is a corrupt directory and other errors.
At which time you may need to restore if you can't fix the problem. And don't rely on only Apple DU First Aid to find and repairs any and all errors.
For Snow Leopard maybe a flashed ATI 4870 to replace the X1900.
You may need to start over from scratch to get things stable once you find what is happening, and work with a test system until then with some trial and error. Format/initialize and clean install of 10.6.x for the OEM 10.4.7+.
At nearly 4 yrs now since it came out, not sure if you have plans for a new one.

Similar Messages

Wake From Sleep Reboots New Mac Pro 2.8 GHz 8-core 10.5.2

Add me to list of users with this problem.
I bought NEW computer yesterday.
Mac Pro 2.8 GHz 8-core 10.5.2
ATI Radeon HD 2600 XT
Yesterday, I ZeroWrote the OEM Apple hard drive and Installed 10.5.1 from OEM Install disks -- ran all updaters, repaired permissions numerous times during build.
Only 2gb OEM Apple RAM installed
Added on (from original installers): CS3, Office 2008, Toast 8.03, Stuffit 12.01, Silverfast AI 6.5x (Epson 4990). It appeared to be waking properly during the build.
Last night, last Software Update updater ran was ATI RADEON HD 2600 XT Firmware UPC 1.0.
This morning, wake from sleep rebooted machine.
Apple had me disconnect all cables, including power cable for a minute and then plug back in.
This worked for a couple few minute sleeps, but after lunch it rebooted again waking it from sleep.

I got my 8-core StartUp Disk deselected and have had only one auto reboot when waking from sleep.
HOWEVER, now I have heavy vertical bands twice now when it wakes up my 30" Cinema Display:
http://discussions.apple.com/message.jspa?messageID=6919620#6919620
It had wide vertical banding, white edges in corners and edges, and white fog over entire screen that seemed burned into the screen -- it eventually corrected itself back to normal after being on over a couple hours.
Second time, I had wide vertical banding, 6" and 3" wide with rows of white, green, blue pixels.
I connected the 30" to the old Mac Pro -- 10.4.11 -- AND THE BANDING GRAINY SCREEN APPEARED CONNECTED TO THE OTHER MAC like it was burned in the LCD.
So it appears the banding is in the monitor the monitor.
The burn-in cleared itself after being on about 120 minutes.
*It seems the new Mac Pros have some devilish issues with sleep on their Apple Cinema Displays to the point it is destroying the monitors -- or it is coincidence...*

I have a new mac pro. i may have changed the settings and now when i log on it shuts off after 10 seconds. not long enough to check settings.

i am new to mac book pro. i was checking out the settings and must have changed something as now when i log on, it shuts down within 10 seconds and i don't have time to get into the settings. the top tool bar is red/pink. please help!

Close all windows and quit all applications.
Hold the option key down and click the "Go" menu in the Finder menubar.
Select "Library" from the dropdown, then "Preferences" folder.
Look for these two files.
com.apple.desktop.plist
com.apple.systempreferences.plist
Right click each one of those and select " Move To Trash" from the contextual menu.
Restart the computer.

I have a new Mac Pro. it was shipped with a 2TB drive and a 500G SSD. After 3 weeks, the machine can no longer see the SSD.

The disk utility cannot see it either. Sometimes I reboot and it is there. other times it is not.

Take it in for service. It's under warranty.

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

New mac pro slow converting raw files any help?

hallo everybody,
can someone help?
my new mac pro 3.7 GHz Quad-Core Intel Xeon E5 / 32 GB 1867 MHz DDR3 is converting raw files in camera raw really too slowly, about twice the time took with an iMac 2,7 GHz.
I tryed all graphic processor options on PS preferences.
I also ran mac check up utility and hardware seems ok.

The normal suspect would be that you haven't rendered out the previews, but the low cpu value would indicate that the problem actually lies elsewhere. Even so, it would do no harm to run the Render Standard-sized preview command (Library module View menu)
Next thought is the operating mode. Lightroom 2.x can run as either a 32-bit or 64-bit application. With the amount of ram you have installed (very low for a box with this sort of power) you might find 32-bit is the best choice. You can change the mode by clicking on the Lightroom application icon then use the Get Info command (Cmd+I) to open the info panel
Tip: you would be well advised to increase your installed ram. Lr likes plenty of ram, especially in 64-bit mode. A good starting point would be 6GB or even 8GB

Using the New Mac Pro (can) - AE will not let me use Race Traced 3-D

Using the New Mac Pro (can) - AE will not let me use Race Traced 3-D
Hi, I'm using the new Mac Pro
2.7 GHz 12-core Intel Xeon E5
64 GB 1867 MHz DDR3
AMD FirePro D700 6144 MB
OSX 10.9.2
I'm using After Effects 12.2.1.5
When I attempt to invoke the race trace 3D renderer in a comp, I get this error
"After Effects Error: Ray-traced 3D: Out of paged mapped memory for ray tracer. Your project may exceed GPU limits. Try closing other applications. Try updating the CUDA driver. (5070::2)"
My preferences are set to use the CPU for Raytraced 3D since I do not have an Nvidia card.
So, obviously there is an issue here in that it thinks I have an Nvidia card.
I know (or assume I know) the cause for this is that when I set up this machine, I used Apple's migration assistant to move most of my data over from the previous gen Mac Pro which DID have a CUDA card.
So my question is, what files can I delete/reset to cause After Effects to no longer look for CUDA files that do not exist on this machine?
I do not have the CUDA control panel in System Prefs, so THAT did not carry over.
Any ideas would be appreciated, thanks!

> I know (or assume I know) the cause for this is that when I set up this machine, I used Apple's migration assistant to move most of my data over from the previous gen Mac Pro which DID have a CUDA card.
Ugh. That causes so many problems.
The first thing to try is deleting the CUDA frameworks from your Mac: Look in /Library/Frameworks for the CUDA.Framework and get rid of it.

A brand new Mac Pro doesn't wake up from sleep

I got a new Mac Pro.
It has an external SATA controller and a video card with NVIDIA Quadro 4000 chipset on it.
It has a Snow Leopard installed.
The problem it has is that it doesn't wake up once it goes to sleep, either by choosing "Sleep" menu item or by using "Energy Saving" setting.
I notice some people mention a keyboard doesn't respond while his trackpad does. In my case, nothing works.
I don't know if it is due to keyboard or a magic mouse. I tried to connect another wired mouse to the enclosure of the Mac Pro directly, but it did't cause Mac Pro wake up.
By searching on Google, many people seem to have this problem, whether they have Mac Pro, MacBook Pro, and so on.
Personally, I have a 17" PPC iMac, 13" MacBook with Core Duo 2, and have used MacBook Pro 17", but they didn't have this problem.
I tried to reset the SMC, but it didn't help.
Do anyone know what cause this problem and how to solve it?
Is there any patch for this?
Thank you.

Does it sound like it's waking up but the monitor just doesn't display anything?
I ask because if so, I'm experiencing the same problem. I have a Quad-Core Mac Pro (no external devices) and if it goes to sleep I have difficulty getting it to display anything on the monitor after waking it up. Now, I just recently hooked up an additional monitor (VGA) for dual display, and the funny thing is, that monitor will wake, but my main monitor won't.
Sometimes I get this error after boot-up too, where the computer will get to the login screen, but my main monitor is receiving no signal ("at least according to my monitor").
If that's the same issue, then I'll post any success I find for you!
Best,
J

New mac pro, CS5 crashes, where to start?

I have a new mac pro which crashes daily while using After Effects (and photoshop). I've seen some indication that this could be a driver issue with the 2 nvidia cards that came preinstalled, or an Adobe issue. Running 10.6.4 Snow Leopard. I can recreate this sometimes by scrubbing the after effects timeline with a spotlight casting a shadow on another layer. The system locks up, left monitor flashes black and I have to hard rest. This is super frustrating, apple has twice told me it's Adobe, but I don't know. All I do know as a business owner is that I'm $13,000 invested in hardware / software that don't seem to work together and I don't have many other options as this is what i do for living. Any thoughts at all? Anyone have any ideas?
2x2.93 quad core xeon
16gb 1066 ddr3
level 5 raid with 4 1TB drives
OSX 10.6.4
MacPro4,1
2 nvidia 120 cards
2 24" cinema displays (one per card)
thanks in advance
scott

For sure it is really frustrating, especially when you convinced the company you work with to switch from FCP to CS5...
I have the same problem with a Mac Pro bought in April and a GTX 280... We were pretty happy with Premiere Pro, when editing a feature shot on RED 4K HD. It is the more stable release of that soft I ever seen, and I'm using it since Premiere 5.1 and the mini-DV.
But I'm disappointed by After Effect, which use to be alway stable in the previous version I used. We're working on a 3300$ computer, using a 450$ graphic card, and the two Samsung monitors keep flashing before AFX craches... That happen every 15 minutes.
The GeForce driven is updated. We have also a Geforce GT 120 in the Mac Pro, to plug a Wacom Cintiq 12WX on it... The screen of the wacom doesn't flash when it happens to the Samsungs, that's why I'm thinking of an issue involving the GTX 280. Anyway, nVidia does not provide any driver for Mac for the GT 120...
So it's probably more a graphic card issue, than a software one... But if someone has any other idea to get rid of this problem (unactivate open GL does not change the problem)... ?
Thanks in advance for who may help...

New mac pro recognises usb 2.0 as 1.0 - super slow data transfer!

updated my new mac pro 3.5 GHz 6-core intel xeon E5 to mac OS 10.9.2 today.
all periphals (standalone hubs, hubs in monitors, harddisks) are now recognised not as is (USB 2.0) but as USB 1.0 (ie transfer rate 12 Mbit/s), no matter whether they are plugged into a port of the mac pro directly or thru a hub. i do not get anything done anymore!
any advice how to get back to USB 2.0?
thank you!

The warranty entitles you to complimentary phone support for the first 90 days of ownership.
If you bought the product in the U.S. directly from Apple (not from a reseller), you have 14 days from the date of delivery in which to exchange or return it for a refund. In other countries, the return policy may be different. If you bought from a reseller, its return policy applies.

Two users on new Mac Pro?

Hello, I am considering a new Mac Pro. My wife and I both have separate Mac's now. My question is with the new Mac Pro, can I have two user accounts (hers and mine) on the same machine that we can use at the same time? More specifically, this would include two different monitors, two different keyboard/mouse set ups, etc. We sit on opposite sides of the desk, but I am considering the Mac Pro as a central unit for the both of us. We are usually in the PC room together and doing whatever we do at the same time. Thanks!

Using the same Mac at different times is really simple -- just add another account and log in as one account or the other.
Using the same Mac at exactly the same time is very complex to set up. It involves using Virtualization software to simulate a second machine running on the first machine.
I recommend you NOT do that. I expect what you are doing is not CPU or Graphics intensive and you would be better served by having two more-ordinary Macs that are independent.

Brand new Mac Pro - Suddenly iOS devices won't charge

So I've been using my brand new Mac Pro 8-core for about a week now and I've already had 1 force reboot (kernel panic, error 14 page fault) and earlier tonight, when I plugged in my iPhone 4S, its screen didn't turn on as usual after being plugged in... The "charging" icon didn't appear in the phone's menu bar, and neither Xcode nor iTunes recognize the phone as being plugged in. I'm running Snow Leopard with all the latest software updates.
I've tried:
plugging it into other USB ports
using a different USB cable
unplugging and plugging in quickly, repeatedly
charging my iPod touch and my wife's old iPhone 3G - they won't charge either
My "old" Mac Pro that this Mac Pro is replacing had a very similar issue... after leaving the computer on for a while and returning, usb devices wouldn't charge, apps would hang, and i'd have to cold reboot. This got progressively worse over time, and eventually "died" when the system crashed w/ a never-ending beachball and wouldn't boot back up. I'm starting to wonder if I should just return it and get an iMac or something since I have a hunch this is hardware related.
Something also weird is that before I plugged my iPhone in, I was using Xcode and had my phone selected as a build target... even though it wasn't plugged it in. (Normally if it's not plugged in, the name will not appear in the list.) Nothing happened when I tried running my app obviously so I stopped the build, then plugged my phone in. That's when I noticed it wouldn't charge.
THEN it gets even worse... while I was typing this, when trying different USB ports, in the process I unplugged my keyboard. After plugging my keyboard back in, it wouldn't work. Cold reboot.
I'm really hesitant to lug this brand new Mac Pro back to the Apple store just to hear them say "The diagnostic test looks ok to me!" and have the issue crop up again a couple weeks later.
Does anyone have any ideas on what could be causing this, or have you seen anything similar with your Mac Pro? Again, I just picked this Mac Pro up last weekend at an Apple store.
Thanks!

Intel-based Macs: Resetting the System Management Controller (SMC)

RAM PREVIEW VERY SLOW (FAR FROM REAL TIME) ON NEW MAC PRO

Good afternoon
I have the new mac pro with 8 cores, 64 Gb of Ram and dual AMD 700 graphic card, but the preview on After effects is slower than in the old mac pro (from 2010). I have set the preferences as told in your website and everything stills the same. Could you please advice? is very frustrating to see that a new machine works worse than the older one.
thanks

Attached below you can see some screenshots from the settings I have on AE CC

After Effects and the new Mac Pro

I recently got one of the new Mac Pros and it doesn't get along great with After Effects, particularly when it comes to ray-tracing. There is no Nvidia GPU option for the new machines, so ray-tracing defaults to CPU. But then, even with a simple solid, it gives you an out of memory error. I've seen postings saying this is fixed in 12.2 but I've got 12.2 and the newest CUDA driver installed and run the machine with all other apps closed, but no luck. Presumably I'll figure out how to get it running after a fashion eventually, but even then, even with the new machines' many fast cores etc, CPU ray-tracing on the new Mac Pro is not looking promising on the speed/usability front.
Element 3D is an option, but its reflections can't interact with the comp the E3D object is within, only with the environment map in the plug-in itself, so there are many cases where it's a poor substitute.
My question isn't really how to get ray-tracing to work with the new machines. That would be great, but my sense is the answer there is, it effectively can't.
My question is, given that motion graphics increasingly involve the complex interplay of light, reflection, transparency, and three dimensional objects, and that from here on out Mac Pros will no longer accommodate nvidia cards, and that many creative types will only work on Macs, how long will this state of affairs continue? How long can it continue? Are there any plans to make After Effects fully functional on the new Mac Pros? Ray-tracing has always been balky and wonky and prone to error messages and crashes, but despite all that it's also an indispensible part of After Effects.

A fun update, long after the fact:
So I've learned Cinema 4D in order to reacquire the capability After Effects once offered internally and have succeeded after a fashion. Let's look at the relative ease of the new method versus the old one using a real-world scene from my project: Adding a bus shelter over actors on a bench.
In ray-trace enabled After Effects of old, I could draw simple draw shapes in Illustrator, extrude them into objects, collect them under a null and position it in my scene. Particularly powerfully, I could bend 2D photograph layers into half-domes for a fun roof, and create planes of transparent glass of any thickness I chose with refraction levels that made for interesting visuals as actors moved behind it, and add reflectivity to any layer I chose -- including the dome roof, for instance, which would then pick up the reflections of any other objects in my scene. I could also put 2D layers in front of my bus shelter as easily as placing a layer closer to the camera than the makeshift model. Well, sometimes it didn't work as advertised; sometimes you also had to have the foreground layer above the background one in your comp even when both were 3D and that wasn't supposed to still apply, but at least it was After-Effectsy. The whole thing was After-Effectsy, which of course is good because presumably AE users know AE, but also it was similarly logical.
To achieve a similar end with C4D and Cineware, all you have to do is this: Build your bus shelter model in Cinema 4D. Wait, first learn Cinema 4D, a hugely complicated piece of software. Come back in 3 months, I'll wait. Hi again. I see you've built your bus shelter. In fairness, you were able to add textures and complicated curves you couldn't in After Effects. But then you always could, if you were willing to learn a hugely complicated piece of software. Anyway, let's get that model into after effects. Just drag that C4D project into your AE project and put it in the comp. Put other layers in front of it or behind it. Easy! Now just a few caveats. 1. Scale. There is no formula available anywhere for the relative scales of your two projects. So tweak that. Just go back and forth between the two software suites -- I hope your computer can have both up and running at the same time! -- until you get that right. 2. Cameras. You can import your AE camera into C4D and vice-versa as easy as pressing a button in Cineware. It shows up somewhere strange in C4D unless you use a workaround unless you are also camera tracking in AE in which case you can't. 3. Scale again: Your camera will match its moves in both suites now. But they are drastically different sizes. If you import your C4D camera into AE it becomes tiny tiny tiny, if the scale of commercial C4D models is to be considered at all standard. Just shrink your model down to say 1% and you should be good to go. And if you tweak your camera in AE or C4D, you have to junk your imported camera and re-do that step. 4. Reflectivity. Your C4D model will only reflect items in your C4D project, not the, um, scene it's going in. 5. Refraction. Transparent C4D items will indeed show your AE items behind them. But you can't add refraction. 6. I've saved the best for last. Say you want your actors in your bus shelter, meaning part of the model is in front of them and part behind them. You used to place them (shot on a greenscreen or roto'd) in the bus shelter model. Now you simply do this: Divide your bus shelter model into halves, the in-front half and the behind half. Put both under nulls. Give the front null a C4D "tag" called compositing. At least its name makes sense. Then go into the tag and enable a numerical "object buffer." You're almost done! Next simply go into "render options" in C4D and into "multi-pass" there and then enable object buffers again there, so intuitive! Make sure to enable the same numerical object buffer you enabled in your compositing tag. Good? Good! Now, all you have to do is place two copies of your C4D project heirarchically in your AE project. You're still almost done! Now all you have to do is go into "multi-pass" in your Cineware plug in in the instance of it that goes in front of the actors and specify your numerical object buffer again. Wait, one tiny thing: If your Cineware plug-in is still set on the default "Standard" setting that option will be grayed-out. Just switch it to the much slower-rendering C4D opions and you're good to go! And don't worry about two copies of your C4D project in your AE one meaning it will now take twice as long to render, because it will. But, as a bonus, you've probably learned a lot of ways to render C4D models really well when learning C4D because Adobe made you. So you can use those to make your AE comp really shine... or wait, could, but they're not supported. You can however render it in that flat ugly video early Pixar style, but life is full of trade offs, no? You end up rendering out the layer you need in C4D and comping it into AE exactly as effects artists have done ever since always. Which is to say AE gave up even trying to do 3D and sent you into the waiting arms of a more-capable competitor, their seeming specialty in the world of video. Maybe it's better this way. AE was only ever for comping. It briefly got a swole head. Now it's back in its comfort zone. The end

IMac vs the new Mac Pro for video editing in FCPX?

Hi.
I am currently using a macbook air for all my editing and rendering of videos in FCPX. The editing process is reasonably smooth when dealing with shorter clips, but when I tried to edit multicam clips, things started to slow down. Also, the rendering and compression processes are tedious. I am planning to edit and process a much larger number of videos in the next years to come, so I have decided to do a serious upgrade of my system.
For the moment, I am torn between a maxed out iMac 27", which would be the cheapest alternative, and the 6 core Mac Pro or 4 core Mac Pro.
When I look at benchmarks of the new Mac Pro's in Geekbench, the iMac is never very far away in terms of performance. Does tests like this tell anything about how well the Mac Pro will perform in FCP? Does the hardware in the Mac Pro have features which makes it superior to the iMac, in other ways than for example the "pure power" of the CPU and GPU?
Christopher.

FCP X 10.1, Motion 5.1 Updates w/Dual GPU Support (new Mac Pros) (from Thursday)
Apple released Final Cut Pro X 10.1 Thursday with support for Dual GPUs in the new Mac Pro and more.
Long list in the Final Cut Pro X 10.1 Release Notes that also links to info on How to back up important FCP X 10.0.x files before updating. (Today's Apple docs listing also has more related to Final Cut Pro X 10.1.)
Also out today are Compressor 4.1 and Motion 5.1. Full release notes below but here's a clip from the App store Motion 5.1 changes:
Optimized playback and rendering using dual GPUs in the new Mac Pro
FxPlug 3 with custom plug-in interfaces and dual-GPU support
Faster project loading, especially for complex projects
Share directly to YouTube at 4K resolution
Spanish language localization
Dual FirePro Dxxx Rendering FCP-X
http://www.barefeats.com/tube05.html
Intel Xeon processors are designed to run 24/7 and stay cool and under load.
Mac Pro so far hold up strongly for years, easy to add and upgrade RAM and processor, and maybe, hopefully, even the twin GPUs. Thunderbolt2 for all your projects and storage as well.
6 or 8-cores is going to walk away from iMac which is breathing hard and not designed for constant heat. Haswell was designed to conserve and reduce.

New Mac Pro 2.66 Ghz Nehalem Quad and FCP and Compressor

Similar Messages

Maybe you are looking for