Source Range in preset suddenly changed to custom range.

Report · Oct 20, 2023

All my videos are suddenly exporting only the first minute as its default. I don't remember changing anything. Exporting used to be automatic, now I have to tweak to make sure "Entire Sequence" is selected.

Report · Oct 24, 2023

Since when is that happening? Are you aware of any changes (updates, presets, project)?

Report · Oct 24, 2023

Report · Oct 24, 2023

AME 23.6 Build 62

I did not change anything except preset name, been using the same presets for 2 years now.
I did think maybe I accidently clicked on something, but after I returned it to "Entire Sequence" it still happens on the next project.

Report · Oct 24, 2023

And it weirdly decides to export only (and exactly) the first minute - so the exported video has exactly 1:00 duration.

Report · Oct 25, 2023

Can you check in Premiere Pro if you accidentially changed the in & out points or workarea in the sequence?

Report · Oct 26, 2023

I have investigated my premiere too, and I don't use in and out points in premiere when exporting.

I export by creating a subsequence, and exporting FROM THE PROJECT WINDOW to Media Encoder. So my sequence doesn't have an In Out. I just need ME to export "The Entire Sequence" as usual, but it suddenly changed to custom. Now I always have to tweak. I have done this method of exporting for a long time, and it's the first time that this issue happened.

Report · Nov 03, 2023

This is happening to me as well, I'm on version 24.02. It wasn't happening before the 2024 update, and I haven't changed any settings or presets.

Report · Nov 05, 2023

@eckiAMETeam i do remember something that changed - I used to export subclip IN PREMIERE's "export media" window, and then click the "Send to Media Encoder" button.

Now, I have set up a keyboard shortcut that will directly put the Sequence in Media Encoder. Here's when the source range becomes "custom" instead of the preferred "Entire Sequence".

But it seems like there's no way to make Entire Sequence the default! Not in ME's Settings, not in the Preset Settings. I hope I'm wrong! Is there a way?

Report · Nov 06, 2023

I just tried to export via shortcut, and I got "Custom Source Range" but with the full length in AME. Would you be able to share your project?

Report · Nov 06, 2023

yes! that's the problem! It defaults to custom, and it seems to decide on its own the range and duration - I want it to default to "Entire Sequence" even when using the shortcut. Is there a way to do this? So far, I have found none because even if I tweak the preset, and save it again, it just goes back to defaulting to custom again.

Report · Nov 06, 2023

For me it did use the correct sequence length.

Report · Nov 08, 2023

Ok, but I do not have the chance to dictate the source range if I'm using the shortcut, instead, I need to tweak it in ME, which defeats the purpose of creating a shortcut! My question is - is there a way to make "Entire Sequence" (or any range) a default? So that your customers can operate with less clicks.

Report · Nov 09, 2023

Are you saying the behavior changed comparing to previous releases?

Report · Nov 09, 2023

Yes, but that's for a different thread (you've already replied to my other problem)

For this thread, it's my behavior that's changed. I'm aware I might have caused a confusion earlier because I have forgotten that it is just recently that I started using the shortcut for "Send to Adobe Media Encoder" in Premiere.

Let me try again.
1. When I export in Premiere, I used to go the Export window, and then click the "Media Encoder" button, which then sends my sequence to AME. There are no issues here. I've used the same preset over and over again, and the source range is "Entire Sequence" This used to work very very well.
2. But then I learned to use the shortcut for "Send to Adobe Media Encoder" - which is supposed to make my workflow faster, but by default, the source range is "custom" in AME, which causes me to export the wrong range! I then have to tweak the preset again to "Entire Sequence" which doesn't make sense because it defeats the purpose of using a shortcut.

Is there a way to make "Entire Sequence" the default source range, even if I'm using the shortcut?

Report · Nov 13, 2023

The default behavior should be to export the whole sequence except if there is an in and out point set. If that is not the case, I would consider this a bug. Moving this item to Premiere Pro and letting our friends know.

Report · Nov 14, 2023

Premiere Pro Team just let me knoow that the issue has been fixed in PPro Beta 24.1x72. Please give it a try.

Report · Nov 14, 2023

Oh wow! thanks for that, and so did they actually find a problem that matches with mine? Ok I will! I'm Ijust a little intimidated by using Beta right now because I have done so before, and migrating my shortcuts was quite fiddly. But this fix usually makes it to the regular Premiere right?

Report · Nov 15, 2023

Luis,

A bit re the Beta versions....

The Beta can be installed independently from your production version(s). You do so from the regular CC Desktop.

Note that the current Beta (24.2.0 Build xx) is the PR project file version 42, which is the same used for the newer release version 24. The release PR 2023.x (what I think you are currently using) is project file version 41. This means that you cannot open a Beta version file in the release version.

See the Beta FAQs:

https://helpx.adobe.com/x-productkb/global/creative-cloud-beta.html

I do not recommend using the Beta version for deadline-sensitive work, but many users use it successfully. The Beta version often works very well. But there are also regular bugs, some of which make the version unusable until the next build, or less commonly, more than one build. Builds appear most, but not all, days.

You can only install the latest version of the Beta, and cannot roll back to a previous version. In the release versions, even though it is easier to roll back, I create a clone of my system drive so I can roll back everything.

Stan

Report · Nov 15, 2023

Thank you Stan, will keep this in mind!

I do am interested in seeing if the problem is fixed in Beta, but also, I'm willing to just wait it out til the bug fix makes it to the next regular Premiere.

Regarding that, does Adobe need my feedback in order for them to move the fix?

Report · Nov 15, 2023

It will move into the stable release in the future.

Report · Nov 22, 2023

Good day. I have updated Premiere to Version 24.0.3 (Build 2), and my problem still persists. Has the fix moved to this version yet, or will it be in the future?

Report · Nov 22, 2023

The fix will be in a future version very soon. Stay tuned!

Report · Dec 12, 2023

Bro thanks for you help. It's my first time to see my issue specifically get resolve and actually make it to the release notes! Great customer experience!

Report · Dec 13, 2023

Thanks for your great feedback and for helping us make our products better!