Skip to main content
funkelodeon
Inspiring
June 1, 2017
Answered

Video Shuttle Support via API?

  • June 1, 2017
  • 1 reply
  • 1691 views

I'm working on a Panel application for Premiere Pro where the user reviews metadata about a clip while the clip plays. We need to enable keyboard shortcuts for a lot of the same functionality that the program pane has (step forward/back 1 frame, play/stop, etc). Because of the limitations of keyboard shortcuts and panel focus, my panel application must handle these playback shortcuts explicitly.

The interactions I'm having trouble finding support for in the API is shuttle forward/back, increasing the speed of shuttle, etc.

I haven't been able to find anything using the Data Browser that looks like it might do this. The nearest thing I can think to do is to call setPlayerPosition() on an interval, making the playhead jump at approximately the correct rate. This seems overly complicated, and wouldn't have sound playback either, so it seems like a poor approximation.

Has anyone had experience with this?

Thanks,

-Nick

This topic has been closed for replies.
Correct answer Bruce Bullis

https://forums.adobe.com/people/Bruce+Bullis  schrieb

Isn't that user experience exactly what happens when people work with (for example, review & approval) markers, using the source/program monitor, and the marker panel?

Yep, and I guess they don't like it.

I'm not suggesting panel developers shouldn't want a transport control API; I'm just trying to understand the motivation, and what makes "how it works today" unworkable.

I could also imagine the metadata is coming from another system and not necessarily in the Premiere project...

I don't get the OP's concept as well, too much room for speculation, and to me it feels like PPro is being used for a process that's not really in its original scope.


"...being used for a process that's not really in its original scope."

Since our original scope was editing and outputting 160x120 .avi files using the Indeo codec, the Premiere team call situations like that, "weekdays".  

I can't make any specific commitments, but we're investigating exposing more/better transport controls.

1 reply

Bruce Bullis
Legend
June 2, 2017

What makes relying on PPro's own transport controls an untenable solution?

sberic
Legend
June 2, 2017

Bruce Bullis wrote

What makes relying on PPro's own transport controls an untenable solution?

Going out on a limb here but I would expect that they expect preview functionality while their extension panel is focused. As there is no fast way to switch between panels​​ (including OS-standard window-switching controls like [CMD+`] in macOS), it only makes sense that they would want to drive other features - think of it like a specialized, custom control deck for Premiere Pro.

Without this, the user experience looks like this:

  1. Click custom extension for focus.
  2. Trigger commands.
  3. Move mouse to appropriate native panel and click.
  4. Trigger commands.
  5. Move mouse back to extension and click for focus.

That's a lot of mouse movement, simply to switch contexts. My guess is that funkelodeon​ is simply looking for a way to simplify life for their user.

Or... I'm way off the mark ;p

Bruce Bullis
Legend
June 2, 2017

Isn't that user experience exactly what happens when people work with (for example, review & approval) markers, using the source/program monitor, and the marker panel?

I'm not suggesting panel developers shouldn't want a transport control API; I'm just trying to understand the motivation, and what makes "how it works today" unworkable.