Skip to main content
braydon
Inspiring
December 27, 2022
解決済み

I can't do what I need to by making Proxies the normal way - what's a work-around?

  • December 27, 2022
  • 返信数 4.
  • 633 ビュー

I'm working with XAVC SI footage shot on  SonyA7S3 at 50fps, on a 25p timeline. I want to slow the footage down so it plays at half-speed, but am hitting a wall of problems. I've been hitting my head against this issue for some years now, figure it's time to ask the community for help.

  • My PC extremely powerful, but just can't handle playing/scrubbing through/editing with XAVC SI clips in Premiere, no matter the frame-rate.
  • If the clips were recorded at 25p I can easily create proxies (ProRes Medium Resolution Proxy option in the Ingest Settings) and work with them, no problems at all.
  • But if the clips were shot at a different frame-rate (eg. 50p), I cannot for the life of me create a proxy that exports at that framerate. No matter how I configue the Ingest Settings, or Media Encoder, or Render & Replace, and set the files to be exported as 50p, the final product is ALWAYS 25p. 
  • It's a known issue that proxies created using the Ingest Settings are useless for footage that was shot off-speed. Adobe have been sitting on this problem since Proxies became a thing, and have seemingly have no intention of addressing it.
  • I know how to Interpret Footage and get 50p footage to play at 25p. But that's not the issue. I need the footage to be transcoded into ProRes to be at all usable with my computer, and that's where I'm getting stuck.
  • I also know I could Interpret Footage to get the clips to 25p, plonk them on the timeline and then use the work area to export each clip individually as ProRes, but I have several cards worth of clips shot at 50p that I need to work with, and need to retain the original clip names. It will be very tedious to export several hundred clips this way, one by one (even if I queue them in the media encoder first). Does anybody know a way to do a batch export for off-speed clips that will retain the original clip names???
  • FYI - these work-arounds don't work. https://www.youtube.com/watch?v=ZdE7OIkgzRchttps://www.youtube.com/watch?v=PRRGRa4TvDU; https://www.youtube.com/watch?v=ClsiT2zZPWw They either export off-speed clips as their original duration and speed but drop every second frame to make a 50p clip into a 25p clip (the opposite of what I want), or they completely rename the clips. I need to retain every frame, and the file name.

 

Surely by now there's a simple way to do this???

このトピックへの返信は締め切られました。
解決に役立った回答 braydon

Thanks all for your suggestions. @basil1891  - that video just changed my life! For the most part, it has fixed my problem. Using 'Interpret Footage' to slow my clips down was indeed playing havoc with my proxy workflow. Both you and @R Neil Haugen are right: Speed/Duration is what I need to be using.

 

That said, this has only fixed the second half of the problem. That youtube video says you can generate off-speed proxies straight from the 'Create Proxy' function, but in my experience it just doesn't. I've tried using the 'match source' settings, I've tried creating my own encode presets in Media Encoder that are manually set to create 50p proxies. Nothing has ever worked. The proxies always, always end up as 25p files. It's just so dispairing to waste entire days of an edit trying to get the Create Proxies function to actually match the original framerate. This in itself was my original question, but I probably confused the issue by throwing in too much of my workflow process and demonstrating I was doing something else wrong.

 

The good news? I've just managed to find a simple way to batch transcode clips into low resolution ProRes files that can be attached as proxies, whilst retaining the same framerate and file name. The clue was right there in one of those videos I said didn't work, but the video was tackling the problem from a different angle, making nested clips on the timeline, etc, which I didn't need to do in the first place.

 

This was my solution:

  • Shift-select all the 50p clips from the bins in the Project panel.
  • Right click > Export Media...
  • In the export settings, choose ProRes 422 and manually set the resolution to 'HD' (1280x720)
  • I also manually set the frame rate to 50p, just to be sure, but probably could have left it as 'Based on source'
  • > "Send to Media Encoder" and start the queue once all the clips are ready.

 

Voila, a few hours later there'll be proxy-quality clips with the same name and the same frame-rate as the original, without me having to put them on the timeline, manually re-time them or manually name them. Super simple, and I can't believe I didn't know I could export clips directly from the Project panel without them needing to go on the timeline first. Now I know.

 

Initially I'd tried to attach these new "proxies" to clips that had been slowed down using the Interpret Footage function, and it didn't work. But after viewing the video suggested by @basil1891 I returned the interpreted clips to their original state and used the Speed/Duration to slow them them down, and the attached "proxies" now play perfectly. A large part of the problem has been solved.

 

But if anyone has any ideas why my Create Proxies function insists on generating 25p files despite my every attempt at forcing it to make 50p proxies, I'd love to know!

返信数 4

braydon
braydon作成者解決!
Inspiring
December 28, 2022

Thanks all for your suggestions. @basil1891  - that video just changed my life! For the most part, it has fixed my problem. Using 'Interpret Footage' to slow my clips down was indeed playing havoc with my proxy workflow. Both you and @R Neil Haugen are right: Speed/Duration is what I need to be using.

 

That said, this has only fixed the second half of the problem. That youtube video says you can generate off-speed proxies straight from the 'Create Proxy' function, but in my experience it just doesn't. I've tried using the 'match source' settings, I've tried creating my own encode presets in Media Encoder that are manually set to create 50p proxies. Nothing has ever worked. The proxies always, always end up as 25p files. It's just so dispairing to waste entire days of an edit trying to get the Create Proxies function to actually match the original framerate. This in itself was my original question, but I probably confused the issue by throwing in too much of my workflow process and demonstrating I was doing something else wrong.

 

The good news? I've just managed to find a simple way to batch transcode clips into low resolution ProRes files that can be attached as proxies, whilst retaining the same framerate and file name. The clue was right there in one of those videos I said didn't work, but the video was tackling the problem from a different angle, making nested clips on the timeline, etc, which I didn't need to do in the first place.

 

This was my solution:

  • Shift-select all the 50p clips from the bins in the Project panel.
  • Right click > Export Media...
  • In the export settings, choose ProRes 422 and manually set the resolution to 'HD' (1280x720)
  • I also manually set the frame rate to 50p, just to be sure, but probably could have left it as 'Based on source'
  • > "Send to Media Encoder" and start the queue once all the clips are ready.

 

Voila, a few hours later there'll be proxy-quality clips with the same name and the same frame-rate as the original, without me having to put them on the timeline, manually re-time them or manually name them. Super simple, and I can't believe I didn't know I could export clips directly from the Project panel without them needing to go on the timeline first. Now I know.

 

Initially I'd tried to attach these new "proxies" to clips that had been slowed down using the Interpret Footage function, and it didn't work. But after viewing the video suggested by @basil1891 I returned the interpreted clips to their original state and used the Speed/Duration to slow them them down, and the attached "proxies" now play perfectly. A large part of the problem has been solved.

 

But if anyone has any ideas why my Create Proxies function insists on generating 25p files despite my every attempt at forcing it to make 50p proxies, I'd love to know!

R Neil Haugen
Legend
December 27, 2022

You might be using the wrong process for the speed change.

 

Interpret Footage is supposedly meant for say when the cadence changes, as per 23.997 to 29.96 or so.

 

Use Speed/Duration to set the speed change on the original footage, then make the proxies. That's always worked to mod the original framerate then make proxies.

 

Neil

Everyone's mileage always varies ...
Legend
December 27, 2022

just a shot in the dark, but see if your footage is something different from rec709.   I went thru a lot of craziness with material shot on a sony camera (not sure which one) which was solved by selecting the clip(s) in the project, right clicking and choosing modify: interpret footage:  color management: and if it's not rec709, enable color space override to rec709.  Worth a shot.  Also which version of Premiere are you using.  The last few years of updates have vastly improved proxy workflow.  Used to be a serious issue with many sony formats.  Also, if you can manually create lower res proxies, you can unlink to the camera original and relink to the lower res files for your edit and then relink to the camera original when ready to output.  Not ideal, but it does work...  at least it worked for me when Premiere was unable to create attachable proxies with sony material because of some sort of proprietary format for the 8 channels of audio.  Let us know if any of this helps...

Legend
December 27, 2022

and if you try the unlink, relink workflow, probably smartest to test the workflow to make sure the relink back to the camera original works.  Always a good idea to test a new workflow before going to far down the rabbit-hole.

Inspiring
December 27, 2022

Not 100% sure if I got your issue exactly, but since it's about slow motion/proxy/interpret footage combo, check this vid first: https://www.youtube.com/watch?v=LDO9RIA_g2Y.  And in case it does not work, maybe it'd be easier and faster to use 3rd party tools (freeware) to solve it. I can assist a bit if you are ready to go that route.