New Mac Pro vs firewire iSight

I have a mid 2010 Mac pro dual quad, I just got my hands on a new never used firewire iSight. Problem 1 the new mac's have changed the firewire configuration, luckily I had an adapter I bought when I purchased my 2010 macbook pro. problem 2 the camera only worked with iChat. After searching the forums, and trying everything from resetting the PRAM etc... I ran across this old thread
"http://discussions.apple.com/thread.jspa?threadID=1954490&start=25&tstart=250"
Thus the camera being still new, but old had the old 1.02 firmware, and needed to be updated to 1.03. Problem 3 Snow leopard does not have the updater, you need 10.5 or older to update the firmware. Lucky for me I had an old Blue iMac in the corner (that was another project), I fired it up and updated the firmware. Now life is good, the camera works with all the apps. The thread is old, but I found it to be the most help. Hats off to EZ Jim & company!

You're welcome.
Thanks for the kind words.
To save some searching for readers running Mac OS X 10.4 or later who are trying to manually
upgrade external (Firewire) iSight's Firmware to version 1.0.3, your options are here:
http://discussions.apple.com/thread.jspa?messageID=10084429&#10084429
<hr width="85%">
Alternatively, user Malcolm Rayfield has suggested another way to apply the
1.0.3 iSight firmware update *using a Snow Leopard Mac.*
• Download the updater that was provided for Mac OS X 10.3.7-10.3.9 from
http://support.apple.com/downloads/iSightUpdater_1_03
• Double click the iSightUpdater103.dmg if necessary to see the "iSightUpdater103.pkg" .
• Right-click the iSightUpdater103.pkg icon and click "Show Package Contents."
• Open the Contents folder and double-click the Archive.pax.gz file.
• That will unzip an Applications folder that contains a Utilities folder.
• Inside the Utilities folder is the iSight Updater 1.0.3 folder.
• Open the the iSight Updater 1.0.3 folder to find the iSight Updater 1.0.3 app.
• Double clicking the iSight Updater 1.0.3 app will run it.
• Note that iSight Updater 1.0.3 is a PowerPC application, so your 10.6 Mac will need Rosetta to run it.
If you have not already installed Rosetta, click the Updater and follow your Mac's on-screen instructions.
If you have difficulty or merely do not want to add Rosetta to your Mac, your Apple Tech
can do the firmware for you, or you can use one of the other options described in the link above.
EZ Jim
Message was edited by: EZ Jim
Mac Pro Quad Core (Early 2009) 2.93Ghz Mac OS X (10.6.6); MacBook Pro (13 inch, Mid 2009) 2.26GHz (10.6.6)
LED Cinema Display; G4 PowerBook 1.67GHz (10.4.11); iBookSE 366MHz (10.3.9); External iSight; iPod4touch4.2.1

Similar Messages

I have interface M Audio firewire 400 new Mac Pro has firewire 800 Do you think an adaptor will provide the same quality? Will the M audio 400 work with lion and new system? Thanks so much

I have interface M Audio 400 with 400 firewire new Mac Pro has firewire 800 Do you think an adaptor will provide the same quality? Will the M audio 400 work with lion and new system or do I need new software? Thanks so much

If you have a little Firewire adaptor, everything should work fine. It does on my system.

External iSight - New mac pro

Hi Guys,
I've bought myself a new mac pro with two 27" screens, and everything works hunky dory, BUT I want to drill through my office wall and put my old iSight camera in the lounge, and run the cable through tje wall back into my Mac pro. Its only a metre so no problem with length. My problem is how do I plug in the old firewire connector into a new mac pro. The idea is that when I'm away from home I can see my lounge and make sure everythings ok. I assume I can change camera in Skype from screen to iSight using back to my mac? Thanks
brett

Some ways to connect your FW400 external iSight to a FW800 Mac port:
• This Firewire 400-800 cable can work: http://store.apple.com/us/product/TP320LL/A
(I use this one.)
• Some report that this low-priced alternative cable works:
http://www.newegg.com/Product/Product.aspx?Item=N82E16812189097"
• To use a FW400 6pin-6pin cable, you can use a 6pin-9pin adapter like one of these:
http://tinyurl.com/ydsbb6m (I use this one.)
http://tinyurl.com/cgll7o
http://www.sonnettech.com/product/fw_adapter.html
EZ Jim
Mac Pro Quad Core (Early 2009) 2.93Ghz Mac OS X (10.6.6); MacBook Pro (13 inch, Mid 2009) 2.26GHz (10.6.6)
LED Cinema Display; G4 PowerBook 1.67GHz (10.4.11); iBookSE 366MHz (10.3.9); External iSight; iPod4touch4.2.1

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

How can I migrate data to new Mac Pro with only 1 monitor

I am ready to set up my new Mac Pro. I know how to migrate my files from my G5 using Firewire and making the new computer a target disk. My problem is, I have only 1 monitor. Is there an easy way around this, OR of not, can I use my Macbook Pro just a monitor and if so how?

If you make the new computer a FireWire Hard drive, the only thing on its monitor will be the firewire symbol. You don't need a monitor to see that.
But if you did, you could start the new computer up first, look at the firewire symbol, get a warm fuzzy feeling, disconnect the monitor and plug it into the old computer to make the transfers.

Help Configuring my New Mac Pro

I just purchased a new Mac Pro (early 2009 Quad Core" 2.66 (2009/Nehalem), and a second (1 TB) internal hard drive. I would like to transfer my applications, files, and profile from my Macbook Pro (early 2008 Core 2 Duo" 2.5) to the Mac Pro. I also want to install with Boot Camp a copy of Windows XP Pro (SP3) on a separate hard drive. I want the XP drive to be the 640 GB hard drive that came with the Mac Pro, and the MacOS drive to be the added 1TB hard drive. I want the Windows drive to have 4 logical partitions ( C, D, E, and F) with the C, D, and E being NTFS (so they can exceed 32GB) and, F drive being FAT (for read/write compatibility with MacOS). I've been doing a fair amount of reading both on this forum and have a tentative plan to accomplish the setup. But, a lot of what I'm planning to do is new to me. So, before executing my plan, I wanted to get some feedback. Any thoughts or comments on the steps in my plan would be much appreciated. Here are my planned steps:
1. Turn on the new Mac Pro computer but don't transfer and applications or files - just transfer the profile. Then check to make sure that the computer is working properly.
2. Turn off computer and install 1 TB hard drive and RAM upgrade.
3. Turn on the computer and transfer applications and files from my Macbook Pro to the Mac Pro using Migration Assistant (located in the applications, utility folder). Connect the computers using Firewire 800 (9 pin to 9 pin cable). I currently don't have such a cable, but from what I have read the migration can be very, very slow if done using the ethernet network or a USB-2 cable. I've got about 200 GB on my Macbook Pro so I assume that the Firewire cable is the only sensible way to go.
4. Test the system to see that the applications are working and check that the data files have been transferred.
5. Download SuperDuper and use it to create a clone of the 640 GB drive on the new 1 TB drive. Make the 1 TB drive the boot drive by choosing it from System Preferences > Startup Disc
6. Check and make sure the bootup from the 1 TB drive works properly.
7. Check to make sure the EFI Boot ROM version on the Mac Pro is up to date. If it needs updating, download latest version from Apple support website and install.
8. Check Apple support for updates to Boot Camp Assistant. Once I have the latest version open Boot Camp Assistant (in the Utilities folder in the Applications folder). Create Boot Camp partition that is the entire 640 GB hard drive.
9. Insert the Windows XP CD and click Start Installation in Boot Camp Assistant. Select the Boot Camp partition for installation of Windows.
10. As I begin the Windows install, I'm expecting that I will be offered at the start of the setup process an opportunity to create the 4 separate logical partitions that I want on the 640 GB hard drive. Format the hard drive with the 4 partitions.
11. Select the partition where I want to put Windows Operating System and follow the Windows setup process to install Windows XP.
12. Once Windows is installed, eject the Windows disc and insert to Mac OS disc. Install the Boot Camp drivers for Windows.

NTFS is read only already. You don't need anything just to access, only if you plan to write files, and NTFS won't like HFS file names if they have special characters.
XP SP2 or later, and would have to be able to transfer to new hardware. What it lacks is good multicore and memory management.
Newegg and Amazon has single system builder versions that can save but can't be used on another system. OEM (Dell, HP, etc) versions or "restore discs" won't work and aren't supported.
I said you can get by without BCA. You don't have to believe me but it is a waste to have to say everything twice. Windows 7 is perfectly capable of doing any formatting and installing without it.
Installing Windows 7 on Mac Pro is easier and different. There is a forum devoted to Boot Camp and Installing Windows.
http://discussions.apple.com/category.jspa?categoryID=237

I have a new Mac Pro. I want to use my old Mac Pro as a storage drive for photos and old documents, linked to my new Mac Pro. How do I set up the old computer?

I have a new Mac Pro. I want to use my old Mac Pro as a storage drive for photos and old documents, linked to my new Mac Pro. How do I set up the old computer? Both computers have OS X10.9.3. Currently they are connected by a Firewire 800 cable.

You certainly could keep the old Mac Pro in Firewire mode (hold down the T key on its keyboard as you boot) to show its drives on the new MP. This is basically as fast as putting the drives into a Firewire enclosure.
Or you could boot it normally and share its files over the network using the Sharing panel of System Preferences. If you turn on both File and Screen Sharing, you don't even need to have a monitor attached - you can do all administration using screen sharing. However, this method requires that you open all files over the network, which will be slower than the direct-connect method above, and may also not work with all applications.
Matt

After Migration to new Mac Pro, intermittent slow downs, SROD's

I started with a my intel mac mini, Leopard OS was installed on an external Firewire drive, most applications were installed on another partition of that same drive. I bought a new mac pro 8 core, and an additional firewire external drive that I set up as my Time Machine drive on my old mac mini. I did a full backup of my old mac mini system and then attached the time machine drive and the other external hard drive to my new mac pro. I used the migration assistant to transfer files to my new mac pro. However, now there appears to be something occuring between my internal mac pro hard drive and the old external hard drive from my mac mini. When using some applications, Itunes, Logic Pro, Firefox, the ap will hang and appears to be trying to access files from the old external drive. I hope I'm being clear with what the issue is. I'm thinking duplicate files on this external drive and my internal drive are causing some problems? I need to know how to repair the issue, and preserve my data files?

bb240z wrote:
Thanks for your quick response. I know I've been somewhat confusing here. I'm running the latest Snow Leopard update on my mac pro now.
Then please update your profile, as it still shows the mini and Leopard.
And I'll ask a Host to move this to the Snow Leopard > Time Machine forum.
All the aps and data were migrated onto the internal HD in the mac pro, and the aps and files and directory structures, etc. are still also on the external drive that used to comprise the OS of my mac mini. I'm thinking that may be part of the issue, but I'm new to Mac and not certain of that or how to fix the issues.
Depending on how you did that, I'm not sure everything on those partitions got on to the new Mac's HD. Check that first, via the Finder.
Let's start with iTunes and/or iPhoto.
First see if you have the same stuff in both places. Use the Finder to see how large each is on the external HD, and compare that to the iTunes and iPhoto folders on your internal HD.
If they're not on your internal HD at all, use these instructions to move them:
Moving your iTunes Music folder
Moving your iPhoto library
If the versions on the external are newer than the ones on your internal, delete the ones on the internal and use those instructions to move from the external to the internal.
But don't delete the versions on the external just yet. Eject and disconnect it, and make sure everything's fine. It won't hurt to leave the data there for a while, especially as long as it's disconnected.
If the music or photos on your HD are the same, or newer, hold down the Option key while starting iTunes or iPhoto. That will give you a prompt where you can select which one you want to use.
Once you've selected the ones you want, eject and disconnect the external. Then use as many apps as you can, to see if everything works properly and all your data is found.
Without knowing what other apps you have, and how they work, I can't tell in advance whether any others will be looking for the external drive. If you get error messages, you'll have to deal with each app that seems lost.
I'd be inclined to keep the old external "on the shelf" for quite a while, just to be sure nothing got missed.
Have you started doing Time Machine backups of the new Mac yet? When you do, you'll get a prompt about whether to "re-use" the Mini's backups. See #B5 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum. You probably want to select "Re-use," especially if there's a considerable amount of space on your TM drive.

Obsolete new "Mac Pro" vs Windows 6 Core 3930K PC - What should I expect?

OK, I ordered a pretty fast PC from Amazon, kind of a no-name gaming PC but it had great specs, i7 3930 Six Core at 3.2 ghz.
Installed a Nvidia GTX 670, did the supported cards text file hack, and Premiere Pro 5.5 on it, along with Quicktime Pro, and fonts I needed. I also installed a nifty program called X-Mouse which allowed me to customize my logitech scrolling mouse to use Premiere Pro as I also using USB Overdrive on my Mac - indispensable software.
Got a KVM so I could use my 2 large displays currently hooked up to my Mac on the PC without totally disabling my Mac Pro 2008 8 core - it is my workhorse and I use it all the time.
Finally got the PC somewhat functional on with Premiere Pro and even got it working with projects and media via a fast network connection. It seemed like butter vs my old Mac Pro. My lack of being a Windows power user I'm sure was responsible for my ultimate failure at getting my Windows system, but there could be hardware issues with this particular PC as well. Ultimately it was a total pain to share projects and media that resided on my Mac. Using Premiere Pro on the PC was identical in many ways to the Mac, just faster.
However the PC started going downhill pretty much as I got it working. It wouldn't properly reboot, always spinning in the 'Shutting Down' screen. I had to hard restart it all the time.
Then things started to go south, probably due to system corruption from having to hard reset it. I installed a fresh OS on the other internal drive in hopes it would fix the problems, a whole new set of software to get Premiere Pro working well. Again, shutdown hangs, without any diagnostics other than windows coming up at the hard restart saying there was a problem with the previous shutdown, and wiping out a lot of stuff each time. Then in hopes of curing the ills, a reformat of the drives, reinstallation of Windows 7 Pro, and then the ability to actually install the OS. 2 reformatted drives that cannot b installed with OS. Epic failure. The replacement is on the way.
But this being said, the amount of time in order to make this environment 'cross platform' as well as the indiocyncracies of Windows (to me, I'm not bashing Windows - it seems to be a fine OS!) makes me rethinking the PC for Premiere Pro switch.
I realize the current Mac Pros are basically obsolete, however, MY Mac Pro really is, it's from 2008 and not the fastest model from that era (2.8ghz 8 core, non threading Xeon.)
Investigating "new" Mac Pros, I can get a 6 Core 3.3 ghz threading Mac Pro plus 32GB of RAM for about $3,500. I can get a 12 Core 3.09 ghz for $6,700 and a refurb 2.93ghz with 32GB for about $5,700. The Windows PC with everything I need is in the $4K range. I don't need any new peripherals to make it a direct replacement for my current Mac Pro, all PCI, peripherals will just work. I'm familiar with the OS, and all my apps and plugins will work, no KVM necessary, no cross platform issues. Just not as cost effective as the PC and perhaps slower.
However...
Disregarding the cost, my time is valuable and I probably spend a good 3 solid days getting something non functional to work. There will be continual inefficiencies because I'm not a Windows shop, and I don't foresee this.
Will any 'new' Mac Pro, regardless of the cost, get me to the speed using Premiere Pro of this 6 core 3.2ghz i7 3930K? If I get the answer that the Mac 12 core will get me there, it may be a viable option. If the 6 core will get me 80% there, it might be the 'best buy' option.
Thanks for any advice, really!
-Keith

Thanks Eric and Harm for the helpful answers. I was hoping that Windows 7 had evolved to the point where knowning and using some of the troubleshooting techniques that Harm mentioned would not have to be necessary. I do have the ability / skill, etc, but not necessarily the desire to troubleshoot, but was kind of hoping that I wouldn't need to get to this level on such a simple installation, really it was just CS 5.5 and Video drivers. It is very possible the KVM was blocking on the USB request. This occasionally will happen with a hung device on Mac OS X and firewire, but usually it times out after a while. However there have been those odd times where I needed to unplug everything and even do a NVRAM reset on the Mac to get it back. This is pretty rare though. I even have my Mac set to 'verbose mode' which leaves the unix console up on boot and shutdown so I can track offending things like this. Maybe there is a Windows equivalent to this, which would have been helpful. Knowing that there might be some request that wasn't returning, I left Windows in this state for hours, it never got back. I had no choice but to hard restart it. I didn't examine logs and such, though I could have. I just want it to work or to fail gracefully, and not fail in such a way that makes it unusable and unrecoverable without in depth troubleshooting. I also have to use the KVM, without it I can't possibly use the system. So if the KVM makes the PC hang, then I can't use the PC. It doesn't make my Mac hang.
I am also quite positive that ADK's systems would have been a lot more robust and their emergency DVD's would have actually been able to help me as well as their expert tech support. I also appreciate that though Eric and ADK are a business, that the advice you have provided to me is just helpful and agnostic. This goes a long way to pushing my next PC purchase in the ADK direction!
Getting back to my original question, which was not one of troubleshooting Windows PC's though that advice is helpful...
Seems like a 12-Core Mac would allow me to edit well. I can edit right now with my 2008 Mac Pro 8 Core with 24GB RAM and 240GB SSD and Quadro 4000 and numerous internal and external RAIDs, but just scrubbing AVCHD I see all 8 processors go to nearly 100 % utilization and it's laggy. Not the best editing experience. If I have a few AVCHDs overlaid, which I do, it's almost unusable. As the Premiere Pro project gets bigger and more complex, it seems that everything gets slower. I have no scientific basis for this but I think it's true. It doesn't have to be just the sequence I'm working on, it seems to be even navigating simple sequences will be laggier if in a larger complex Premiere Pro project file.
On the Windows PC i7, for the few hours it was functioning, I was able to scrub AVCHD 1080P footage over a gigabit ethernet like butter. I was pleased with this. It was a very simple 1 track sequence, however. I didn't have a chance to try it with more complex projects before it was unusable.
Would I get smooth performance from a Mac Pro 6 Core, which is $2,500 less than the 12 core? From the basic Mac benchmarking I see, I see a 'rating' of 14000 for the Mac Pro 6 Core, and around 9000 for my current Mac Pro 8 core. This is about 50% more. I don't think 50% is going to get me to 'butter.'
Thanks again for all the helpful advice, Harm and Eric.
-Keith

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.

My new Mac Pro will not recognize my old Canon video camera

My new Mac Pro will not recognize my old Canon video camera

We've used the 400 to 800 firewire cables with limited success in the past...dropped frames was the main problem. Only used them until the Sonnet FireWire PCIe Card came in to allow a 400 firewire.

Last Mac Pro with Firewire 400?

The new Mac Pro's look nice, but without Firewire 400 they're useless to me... Can anyone tell me when the last Mac Pro with Firewire 400 was released?...and what the speeds were on them? Thanks in advance if anyone can help.

Fair points, to be sure. I just think that, given the number of common/popular devices that are FW400 only, the removal of FW400 ports is a bit premature at this time. Like the OP said, it would be frustrating to buy a very expensive computer, and immediately have to expand in order to make use of fairly standard and not yet out-dated gear.
Dave Sawyer wrote:
Sorry to disagree, but to me, expecting a company to go to the expense of engineering in a different physical port just to save someone from having to use a simple, inexpensive cable adaptor seems a bit silly.
It couldn't be that hard/expensive, given that previous models had both. Though I certainly understand the idea of reducing cost wherever possible.

How do you new Mac Pro owners like your machine with Logic?

Don't mean to be a PITA but I need to get this right before I drop three to five grand on a new set of music tools. I'm trying to decide between Mac Pro and iMac for use with Logic. Seems there are a lot of posts regarding glitches with the new Mac Pro and Logic, whereas the posts from people with older G4s and G5s seem to indicate they are running rock solid. So you new Mac Pro folks or anyone else, please weigh in. Is the new Mac Pro "glitch heavy" or is it just a matter of tweaking the system to where it runs smooth? In general, how do you new Mac Pro folks like the way it works with Logic?

I'm mostly pleased with my MacPro 2.66. Almost no crashes with Logic, although I experience a few more bugs here and there than with my G4. Occasional CoreAudio errors, I have to restart CoreAudio if my external word clock is set to the wrong sample rate when I open a session, there seems to be a bug between high fader levels (above +4dB) and panning... little things like that.
Then again, compared to my G4, the FireWire bus is screaming fast--with most sessions, I can run a buffer of 128 samples at 96k with my MOTU 828mkII, while my G4 would sometimes glitch at 96k with 512 samples. At 96k, 256 samples, my MacPro/828mkII rig is rock-solid... I informally tested it by recording 12 test tracks simultaneously for 20 minutes, with the CPU nearly maxed out (which was difficult to do--took a bunch of Space Designers and Ultrabeats)--absolutely zero clicks or pops.
And of course, WAY more processing power than my G4.
I'm assuming that MacPro compatibility is a fairly high priority for Apple these days, so hopefully the bugs will get worked out soon. And as things are, Logic is definitely usable on a MacPro--the bugs I encounter rarely slow down my work.
So, far from perfect, but as far as new technology goes, I'd say Logic on the MacPro is above average.
Good luck!
James
[email protected]

Best way to set up a new MAC PRO

I am a free lancer who has just taken the (huge) step to setting up a small graphics/final cut studio in my apartment (NYC). The core of my operation is a brand new MAC PRO. 3 questions:
1. What is the best physical environment for the new system in terms of temperature, dust, and access to the back of the tower? I am planning on using Metro Shelving to put the tower on.
2. I ordered a 1 terabyte hd. What is the best way to partition a hd this large?
3. So far I have only had experience setting up laptops purchased off the shelf. The tower was "made to order", what are decisions that need to be made when you are setting up the system for the first time?
Any other words of wisdom on the care and feeding of the new tower would be greatly appreciated!

You can skip on the Apple Pro RAID card. Pick up a 3rd party card later.
I would pick up three of the above F1s for $150 ea. and can be used in RAID using Apple software, works fine.
I would have saved $$ and skipped the 1TB drive. Great for Time Machine and backups.
Why use external drives for media if you can have native SATA, use those for backup too.
When you have more drives you can clone your system and files as needed. One thing I would do now is make a clone of your system to one of your FireWire drives that you can boot from and use to restore to another drive later.
You may as well partition the new drive so you can isolate the system and apps if you want, and before the files fragment the drive more than it is so you can resize and create partitions if it helps.
I have only used mirrors a couple times, I find I'd rather put two or more drives to separate uses, and it isn't a replacement for backups.
There are some RAID5/6 3rd party external controllers that can drive up to 4 x 5-drive cases (Port Multiplier).
http://www.amug.com - click on Reviews.

New Mac Pro vs firewire iSight

Similar Messages

Maybe you are looking for