Skip to main content
Known Participant
May 16, 2025
Question

Generative extend not working on REC 709 Clip

  • May 16, 2025
  • 21 replies
  • 1683 views

When I try using generative extend, I'm told my clip needs to use REC 709 color space. 

 

My clip is 3840x2160, 23.98fps, REC 709.

 

I'm on 25.2.1.

 

See attached.

21 replies

Smit-Shah
Community Manager
Community Manager
May 23, 2025

Hey @JesseSchluntz 
Generative Extend currently does not support Log files, and I see your file is SLog3. 

Participant
June 8, 2025

Ok, i see a problem, not being able to use generative extend on ungraded raw footage is a fail, who wants to know if their cut cant be saved with a client over there shoulder based on colour space. LLMs are basic yet capable, i see not difference in being able to work with LOG vs Rec709. Explination please Adobe... ps LLms work fine in 3d with LOG content

MyerPj
Community Expert
Community Expert
May 22, 2025

Well done! Glad you found a way to get past this for now. And you've suggested a bug/idea for Adobe to work on. Hopefully as the feature matures other formats will be supported.

Known Participant
May 22, 2025

Update. I exported a portion of the problem clip out of premiere at prores 4444. Generative extend finally worked. 

 

@13409279 @Kevin-Monahan It would be great if Adobe could fix this bug. Thank you.  

R Neil Haugen
Legend
May 22, 2025

I kinda expected that. 

 

 

But it's worth the asking.

Everyone's mileage always varies ...
Known Participant
May 22, 2025

@R Neil Haugen Sorry but I can't. The footage is client's property. Also the files he shot are quite large. Thanks though. 

R Neil Haugen
Legend
May 21, 2025

Sony mxf files are occasionally problematic in Premiere, no clue when or why. As one possible thing.

 

Past that, it shows the original was full range though this clip is in limited. I'm wondering if Premiere sees the 'full' in the file header somewhere and goes goofy.

 

Would love to test here if you could share the file.

Everyone's mileage always varies ...
Known Participant
May 21, 2025

@MyerPj and @R Neil Haugen I'm touched by your interest and persistence. I also assumed you guys were with Adobe. Here you go...

MyerPj
Community Expert
Community Expert
May 21, 2025

Indeed, as @R Neil Haugen said, it's for us here, user to user, as we try to figure out what might be happening with your issue. I'm no mac guy, but we always ask for the Tree view from MediaInfo, it's a free software. I was told once and not that long ago, that Mac users must pay $1.00 for the Tree view, thus any view, for instance the plain text view is fine in that case if the $.99 is too much in cost or principal. In short, Neil and I are  not Adobe.

R Neil Haugen
Legend
May 21, 2025

I'm just puzzled you have to pay for it. Downloading from their site doesn't cost a dime on PCs.

 

And the usefulness is so we can see internal file header data. Not a normal function of Premiere.

Everyone's mileage always varies ...
Known Participant
May 21, 2025

thanks @MyerPj and @R Neil Haugen 

 

Again, I'm not looking to, as my dad would say, "pick the fly crap out of the pepper" here regarding mediainfo. I just don't see why I need to spend money to diagnose an issue that pay Adobe monthly to have a fix for.

If there's no update to Premiere that fixes this soon, and I absolutley need generative extend to work in order to complete my current edit, I'll pay the buck for the app and send you guys what it says.