• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Error when setting track clip end time in premiere pro scripting

Explorer ,
Nov 29, 2020 Nov 29, 2020

Copy link to clipboard

Copied

Hi everyone. I want to change some clips' end time in my timeline via scripting.

This is my code:

 

var proj = app.project;
var srcSeq = proj.activeSequence;

var time = new Time();
time.seconds = 10;
var vClip = srcSeq.videoTracks[0].clips[0];
var aClip = srcSeq.audioTracks[0].clips[0];
vClip.end = time;
aClip.end = time;

 

The problem is when I execute my code, it always gives  me error saying that 'cannot set property end'(last two lines giving the error).

err.png

However, it actually does change my clip end time.

timeline.png

This happens when I set the inPoint/outPoint/start/end time on my track clip.

Am I doing somthing wrong? Or it's a bug?

 

Hope I can get some help.

 

BTW, I am on Windows 10, Premiere Pro 14.6.0(should be the latest at the current time). And I script in vscode with ExtendScript Debugger extension.

 

 

 

TOPICS
Error or problem , How to , SDK

Views

579

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 2 Correct answers

Adobe Employee , Nov 30, 2020 Nov 30, 2020

The error you're seeing, is the bug. 🙂

 

We're tracking the issue as DVAPR-4224243.

Votes

Translate

Translate
Adobe Employee , Dec 02, 2020 Dec 02, 2020

Yes, this one is New World only.

 

It's unlikely that we'll add any new APIs to Old World; I'd also anticipate very few additions to the ExtendScript API, between now and when UXP support becomes available (no dates available).

Votes

Translate

Translate
Adobe Employee ,
Nov 30, 2020 Nov 30, 2020

Copy link to clipboard

Copied

The error you're seeing, is the bug. 🙂

 

We're tracking the issue as DVAPR-4224243.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Nov 30, 2020 Nov 30, 2020

Copy link to clipboard

Copied

Great thanks, Bruce! And another small issue of NewWorld scripting is that it complains every time the value passed into 'Alert()' is not a string. Can we have how it behaves like in the OldWorld scripting(not complaining when getting a non-string value) in the future?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Dec 01, 2020 Dec 01, 2020

Copy link to clipboard

Copied

No, because implicit type conversion to string went away, with the move to New World. It's unlikely to make a return.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 01, 2020 Dec 01, 2020

Copy link to clipboard

Copied

Thanks! And another question: Are some api methods NewWorld Scripting only? This method 

'app.project.createNewSequenceFromClips()' works only in NewWorld scripting on my side. Once I turn off the NewWorld, it gives an error saying this method is not a function(see pic below). Is it a  bug? Or it's a NewWorld Scripting only feature? And in the future if you add new features to the api, will it be NewWorld scripting only?
error.png

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Dec 02, 2020 Dec 02, 2020

Copy link to clipboard

Copied

Yes, this one is New World only.

 

It's unlikely that we'll add any new APIs to Old World; I'd also anticipate very few additions to the ExtendScript API, between now and when UXP support becomes available (no dates available).

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Dec 02, 2020 Dec 02, 2020

Copy link to clipboard

Copied

Thanks, Bruce! Super helpful. Looking forward to  UXP stuff.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Feb 13, 2021 Feb 13, 2021

Copy link to clipboard

Copied

LATEST

Any Update/Workaround for DVAPR-4224243?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines