[Nat Wilson]

Hi Exy,

I’m glad that the answer helped you resolve the problem, thanks for letting me know, and good luck with avoiding the bugs 🙂

Nat

—
Nat Wilson, Editor / Animatior
Adobe CS5 Production Premium running on Win 7 Pro x64 8GB RAM

[Nat Wilson]

Hi Jan,

thanks for your reply. The error occurs across a variety of video formats, including H264 .movs, H264 megs, EXCAM .mxf files, interestingly it also occurs after I unlink and delete the video (leaving only the audio on the timeline) which leads me to believe it’s audio related…..

The drop frame indicator stays green the whole time.

Nat

—
Nat Wilson, Editor / Animatior
Adobe CS5 Production Premium running on Win 7 Pro x64 8GB RAM

[Nat Wilson]

Hi Nathan,

thanks for explaining in further detail the work around – thats the best solution right now, until Adobe find a fix.

I’m told that’ll happen soon, fingers crossed, as otherwise Premiere CS5 is a great release.

cheers,

N

—
Nat Wilson, Editor / Animatior
Adobe CS5 Production Premium running on Win 7 Pro x64 8GB RAM

[Nat Wilson]

Hi Andrew,

It sounds like you’re experiencing something very similar to that which I and others have seen. Adobe have looked at my project files and have confirmed that there is a bug in CS5 Premiere. I understand that they are working on a fix at the moment and that an update will be sent out for Premiere shortly, but I don’t have a date. There has been no mention of this problem in CS4 though, but now that they know what the problem is, they should know if it affects CS4 and update that also if needed. The word from Adobe is that the problem relates to renders that are done within the editing environment being saved with the project file. You can find out more info by reading the threat which I’ve linked to previously, over at the Adobe Support Forums. I hope this helps, and good luck solving the problem.

cheers,

Nat

—
Nat Wilson, Editor / Animatior
Adobe CS5 Production Premium running on Win 7 Pro x64 8GB RAM

[Nat Wilson]

Jon – thanks for the suggestion. I didn’t know that AAFs would do that and will try it. A work around has come in from an Adobe employee whereby you create a new project in CS5 and import the timeline, but not the project, which I’ve tested and which works, however there are other people with this problem now and this includes people who originated their edits in CS5, which probably rules out this being a CS3 – CS5 migration issue and hence means the problem won’t necessarily be fixed by this work around.

I’d encourage people with this problem to also have a look at the Adobe forum where some other people with the problem have posted, and which has the eye of an Adobe employee at the moment:

https://forums.adobe.com/message/2845669#2845669

thanks for your help everyone and if I get a solution, I’ll post it here.

—
Nat Wilson, Editor / Animatior
Adobe CS5 Production Premium running on Win 7 Pro x64 8GB RAM

[Nat Wilson]

Hi Bob, thanks for taking the time to reply. Unfortunately, although I’m using CS5, I’m not using a video card that can make use of the realtime rendering afforded by the Premiere Pro CS5. Because it’s HD footage I’m needing to render to view a reasonable copy of the edit, which as you guessed is not completed.

I have plenty of space of the RAIDed edit drive (1TB free). The problem seems to be specific to the project file. I may have to export and EDL and bring that into a brand new CS5 project in order to rule out it being something to do with the project having been converted from CS3, which someone else has suggested could cause a problem. If I do that though I’ll loose a load of grading and reframing that I’ve done 🙁