New Mac Pro, Firewire issues

I just purchased a Mac Pro and have only had it for a couple of days. I installed several internal drives and moved my data from my Windows machine to the Mac using a firewire drive. That went well, but the Mac could only read it as it was NTSF. I decided to format it as a mac drive (journaled) so I could use it to back up to. The Mac Pro will not format the drive. It fails the verify and repair. I hooked it up to my son-in-laws computer i-Mac and it formatted perfectly. I hook ti back to the mac pro and it is really buggy. Reads slowly and writes even slower. I again run the verify and it does not pass. Hook it again to my son-in-laws computer and it passes the verify. Is there an issue with my mac, or the operating system and firewire drives?

This is the only firewire drive that I have, but my mini DV camcorder works fine, but that is a different cord. When I plug in the drive to my son in laws imac with the same cord, it works fine.

Similar Messages

New Mac Pro Firewire 400 solution !

I was surprised to see that my NEW Mac Pro (2009) does NOT have even a single FW 400 port. Everything is FW800. That doesn't help with my legacy camera and hard drive.
Another surprise is that Apple doesn't sell any kind of solution, (Except a 6 foot long cable) for this problem.
But, I have found this adapter available through Amazon:
http://www.sonnettech.com/product/fw_adapter.html
If Amazon can sell this adapter, why can't Apple?
Cheers.
Ron

I picked that one up as well to plug my cinema display into. I wondered at first if it would cause any issues, but other then seeming to fit a little loose, it is okay so far.
I also heard another option (if available) is to plug the firewire into the back of an external drive. I don't know if this would be better or not.

New Mac Pro major issue's with Premiere CC 14

I bought the latest Mac Pro with top spec but it runs like a pig with Premiere cc 14, Adobe's video shows the Mac works perfectly. However mine takes forever to render, and has a jerky image on full quality playback with some clips, tried multiple setting, also been on the forum about open cl and open gl and other forums saying it's a mac issue and other saying it's adobe issue
Has anyone got a solution.
Would Adobe like to comment on the issues with the new Mac Pro's

I add to Jason's response with this: If you are having any suspicious behavior with Premiere Pro CC 2014 running OS X 10.9.4, please update your permissions to Read/Write first. Your permissions may be set to Read Only (this happens when you update, rather than clean install OS X). See this link: fixing permissions problem that impedes start of Adobe applications | After Effects region of interest
This forum post details the process: Re: Premier Pro 2014 is very sluggish
Thanks,
Kevin

New mac pro playback issues & sluggish

got my new mac pro this week. wanted a fesh start, so didn't migrate anything. started by installing my must-have apps: adobe cc, ableton, apogee, fontexplorer, natove instrument komplete. everything worked great. then suddenly, when vreating a simple project in premiere, playback didn't work. and neither in quicktime nor itunes. started seeing the beachball in many apps, everything totally sluggish. started deleting apps, but nothing seemed to help. anybody had similar issues?

My own remedy is more of the ounce of prevention:
Clone the system so you have the nice vanilla system as it was backed up to another drive volume or sparse image.
One person runs multiple copies of Mavericks in VMs using VMware Fusion to allow testing any changes first; restore a VM back to before changes, or to switch a VM to a boot image.
Create a bootable clone of the system, before making changes, in case a system does go south, or just for testing.
Sluggish is so common but generic, and how many apps run concurrently or have been tested to work even with 10.9.1 builds along with change to new hardware?
The things we may not see or be aware of, might be like this one uncovered and mentioned on Ars:
In our recent review of the late 2013 Mac Pro, one of our sticking points was the OpenGL performance that trailed Windows on the same hardware. A particularly damning case was the high-polygon-scene performance in Autodesk Maya showing how OpenGL viewport 2 performance fell off a cliff when you pushed into very high polygon counts of over 20 million with the D700 in OS X.
While this issue still needs to be resolved for some programs like modo, some quick sleuthing by Apple and AMD shows that the problem was on the Autodesk side. Maya was not simply querying the GPU RAM; for some reason, it was using a hard ceiling on OS X, so the brutal performance hit was the result of that ceiling. Once you explicitly tell Maya to use your available VRAM with the environment variable MAYA_OGS_GPU_MEMORY_LIMIT=6000 in ~/Library/Preferences/Autodesk/maya/2014-x64/Maya.env, performance is perceptibly the same as in Windows in Boot Camp with very large scenes:
If you have a GPU with more than 1GB of VRAM, I highly recommend setting this environment variable to your GPU's VRAM amount. This issue will reportedly be fixed in Maya 2015, but Maya is clearly an absolutely massive program with some annoying issues—here is my blog post on how to fix Maya performance when the Help Line is visible in OS X.
So, fellow Maya users, I just need to implicate Apple in another 17,000-word article about our other bugs, and we'll have them fixed in no time! This brings us to the question of why I thought to blame this on drivers and not the Mac Maya version to begin with. It's odd that this Mac-only hard-coded VRAM amount existed at all because Maya is very much the same beast on all platforms, and from my knowledge of it as a beta tester, platforms don't get specific attention for tuning, and that's the case for the dominant platform as well. That's why I assumed that this was a driver bug and not Maya-specific.
Anyway, we'd like to thank AMD and Apple for their quick work with Autodesk to resolve this issue. We'll be updating the review today to account for this new information.
http://arstechnica.com/apple/2014/02/2013-mac-pro-firepro-d700-opengl-is-better- than-we-thought-it-was/
I don't always follow my own advice, sometimes it works out, sometimes not, but any OS like Apple's needs a couple updates, and any new hardware needs some firmware revision, chips, changes in production, and time to ah "field test" new system in the real world.

Sony J30 SDI Deck, New Mac Pro FireWire 800, Arrgghhhhh!!!!

Anyone else had this problem and got around it?
We have a new MacPro that only has Firewire 800. We usually shoot DigiBeat and capture via a Sony J30 SDI deck using Firewire (before you say it, I know, but its fine for what we need).
We have tried a FireWire 6 pin to 9 pin cable but FCP refuses to recognize the deck. Have tried another cable in case it was that.
We used a standard Firewire 400 cable from the deck to a Ext HD, then a Firewire 800 out of the HD to the Mac. Surprisingly this worked, Once!
Can you get a FireWire 400 for the new Mac Pros?

+A Mac Pro (desktop) has Firewire 400 and 800. (edit) Sorry, I didn't realize Apple dropped this from the desktops as well.+
Yup, Firewire 800 only now on the Pro macs.
+Are you referring to a new MacBook Pro? If so, only the 17" model can accept a PCMCIA card.+
John's talking about a MacPro tower, not a laptop. FWIW The 17" MBP sports an ExpressCard/34 interface not PCMCIA which is much older and slower technology. PCMCIA wont work in an ExpressCard slot without an adapter
+I think I would obtain a Firewire 800 to 400 (direct) cable (Apple store) and not daisy chain between the computer and the deck. Most Firewire problems can be traced to daisy chaining.+
I think John's first post mentions that he's already tried this ... unfortunately unsuccessfully as that would have been the obvious option.

New Mac Pro display issues with Thunderbolt display

When connected to a 27inch Thunderbolt display after a while I get vertical blue lines on the display. If I plug my Macbook Air into the screen, after a while the blue lines clear. How do I find out if it's the Mac Pro or the Display?

Thanks Turbostar, that's exactly right, it takes about 30 minutes having the Air plugged in and the stripes disappear.

My brand new mac pro always had Internet connection issues at school. WHY is that? I see the school's Internet working perfectly fine on other PC's, but there is never a day where my mac doesn't have Internet connection issues at school. How do I fix it?

I got my mac pro in the middle of August. School started the week after. Internet was working perfectly fine at home. But at school, I never had a good connection. Sometimes on the good days I get a connection when I'm sitting at the exact spot in class I always sit at. It's ridiculous and it's frustrating. I invested my money into this laptop and I'm beginning to regret it. I thought it was the school's Internet, but I don't see Internet issues with other PC users. It's most frustrating on registration days and I'm trying to register for my classes before it gets taken, but again... Internet connection issues. It's random. Majority of the time, it doesn't work at all. I've done Network Diagnosis and turning WiFi off then turning it on again. I've done everything I could. I put my money on this laptop and it was a lot of money. I could have bought an 800 dollars laptop and I would have Internet connection anywhere on campus. So, I don't want to continue everyday to regret on buying this laptop every time I try to connect to the Internet at school or Starbucks or anywhere else. How do I fix this? What's the problem ?
At school, I heard this guy had a problem with Internet connections too and he owned a new mac book pro. He said something like Apple messed up on something, but he fixed it. If I knew mac book pro's had these issues I wouldn't have bought it in the first place. It's freezing on me every other day. It's ridiculous. But what concerns me the most is the Internet connection. So someone please tell me what can I do next to prevent the problem? Am I doing something wrong maybe?

Hi Kevin,
I'm using an XLR input mic which is connected to the phantom power enabled XLR mic socket on a USB M-Audio M-Track. The M-Track is connected by USB to the Mac Pro - so effectively I've got an M-Audio USB soundcard with a mic input. I've also tried a microphone that is a straight XLR to USB cable (guessing with some soundcard chip buried in the usb plug) but that also yields the same effect of bad latency, intermittent quality, stuttering and repeating and echoing (without the speakers on during record so its not feedback).
The mic works absolutely fine with other recording applications I have on the mac at the moment - albeit non-adobe ones (tested it on the EasyAudioRecorder - and it lives up to its name. it's easy)
I will try with Audition and report back, but sitting here right now I can imagine it would work fine with audition too - it just seems to be the way premiere is set up for recording into the timeline is a bit sketchy. I'm willing to accept it might well be a quirk with the new Mac Pro trashcan - I'm not weighting all the woes on premiere.
Any thoughts or am I out of luck to sit with my fingers crossed for a fix in the next round of updates?
Nathan.

Has anyone had issues with the new Mac Pro computers and the Adobe Application Manager?

We just purchased a new Mac Pro and transferred everything from the old computer to the new one. Now we are getting Adobe Application Manager errors and it wants us to download Application Manager. That leads us to the Adobe Installer that encounters the following issues
Installer failed to initialize. Please download Adobe Support Advisor to detect the problem. But that doesn't work either.
Anyone run into this?

Yep, half of my tracks are coming up displaying an error -69 ( http://docs.info.apple.com/article.html?artnum=302684 ) and every time I remove a track from the shuffle or update the shuffle, Itunes opens a window displaying the contents of J:\ (obviously the ipod) and hidden folder \iPod_Control.... I'm really irked with this. Been mucking around with the stupid thing for hours now.
Nothing was wrong with it until it suddenly decided to stop working, it wouldn't play tracks and Itunes wouldn't recognise it, hadn't missed a beat up till now. Sifted through the Support site for an answer and getting told I needed to update Itunes and update the Ipod software, ***?? It was working fine before. Me thinks Apple have inserted software in ipod to force users to update to newer version of Itunes. Anyway, ever since updating to the latest Itunes, the Ipod is back in action, but it is trying to tell me that half of my mp3s are corrupt (see error -69), rofl, um no, it's your stupid software Apple, I'm off to by myself a decent MP3 player without the bloat software.

Urgent Issue New Mac Pro (Im going CRAZY)

I recently purchased a MAC Pro with the following specifications:
Processor Name: Quad-Core Intel Xeon
Processor Speed: DUAL 2.26 GHz
Total Number Of Cores: 8
L2 Cache (per core): 256 KB
L3 Cache (per processor): 8 MB
Memory: 6 GB
Graphic Card:
Chipset Model: NVIDIA GeForce GT 120
and I seem to be getting very slow results in Motion. I have an IMAC with motion and it is able to process and playback faster than on my MAC PRO.
FCP is a thousand times faster but I am mainly working with Motion.
Also when I am on the internet and looking at some websites with Flash I notice a slower results with the MAC PRO
I am guessing my issue here is with the Graphics Card..
But How WHAT? I am using a NVIDIA GeForce GT 120 (I know its not super fast but faster than that on my IMAC)
Is there some type of control of allowing me to use more of the graphics card? I just am wondering if the graphics card is being maximized and if it is what does this mean? I know that I could buy another NIVIDA GeForce GT 120 but will my system be able to use them both. I am using Leopard and I know that the software like motion and even leopard are limited to how much of the graphics card may be used.
Ahhh
Please help!!

First, what versions of FCS/OS are you using on your i-Mac and what versions on your new Mac Pro?
Second, Motion does not like working with more than one card installed, however, I have two 2400HD cards installed and have no problems with motion (FCS 2). Some believe the two card problem is with Plugs, not Motion. I tend to agree.
Third, there is a known problem with Flash player in both Macs and PCs. I answered this question yesterday on this dissucussion board. You need to uninstall all traces of Flash player and then reinstall the latest player. The uninstaller, instructions and info about the problem is on the Adobe support page.
Post back with the info from my first comment and we'll go from there.

New Mac Pro, AMD, Prem Pro CC & GPU Acceleration Issues

Hi,
I am not exactly what you would call an expert at Adobe Premiere Pro but I have been struggling to make a few exports over the last few days and yesterday discovered that the issue was about Premiere Pro not playing nicely with the AMD FirePro D500 installed.
With GPU Acceleration (OpenCL) turned on I get strobing and all sorts of glitchiness. Once it is turned off, everything works fine. The exports seems to take more than twice as long but they are perfect.
I have found very little about this online and nothing identically matched my experience.
Has anyone else had this? Have you found a work around?
Machine is nMP 3.5 Ghz 6-Core 64GB RAM with AMD FirePro D500.
[Text formatting corrected. Please type your posts into the forum, as copy/paste often carries with it unwanted code.]
Message was edited by: Jim Simon

samfaulkner wrote:
I have been struggling to make a few exports over the last few days and yesterday discovered that the issue was about Premiere Pro not playing nicely with the AMD FirePro D500 installed.
With GPU Acceleration (OpenCL) turned on I get strobing and all sorts of glitchiness. Once it is turned off, everything works fine.
Pr has been perfect on my new Mac Pro (D700s, but that shouldn't matter). Are you exporting direct from Pr or queuing to AME? If one, can you try the other and see if the same thing happens?
What are you exporting to?
Is OS X all up to date, I assume? And you're running the latest version of Pr CC?

New Mac Pro / Premiere Pro CC / Open CL - Known issue??

Hi all
I've been using Premiere Pro CC on a new Mac Pro since it was delivered in January. After some initial teething issues and system crashes everything was running VERY nicely until the last update (build 33) but since then I have been encountering all kinds of issues.
PP is now constantly freezing and crashing not only the software itself but the entire system requiring a reboot. Whenever I need to render I get all kinds of weird and wonderful glitches in the images and I've had to turn off GPU accel through Open CL just to get the system workable again.
So my question - are these known issues with build 33 or is something else going on??
Another issue unrelated to Open CL (i think) is that XML import / export now appears to be bugged to the point of being unusable. Very very frustrating!

Hi simonspear,
Please check the forum discussion which states the same issue. Hope it helps.
Render & Export Glitching
Regards,
Vinay

Premiere Pro CC & New Mac Pro - Audio Line Out Issue

I'm having a few issues with the audio line out on the new Mac Pro. For some reason, Line Out locks into Premiere Pro. When I switch programs, the audio line out device stays locked to Premiere Pro and the only way to get other programs to be able to output audio when Premiere Pro is not current application, is to go into System Preferences > Sound and click onto an alternative output and then click back onto Line Out.
Thanks,
Jon

Thanks.

Adjustment Layer Issue in CS3 & new Mac Pro

anyone having the following issue:
when adding an adjustment layer to a file I get a spinning beachball for 10-30 seconds before the adjustment layer is applied. Strange behaviour never seen before. New Mac Pro Dual Quad 3.2ghz, 10gb Ram, Nvidia Gefore 8800GT.
S.O.S.
Thx!

How did you update to 10.5.3?
Via Software Update; or from the COMBO?
[I notice that MacFixit are also now strenuously urging people to stay away from SU and to use the COMBO instead.
[Pace Stockholm!]
And did you run DiskWarrior and Repair permissions both before and after you installed the new software?

AMD Crossfire, Boot Camp, and the new Mac Pro Issue

Hello, all.
I have a new Mac Pro (Late 2013) with 6 cores, 32 GB RAM, and dual D700 AMD graphics cards. I'm using an older 30 inch Apple Cinema Display (with the dual link DVI adapter). I've successfully installed Windows 8.1 under Boot Camp. Here's my problem...
I understand that for the new Mac Pro under Boot Camp enables AMD CrossfireX by default from multiple sources online. However, it's disabled on mine, and every time I try to enable it (and hit "Apply" in the AMD Control Center), it disables again.
Is Crossfire only available for use with a Thunderbolt Display attached? Could that be the problem? Or is the AMD Control Panel lying to me?
Now, games in Windows are still running well... But I'd like to take full advantage of the dual graphics cards in the new Mac Pro with Crossfire. Any help is greatly appreciated, thanks!

Fixed it!
So, not only would Crossfire not enable under Windows 8.1 on my Mac Pro in Boot Camp... But Windows started crashing massively. I was about to wipe Boot Camp entirely and try a clean install (even though the only three things I'd installed were Windows itself using Apple's exact instructions, Steam, and Skyrim), but decided in a last ditch effort to try disconnecting and reconnecting peripherals.
Turns out the culprit was my Belkin Thunderbolt Express Dock.
Disconnecting the Belkin Thunderbolt dock not only stopped Windows from crashing, but now I can enable Crossfire, as well!
Now, this is especially strange since I have read elsewhere that people have no problems using the Belkin dock under Boot Camp with other Macs... This issue is probably isolated to using it in Boot Camp with the new Mac Pro. But disconnecting the dock from my Mac Pro has solved not just one but all of my Boot Camp issues. (Of course, using the Belkin dock under OSX on my Mac Pro is no problem.)
Long story short, if you have a new Mac Pro and plan on using Windows 8.1 under Boot Camp, don't have the Belkin Thunderbolt Express Dock attached.
I'm going to contact Belkin and tell them what I've discovered.
Hope that helps y'all.

New Mac Pro 2013 late version USB 3.0 hub issue during boot

Hi all, I just purchased a new Mac Pro 8 core with 32GB of ram and 1 TB drive. When I connect a USB powered 3.0 hub and turn on my Mac Pro, it gets hung on while booting. (Gray screen before the Apple logo appears on boot). If I pull the USB 3.0 hub out, the Mac Pro proceeds to boot normally. Once I am fully booted on my Mac Pro and I plug the USB 3.0 hub back in, everything seems to work fine. I have an enclosure that works off of lightening connector and the enclosure has a USB 3.0 hub onboard. I plug the USB 3.0 hub in that device and every thing seems to boot up fine on the Mac Pro. Any idea why when I plug in the USB 3.0 directly why the Mac Pro ha issues booting up?
Thanks in Advance.

The Driver for the Hub does not get loaded until late in the Boot-up process.
It is common not to be able to use devices on a Hub during boot-up, as they will not be ready (and therefore not available) until the Login screen appears.
For devices you need during boot-up, attach directly to a built-in USB port on the chassis, not on a display or any other Hub.
If your issue is only that the device interferes with Booting in general, ask the guys at OWC. They select their stocked items for trouble-free, and train their support people to resolve remaining problems quickly. If there is a problem, they will help you get is fixed quickly -- often providing an advanced exchange if that seems appropriate.

New Mac Pro, Firewire issues

Similar Messages

Maybe you are looking for