Skip to main content
A
agckent
Participating Frequently
January 20, 2019
Answered

Keys frames not working when content is a photo not a movie clip

  • January 20, 2019
  • 1 reply
  • 404 views

Shortly after having a major Windows upgrade (The belated OCT 2018 version) and upgrading Premiere Pro to version 13, I started a new "Hello world" type project intending to make a slide show of various still jpeg photos with Scale and Position key frames to allow a Pan and Zoom (Ken Burns?) effect.

I kicked off with just one single JPEG in the project. I added it to the time line. I added start and end  keyframes for both Position and Scale.

The result was very erratic. When playing, the Play head kept jumping backwards randomly and intermittently. . When adjusting the key frames position or value the Program Monitor  went on and off despite the play head being positioned over the selected photo. The keyframes did not work, or if they did, jumped to the new value rather than incrementally changing from the first value to the new value.

I tried various tips found here like ensuring no  other effects were activated, or  setting the Audio Hardware to something other than default. All were to no avail.

I started a second Hello World type project and this time added a a single short movie clip as the sole content. The Scale and Position keyframes worked perfectly. I then added the same jpeg photo with which I was having trouble in the first  Hello World type project. It's Position and Scale effect keframes worked perfectly when it was placed in  the time line after the movie clip.

My question is "Is there something I need to do  if I want to add keyframe effects to a photo only project, other than importing the photo and dropping it onto the timeline?"

    This topic has been closed for replies.
    Correct answer R Neil Haugen

    When you drop any clip or still to a blank timeline area, Pr makes a sequence suitable for that material. That was the difference.

    Create a new sequence at the framerate and frame-size you want to use ... 23.975 or 29.98 (or 25 or 30) probably and say 1920x1080. Have the Preferences option set to "Set to frame-size".

    Then drop your still onto it.

    Neil

    1 reply

    R Neil Haugen
    R Neil HaugenCorrect answer
    Legend
    January 20, 2019

    When you drop any clip or still to a blank timeline area, Pr makes a sequence suitable for that material. That was the difference.

    Create a new sequence at the framerate and frame-size you want to use ... 23.975 or 29.98 (or 25 or 30) probably and say 1920x1080. Have the Preferences option set to "Set to frame-size".

    Then drop your still onto it.

    Neil

    Everyone's mileage always varies ...
    A
    agckentAuthor
    Participating Frequently
    January 21, 2019

    Hello Neil

    Thank you for your speedy response and helpful advice.

    I have had a play to see if I could re-create the problem then solve it.

    I started a new project, imported the same photo which was 6000 x 4000 res.

    Dropped it on the time line. (A sequence was auto created with 25FPS and 6000 x 4000 res).  Set up the waypoints and whilst it worked on first showing, it became increasingly erratic on subsequent showings as per my earlier attempts.

    I then removed the photo from the timeline and adjusted the Sequence,s parameters to 25 fps and resolution as per your recommendation of 1990 x 1480.

    I dropped the photo onto it and the centre section only of the large photo was displayed.

    I right clicked the photo and chose “Set to frame size” and the whole photo was displayed.

    I then fiddled with various Position and Scale keyframes and they all worked perfectly.

    So thank you for you help, you have solved the problem.

    As a matter of interest, do you think the only reason the keyframes did not work originally was because the photo was too large for my Microsoft Surface pro 2 computer to cope with at the high res of 6000 x 4000? Or is there something else which I have yet to learn about?

    R Neil Haugen
    R Neil Haugen
    Legend
    January 21, 2019

    I think that frame-size was way too large for the computational device you're using. Full desktops can be bogged with that many pixels to push 25 times per second.

    Neil

    Everyone's mileage always varies ...
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices