I wonder if it is supposed to work? Why would audio and a thumbnail import? How did it work before this update? Did it not even import anything? Someone needs to raise some hell! Im in a X70 group on Facebook and someone posted from NAB saying that there is alot of buzz on this cam!!! Supposedly the price drop was to make up for the upgrade cost when it comes out. So no new cam until then when I assume it will just ship with the update...

I wonder if it is supposed to work? Why would audio and a thumbnail import? How did it work before this update? Did it not even import anything? Someone needs to raise some hell! Im in a X70 group on Facebook and someone posted from NAB saying that there is alot of buzz on this cam!!! Supposedly the price drop was to make up for the upgrade cost when it comes out. So no new cam until then when I assume it will just ship with the update...

With the prior version of FCX, it didn't work either. Same thing; blank video and just audio came in.

Both Apple's and Sony's sites _minimally_ have documentation errors. Both sites say that you can import XAVC. Which in my eyes means all flavors of that. But that's of course not true since XAVC-L fails to work.

What I'd minimally like to see is for Apple/Sony to change their documentation to reflect what actually works. That means explicitly citing the exact flavors of XAVC that can be imported. That of course doesn't fix the issue, but would at least let consumers not waste time.

Sony guy at nab said apple will b announcing upgrade in app store in next few days.sony had given apple what they needed months ago.this delay is on apple not sony

Just to inform that Lightworks 12.0.3.A can read the XAVC-L 1080/60p 50Mbps natively without any transcoding. I'm a Vegas Pro 13 user and it's a bummer that this program as such a big learning curve...

It's no more difficult to learn than Vegas, but just has a different approach. You can drag and drop together with doing a number of similar timeline operations as Vegas, although if you do try to use Lightworks exactly like Vegas you'll find it a frustrating business. I say this as a Vegas owner. The best best one for you probably depends on what type of productions you edit.

I just found out today that Sony are bringing out a 'Catalyst Production suite "which contains Prepare and a new 'Edit' It claims tight integration between Prepare and Edit and claims to cope with X70 files. I have only seen the promo on the Sony website. Does anyone have any more information? If this really is true, it might be a good way forward.

Sony guy at nab said apple will b announcing upgrade in app store in next few days.sony had given apple what they needed months ago.this delay is on apple not sony

An update beyond version 10.2 that was released yesterday? Or was ysterday's update suppose to have the necessary fixes?

Unless there's a ProApps codecs release soon, there's likely not going to be another FCPX update for about 3 months give or take.

HD Warrior has a good step by step of the XAVC-L problem regarding the FS7 and the X70.
It seems that the FS7 may work with HD files.

HD Warrior » Blog Archiv » Importing Sony’s XAVC footage into FCPX v10.2 (http://www.hdwarrior.co.uk/2015/04/14/importing-sonys-xavc-footage-into-fcpx-v10-2/)

I just spoke with Ian (I believe his last name is Cook) at the Sony booth at NAB. Everyone said he's the most knowledgeable person in the Sony booth on this question. He said that Apple (and Sony in Japan) promised him that a new version of FCP X, version 10.2, would be released on Monday and it would have the fix for bringing XAVC-L files into FCP. I said that I thought v.10.2 had been released this past Monday. He didn't think that was possible but he checked and I was right. He obviously had not been able to check the update to see if it worked with the XAVC-L files but I told him that my understanding from reading this and other x70 forums was that the problem persisted. (Is this true? Did the v. 10.2 update not fix the problem?) He said that there might be a problem with the difference between xdcam file structures (used on sxs cards and optical disks) and the file structure used on SD cards, like in the x70. It could be that FCP was looking for the video files/folders to be at the root level on the storage device and that the SD card protocol required those files/folders to be inside of a "Private" folder. So it's possible that if one pulled the contents of the Private folder out and placed them at the root level of the SD card, things might work. You might need to delete the (now empty) Private folder. I'm not going to be home for another week so I have no way to check this. Can anyone try this?

No, pulling things out of the Private folder doesn't help, nor does doing that and also deleting the Private folder. I tested this using a card in a card reader, not from an archive.

The problem is not that FCPX can't find the clips, it's that it can't read/import anything but the audio and a jpeg of the first frame of the video.

Others need to try though but it doesn't change anything for me.

OK, so by moving the XDROOT folder to the top of the cards directory structure, FCPX now reads the card & sees that the clip is a video clip (single clips show correct start/stop/duration now, but are greyed out) - however FCPX then quits & crashes before it finishes reading the card.

This says to me that FCPX knows nothing about XAVC-L whatsover & by changing the cards file structure it thinks it's seeing regular XAVC files, gets confused by the 'L' variety and then crashes in a blaze of glory!

So no - 10.2 does not add any XAVC-L functionality whatsoever - no cigar!


I know one thing though - I definitely won't be upgrading my X70's to 4K until this is sorted.

Two steps forward, one step back. The supplemental update OSX 10.10.3 still doesn't fix the XAVC-L problem with Final Cut Pro X, version 10.2. I did the update today (The OS X Yosemite 10.10.3 Supplemental Update fixes a video driver issue that may prevent your Mac from starting up when running certain apps that capture video.) and when I tried importing XAVC-L files from the X70, FCPX crashes. Before the update, FCP X would see a thumbnail and an audio file. Now nothing. I tried to import directly from the card as well as from a desktop folder with card contents copied. Sony Catalyst Browse sees the XAVC-L clips on the card. Enough troubleshooting for today. Wait. Maybe I should try cleaning the spark plugs?

I just spoke with Ian (I believe his last name is Cook) at the Sony booth at NAB. Everyone said he's the most knowledgeable person in the Sony booth on this question. He said that Apple (and Sony in Japan) promised him that a new version of FCP X, version 10.2, would be released on Monday and it would have the fix for bringing XAVC-L files into FCP. I said that I thought v.10.2 had been released this past Monday. He didn't think that was possible but he checked and I was right. He obviously had not been able to check the update to see if it worked with the XAVC-L files but I told him that my understanding from reading this and other x70 forums was that the problem persisted. (Is this true? Did the v. 10.2 update not fix the problem?) He said that there might be a problem with the difference between xdcam file structures (used on sxs cards and optical disks) and the file structure used on SD cards, like in the x70. It could be that FCP was looking for the video files/folders to be at the root level on the storage device and that the SD card protocol required those files/folders to be inside of a "Private" folder. So it's possible that if one pulled the contents of the Private folder out and placed them at the root level of the SD card, things might work. You might need to delete the (now empty) Private folder. I'm not going to be home for another week so I have no way to check this. Can anyone try this?

I am having my FCP-X updated tomorrow. I have an X70 and an X180. Perhaps I can copy/paste X70 footage from an SD card onto my X180's SxS cards, and attempt an ingest to see if it's the file structure? Didn't someone post that the X70 XAVC L files have different attributes than other XAVC L files from other cameras?

Paul

I see that Pro Video Formats 2.0.1 is now available. Cross your fingers! Will try this myself in a few hours.

No No No - the 'Pro Video Formats 2.0.1' update makes absolutely no difference whatsoever

This is unfortunate as I was hoping XAVC-L support would be added via this kind of update & not a full FCPX release, however as this recent update has done absolutely nothing to help this sorry situation - I think it'll now be a long long wait before a fix is released!

No No No - the 'Pro Video Formats 2.0.1' update makes absolutely no difference whatsoever

This is unfortunate as I was hoping XAVC-L support would be added via this kind of update & not a full FCPX release, however as this recent update has done absolutely nothing to help this sorry situation - I think it'll now be a long long wait before a fix is released!

Grumble, grumble. Confirmed that this is still broken. My X70 arrives today. I will be capturing a very short clip over the next couple days to attach to a new bug report filed at Apple. Probably will be sent back as a duplicate of the original closed bug, but still worth a shot.

I just finished my first night of full on 1080p60 XAVC L shooting.......ingested like magic into FCPX 10.2, looks amazing, I am soooo happy! With color correction and a broadcast filter in place, my 1080p60 XAVC L exports to 720p60 HDV at 45 seconds to the minute, very fast! 10.2 is SWEET.

That was on my X180 though......... :-\

Paul

what I don't understand is why if Catalyst Browse, Prepare, Prem Pro CC, Avid etc etc can 'see' X70 long GOP why can't FCPX developers just look at it . There must be common threads in their programmes, why can't they just copy/modify them? Would make even more sense for Vegas ( but I'm on a mac)
Must be a reason, there's a reason for everything!:)

I just put the entire card contents of an SDXC X70 XAVC L card onto my X180 SxS card. I tried adding the files as clips in the X180 video folder, they refused to show. I deleted the card and put the SDXC file structure on the SxS, and FCPX 10.2 still saw the clips as untouchable, with matching JPEG files. Obviously, not a card thing.

Paul

Something is really goofy with Pro Video Formats 2.0.1 update. I keep installing it (via the App Store app) and once even directly by downloading the .pkg file.

But the App Store app continues to show it as an available update. Anyone else seeing this?

Something is really goofy with Pro Video Formats 2.0.1 update. I keep installing it (via the App Store app) and once even directly by downloading the .pkg file.

But the App Store app continues to show it as an available update. Anyone else seeing this?

Seems like a common problem - this is a workaround courtesy of 'rgilman' over at FCP.co (http://www.fcp.co/forum/4-final-cut-pro-x-fcpx/23226-why-do-i-keep-needing-to-update-provideo)

Here's the workaround:
1) You download the Pro Video Formats (https://support.apple.com/kb/DL1396?viewlocale=en_US&locale=en_US) package directly from Apple.
2) Open that package in Pacifist (http://www.charlessoft.com/) and then use Pacifist to install it.

Worked perfectly for me!

Seems like a common problem - this is a workaround courtesy of 'rgilman' over at FCP.co (http://www.fcp.co/forum/4-final-cut-pro-x-fcpx/23226-why-do-i-keep-needing-to-update-provideo)

Here's the workaround:
1) You download the Pro Video Formats (https://support.apple.com/kb/DL1396?viewlocale=en_US&locale=en_US) package directly from Apple.
2) Open that package in Pacifist (http://www.charlessoft.com/) and then use Pacifist to install it.

Worked perfectly for me!

Thank you! Fixed my issue as well. I was working with Apple support, but we couldn't get it fixed. This saved me from having to call their Enterprise support (was the next step).

Note to self: probably should become a member of FCP.co

I just recorded a 5-second clip (color bars and tone) with my X70. Then filed a new bug report with Apple against FCP X 10.2 and Pro Video Formats 2.0.1. I attached a zip of my memory card.

If the outcome will be to simply close the bug without any information as to why, I will pursue one final option which is to use a DTS (developer tech support) incident. I get 4 of those per year. My aim is to find out exactly why these bugs are being closed when obviously the footage still cannot be imported. But DTS is primarily for code-level support (i.e. writing software). So they may not be too keen on this particular usage.

They probably don't consider incompatibility as a bug. That's like saying your CD plater not playing DVD's is a bug! :)

Paul

Still can't work it out in my simple brain. Adobe CC, Lightworks, Catalyst browse/prepare etc can do it. It can't be that difficult to sort out can it and I thought these IT guys got paid lots of money?
Would anyone like to respond? I'm a simple person!!!!!:)

I remember it took Apple a long time to make AVCHD Lite format readable and directly ingestible into FCP7. When they actually implemented it almost nobody who had used FCP7 was shooting in that format anymore. Same to AVCHD 2.0 (1080/50p,60p 28Mbps) ingest in FCPX, it took them quite a while, maybe until 10.0.1 or 10.0.2 to make the raw clips directly ingestible.

Wait for it, it will come.

I would guess it has a lot less to do with being ABLE to get it working than get it working CORRECTLY. You can get anything with 4 wheels rolling on it's own power, but there is a lot more to driving for a living than forward motion. I would also guess there are a lot of ways to get a codec to perform poorly when processed in someone else's, or even your own NLE.

Paul

We use EditReady to transcode AVCHD and XAVC-L directly to ProRes 422 in our workflow. EditReady : Transcoding Without The Hassle - divergent media (http://www.divergentmedia.com/editready)

We prefer preparing, transcoding and renaming the ProRes files BEORE importing into FCPX.

Tagging onto what Paul said (post #77), there are probably other issues in the way of a quick fix for the importing problem. Apple’s Developer’s Conference (WWDC 2015) will be in a little over a month on June 8. They’ll be rolling out new versions of iOS, OS X and who knows what else.

There may well be an update to FCP X so it seems likely that all hands will be working to make sure all the releases are trouble-free and there won’t be any hic-ups to mar the WWDC show or the releases that come afterward. It takes time for applications to be tested so they’re as trouble-free as possible and all it takes is one good “gotcha” to go viral.

On top of all this, there are undoubtably contract agreements between companies (Apple and Sony in this case) and lawyers have a reputation for “time is NOT of the essence.” Anybody know if there is any money changing hands between the companies?

For the past few years both the Panasonic and Sony corporations have been bleeding financially. That’s one reason Panasonic spun off JVC and I think Sony has spun off some of their company too. In contrast, Apple keeps making a profit and has a huge pile of cash. A camcorder that can export easily to FCP X will obviously benefit from increased sales. Could there be some corporate gamesmanship going on here? Patent trading?

The plan last summer was to get the X70 when it came out but it wasn’t FCP X friendly. A Sony rep told me they should hopefully have something by fall (2014) so I waited. Thanks to all of Paul Anderegg’s testing and posts on the X70, not to mention the hype on 4K and my waiting, there are now more cam choices available. More decisions. While ClipWrap has been working good at re-wrapping, the next cam(s) will be FCP X friendly (among other requirements) or I won’t buy it (them).

We use EditReady to transcode AVCHD and XAVC-L directly to ProRes 422 in our workflow. EditReady : Transcoding Without The Hassle - divergent media (http://www.divergentmedia.com/editready)

We prefer preparing, transcoding and renaming the ProRes files BEORE importing into FCPX.

I just submitted a support question to divergent media. I'm seeing a glitch in the transcoded time code track. Other differences exist too.

My test: XAVC-L 50 Mbps clip shot with Sony's PXW-X70. Transcoded to ProRes 422 in Catalyst Browse, Catalyst Prepare (trial) and EditReady (trial).

I then used QuickTime Player 7 to inspect the tracks. Browse and Prepare both produced files with 10 total tracks: 1 video, 8 sound, and 1 timecode. EditReady produced a file with 6 total tracks: 4 sound, 1 video and 1 timecode. And EditReady's timecode track is displaying garbled characters in the 'TimeCode Start' and 'TimeCode Stop' column of the Properties window. And the garbled characters rapidly change over time. That tells me the software (QTP 7) is attempting to read data about the timecode track and not succeeding.

All footage plays back a-ok in Final Cut Pro X, QuickTime Player and QuickTime Player 7. Still, I haven't used any features that would rely upon the timecode track. So possible something may break down if using the EditReady files.


UPDATE: divergent's support is fast! They haven't heard about this issue, but it may be an edge case involving just QT Player 7. So probably not worth any fix. I was only using that player to inspect transcoded files; it won't be used in any of my workflows.

FYI: FCP X version 10.2.1 still doesn't fix the issue. I've updated my bug (still open by Apple) with these new findings.

Yep, that's the first thing I tried also - still doesn't work. In fact, even clicking on the X70 volume in the import window crashes FCPX.

I read yesterday someone promoting the use of an Odyssey, etc. 4K recorder in conjunction with the 4K upgrade - but isn't that making an assumption that the upgrade will provide 4K @ 4:2:2 out thru the hdmi port? We don't really have confirmation of that do we? Not to mention that I'm not sure what I think about the idea of adding $500 for the 4K plus $2000 for a recorder to use with a $2000 camera.

Lastly, I also read that the actual date the 4K will be available - still @ $500 US - will be June 15. Again, rumor or fact?

I for one will not be upgrading at all to 4K. While I cannot prove the following, my assumption is that the in-camera downscaled HD footage will be better than capturing 4K and downscaling in post. Here's why I think this:

* 4K footage will be captured at 8-bit 4:2:0. And David, no clue if that will be 8-bit 4:2:2 out of the HDMI port.

* 4K footage only captured at 60 Mbps. While there is less chroma being captured and 8-bit vs. 10-bit, I still think the low bit rate will result in higher compression being applied.

* Sony has no details on the layout pattern used (e.g. bayer) to capture 4K. But as it's not an 8K sensor in a bayer pattern, I don't believe it can record 4K worth of red, green and blue. Whereas from what I can tell, HD footage benefits tremendously from truly having 2K worth of red, green and blue (with probably an extra 2K of green to help with luma calculations). Thus, more interpolation going on for the 4K footage.

In summary, I believe recording in 4K and then downconverting to HD would suffer from more interpolation, higher compression and less bit depth. And if doing in-camera, worse chroma subsampling.

One thing I have on my radar is blackmagic's video assist (coming out hopefully in July). A pretty lightweight unit that allows recording 1080p to ProRes on U3 SDXC cards. Since I'm already transcoding XAVC-L to ProRes 422 (via EditReady), I may as well get a first-generation ProRes recording right off the cam.

Article regarding the Sony x70 4k upgrade. I hope it's OK posting here as they don't have a competing forum.

Pro Video Coalition - PXW-X70 users will want a Shogun or PIX-E5 even more after the 4K upgrade by Allan Tépper (http://www.provideocoalition.com/pxw-x70-users-will-want-a-shogun-or-pix-e5-even-more-after-the-4k-upgrade)

Craig - yes, that's the article that I was referring to. Ricky and I seem to disagree with some of his opinions :-)

Ricky - a good assessment. I think 4:2:2 out of the hdmi @ 4K is probably just wishful thinking. I've also been looking at the BM Video Assist, especially since it records HD @ 60fps, which not all recorders will do. I do wish it had a waveform rather than just a histogram, but depending on the kinds of things you shoot, you could make a good case that the Video Assist might be a better place to invest $500 rather than the 4K upgrade. The one 4K clip that's been posted looked pretty great, but glaringly did not include much camera or subject movement.

The X70 is an amazing camera for $2K. For me, the only real drawbacks are:

1. the rather average stabilization
Compared to my previous Canon XF100 I'm having to use tripod/post stabilization/Active Stabilization far more.

2. random minor things
There is no waveform, no 120fps, and of course I'd like even shallower DOF than the 1" sensor @ 2.8 can provide.

3. the most major thing for me? - highlight handling
I find highlights have to be treated very carefully, and attempting to control them (more than just minimally) using the available Knee settings makes it even worse. I'd love a true flat "log" PP.

I was considering renting an AX100 for a dance recital's lock down wide shot, hoping I could crop/zoom for "close" shots as a backup for the primary camera (I am delivering on DVD). The comments here are scaring me off, especially since I'm still editing in Final Cut 7. However I did find a transcoding product from Acrok that claims to be able to convert to ProRes (422 and 4444) that can be used by either FCX or FC7.

I was only able to find a single reference to this product on DVINFO, but it's 2 years old and doesn't discuss if it works.

Has anyone on this thread seen/heard/tried Acrok? Seems cheap enough at $39.

Thanks.

Why not just go with EditReady - great company, great support, $49
Same company that did ClipWrap for years.

EditReady : Transcoding Without The Hassle - divergent media (http://www.divergentmedia.com/editready)

Why not just go with EditReady - great company, great support, $49
Same company that did ClipWrap for years.

EditReady : Transcoding Without The Hassle - divergent media (http://www.divergentmedia.com/editready)

I have been using EditReady as my workaround of choice as well. My second bug filed with Apple is still open. Sony hasn't budged either on their Catalyst Browse issues.

The one thing I'm missing about Catalyst Prepare (I used the trial a while back) is that it transcodes clips measurably faster than EditReady. At least on my 12-core Mac Pro. Not a huge deal though for me. Definitely worth the savings of $150.

But if one would be dealing with tons of footage, the higher price of Prepare may get offset by time savings.

We have a report that the V2 firmware has fixed the FCPX issue!!! Anyone test this yet. Im gonna try to mess around tonight if I have time! FINALLY!!!

Yes! Works flawlessly, and the native clips are very fluid to edit. So, was there some glitch in Sony's implementation of XAVC-L in the X70? This final fix came from Sony, not Apple...

For the record, this is the (free) 2.0 firmware update. It only adds a few features, but is required in order to do the (paid) 4K upgrade supposedly coming in mid-June. I got it from the UK Sony site, but worked fine. The update claims to require the original USB cable that came with the camera. I don't know if that's really necessary, but I used it just in case. The update took about 5 minutes, but does a full factory reset, including all Picture Profile and custom button assignment changes you've made.

http://www.sony.co.uk/pro/support/software/SET_150526_PSG

The import window shows in the PRIVATE folder a Clip file, an audio file, and a thumbnail for each clip. I just imported the main Clip file and the audio was included. Unlike ProRes, you *can* set In/Out points to avoid importing the whole clip. You also have the option to select Optimize in the Import window and FCPX will transcode (in the background) to ProRes.

However, previous clips recorded using the old firmware still will not import, and FCPX crashes if you try. So, a change was made in the way the codec is recorded and/or stored.

Hmm... multiple recording formats don't work?

I did a quick test after updating to firmware 2.0. First, completely initialized my two SD cards (SDXC U3, 128 GB) Recorded a total of 5 clips with simultaneous recording. All were XAVC-L 50 Mbps. First clip at 30p, next two at 24p and last two at 60p.

In FCP X's import window, only the first clip contains both video and audio. The remaining clips only provide me audio and thumbnails.

Dragging the five .MXF files to my hard-drive results in FCP X only being able to import audio from those files. So there's definitely a requirement to only import media from Sony's file/folder structure.

Later today will re-initialize the cards and only record one format. Perhaps one cannot mix 24p, 30p, 60p on the same card? That would really be messed up.

Well this stinks. Did a second test. Reformatted both SD cards. Recorded three separate clips in XAVC-L 50 Mbps at 60p.

Only the first clip can be imported directly into FCP X. Latter two show audio and thumbnail data only.

Will update my bug report with Apple with this new information.

Anyone else experiencing this issue where only the first clip works?


Back to EditReady for me... thankfully, it can directly work with the .MXF files (doesn't need to be in Sony's folder structure). Transcoded these new firmware 2.0 recorded clips a-ok.

FWIW, my workflow...

Copy the individual .MXF files to my hard-drive (I am opting to not copy the entire folder structure). These files are part of my backups.

Transcode to ProRes 422 with EditReady. These files are on my "scratch" drive and not backed up.

In FCP X, I import the ProRes clips while leaving them in place (no copy made since this is the transcoded material). And of course, no optimized media created since I have ProRes already as my "original source".

Ricky - I'm not seeing that. I just recorded three clips, and all three show up in the import window. If I just choose the top three clips with the movie icon they come in flawlessly with audio.

Ricky - I'm not seeing that. I just recorded three clips, and all three show up in the import window. If I just choose the top three clips with the movie icon they come in flawlessly with audio.

Glad it's working for you, David. I'll have to continue troubleshooting to see why it's messed up on my end. Here are some extra details; perhaps something is different in our setups:

* OS X 10.10.3
* FCP X 10.2.1 with the most recent Pro Video formats update
* At one point, I had the Sony Plug-in installed, but had completely uninstalled it a while back (since it didn't work anyhow, and the more recent FCP X updates claimed it was no longer needed).

Ricky, not sure what's going on. I also have the latest OS and FCPX and the memory card was reformatted in the firmware-updated camera. I shot @ 1080p60 on all three clips, XAVC of course.

I'm curious - your screen shot shows the XDROOT folder inside the PRIVATE folder. Mine is exactly as shown - FCPX does not see the XDROOT but just the PRIVATE folder and a "private" folder. This may be a clue to the difference but darned if I know what to make of that.

I get the same as you David. Any idea why the audio track repeats? It comes through on the main track so why is it repeated? Mac OS, FCPX 10.2 only but working fine

TL;DR : It appears the name of the SD card volume is causing the issue. My SD cards are named 'Untitled' and 'Untitled 1'. Going to see how I can change that. Full details below.


The mystery continues...

Yesterday I re-installed the Sony plugin (PDZK-LT2_1.2.1.dmg). No change.

This morning, I made a copy of my SDXC card to my Mac (copied the entire PRIVATE folder structure).

I then attempted again to import from the card of the connected cam. But I no longer see the nested XDROOT folder in FCP X's import window (see first screenshot). But only the first clip contains video and audio. So basically the same issue as yesterday's tests. FCP X along with the Sony plugin must be doing something magical to create a logical folder structure. What I mean by that is that the real file structure does have an XDROOT inside PRIVATE. There are then XML files that describe where the clips and thumbnails are.

But here's where it gets really interesting...

If I import from my local copy on the Mac hard drive, it works! See second screenshot. I can switch between the two sources and see the problem come and go. So I may need to first copy the card's contents to my Mac (no big deal there; I want the original footage and will back that up anyhow).


By the way, If I attempt to import from the second SDXC card (named 'Untitled 1'), same issue as with the primary card ('Untitled').

Additional tests...

Copied the PRIVATE folder to the root of an empty drive partition named 'Empty'. Import works.

Renamed 'Empty' drive partition to 'Untitled'. Issue returned! Only first clip shows up correctly.

Renamed 'Untitled' back to 'Empty' and import works again!


So for others here... what is the name of the volumes that are mounted on your Mac that represents your SD cards? Are they 'Untitled' and 'Untitled 1'? I suppose if I name those cards somehow, this problem will go away?

Very baffling that the name of the volume is preventing FCP X from doing the right thing.


Later today I will completely uninstall the Sony plugin, reboot, etc. and repeat these tests. Want to see if that plugin has anything to do with this strangeness.

Yesterday though (prior to reinstalling the Sony plugin), attempting to import from the mounted 'Untitled' volume still had the issue. Although as seen in my earlier post screenshots, FCP X decided to display the XDROOT nested folder in the import window.

For what it's worth, I do not have the Sony plugin installed - I don't know if it causes problems but is definitely not needed.

I've only tried importing from the camera card placed into a card reader, not from the hard drive.

The volume of the card shows up as Untitled.

So it does not have to be on a hard drive, and being named Untitled is not the issue. I'm betting it's that Sony plugin.

Hope this helps.

No luck. As I mentioned, I had the issue before re-installing the Sony Plugin. I've since unisntalled that plugin again, and the problem remains.

Interestinly, when I renamed my hard-drive partition back to 'Untitled', it now works there. So the Sony plugin seemed to alter a bit how that hard-drive partition was treated.

Thanks for confirming that your cards are mounting as 'Untitled'. So the name of the volume itself isn't the issue.

The only difference I do see in the cards vs. hard drive is that the cards are mounted as Read-Only. Perhaps when creating the logical structure, FCP X attempts to write a file to that volume? The mds process appears to want to do something with that volume. Although that's just the metadata service for the sake of creating data for Spotlight. I don't see anything in Console regarding issues with the 'Untitled' volumes outside of that.

If you do a Get Info on your Mac on the 'Untitled' SD card volumes, does it say 'You can only read' under the 'Sharing & Permissions:' section?

I've only tried importing from the camera card placed into a card reader, not from the hard drive.

Didn't catch this at first. I've been trying to import directly from the cam itself (connected to my Mac via its supplied USB cable). I do not have an SD card reader.