Get info for clip loaded in source monitor using ExtendScript

[dheidel]

Hello,

So, the short version: I was wondering if there's a way to get information about the clip currently loaded in the source monitor using ExtendScript. Specifically, I'd be interested in the name, starting timecode, and in/out points. I don't see anything obvious in the Data Browser in ExtendScript Toolkit, but I thought I would ask.

The long version of what I'm trying to do: I have a clip in the source monitor that I know is in the active sequence. I'd like to take the in/out points of the source clip and set those as in/out points in the sequence. This is sort of a hack to get around the fact that you can't associate speech analysis with a multicam clip so I'm cutting with one of the audio clips in the multicam clip and then I'm trying to translate those edit points to the multicam sequence. I have a way to do it with an AppleScript macro, but I'd like to find a more robust (and cross-platform) solution.

Thanks!

[Bruce Bullis · Accepted solution]

There's no capability to get back from a Source monitor item to the actual projectItem, in PPro CC 2015.

However, you wouldn't be the first to request such functionality, and (ahem) I can neither confirm nor deny that it may be added in the near future.

[dheidel]

Thanks, bbb. I can (ahem) confirm that that would be amazing. The scripting ecosystem that's built up around After Effects over the last few years is incredible. If Premiere got to that same level of scriptability, it would be a killer, and, as far as I know, unique, feature among mainstream NLEs. (And yes, I've filed a feature request).

[Fred CRETET]

Hello Bruce,

I need also to get IN and OUT points from source monitor...

The idea is to send footage to fter Effects and replace them in a comp...

You can add my vote to this feature request.

Thanks

Fred

[Bruce Bullis]

Will do!

[Premiopolis]

Is there any progress on this request?  Would love to be able to the project item based on what's loaded in the Source or Program Panel.  Anything under the hood of app.enableQE?

[Bruce Bullis]

I have no publicly available news on that front.

Partial workaround = get the path from the Source monitor, then use app.project.findItemsMatchingMediaPath() to find related projectItems.

[Premiopolis]

Actually that might very well work.

While we're at it, any way to load an item into the source monitor by bin items (as opposed to via media path) -- Actually I'll post as a separate question...  Is it possible to load a bin item in the Source or Program Panel?

[eyali_av]

Hi Bruce Bullis, 

How's getting the projectItems help with getting clip's mark in (from source monitor)? 

Is this even possible? Or should it only retrieved from sequence?

Thanks!

[Bruce Bullis]

Once you have the projectItem, you can get/create associated markers (see PProPanel's clip marker handling).

[eyali_av]

Thanks, Bruce Bullis​.

If you don't mind, I still have some questions: 

1. And if I would like to get the Mark In/Mark Out (the I and O keyboard shortcuts, or the { } icons in the action row) from a *Source monitor*? 

2. Is There a way to associate a projectItem to a source playing it? 

3. Is there a way to open a bin item (or projItem) in the source monitor with API?

[Bruce Bullis]

1. There's no way to intercept the handling, of those functions.
2. No.
3. Not directly, though you can get the path from the projectItem, and open that. Feature requested.

[Premiopolis]

Is there a way to retrieve the File Path of the app.sourceMonitor object or via any other means?

While we're at it, is there list of properties, methods and events available to app.sourceMonitor?

I'm aware of the following, to date:

app.sourceMonitor.openFilePath(FilePathAsString); 
app.sourceMonitor.indexOf(searchElement, fromIndex);
app.sourceMonitor.filter(fun,thisArg);
app.sourceMonitor.map(callback,thisArg);

Not sure what indexOf, filter, and map methods do, if anything.

Are there more options?

[Bruce Bullis]

There are no further options.

[eyali_av]

And what are those functions do?

app.sourceMonitor.indexOf(searchElement, fromIndex); 

app.sourceMonitor.filter(fun,thisArg); 

app.sourceMonitor.map(callback,thisArg);

[Premiopolis]

eyali.av  wrote

And what are those functions do?

app.sourceMonitor.indexOf(searchElement, fromIndex); 

app.sourceMonitor.filter(fun,thisArg); 

app.sourceMonitor.map(callback,thisArg);

+1 on eyali.av question.

For instance what are the options for the "thisArg" parameters?

Better still, what's that "fun" parameter?  I could use some of it.

[Bruce Bullis]

Where are you seeing those  indexOf / filter / map functions?

Not in ESTK...

[Premiopolis]

In 'reflects', for instance...

IterateReflects(app.sourceMonitor);
function IterateReflects(thisObj){
  var i,thisReturn;
  thisReturn=[];
  for(i in thisObj.reflect.properties){
       thisReturn.push(i+": "+thisObj.reflect.properties);
  }
  return thisReturn;
}

[Bruce Bullis]

We think it must be inheriting some core ExtendScript Array object properties; those are certainly not intended API features.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/indexOf
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/map
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/filter

[Premiopolis]

Very possibly.  It was the "fun"  parameter -- which didn't look like a JS inheritance -- that gave me hope someone on your team had customized them with some easter eggs a lá...

- LoadProjectItem

- GetPath

...which would be my idea of 'fun'

Hoping against hope?

[Bruce Bullis]

If we'd already written those functions, I wouldn't tease you by saying that the feature had been requested.

[eyali_av]

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

1. There's no way to intercept the handling, of those functions.

I'm not sure you answered my question: I didn't ask about "listening" to an event of Mark-In or Mark-Out actions, I was just wondering if those points in a clip opened in a source monitor can be retrieved.

[Francis36985154rpnu]

Hi Bruce,

> Partial workaround = get the path from the Source monitor, then use app.project.findItemsMatchingMediaPath() to find related projectItems. 

Long shot reviving this old thread here here but from this comment it sounds like it is somehow possible to get the path of the media currently opened in source monitor, and then use that to find the associated project item. But how would you get the path of the media opened in source monitor?