Why the duplicated clip when importing from Panasonic AG-AC160AP?

Well, Adobe Prelude shows the clips as "Clip #12" and "Clip #14" with no "Clip #13" but is able to import the 2 clips correctly. However, it creates an AVCHD wrapper file. Premier is able to read this file but FCPX is not.

I'm not really sure what's causing the problem. The only way this would be fixed is if Apple know about it. Have you contacted Apple to let them know? That would be great if any of you guys having this issue let both Apple and Panasonic about the issue. At least use the Feedback link in FCPX so this gets documented. I really don't want to have to use a re-wrapper to get these files into FCPX correctly.

It is very annoying.

Any one got the solutions yet?

Problem still remained in 11 July 2015 build.

I guess none of FCPX team member care Panasonic users!?

I recently experienced the identical issues that you experienced in your original post on this issue--in every detail. Did you ever get a workable solution to this problem? --thanks

I had this problem again with FCPX importing Panasonic AGAP160AP AVCHD file. It was a 48 min clip of a live performance so NOT GOOD! Before shooting the performance I reformatted both cards on the AGAP160AP and they showed Simultaneous Recording possible. It was the last clip out of the 4 that had the problem. FCPX had the same problem with both cards. On FCPX import screen all 4 clips showed up but clip 3 & 4 appeared to be the same clip. I know they were not. I tried importing all and it ignored the 4th clip. I found a panasonic utility called AVCCAM Restorer, https://eww.pass.panasonic.co.jp/pro-av/support/dload/avccam_restorer/dl_e.htm. It appeared to run fine on El Capitan. It said it found an error and fixed it. However, FCPX still could not read clip 4. I Also tried creating an archive of the SD card in FCPX and open the clip from that. Same problem with Clip 4. I noticed Photos, seemed to recognize the clip and used Photos to import the clip then imported that into FCPX. I did not notice any lose in file size. However, the codec shows a little different from the other 3 clips I imported, AAC vs PCM. But whatever, that should not be a problem. At least I did not loose the 45 minute clip from a Multicam shoot. Not sure, but I think using Photos is cleaner than converting the file using QT.

On a side note, why does Apple name the new photos program Photos. This is completely confusing when describing the app. It's like naming a new car "Car". At least with the "i" it was obvious what one was talking about.

So long story short: Photos was able to import the clip. I'm going to call apple and show them this tomorrow.

On a side note, why does Apple name the new photos program Photos. This is completely confusing when describing the app. It's like naming a new car "Car". At least with the "i" it was obvious what one was talking about.

I suppose that's for the same reason they call their mail application Mail, or their calendar application Calendar.

For me, it makes total sense. They might as well rethink the whole iTunes mess and call it "Music"... 😝

Then they should call Logic "Music" and FCPX "Video".

🙂

TThose are not included apps. Besides isn't iTunes going to be Music?

Well, after editing my video in FCPX I realized I was getting a pulsing in the motion for the clip I used Photos to import, as if frame rates didn't match my timeline even though FCPX showed the frame rate for the clip to match the project, 23.98P. So then I reverted to using Quicktime to read and convert the clip of the SD card. It resulted in a file half the size, 3 GB vs 7 GB and the pulsing still persisted in FCPX again as if the frame rate did not match my project even though FCPX again showed the clip to be 23.98P. The weird thing is, if I used Preview to play the clips from finder the play smooth.

I finally got this clip into FCPX by using Adobe Prelude. It created an AVCHD file FCPX was able to read and import the clip. File size was correct, frame rate was correct and pulsing in motion was gone, the clip played smooth. Finally. Yay!

I'm not so sure this isn't something in the Panasonic camera causing this. Adobe Prelude also showed an anomaly in the clip numbering. It went 0000,0001,0002,0004. However, Prelude seemed more forgiving and was able to complete the task.

WDI what version of FCPX are you using?

10.3.2