[Ciro Coleman]

Hi Evan,

Although this may not be a ‘fix’, try turning the Autosave off and not Saving to see if it still ‘plays’ with your key frames.

I discovered by chance that the Save and Autosave features were changing the key frame values and have just posted a thread to see if anyone has an answer to that. I now have a work around so that before making any Position/Scaling changes I deselect Autosave, then Save my project before applying any motion keyframes and render to final output.

Of course, once rendered, I check the video through and if necessary make any changes without Saving until I’m happy with the final video. On closing Premiere down it’s going to ask you to Save the Project, which in my case will change the keyframes.

If I choose not to Save it, it will remain at the last Save before adding the Motion/keyframes. Hopefully, by this stage your project is finished with no further editing but if you need to go back and tweek it then bear in mind that you will have to readjust all the keyframes again. Naturally, this a work around if you’re being affected in the same way by the Save and Autosave feature. But this shouldn’t be happening!!

Anyway, I hope this helps and makes some sense and perhaps sheds light on your own problem. If not, hopefully someone has a cogent answer?

regards

Ciro

[Ciro Coleman]

Jake,

Thanks for giving a cogent, straight answer to a straight question. Worked a treat!!!

It has driven me mad not knowing how to resolve this problem and driven me mad when asking this question on various forums and getting NON answers and waffling that resolves NOTHING.

Excellent!

Cheers

Ciro

P.S. to others with this problem – it WORKS!!

[Ciro Coleman]

Hi Vince,

Thanks again for the update. I’ve managed to resolve the problem.

I was working in a Premiere HDV project with the HDV footage and then rendering down to DVD using the media encoder, which, in my mind was messing the end result up.

I opened a DV-PAL widescreen project and imported the original uncut HDV footage. Resized the footage to 54% to fill the screen and hey presto, no blurring on test renders I’ve done.

I’ve now copied the time line footage of my HDV project and pasted it into a new DV-PAL widescreen project. Of course, it means resizing all the clips and putting in the dissolves in again but a lot less work than having to start all over.

I will still look at some of the ideas you put forward as it’s always good to have other fallbacks.

many thanks and hope this helps anyone else who may have the same problem.

regards

Ciro

[Ciro Coleman]

Hi Vince,

My export settings are 16:9 widescreen 25fps and vid clip of 5 minutes.

I’ve tried exporting the clips as targa files at the Anamorphic HD 1.33 pixel setting then used After Effects with the same pixel aspect ratio and rendered out to a Windows avi file. There isn’t any blurring so I suspect that trying to convert from HDV 1440:1080i 1.33 pixel aspect ratio to Widescreen 720:576 16:9 1.422 aspect ratio is mucking it up somewhere?

If I’m seeing keyframes when compression shows a full frame, instead on one based only on changed pixels what would I need to do to resolve the issue?

many thanks

Ciro

[Ciro Coleman]

Hi Tim,

Thanks for your response. I have, fingers crossed, seemingly fixed the problem.

In the Windows’ Error report I clicked the ‘details’ button and found that it pointed to – nvoglnt.dll, which, after some ‘googling’ pointed to Nvidia graphics drivers. I downloaded a nvoglnt.dll file, and replaced the one I had in Windows\system32. The one I had originally was just over 3 megs and the one I replaced it with just over 300 kilobytes. I loaded Premiere and waited with baited breath whilst Media Encoder loaded. No warnings came up and I rendered the sequence successfully. Hoorah!! I also opened Media Importer on its own and imported a sequence and voila, it, too, rendered.

I would probably guess that any others who have the same problem may be able to do the same thing and replace/update whatever file the Error report points to albeit may not be just Nvidia.

Whether this is the only cure would be a matter of having a totally ‘clean’ computer and adding and testing one thing at a time starting off with the updated file in the Error report. Hope this a help to any others seeking a better explanation to the solution of how to fix the PProheadless.exe problem.

regards

Ciro

[Ciro Coleman]

Hi Tim,

Hope you can help me? I’ve just got Adobe Premiere CS4 and am having the error message “PProheadless.exe” failed when I go to render a sequence. The Media Encoder works fine on its own but will not import a saved sequence even from within the sequence’s own folder. (as mentioned in your thread)

I’d uninstalled my other Adobe products, flushed the registry etc, updated DirectX and .Netframework as some others had advised before reinstalling and trying again.

I’ve been to an Adobe Forum and most of the answers are, well, no answers as they seem to be shooting into the dark on a trial and error basis. My question is:- how does one fix the problem? Why is it happening? Is there something missing or something impacting the system so the link is not being made? Is the file corrupt? If so, how can you find out?

I’m looking for a cogent answer that tells me . . . you have to do this or having such and such a program is interfering with PProheadless.exe that then causes it to crash and you need to do X, y and Z to remedy the problem or . . . etc etc?

Any sound advice will be greatly appreciated

thanks

Ciro Coleman (UK)