Return-Path: Received: from nk11p00mm-asmtp001.mac.com ([17.158.161.0] verified) by media-motion.tv (CommuniGate Pro SMTP 4.2.10) with ESMTP id 5414209 for AE-List@media-motion.tv; Sat, 22 Mar 2014 17:00:27 +0100 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_PdV7efsnzZmUdxueD4iSFw)" Received: from [192.168.1.68] (99-152-153-100.lightspeed.dllstx.sbcglobal.net [99.152.153.100]) by nk11p00mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N2U0043BHUGBD50@nk11p00mm-asmtp001.mac.com> for AE-List@media-motion.tv; Sat, 22 Mar 2014 16:01:30 +0000 (GMT) From: Jim Curtis Message-id: <2A857E63-204A-45BF-A759-E3BC47BC57A6@me.com> Subject: Re: [AE] Adobe Premier Importing Problem Date: Sat, 22 Mar 2014 11:01:28 -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-22_01:2014-03-21,2014-03-22,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=2 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1403220092 --Boundary_(ID_PdV7efsnzZmUdxueD4iSFw) Content-type: text/plain; charset=windows-1252 Content-transfer-encoding: quoted-printable I'm on Mac. Prior to CC, my experience was that Pr was prone to corrupt = its prefs and its own render files. My bane was the "Serious Error," = not the one you reported. I had a scatter gun approach to getting back to work that included = refreshing the prefs, deleting renders and caches. That worked for a = while, until the problems started recurring. But, then it was repeat = the same procedure at every crash. I also probably reinstalled the app 20 times. And to make things even = more fun, Pr has an outright allergy to corrupt footage items. CS6 was = a big improvement over 5.5, and the CC version has been nearly = trouble-free by comparison. And to be complete, I've also had hiccups that reinstalls of the GPU, = CUDA and io card (AJA) drivers cleared up. Another troubleshooting tip is to create a new project and try to import = the same footage. If it imports OK, you may have a corrupt project. If = it doesn't, the footage or codec may be the culprit. On Mar 22, 2014, at 10:46 AM, "Mr. Eric D. Kirk" = wrote: > Thanks Casey, >=20 > I realize everyone likes to get tons of info, was just looking to see = if anyone has experienced this type of sudden change. The reason I = didn't include all the codec info, etc is because it's been business as = usual, then suddenly it stops importing correctly which is why I doubt = it is any format or codec issue. >=20 > However - I'm using premiere pro version 6.0.5 and updated yesterday = after experiencing issues but no change. I work on a PC, Windows 8.1. = My routine has been pretty simple. I've been working in AE 6, = outputting files to DNxHD, importing in to premiere and normally no = problem. It may also import a file that didn't work on a second try or = after restarting premiere. >=20 > In my mind, clearly a premiere issue. I did also do some conversions = to ProRes using CINEC, also a standard procedure and it's had same = symptoms with both before and after. >=20 > Eric >=20 >=20 >=20 >=20 > On Sat, Mar 22, 2014 at 11:12 AM, Carey Dissmore = wrote: > Premiere version? / Patch level? > Media type?=20 > Container?=20 > Codec? > Are these camera card dumps with all card data intact? >=20 > Also=85 > Mac or PC? > OS level? > OS patch level? > Graphics card and driver level? >=20 > Also=85 > Storage device type? > Connectivity/format/bus type? >=20 > This could be caused by many many things, need more info to try to = track it down. > This could require testing a lot of angles before finding the fix, but = the general order I posted above it probably the order I would = investigate in. > Based on what I know now. >=20 >=20 > carey >=20 >=20 > On Mar 22, 2014, at 9:45 AM, Mr. Eric D. Kirk = wrote: >=20 >> Hello, >>=20 >> Not sure why but in the past couple days, Adobe Premier Pro suddenly = started having import problems, the error being "importer reported a = generic error". It's not all files either but while importing a series = of files, all of the same format and used previously, it will import a = portion and then randomly leave others with that error. All of the = files play and open fine outside as well as in AE. It's definitely not = a format issue. >>=20 >> Coincidentally, when they do import right, it's hit and miss on = whether the video shows in the preview screen. So, it might show but = then it won't play, just locked on a still image. >>=20 >> In short, Premiere Pro is horrendous at the moment serving me no = purpose. >>=20 >> Ideas? >>=20 >> Thanks, >>=20 >> Eric >>=20 >> --=20 >> Eric D. Kirk | Kirk Productions >> Hidden in the Woods | VFX >> The Night Visitor | VFX >> 443.206.1347 >> www.kirkproductions.com >> kirkproductions@gmail.com >> IMDB: http://www.imdb.com/name/nm3351363/ >> =20 >=20 >=20 >=20 >=20 > --=20 > Eric D. Kirk | Kirk Productions > Hidden in the Woods | VFX > The Night Visitor | VFX > 443.206.1347 > www.kirkproductions.com > kirkproductions@gmail.com > IMDB: http://www.imdb.com/name/nm3351363/ > =20 --Boundary_(ID_PdV7efsnzZmUdxueD4iSFw) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: quoted-printable I'm = on Mac.  Prior to CC, my experience was that Pr was prone to = corrupt its prefs and its own render files.  My bane was the = "Serious Error," not the one you reported.

I had a = scatter gun approach to getting back to work that included refreshing = the prefs, deleting renders and caches.  That worked for a while, = until the problems started recurring.  But, then it was repeat the = same procedure at every crash.

I also probably = reinstalled the app 20 times.  And to make things even more fun, Pr = has an outright allergy to corrupt footage items.  CS6 was a big = improvement over 5.5, and the CC version has been nearly trouble-free by = comparison.

And to be complete, I've also had = hiccups that reinstalls of the GPU, CUDA and io card (AJA) drivers = cleared up.

Another troubleshooting tip is to = create a new project and try to import the same footage.  If it = imports OK, you may have a corrupt project.  If it doesn't, the = footage or codec may be the = culprit.




=
On Mar 22, 2014, at 10:46 AM, "Mr. Eric D. Kirk" <kirkproductions@gmail.com>= ; wrote:

Thanks Casey,

I = realize everyone likes to get tons of info, was just looking to see if = anyone has experienced this type of sudden change.  The reason I = didn't include all the codec info, etc is because it's been business as = usual, then suddenly it stops importing correctly which is why I doubt = it is any format or codec issue.

However - I'm using premiere pro version 6.0.5 and = updated yesterday after experiencing issues but no change.  I work = on a PC, Windows 8.1.  My routine has been pretty simple. =  I've been working in AE 6, outputting files to DNxHD, importing in = to premiere and normally no problem.  It may also import a file = that didn't work on a second try or after restarting premiere.

In my mind, clearly a premiere issue.  I did = also do some conversions to ProRes using CINEC, also a standard = procedure and it's had same symptoms with both before and = after.

Eric




On Sat, Mar 22, = 2014 at 11:12 AM, Carey Dissmore <carey@imugonline.com> wrote:
Premiere version? / Patch = level?
Media = type? 
Container? 
Codec?
Are these camera card dumps with all card data = intact?

Also=85
Mac or = PC?
OS level?
OS patch level?
Graphics = card and driver level?

Also=85
Storage device type?
Connectivity/format/bus = type?

This could be caused by many many things, = need more info to try to track it down.
This could require = testing a lot of angles before finding the fix, but the general order I = posted above it probably the order I would investigate in.
Based on what I know = now.


carey


On Mar 22, 2014, at 9:45 AM, Mr. Eric D. Kirk <kirkproductions@gmail.com> wrote:

Hello,

Not sure why but in the past = couple days, Adobe Premier Pro suddenly started having import problems, = the error being "importer reported a generic error".  It's not all = files either but while importing a series of files, all of the same = format and used previously, it will import a portion and then randomly = leave others with that error.  All of the files play and open fine = outside as well as in AE.  It's definitely not a format = issue.

Coincidentally, when they do import right, it's hit = and miss on whether the video shows in the preview screen.  So, it = might show but then it won't play, just locked on a still = image.

In short, Premiere Pro is horrendous at the moment = serving me no = purpose.

Ideas?

Thanks,<= /div>

Eric

--
Eric D. Kirk | Kirk = Productions
Hidden in the Woods | = VFX
The Night Visitor | = VFX
 




--
Eric D. = Kirk | Kirk Productions
Hidden in the Woods = | VFX
The Night Visitor | = VFX
443.206.1347
 

= --Boundary_(ID_PdV7efsnzZmUdxueD4iSFw)--