Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Motion Keyboard Command Problem: Go to In Point of Selected Object

  • Keyboard Command Problem: Go to In Point of Selected Object

    Posted by David Intrator on November 26, 2011 at 3:10 am

    In Motion 5, when I press shift+i to go to the input of a selected object on the timeline, the playhead always moves back to the 1st frame of the composition. Pressing shift+o does not present a problem, and takes me to the end frame of the selected object.

    Any ideas?

    Thanks.

    david

    Stojan Stojanovic replied 12 years, 9 months ago 4 Members · 6 Replies
  • 6 Replies
  • Ken Caron

    May 6, 2012 at 12:40 am

    David,
    Did you ever find a solution to this problem?

    Ken

  • Dan Shuta

    August 2, 2012 at 9:54 pm

    running into this now as well. i tried making a new proj. with a few rectangles at points in the timeline, however, and couldn’t repro. it (worked as expected), however in a project that i’m building, even if i make a new group/rectangle at the top level, with its in-point set mid-way down timeline, and select this layer only, it jumps to start of timeline when i try to go to selection in.

  • Dan Shuta

    August 2, 2012 at 9:55 pm

    i’m using motion 5.0.4, mac pro 10.7.4.

  • Dan Shuta

    August 2, 2012 at 9:59 pm

    also can confirm that go to out point works as expected, universally. it’s this lousy go to selection in that’s being fussy.

  • Dan Shuta

    August 2, 2012 at 11:11 pm

    ok, i’ve isolated the issue somewhat. i’ve attached an example file, here’s what i’m experiencing:

    – select rectangle 1, rectangle 2, or their parent group
    – from menu bar — mark -> go to -> selection in point
    – playhead jumps to in point of USDA text

    if i delete the “USDA” text layer, behavior resolves (going to in point of selected rectangle does as expected).

    now, the USDA text layer was copied from the project that i was originally noticing the issue in the first place. oddly, the “more text” layer (added freshly to this test project) doesn’t catalyze the same problem. i can find no reason why the copied USDA text layer would be causing any issues, the properties seem the same as the newly-typed text layer. what is going on here?!

    4487_gotoselectioninpointissue.zip

  • Stojan Stojanovic

    August 2, 2013 at 11:07 am

    Same problem back from Motion 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy