[..\..\Src\pp\\PPixHandleUtilities.cpp-114] Dropped Frame CS3 Rendering Error

So, I recorded a small film (~15 minutes) on a Kodak Zi8 camcorder. I loaded it all into Premiere Pro CS3 fine, and I have it all in the timeline just fine... except I can't export it.
The Zi8 recorded in 720p H.264 mode, and when I try to export the whole timeline, the computer gives me the [..\..\Src\pp\\PPixHandleUtilities.cpp-114] error, then says a frame was dropped. I thought the length of the clips was the problem, so I broke them up into 3/4 minute chunks. Still same problem. It'll stop whenever - not always at the same spot, give the error, then stop rendering. I'm trying to export it as a Quicktime H.264 HD video.
I have a Dell Inspiron 530s running Windows 7 Professional, Core 2 Duo 2.53Ghz, 3GB RAM, 320GB HDD, ATI Radeon HD 3450 video card.
So far, I tried making the video into 3-4 minute clips, but that didn't help. I also tried dropping a transparent video layer on top of the whole thing (in case it had something to do with a dropped frame) but it still gave me the error. I also changed the rendering mode to "Memory" instead of "Processor" but to no avail...
I'm stuck. Part of me thinks it's just because I don't have enough memory to render, but I close out of every other program while I'm rendering. Plus, this is a relatively new computer. I purchased it back in November of 2008, and it has a dedicated video card.
Any suggestions? This video is for a class project and it's due in a couple weeks!
Thanks in advance guys,
Christian

I am nearing my last strands of sanity. This project has been due two days ago has been giving me fits with the same error message. My system wotks on AMD Athlon, 64 X2 Dual Core, 3 GHz with 8 GB RAM. Working with Premiere Pro CS3. I have an external 1TB drive with 200gb of available space. This is my first foray into the world of DSLR. I am editing with a combination of my regular Mpeg files from my Sony ZIU and MVI files from a Canon 5D DSLR. Editing the project was painstaking slow because I had to render all the MVI files even before I could use them. The error message [..\..\Src\PPixHandleUtilities.cpp-114] came up quite often but clicking on okay made it go away without closing my project. Come encoding time to Encore it will stop at the 43.3% mark. Have tried transcoding to a DVtape, no luck. Tried encoding to Mpeg2, uh uh. Always stopped at the 43.3% mark. One blogger here had posted that gaps on the video track might cause this.......I have been editing on Premiere for 10 years and that is the 1st time I have ever heard of that. I have always placed gaps on my video track and this particulare project is no exception and have never experienced this. I tried converting the MVI files to Mpeg but could not find a converter that would retain the same file size of the original files. Suffice it to say that my level of frustration is on red. Did you solve your issues? Any idea on how to fix mine? Guys? Anyone? Anything?

Similar Messages

[..\..\Src\pp\\PPixHandleUtilities.cpp-114] Error

Im sorry if this is the wrong place to post this but I dont know what else to do. When i use AME or Export as Movie Im getting the ugly [..\..\Src\pp\\PPixHandleUtilities.cpp-114] error! Afterwards i get an unable to compile error. i have scoured the internet looking for answers. I have tried a few of the solutions but nothing seems to work. I have a project for my college class im working on and i need to figure this out. To start over would be a hefty process that does not sound like something i want to do. Any advice on what i can do or where i should to look for answers would be great! Thanks!
So far i have tried zooming all the way in on my tracks and looking for blank spots, i have tried adding a transparent video on the top layer spanning the entire sequence, i have tried uninstalling and reinstalling, importing my project into another project, using different project setting, different export settings, and so far nothing has seemed to work.
I know its ancient but im running CS3 and my machine is running AMD Quad-Core Processor with 8GB ram.

Some general reading... and then some questions
Run as Administrator http://forums.adobe.com/thread/771202
-Set to always "run as" via icon http://forums.adobe.com/thread/969395
Odd Errors http://forums.adobe.com/thread/670174
Long File Names or odd characters cause problems
Read http://forums.adobe.com/thread/588273
And #4 http://forums.adobe.com/thread/666558
And This Message Thread http://forums.adobe.com/thread/665641
Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037
What is a CODEC... a Primer http://forums.adobe.com/thread/546811
What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037
Report back with the codec details of your file, use the programs below... a screen
shot works well to SHOW people what you are doing
For PC http://www.headbands.com/gspot/ or http://mediainfo.sourceforge.net/en
For Mac http://mediainspector.massanti.com/
http://blogs.adobe.com/premiereprotraining/2011/02/red-yellow-and-green-render-
bars.html
If you have a red line over the timeline after importing a video and before adding any
effects... your project is wrong for your video... read above about codecs
Once you know exactly what it is you are editing, report back with that information...
and your project setting, and if there is a red line above the video in the timeline,
which indicates a mismatch between video and project

[..\..\Src\pp\\PPixHandleUtilities.cpp-114] error-please help

Hi
I am new to Premiere and video editing and trying to render a sequence that I need to return tomorrow as a project.
My sequence concists of a few WMV clips that have been cut(some are in fast motion), some JPEG pics, and a .wav song.
In the process of rendering I get the error :[..\..\Src\pp\\PPixHandleUtilities.cpp-114]
Rendering stops.
I also get the same error when playing individual WMV videos(It comes at the end),but not when all the videos are assembled together?!
I hope someone could somehow help me get through this....
Thanks
Dani

FAQ: How do I import xyz format files?
FAQ:How do I automatically scale clips to the Project Size?
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

CS3 PPixHandleUtilities.cpp-114 error

I am running Windows Vista 32 bit and Adobe Premiere Pro CS3. I have been working in HD video for over 6 months now and haven't had any troubles exporting footage from Canon T2i or T3i.
However, now when I export it will render out about 30-45% and display an error "Src/PPixHandleUtilities.cpp-114"
Sometimes it will say a video frame failed to generate content, and I go to that frame and change the footage, etc, and then it will give me a different frame that is the issue, so I don't think it's a problem with my video, but instead sometime corrupt in my Premiere. Sometimes it says that Adobe's memory is low, but it has around 1.3 TB of storage, though I can't change the main media scratch discs, but there is still enough room where they currently are.
I have searched Google and other forums and tried everything they suggested. Two things I am unable to try are to put a transparent video on the top video layer above the entire project (the clip drop down menu is all grayed out all of a sudden), and another was to take a file from the Encore CS3 and copy it into Premiere, but I have Premiere CS3, and the rest of the suite is the older version, CS2 or 2.0.
I called Adobe and they told me to upgrade to the newest version of the software. I am working on building a new computer and with that I will be upgrading all of my software, however until I can save up the money and get all the components I am stuck with what I have.
It is important to me to resolve this as quickly as possible, and I will provide any further information required to try and get to the bottom of this issue. Thank you

Welcome to the forum.
I am not familiar with that particular error message, but with "Failure to Return Frame," or similar syntax, it is caused by there being a gap in the Video Stream. That might be a tiny, one-Frame gap, or a larger one.
I would check the Timeline very carefully (zooming in horizontally to the max), and especially about the point, that the Transcode is failing, but remember, that might just be the first problem, and there could be more lurking down the Timeline.
If you need a gap between Clips in the Timeline, create some synthetic Black Video (New Icon in the Project Panel) and fit that into the gap.
Another "trick" is to create Transparent Video, place it on a higher Video Track, and extend that to "cover" all gaps in the lower Video Tracks. Personally, I like Black Video.
Good luck, and hope that it is just a gap in your Video.
Hunt

Debug Event : Premiere Pro has encontered an error. [..\..\Src\PPixhandleUtilities.cpp-114]

Hello,
I have problems in Adobe Premiere CS3, as below:
1. =================================
Debug Event:
Premiere Pro has encontered an error.
[.. \ .. \ Src \ PPixhandleUtilities.cpp-114]
2. =================================
Adobe Premiere Pro is running very low on system memory. Please save
your project and proceed with caution.
================================================== ======
I've tried to reinstall Adobe Premiere of her, but the problem persists.
What should be done to solve this problem which paralyzes all my work?

How to repair projects that get a "TickTime.cpp-290" error after opening a specific project.

Dropped Frames / Odd Rendering

Hello,
As background, I recently completed a project (DVCPRO HD 720p) at a workshop on an iMac. I don't have the specs on the iMac but it's at least a year or two old. I wanted to continue working on this project at home so I have purchased a brand new Macbook Pro 2.0Ghz i7 - 8GB 1333 Mhz DDR3 RAM - AMD Radeon HD 6490M 256 MB. I've installed Final Cut Pro 7.0.3 and I'm using the same GRaid Mini 500GB (Raid 0 - FW800) drive I used in the workshop which is writing at 65MB/sec and reading at 76MB/sec. I'm now getting requests to render clips as well as dropped frames messages where I never did on the iMac. I've spent hours scouring forums (this one, Creative Cow, DV, etc...) and the only suggestion that's made any difference was pumping up the number of real time audio tracks on playback, but most of my problems seem video related. I've turned off the energy saver features, tinkered with render settings, memory, etc..., although I stopped short of modifying the RT Software Enabler file. I'm just not sure what else to try or if I'm even looking in the right place. I have to believe this Macbook should blow the doors off that iMac but maybe I'm wrong. Any help is appreciated.

OK, your problems are:
You are tying to edit with video that is in the H.264 codec.
H.264 is a recording and delivery format, it is not designed for editing, as it is very, very processor intensive.
Your clips are also in a different frame rate than your sequence 29.97 and your sequence is 23.98.
The source clips are a non-standard frame size 540 x 360.
It would be tough going for any computer to play this combination of incorrect item properties back in real time on a timeline that has a 23.98 frame rate and a DVCPRO 720P60 codec.
This is a perfect storm of miss-matched material.
Is your sequence setting because you have camera footage shot in that format? Is the camera material 23.98?
What format material do you have the most of?
What are you intending to do with this once you have completed it (Make DVD, post to web site, make Blu-Ray, etc.) ?
MtD

Black strobe glitch / dropped frames on rendered, exported video

I'm editing a sequence with 30+ clips and multiple layered tracks in Premiere Pro CC 2014. I've added multiple effects through Adjustment Layers, sometimes multiple layers where masked videos + track matte was needed to add further elements. After a fresh render a weird thing started to happen - black 'strobe' starts to appear on the video, like some frames are dropped and it fades in and out to and from black 2-3 times within a second. This is visible after rendering a preview and also if I export.
Here is an example:
adjusment_prob
If I remove all Adjustment layers, everything's back to normal and it renders fine (this is visible in the video).
I've tried removing all third party effects from the timeline and from PP altogether.
I've tried resetting all preferences, now even reinstalling Premiere Pro CC.
The weird thing is after it happens, of I try a completely fresh project and sequence with a clean video and drop an adjusment layer on it the problem appears again! Like my whole system or a codec or something else is corrupted.
I'm struggling with this issue for 2 days now without solutions and it's becoming very frustrating.
Any suggestions?

Wow! Actually I didn't try software only, however your suggestion brought me to the realisation that my Mercury hardware acceleration was set to OpenCL instead of CUDA! I switched it to CUDA and I believe it's all fine now! Thanks!!

Error: AeInData.cpp-712 and VideoSegmentsImpl.cpp-114

This error occurs both when I try to drag a clip with a speed adjustment applied to it and now randomly when I export to Windows Media Video
Premiere Pro Debug Error:
[..\..\Src\AESupport\AEInData.cpp-712]
I'm also getting the below errors,
Premiere Pro Debug Error:
[..\..\Src\AESupport\VideoSegmentsImpl.cpp-114]
Anyone know why these happen?
The dragging clip error and VideoSegmentsImpl error happened prior to installing the CS4 4.0.1 update. Haven't tried it post update. The export error happened post 4.0.1 update.

Yes latest video card drivers.
Captured on a Sony VX1000
There's an opacity change to a freeze frame with a vector graphic. Then 10 frames later is a photoshop file with a title file.
I cleared the media cache and am re-rendering to test. If it's still erroring in the same spot I will remove things one at a time to test. Otherwise I'm told it might be an issue with the original AVI and that I might need to open it in windows movie maker and re-render it.

Drop frame video to non-drop frame clip warning (again)

So my most recent search of why this warning comes up reveals no good answers (unless someone can point me to a thread I overlooked...cuz I can't narrow it down without getting threads about folks who have gotten dropped frames during capture, which isn't the same situation)...
I shoot on an XL2 (drop frame) and capture with a DSR-11. Once in a while I will finish going through log and capture (in the log and capture window), setting ins, outs, etc. but I go to batch capture and it gives me the warning. All my ins/outs have semi-colons, I haven't changed the setting on my camera since I started using it more than 18 months ago, and it doesn't happen all the time. I do have the "abort capture on dropped frames" box unchecked as well (if that matters).
99.99% of the time, I've captured and there's no problems with syncing or anything. Thoughts?
Thanks,
Jonathan

If I recall right someone suggest to have your tape playing while opening Log and Capture, but I might recall wrong
I already have the "Abort on dropped frames" and "report dropped frames" unchecked.
Don't be mistaken: Dropped frames are a totally different issue from non-drop and drop frame timecode.
Drop frame timecode drops (or better: skips) timcodenumbers while counting the videoframes. That is a system to compensate for the 29,97 frames per second in order to calculate the correct length of a clip.
Dropped frames (as in "Abort on dropped frames" and "report dropped frames") is an error. Due to some reason the hardware isn't capable to record/digitize every single videoframe to your harddisk. e.g. Your captured file will have 2000 frames, while your footage on tape had 2003. Three frames were dropped then during capture. And your video will noticeble stutter at these points.
So I'd strongly recommend to do check the "Abort on dropped frames" and "report dropped frames"-options. You don't want stuttering video do you. So if your hardware couldn't handle the videofeed somehow, it would resp. abort capture or warn you that it happened.
Rienk

Dropped Frames -- Releted to Capture?

I was quickly working on a project for old friends, which I have now easily been able to finish to satisfaction, but got some dropped frames warnings during the process, which it did not hurt to ignore. Now I want to analyze why this happened?
I had some previously footage on DV tape that had been copied from VHS, via VCR to camcorder in VTR mode -- no problem with these in FCP, utilizing In/Out timecodes. However I had to quickly review a lot more old VHS tapes, and chose to use my Canopus ADCV 110 to allow for rapid review and selective capture. Furthermore, it seemed much easier to do this in iMovie HD, capture selectively, and then export as QT dv, and import into FCP. All this seemed to work, and I could edit. But exclusive to those clips captured in iMovie and exported, I started to get this warning about dropped frames.
Was this caused by the path of capture/export directly, or did the fact that I exported to the same scratch disk drive as those clips captured directly in FCP matter? Although using my new Mac Pro, I was still using my LaCie FW 800 disk as capture scratch. Is it the lack of timecodes on those assets captured via the Canopus, and should I expect the same issues if I capture via the Canopus, but in FCP? Part of the reason I used iMovie to capture, was I couldn't figure out how to monitor the sound from the VCR, which had no headphone jack, if reviewing via the Canopus and FCP.
I love the Canopus, but have not made extensive use of it in this situation. However, I believe it actually gave better quality than "remastering" to DV tape, first, btw.
Ernie

I have also come to the same conclusion. I've been capturing video just fine and now I get this "dropped frames during capture" error message.
SAME computer
SAME external 7200 rpm drive for capture
SAME fire-wire cable
SAME camcorder
SAME mini-dv tape
I upgraded to OS 10.4.9 and iTunes 7.1.1 a few days ago and only now am I receiving this error message. Does anyone have any suggestions?

"Dropped Frames on Playback" - when playing back FCP's Bars+tone

We've been having a problems with one of our edit suites dropping frames when playing back to tape (Edit to tape).
In checking it out, I created a new project and added DCP's PAL Bars and tone to the default sequence. FCP is stopping playback with the "Dropped Frames on Playback" error after 13"-15". I've tried all the usual stuff - trashing FCP prefs, zapping PRAM, repairing preferences etc.
Has anyone any further suggestions??
RT is set to Safe, with dynamic frame rate and video quality.
The Mac is a Dual 2.66GHz Dual Core Xeon, 4Gb RAM, with an AJA kona lhe card, connected to an XServe Raid via fibre. The tape deck is a DigiBeta M2000.
I've read all the posts I could find, and checked Shane's stock answer #12.
Cheers
Steve

Try creating a new user, log into that and test FCP.
In my case, a new user worked, for awhile.
Through a lot of trial and error and a reinstallation that was ineffectual - properly surmised by a very learned friend of mine, Mr. Sheffield - I found a project to be corrupt. So thoroughly corrupt that it would corrupt FCP and any projects opened downstream which is why my new user worked for awhile. Took me some time to figure out the proper order to open things after a system restart. Looks like I'll be doing a rebuild of the project through xml which shouldn't take to long.
In your case, if a new user doesn't help and you go the reinstallation route, uninstall FC Studio with this jewel of a utility. Many thanks to Jon for writing and distributing. http://www.digitalrebellion.com/blog/posts/fcsremover_1.0.6released.html
Zeb

Dropping frames in QT export from CS3

I just got CS3 for my PC and I was all excited about the new
feature that lets you export dynamic/actionscripted/MovieClip
content. I do animation targetted at TV, so everything needs to be
rendered to AVI or Quicktime, so I figured that this new feature
would let me use a dynamic camera symbol as I've always wanted to.
I've run into a problem, though: the export process seems to
drop frames! As far as I can tell, Flash is rendering and recording
the frames of the animation in real time (or perhaps just close to
real time). If the computer has any hiccups because of another
process demanding some processor time then the resulting quicktime
will have frozen bits where the renderer couldn't keep up.
You can see what I'm talking about by looking at the
quicktime and an AVI of the same scene here:
http://www.pinkandaint.com/flasherror/bad.mov
http://www.pinkandaint.com/flasherror/good.avi
To test this theory, I tried witching applications a bunch
during a render. Sure enough, there were long sections in the
resulting quicktime where the renderer missed frames. The quicktime
is the right length and number of frames -- it just repeated the
same frame over and over where it couldn't keep up.
That's not the only problem, though. When I look at the
exported quicktime file in either Quicktime Player or Premiere pro
(version 1.5) it reports a framerate significantly lower than in
the original FLA. In the file I'm looking at right now, the FLA's
framerate is listed as 29.97 but the MOV file reports a rate of
19.29 (which is, incidentally, different than the framerate I got
any other time I exported the same scene). In premiere, when I tell
it to interpret the footage as having 29.97 fps the clip gets
significantly shorter than it should be -- in this case 161 frames
rather than the 208 frames that it is in the FLA.
I'm pretty sure this is the same way that the various
SWF-to-video programs do things. I thought it was an interesting
kludge to use those external programs but I was sure Adobe would be
able to do something more elegant and sure-footed with this new
export feature. Couldn't they have somehow guaranteed that each
frame would get captured? It seems like they could have just
modified the Flash player to play with artificial time, where the
time to render each frame was always reported as 1/framerate.
Oh, and there's one more problem. The Quicktime renderer
seems to do something different about the order of execution of
actionscript or something. In the rendered quicktime movie the
first frame displays my camera symbol even though I explicitly made
it invisible with actionscript on the first frame of its timeline.
When displaying in the Flash player the first frame does _not_
display the camera symbol....
Has anyone else encountered these problems? If so, have you
figured out a workaround? I tried setting the framerate really low
(I was at 29.97, so I set it down to 10) but it still seemed to
miss frames.
-David

I can understand your frustration with this feature as it
tries to capture in real time what's being
compiled in the player - but your last line is a bit unfair:
"...it
> exemplifies the Flash team's disregard for animators in
favor of web developers."
Copy Motion and Copy Motion as AS3 are useful new additions
for animators. I will add however that I
myself have a list of animation oriented features I would
love to see added in flash but for now
have you checked out www.flashants.com and their SWF2Video
tool? It exports an SWF to AVI with
flawless results. Worth looking into if you have the need to
output any kind of flash content to video.
Chris Georgenes
Animator
http://www.mudbubble.com
http://www.keyframer.com
Adobe Community Expert
*\^^/*
(OO)
<---->
animator_geek wrote:
>
quote:
Originally posted by:
Newsgroup User
> [...]
> Turn off other applications. When recording, Flash uses
all of your system's
> available resources as much as possible, so any
interference of the system
> performance affects the result of the recording. We
recommend you exit other
> applications while exporting to a video.
>
>
> So you're telling me that Flash makes my computer
completely unusable while
> it's rendering? Sorry, I thought we left that kind of
limitation behind with
> DOS. Particularly for something like this, where the
rendering process should
> be
completely independent of real-time. The renderer should go
exactly
> as fast as it needs to in order to capture every frame.
Whether I set the
> frame rate to 1 or 1000 should make no difference in how
many frames are
> dropped in the rendering process.
No frames should ever be dropped I
> mean, what's going on here? You guys have access to the
actual source code of
> the renderer. Can't you adapt it so that it when it's
rendering non-real-time
> the SWF thinks that it's executing at exactly the frame
rate it desires? You
> could just set the renderer's "clock" to whenever the
render was started, then
> increment it 1/fps seconds every frame. The program
would never be the wiser.
> You could even let the timer run (or simulate it
somehow) for 1/fps seconds
> between rendering each frame, thereby handling any timer
events that need to be
> sent while the SWF is running.
>
> Clearly I'm not privy to the inner workings of the Flash
player but as a user
> there's a certain standard I expect, particularly when a
company touts this
> great new feature. It's supposed to work as advertised.
This feature clearly
> does not.
>
> Now I've been a software engineer in the past and I know
that sometimes
> workarounds have to be made but this is just too much.
To me as a user, it
> exemplifies the Flash team's disregard for animators in
favor of web developers.
>
> -David
>
>
quote:
Turn off audio. The audio in a Flash movie may also slow the
performance
> possibly causing dropped frames. Turn off the audio, if
you have many
> dropped frames in the first attempt. Other video editing
tools can be used
> to add the audio to the video after export.
>
> Reduce frame rate. If the movie dimension is a full size
NTSC video, 740 x
> 480, and frame rate is 30 fps, you are more likely to
have dropped frames.
> Reduce the fps of Flash movie increase the chance of
grabbing all the
> frames. Other video editing tools can be used to adjust
the frame rate of
> the video after export.
>
> Optimize your animation. Try to avoid a lot of screen
motion. The greater
> the area of change on the screen, the more likely
slowdown will occur. Also,
> if possible, restrict your use of transparency and alpha
channels as they
> too can cause poor performance.
>
> Use ActionScript 3. Animation created by ActionScript 2
and ActionScript 3
> are different in play back performance. Convert the
ActionScript in your
> animation to ActionScript 3 for optimized performance.
>
> Dimension settings in 2 places. The dimension settings
in Export Settings
> dialog sets the dimension of the SWF movie to be
captured. The Size settings
> in QuickTime Settings dialog sets the dimension of the
exported MOV files.
> If the SWF size is smaller than the exported MOV size,
the picture quality
> will be degraded; if it is larger than the exported MOV
file, you may have
> better picture quality. For best quality (and often
performance) these
> settings should match.
>
>
>
> "animator_geek" <[email protected]>
wrote in message
> news:[email protected]...
> >I just got CS3 for my PC and I was all excited about
the new feature that
> >lets
> > you export dynamic/actionscripted/MovieClip
content. I do animation
> > targetted
> > at TV, so everything needs to be rendered to AVI or
Quicktime, so I
> > figured
> > that this new feature would let me use a dynamic
camera symbol as I've
> > always
> > wanted to.
> >
> > I've run into a problem, though: the export process
seems to drop frames!
> > As
> > far as I can tell, Flash is rendering and recording
the frames of the
> > animation
> > in real time (or perhaps just close to real time).
If the computer has
> > any
> > hiccups because of another process demanding some
processor time then the
> > resulting quicktime will have frozen bits where the
renderer couldn't keep
> > up.
> >
> > You can see what I'm talking about by looking at
the quicktime and an AVI
> > of
> > the same scene here:
> >
http://www.pinkandaint.com/flasherror/bad.mov
> >
http://www.pinkandaint.com/flasherror/good.avi
> >
> > To test this theory, I tried witching applications
a bunch during a
> > render.
> > Sure enough, there were long sections in the
resulting quicktime where the
> > renderer missed frames. The quicktime is the right
length and number of
> > frames
> > -- it just repeated the same frame over and over
where it couldn't keep
> > up.
> >
> > That's not the only problem, though. When I look at
the exported
> > quicktime
> > file in either Quicktime Player or Premiere pro
(version 1.5) it reports a
> > framerate significantly lower than in the original
FLA. In the file I'm
> > looking at right now, the FLA's framerate is listed
as 29.97 but the MOV
> > file
> > reports a rate of 19.29 (which is, incidentally,
different than the
> > framerate I
> > got any other time I exported the same scene). In
premiere, when I tell
> > it to
> > interpret the footage as having 29.97 fps the clip
gets significantly
> > shorter
> > than it should be -- in this case 161 frames rather
than the 208 frames
> > that it
> > is in the FLA.
> >
> > I'm pretty sure this is the same way that the
various SWF-to-video
> > programs do
> > things. I thought it was an interesting kludge to
use those external
> > programs
> > but I was sure Adobe would be able to do something
more elegant and
> > sure-footed
> > with this new export feature. Couldn't they have
somehow guaranteed that
> > each
> > frame would get captured? It seems like they could
have just modified the
> > Flash player to play with artificial time, where
the time to render each
> > frame
> > was always reported as 1/framerate.
> >
> > Oh, and there's one more problem. The Quicktime
renderer seems to do
> > something different about the order of execution of
actionscript or
> > something.
> > In the rendered quicktime movie the first frame
displays my camera symbol
> > even
> > though I explicitly made it invisible with
actionscript on the first frame
> > of
> > its timeline. When displaying in the Flash player
the first frame does
> > _not_
> > display the camera symbol....
> >
> > Has anyone else encountered these problems? If so,
have you figured out a
> > workaround? I tried setting the framerate really
low (I was at 29.97, so
> > I set
> > it down to 10) but it still seemed to miss frames.
> >
> > -David
> >
>
>
>
>
>
>

..\..\Src\AudioRender\AudioPrefetch.cpp-99 error message and what caused it.

I found that when I zoomed into the sequence a lot using the +- keys, that the error message "..\..\Src\AudioRender\AudioPrefetch.cpp-99" kept jumping out at me. It was the last 3 steps of zooming in or out that brought the error message up on screen - a lot of times. It was only happening in one sequence in a particular project. I tried the suggestions for similar error messages that I found on this forum, but I eventually realised that in this project I had a WMV file (PowerPoint exported as a WMV file) which also had *audio* with it. (All the other sequences have WMV files but without audio.)
Going to the troublesome sequence and deleting the sound track from the WMV file fixed the problem. Next, I deleted the WMV file and put it back again. No error message. I then dropped the audio level to zero using the yellow line and the problem came back.
There is one other thing, the PowerPoint WMV file is 30fps and I’m in PAL land, so I interpreted the frame rate to 25fps. (So that PowerPoint transitions and movements etc. are smoother). I re-imported the original 30fps WMV file and put that in the sequence as 30 fps. Lowered the audio level to zero, and zoomed into the sequence. No error messages.
So it looks like a combination of WMV file, interpreting the footage and lowering the audio level to zero that caused this problem.
Do I need to post this somewhere so that Adobe gets to see this bug? (OK it is a rather unlikely combination of events.)

It's not as unlikely as you think. I just ran into the same exact thing. But I don't think it's the WMV.
I'm using footage from a Canon 5D Mark III shot at 60fps, then interpreted to 23.976 and dropped in a 23.976 timeline. I've also adjusted the volume on some of these clips, but not down to -∞. Since the error is "...AudioRender/AudioPrefetch.cpp-99" it makes sense that this is an audio related issue. I have also noticed that in the timeline, my yellow levels line and waveforms disappear when this error comes up.
So far I've been able to get around this bug by copying the clips into a new timeline, but this eventually comes back again.
The one question I have, is are you editing from an external hard drive? I've been editing at work off an external, then backing it up and working off internal drives when I get home. My external drive has been disconnecting itself lately, but it's never been around or at the same time as this error. Thought I'd still check with others though.

Error message [..\..\Src\Win\WinFile.cpp-758]

i tried to encode AVI video file with media encoder CS5 to MPEG2
and after it seemed the encoding was done i got this message?
[..\..\Src\Win\WinFile.cpp-758]
can enyone help me with this?

I had the same problem with recently updated Encore (5.01.) Tried shortening & simplifying file names with no luck either. I tried half a dozen things that sometimes work (e.g., refreshing source material, restarting Prmier Pro project from scratch) because of an error I overlooked. Nothing worked. Then, much by accident, I looked at the Media Cache. I had recently shifted the Media Cache to a new 3 TB hard drive that wasn't being used very heavily, figuring I had a lifetime supply of space. Wrong. It was completely filled up, mostly with the Media Cache. I cleared the Media Cache [Edit > Preferences > Media...] and BINGO! The project rendered cleanly.
Hope this helps.
Adobe needs to address this issue. The best solution would be to automatically clear out the cache materials associated with a perticular project whenever the project drops off the radar. A minimal solution that should be quick and easy to implement would be to monitor the empty space on the scratch disk and flash a pop-up warning when it was getting too full.
Addendum, 10 May 2012:
This one has left me thoroughly confused. Just ran a similar set of files through Encore, cleared the cache first, then good ole 758 again. It took several attempts, but finally it went through. Then I discovered I had forgotten to set something minor in the navigation and had to re-do it. Three tries later, it worked. Phase of the moon, I suppose.
This is not the first time this has happened - it happens occasionally with other similar files. I have had my best success running Encore when I let it run alone. It doesn't seem to time share very well with other programs, which is inconvenient because I like to work with Premiere and Photoshop getting the next project ready to go while Encore is processing the current one. Encore needs a batch queue like the one Premiere uses so I could prep the projects in Premiere/Photoshop during the day and then let the Encore queue run overnight. The queue would have to be configured so that if one project failed it would set it aside and move on to the next one.
Another problem Encore has is hanging temporarily. It doesn't die but just quits responding for a short time. It took me a while to discover that Encore was running but just not responsive to the operating system. I'm a little surprised because I have a fairly fast AMD 6 core chip and lots of RAM (or so I thought) at 16 GB. The gadgets and Resource Monitor tell me that the six cores are frequently using over 90% of the available combines cpu cycles and occasionally most of the available RAM.
I put in a 256 GB solid state drive, divided between the o/s and installed programs, leaveing about 120 GB for the files I was processing. The idea was that everything would be moving strictly in solid state. Maybe that speeded the system up too much. Putting in a 120 GB SSD sure made an 8-year old XP box scream though.
I am looking forward to getting CS6 in the next few weeks - I hope they have these bugs sorted out by then. From what I have seen in the forums, similar WinFile.cpp problems have been in existence since CS4 at least.
Message was edited by: Retired Spook

[..\..\Src\Win\WinPathUtils.cpp-427] error?????

I am running Adobe Production bundle CS3 and in Encore when I try to import an asset this message window appres "Adobe Encore has encountered an error [..\..\Src\Win\WinPathUtils.cpp-427]" and then I click the "continue button" and this pops up "An input contract violation has occured!'
I am running windos XP Sp2, fast machine with lots of ram and memory! any ideas? Previous Production Bundle ran perfect, but I unistalled it and installed the new CS3 and now I get this problem.
Any ideas anyone?
and a HUGE thanks in advance

While using Adobe Premier Elements 7 to edit AVC HD I encounted the error message (..\..\Src\Win\WinPathUtils.cpp.533) when trying to reopen an almost completed video project.
After days of trying to solve why opening the project I encounter error message (..\..\Src\Win\WinPathUtils.cpp.533) I decided to re-edit the video starting with a different project name. When I came to place AVCHD clip 00055 on the time line I encounter error message (..\..\Src\Win\WinPathUtils.cpp.533) I deleted clip 00055 from the hard drive (these clips were a copy from my camera I still have the originals)
I was able to reopen the original project as this AVCHD clip 00055 was the cause of error message (..\..\Src\Win\WinPathUtils.cpp.533) I renamed AVCHD clip 00055 to 05555 reinserted it in original project this saved me many hours of re-editing
Therefore I think in my case error message (..\..\Src\Win\WinPathUtils.cpp.533) was to do with a corupt AVCHD camera file within the project which was removed and the original project was abled to be opened.
Chris

[..\..\Src\pp\\PPixHandleUtilities.cpp-114] Dropped Frame CS3 Rendering Error

Similar Messages

Maybe you are looking for