Return-Path: Received: from nk11p00mm-asmtp005.mac.com ([17.158.161.4] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5416372 for AE-List@media-motion.tv; Wed, 26 Mar 2014 01:19:29 +0100 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_lww3QHsKV1W/Lsa//fwGHA)" Received: from [192.168.1.68] (99-152-153-100.lightspeed.dllstx.sbcglobal.net [99.152.153.100]) by nk11p00mm-asmtp005.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N3000DFQOYDP430@nk11p00mm-asmtp005.mac.com> for AE-List@media-motion.tv; Wed, 26 Mar 2014 00:20:38 +0000 (GMT) From: Jim Curtis Message-id: Subject: Re: [AE] Cannot import Canon C300 & Sony F5 mxf files directly into Adobe After Effects CS6 11.0.4 and CC 12.2.1 since upgrading to Mavericks Date: Tue, 25 Mar 2014 19:20:36 -0500 References: To: After Effects Mail List In-reply-to: X-Mailer: Apple Mail (2.1510) x-icloud-spam-score: 34444444 f=me.com;e=me.com;is=no;ir=yes;pp=ham;spf=n/a;dkim=n/a;dmarc=n/a;wl=n/a;pwl=n/a;clxs=n/a;clxl=n/a X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87,1.0.14,0.0.0000 definitions=2014-03-25_07:2014-03-25,2014-03-25,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1403250144 --Boundary_(ID_lww3QHsKV1W/Lsa//fwGHA) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable I know. And also for using the Browser only as a method for importing = from a camera card. When I've done this, I dragged the MXF files from = the Finder, and they import fine. I thought this could be a camera glitch at first. But, the second job I = got from the same camera guy was a two-camera shoot, and I had the same = problems with both his cameras. And the same solution got me back to = work editing. What was happening is that before I learned this workaround, all my = clips would import through the Media Browser. So, I'd have say 20 = clips. I'd select them all, and use the Make Sequence from Selections = command. I'd get a new Sequence with 20 clips in it, with 20 different = clip names, but they all played the media from the first clip! On Mar 25, 2014, at 7:02 PM, Carey Dissmore = wrote: > Wow, if true that really flies in the face of =93Keep camera card = structures intact=94 conventional wisdom. >=20 > carey >=20 > On Mar 25, 2014, at 6:32 PM, Jim Curtis wrote: >=20 >> I've had some issues in Pr with MXF. This may or may not help. = Probably won't, but nobody else has offered anything so far. >>=20 >> I discovered that the files other than MXF in the camera card = structure were causing problems. I fixed it by separating the MXF from = the other files, and then import the MXF into Pr. Then they'd play and = work fine. >>=20 >> Might be worth an experiment on your system. >>=20 >>=20 >>=20 >> On Mar 25, 2014, at 12:28 PM, Bruce Lambert = wrote: >>=20 >>> Had a machine working perfectly fine importing Sony and Canon mxf = files into projects running both Adobe After Effects CS6 11.0.4 and = Creative Cloud 12.2.1 on Mac System 10.8.4. Upgraded to Mavericks = 10.9.2 and now I get error messages that the files are corrupt or = unreadable from After Effects. Nothing changed except the operating = system. =20 >>> =20 >>> If I take those same files that my Mavericks system says is corrupt = and import them onto another one of my machines running 10.8.4 they = import into After Effects just as before.=20 >>>=20 >>> Just a note: My mxf files from our Panasonic 370 import just fine = using either system. Anyone have any ideas or experienced this?=20 >>=20 >=20 --Boundary_(ID_lww3QHsKV1W/Lsa//fwGHA) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable I = know.  And also for using the Browser only as a method for = importing from a camera card.  When I've done this, I dragged the = MXF files from the Finder, and they import fine.

I = thought this could be a camera glitch at first.  But, the second = job I got from the same camera guy was a two-camera shoot, and I had the = same problems with both his cameras.  And the same solution got me = back to work editing.

What was happening is that = before I learned this workaround, all my clips would import through the = Media Browser.  So, I'd have say 20 clips.  I'd select them = all, and use the Make Sequence from Selections command.  I'd get a = new Sequence with 20 clips in it, with 20 different clip names, but they = all played the media from the first = clip!




On Mar 25, 2014, at 7:02 PM, Carey Dissmore <carey@imugonline.com> = wrote:

Wow, = if true that really flies in the face of =93Keep camera card structures = intact=94 conventional = wisdom.

carey

On Mar 25, = 2014, at 6:32 PM, Jim Curtis <jpcurtis@me.com> wrote:

I've = had some issues in Pr with MXF.  This may or may not help. =  Probably won't, but nobody else has offered anything so = far.

I discovered that the files other than MXF in = the camera card structure were causing problems.  I fixed it by = separating the MXF from the other files, and then import the MXF into = Pr.  Then they'd play and work fine.

Might = be worth an experiment on your = system.



On Mar 25, = 2014, at 12:28 PM, Bruce Lambert <bruce.e.lambert@gmail.com>= ; wrote:

Had a machine working perfectly fine importing Sony and Canon mxf files = into projects running both Adobe After Effects CS6 11.0.4  and = Creative Cloud 12.2.1 on Mac System 10.8.4.  Upgraded to Mavericks = 10.9.2 and now I get error messages that the files are corrupt or = unreadable from After Effects.  Nothing changed except the = operating system.  
 
If I take those same files that my Mavericks system says is corrupt and = import them onto another one of my machines running 10.8.4 they import = into After Effects just as before. 

Just a note:  My mxf files from our Panasonic 370 import just fine = using either system.  Anyone have any ideas or experienced = this? 
=



= --Boundary_(ID_lww3QHsKV1W/Lsa//fwGHA)--