Hi,
when I connect our PDW-F70 to our new intel Power Mac (2x3GHz Dual core) via firewire, the discs won't get mounted in the finder.
I've installed the latest version of Sony's XDCAM transfer tool (1.1.0).

The funny thing is that the disc shows up in the Mac's disk utility. I can also use the FAM driver tool to switch the PDW's iLink mode from AV to FAM and back.
But the Media just won't get mounted in the finder and the transfer tool also doesn't "see" the inserted disc.

I also connected our PDW-F350 to the intel mac - same result.

When connecting PDW-F70 to our G5 again there were no problems. The inserted discs mounted immediately and importing worked fine.

Anybody here having the same problems? Any ideas?

Thanks in advance,
Christian Hoffmann

Make sure the camera really is in FAM mode and not AVC mode. I've made that mistake several times in the past.

Also, try plugging in the cable to computer and camera, and then turn the camera on (in FAM) and wait a few seconds, it may come up then...

best,
-Greg

The PDW-F70 deck as well as the PDW-F350 were definetely in FAM mode. I even changed the mode from FAM mode to AV mode and back several times, using the FAM driver tool. And as I mentioned - if I connect the PDWs to our old G5 everything works fine. But I stumbeled on something: In the information window of the FAM driver tool on the intel Mac it states that the driver "prodisc_fs" is not loaded (see attached screenshot.). Th FAM driver tool on the G5 states that "prodisc_fs" is loaded. So that seems to be the problem. I tried to install the transfer tool again, hoping the driver might be correctly installed on the second try. No luck. Maybe I should completely uninstall the package but I don't know were all the drivers are located. Any ideas how I could get ALL the XDCam transfer stuff off my system so I can do a clean reinstall of the software?

Thanks in advance,
Christian Hoffmann

Christian,

It seems the owner/permissions are incorrectly set on your FAM drivers during install. Try install again after doing the steps below to remove the FAM drivers.

How to manually remove the Sony FAM Driver software from the computer.

Okay. Break out the terminal. Take a deep breath and type the following in:

sudo rm -rf /System/Library/Filesystems/prodisc.fs

sudo rm -rf /System/Library/Extensions/FAMProtocol.kext

sudo rm -rf /System/Library/Extensions/prodisc_fs.kext

sudo rm -rf /sbin/mount_prodiscfs

** You will be prompted to enter your password upon first command.
** Warning! I take no responsibility for any damage done to your OS when doing this. Yadda Yadda Yadda...

After doing this, re-install the XDCam 1.1 software. If you still aren't successful, run the Disk Utility and Repair Permissions on your disc. The utility will read the installed package receipts and reset the permissions for the installed itsems so the OS doesn't freak out.


Plan B:

Alternately, you may MANUALLY change permissions of the FAM driver installed components so that the MacOS will load them by doing the following:

Open the terminal. Take a deep breath and type the following in:

sudo chmod 755 /System/Library/Filesystems/prodisc.fs

sudo chmod 755 /System/Library/Extensions/FAMProtocol.kext

sudo chmod 755 /System/Library/Extensions/prodisc_fs.kext

sudo chmod 755 /sbin/mount_prodiscfs

Then...

sudo chown root:wheel /System/Library/Filesystems/prodisc.fs

sudo chown root:wheel /System/Library/Extensions/FAMProtocol.kext

sudo chown root:wheel /System/Library/Extensions/prodisc_fs.kext

sudo chown root:wheel /sbin/mount_prodiscfs


Then restart your mac.

** You will be prompted to enter your password upon first command.
** Warning! I take no responsibility for any damage done to your OS when doing this. Yadda Yadda Yadda...
** now that the permissions/owner/group is set right, the Mac should load these at startup...

best regards,
-Greg

Greg,
thanks a lot for your help. I won't be able to try this before Monday.
I'll let you know if it worked.
Thanks again and have a nice weekend.

Christian

BTW Greg, can he not copy and paste the text you've provided? That helps eliminate typing the wrong commands in the terminal window.

I was also wondering if the usual first two lines of defense in the OSX world might work. Trash the preferences, then repair disk permissions.

regards,

-gb-

Hi,
I tried both of your methods - nothing worked. Even logged in as root and deleted the files you mentioned manually, then rebooted, then reinstalled - no luck. Media still doesn't mount in finder. Any ideas except for reinstalling or throwing the Mac out of the window?

Thanks for your help so far.
Christian

prodisc driver notwithsatnding, i noted that you are using the FAM driver tool to switch between FAM and AV/C mode ... try changing to FAM mode in the menu pages of the F70 instead and see if that works any better
Menu > Setup Menu > Interface Select > iLink Mode > FAM

I tried both methods of switching to FAM mode. No luck. In fact I always used the PDWs menu to change modes before this problem occured. I only tried the FAM driver as alternative to switch between modes. But just to be sure I just tried again and changed the mode in the PDWs menu manually - same result.

But thanks for your input.

Christian

Is it possible that your computer has a newer version of OS than what is accomdated by the Sony transfer tool?

Is it possible that your computer has a newer version of OS than what is accomdated by the Sony transfer tool?

Not likely, Peter. I have the latest version of OSX and my system works fine with XDCAM Transfer. However, I should qualify that by saying that I have a G5 based system and Christian says his G5 systems are working, the Intel based Mac is the one with the problem.

-gb-

Christian, at this point I'd:

1-Start with re-installing the system over top of the existing. It only takes 15 minutes or so.

2-Failing that, wipe it and start over.

#2 is drastic I know, but it only takes 2-3-4 hours to do that and reinstall all your software, and I suspect you've already spent at least 3 on this already.

I'm curious to hear how this is resolved!

2-Failing that, wipe it and start over.


I was afraid that at some point somebody would post something like this.... ;-)
The funny thing is that the intel mac is brand new out of the box and freshly installed. But me and my dealer had a hell of a time to get our fibrenetix raid up and running with MetaSAN. That' why the thought of a reinstall scares me. Maybe the MetaSan software (http://www.tiger-technology.com/article.php?story=MetaSAN) IS the problem. On the other hand the combination of both softwares is running fine on the G5.
Regarding a system reinstall - I think for the moment I'll stick to capturing the material as DVCPro HD over HD-SDI. If it has to be native XDCam HD I still can carry over the PDW to our old trustworthy G5. 10.5 is somewhere out there on the horizon and then I'll have to reinstall anyway.
Lots of thanks to all of you who were willing to help me. I appreciate that very much.
I'll let you know if there are any news.

Thanks,
Christian

I have the latest OS-X updates on an Intel Macbook and a MacPro and everything works fine. I would suspect your MetaSan installation.

Wow. If the reinstall didn't work, I wonder if you need to zap your PRAM to get the firewire port recognized.

Restart the MacPro and hold down <Option><Cmd><P><R> and hold it down for a few 'bongs' as the mac starts... then your PRAM should have been zapped. Then try mounting the XDcam again...

best,
-Greg

Didn't help. I resetted the PRAM, removed the drivers according to Greg's "how to...", then deleted the applications themselves (XDCam transfer and FAM driver tool), deleted the installation receipts, repaired permissions, rebooted the Mac, then installed the software again - same result. Disc won't show up in the finder. Here comes the really interesting part: since going through this procedure neither Quicktime nor Final Cut Pro can read the last XDCam HD clips I transferred to our raid using our G5. I imported them when I started this thread and noticed the software wasn't working with our intel mac. The files were all ok and I already finished a project on the intel mac using them. Now I can neither open them on the intel mac nor on the G5. The screen in FCP gets green when I open them and Quicktime gives me an error message. I have no problem opening older XDCamHD files, just this last project seems to be affected. Scary, huh?

Christian,

Perhaps your OSX installation got corrupted. Hmm. How about doing this:

1. Boot from MacPro install disc. Do a clean install. Options: Erase and Install. Customize -> No printer drivers, no language translations except the ones you need. No extra fonts. No additional printer drives. Select X11 .
2. Do a basic install of FCP Studio for now. Just pick FCP and Compressor only, that way it will install in only 2 minutes. Install everything else later.
3. Do Software Update. Get all updates.
4. Reinstall XDcam 1.1 drivers/xfer
5. Try FCP again with import and see if it works...

best regards,
-Greg

Hi guys,
some of you might be interested what exactly the problem was. Like Alister said: it was the MetaSan software. I had a 4 hour remote desktop session with one of the support guys from tiger technologies and he managed to fix the problem. He said it has something to do with MetaSan blocking non-HSF volumes. The funny thing is: this bug only affects intel Macs.
Once again: Big thanks to all of you who tried to help me.

Christian

Hi guys,
some of you might be interested what exactly the problem was. Like Alister said: it was the MetaSan software. I had a 4 hour remote desktop session with one of the support guys from tiger technologies and he managed to fix the problem. He said it has something to do with MetaSan blocking non-HSF volumes. The funny thing is: this bug only affects intel Macs.
Once again: Big thanks to all of you who tried to help me.

Christian

Christian, many thanks for that follow-up. I had a software conflict last fall, affecting my import of XDCAM. It would max out the processor and take forever to import stuff. Wouldn't show thumbnails either, unless I manually created them from XDCAM transfer. It turned out to be the 3ivx codec package version 4.5.1.

Glad you got it resolved!

-gb-