Addressing Limits on Proxy Workflow - "Modify" clip command

Thanks, R Neil Haugen,

Once again, you've posted the exact single reference which started this thread.

And while you have confirmed that no one in the thread has said they "don't see anything", you have provided a vivid example of how hearsay develops through personal interpretation and why solid documentation is necessary, so thanks for that.

R.

Thanks for the follow up. The references you've posted do not offer any insight or elaboration of the differences between Interpret Footage and Speed effects.

"Adobe Long-form and Episodic Best Practices Guide [Adobe]"

I've been going through this document - the only reference to "Interpret Footage" in the entire 140 page document is the one I've quoted above, which began this thread.

"Jarle’s blog expansion of the pdf Multicam section: Premiere Pro Multi-Cam [PremierePro.net]"

A search of this article for "speed" and/or "interpret" returns zero hits. It appears to be about multi-cam workflows.

In the Introduction, the first mention ... is do NOT use merged clips to join video/audio, as that is both common and leads to major problems ... something that many users still need to know.

Then the entire Chapter 5 is about proxies, and on page 55, as noted in the TOC for that chapter,  is the following ... 

Additional Considerations When Using Proxies in Premiere Pro Modifying Clips

(Audio Channels, Interpret Footage, etc�)

If your workflow relies on modifying the source clips using any of the following commands, do not use proxies in Premiere Pro. Doing so will result in unexpected behavior:
Modify > Audio Channels

Modify > Interpret Footages

Modify > Timecode

Modify > Captions

"I could post the quote if you need of course"

Please do.

R.

You might look up to one of your own posts a bit above this ... which is what I referred to.

I could post the quote if you need of course ... but it's your post.

"I'm puzzled you say you don't see anything."

No one in the thread has said this.

R.

 I think most users would really love better overall documentation. Maybe not the 4,000 plus page Resolve manual ... which not only is HUGE, but uses such Resolve specfic terminology that unless you know exactly what they call something in their unique lexicon, you can't find it.

You know it's there, somewhere ... but ... where?!

The docs I linked above do cover the use of Speed/Duration, rather than Modify/Interpret, and the limitations of the latter. Very clearly, right off the bat in fact. As does Jarle's follow-on expansion post, so I'm puzzled you say you don't see anything. It's one of the few pieces of documentation they have that's actually decent.

Now, their suggestion is not what many users want to hear, but hey, I can't help with peoples emotions. Just the practical stuff of what does work versus what ain't gonna.

As to listing devs by name, if you have much professional pro video experience, you would probably understand that is normally considered a HUGE professional faux pax. And actually, I'm one that does occasionally, when the item is a major one, and the source was clearly talking 'in the open' with others listening, list the name of the source.

Which is why ... apparently ... I'm no longer an ACP or AC Expert or whatever they call their volunteer group anymore. One dev asked me to get people to connect with him over one issue, so ... I mentioned that online. All Hades broke loose ... twas kinda funny in a weird sort of way. And I got notably dumped.

"the online user guide existed before the introduction of the Proxy Workflow"

Premiere Pro also existed before the Proxy Workflow.

The difference is that Adobe puts resources into maintaining, updating, and improving Premiere Pro. Though they haven't addressed the limitations of proxy workflow since it was introduced.

Thus, my 2 requests in the headline post from February, both of which have gone unanswered.

R.

Yes, the online user guide existed before the introduction of the Proxy Workflow.  

For those not using a proxy workflow (for example, someone with a 2160p ProRes 422 HQ workflow on a Mac from 2017 or later with Thinderbolt storage probably does not need to think about proxies), then a user just needs the information from the corresponding sections.

Some type of caution that might adversely affect the Proxy Workflow sounds like it would be very good addition to the documentation beyond what's currently there.  I've upvoted this topic.  It would even be a great in-app feature request where when proxies are enabled any non-reomended options are flagged in some way.

Personally, I wish tbe Premiere Pro user guide was more like the Final Cut Pto classic user guide.  That was part user guide and part 2,000 plus pages of editing wisdom.

Premiere Pro's built-in proxy workflow was introduced in 2016.

You suggest as a possible explanation that Adobe publishes documentation "written before the Proxy Workflow was available".

It may be true, or it may be simply that it strikes users like me as credible conjecture that Adobe hasn't updated parts of its documentation in 7 years.

And yet they don't even maintain documentation for last year's version.

R.

There are definately sections of the user guide guide that could use something along the lines of "Caution:  This is not supported by the Premiere Pro Proxy Workflow."  As best as I can tell, it's sections that were written before the Proxy Workflow was available.