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

Possible bug with InPoint and OuPoint functions combination

Engaged ,
Feb 06, 2024 Feb 06, 2024

Copy link to clipboard

Copied

Depending on wether the value of In is superior or inferior to the value of Out, you can have a bug or a feature.

The experiments I did were in ticks, I don't know if they are valid in seconds.

1) Experiment 1:

If the value of In is inferior to the value of Out, but the difference between them is inferior to One frame, the project item will be inserted with FULL DURATION (ignores all ins and outs, even if they were set to a specific values before), this actually resets the values of in and out it seems.

 

2) Experiment2:

If the value of In is superior to Out, without any focus on the difference between of the 2 (it can be whatever), the same happens, FULL Duration of items.

 

I consider experiment 1 to be a bug because it should round up to 1 frame in such case.

I consider experiment2 to be a feature because it informs you that you "reversed" the order of in and out.

TOPICS
SDK

Views

191

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 ,
Feb 06, 2024 Feb 06, 2024

Copy link to clipboard

Copied

ExtendScript that demonstrates Experiment 1, please? 

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
Engaged ,
Feb 06, 2024 Feb 06, 2024

Copy link to clipboard

Copied

Yes, inside a sequence that has 25 frames:

Item is an audio:

 

 

Item.setOutPoint("15000000000", 4);
Item.setInPoint("10200000000", 4);
$.writeln("outpoint: ");
$.writeln(Item.getOutPoint().seconds); // result full duration (in my case: 2.784 seconds)
$.writeln(Item.getOutPoint().ticks); // result: full duration of an audio (for my case: 707180544000)

 

 

Interestingly enough, if I try a very simple example like

 

 

Item.setOutPoint("1", 4);
Item.setInPoint("0", 4);

 

 

There is not problem it is rounded up to one frame,

But with the numbers I provided the problem appears (cf, result of the prints)

Strange isn't it?

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 ,
Feb 06, 2024 Feb 06, 2024

Copy link to clipboard

Copied

>Item is an audio

Do you mean that the projectItem behind this trackItem is audio only, or do you mean that this trackItem is from an audio track


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
Engaged ,
Feb 06, 2024 Feb 06, 2024

Copy link to clipboard

Copied

>> that the projectItem behind this trackItem is audio

Yes this one!

But first time I encountered this problem was with a video actually, so I don't think it matters. I used an audio when I was testing again to understand what was happening.

The "Item" is from the "children" of the project aka project items. No need to interact with the tracks actually, just using the getter for outpoint will show that the values have turned to "original out point" of the item => max duration of item.

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 ,
Feb 06, 2024 Feb 06, 2024

Copy link to clipboard

Copied

>But first time I encountered this problem was with a video actually, so I don't think it matters.

>The "Item" is from the "children" of the project aka project items

 

If it's a projectItem, not a trackItem, you've just completely changed the scope of the problem report. 

In order to pursue your issue report further, we would need all available specifics about the project, sequence and media in use, as well as a complete ExtendScript script that reproduces the problem (not just the snippet above). Upload space available upon request.

 

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
Engaged ,
Feb 06, 2024 Feb 06, 2024

Copy link to clipboard

Copied

LATEST

Absolutely, but not today, if that's not urgent, I wanted to continue other tasks and get back to this. My prediction for this bug is that the in "rounds up" to the next frame, whereas the out does not, so despite having an out superior to in, out converts to its full value (initial value) somehow.

I only mentioned the sequence to explain where my experiment (was displayed) before I started using prints and see that out values got indeed changed to unwanted values. That was misleading sorry.

Will try to come back to this later in the week.

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