-
(CS5.5) Video export fails because of Title keyframes
I’m having a strangely specific problem with Premiere ever since I upgraded my PC about a month or so ago – any attempt to export a video project has failed in a particular place. For reference, the specs of this new machine are as follows:
Intel Core i5-9400FCPU @ 2.90 GHz
16GB RAM
NVIDIA GeForce GTX 1050 Ti
Windows 10 Home (64-bit)Thus far it has been fully able to run Premiere Pro 5.5, and previews everything I do effect-wise just fine within the program itself. It is only when it comes to attempting to export the video that it encounters a problem – whether this is done by queueing the project in Media Encoder and attemping to output from there, or directly exporting from Premiere. In the former case, the video reaches a specific point and then freezes entirely, whereas in the latter the encode fails with an ‘unknown error’ at the same point.
All of the similar Titles I use within the project have some movement keyframes in them, to have them both ‘appear’ and ‘disappear’ with a little bit of flourish, but it is only the ones that have movement keyframes in *addition* to these that cause the freezing (they move while present on screen to follow a moving camera angle and stay in the same place relevant to an on-screen object). From experimentation, it seems that it is the number of keyframes, rather than the nature, that is causing the problem – I tried removing a few existing keyframes from the first problematic Title and it was then able to render. However, given that the number of keyframes apparently causing the problem is as few as sixteen, this is not at all practical for my work and thus still needs to be solved at the root rather than worked around.
It seems alarmingly specific a thing to vring the program to a standstill, especially given the comparative power of this new computer versus the old one – which was first obtained around eight years ago – and given that the older machine was able to handle everything.
I have checked my export settings and they are identical to what I used before (using the H.264 codec), I have tried freeing up as much memory as possible as well as allowing Premiere/Media Encoder to use as much of it as they are permitted to, and the hard drive I am exporting to has plenty of space available for the finished video. I’ve tried rendering my work area within Premiere first, changing codecs, clearing the media cache, deleting and remaking the problematic Title; I’ve even tried elevating my machine in order to create better airflow with the underside cooling fan, but all to no avail.I’m at a loss as to what could be causing the problem, and have no idea how to approach solving it – extensive online searching has yielded no similar scenario encountered by anyone else. Upgrading to a newer version of Premiere/Media Encoder is not an option for a variety of reasons (not least of which financial), and having access to so little keyframe usage is not at all something I can just accept as a limitation on my work.
If anyone can shed any light on this madness at all, that would be fantastic – this is my livlihood and I am at my wits end!
-
1 Reply
-
There’s lots of changes between your previous OS and Windows 10. And Premiere Pro 5.5 is pretty long in the tooth.
This simply may be a situation where Premiere Pro 5.5 doesn’t know what to do with a generation of video card that didn’t even exist when 5.5 was released, or fundamental changes at the OS level.
I don’t think 5.5 offered render hardware acceleration. But if it did, try switching that off and going to software only. You can also try outputting to a series of still, like PNG. That can easily be reassembled into a clip with After Effects.
System:
Dell Precision T7600 (x2)
Win 7 64-bit
32GB RAM
Adobe CC 2017.1 (as of 8/2017)
256GB SSD system drive
4 internal media drives RAID 5
Typically cutting short form from UHD MP4, HD MP4, and HD P2 MXF.
Reply to this Discussion! Login or Sign Up