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

Image Corruption Using Sample SDK_Exporter Plug-In

New Here ,
Mar 21, 2017 Mar 21, 2017

Copy link to clipboard

Copied

Hello.  I recently downloaded the current Windows Premiere Pro 2017 CC.  The problem is that, with UHD video, the output seems to start getting corrupted around 128 frames or so,  By this, I mean parts of different frames are merged into a single frame.  If I reduce the video size from 3840 x 2160 to say 3000 x 1688, I am able to get a greater output of usable frames, but inevitably the corruption sets in at some point.  I am aware that an uncompressed UHD frame requires a lot of memory, although there are no indications I am running out of memory during this process.  Still, this has all the markings of a memory corruption problem.  I have attached a couple of images showing the last good frame and the one following it.  Any help would be greatly appreciated.

Frame_129.jpgFrame_130.jpg

TOPICS
SDK

Views

853

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 1 Correct answer

Adobe Employee , May 10, 2017 May 10, 2017

Hi Gary, this issue is fixed in the new release of the SDK, available now:

http://www.adobe.com/devnet/premiere/sdk/cc2017.html

Regards,

Zac

Votes

Translate

Translate
Adobe Employee ,
Mar 22, 2017 Mar 22, 2017

Copy link to clipboard

Copied

I'm not sure why you think it's memory corruption...? Seems like a math error, from here...

Zac will know for sure.

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
New Here ,
Mar 22, 2017 Mar 22, 2017

Copy link to clipboard

Copied

Point taken.  Just a guess on my part.

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 ,
Apr 13, 2017 Apr 13, 2017

Copy link to clipboard

Copied

Sounds like it could possibly be a pointer using too small of a data type, and it is wrapping around.  Are you still looking for help here?

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
New Here ,
Apr 13, 2017 Apr 13, 2017

Copy link to clipboard

Copied

Hi, I've worked around the problem by making multiple exports, with each export being limited to 125 UHD frames, but I wouldn't mind a better solution.

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 ,
May 10, 2017 May 10, 2017

Copy link to clipboard

Copied

Hi Gary, this issue is fixed in the new release of the SDK, available now:

http://www.adobe.com/devnet/premiere/sdk/cc2017.html

Regards,

Zac

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
New Here ,
May 13, 2017 May 13, 2017

Copy link to clipboard

Copied

LATEST

Thanks, Zac!

I checked the revised plug-in out this morning, and the problem is indeed gone.

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