Participant

Answered

No option to select LOCATION to export

Forum|Forum|3 years ago
June 7, 2022
23 replies
14811 views

Such a funny bug. Adobe Premiere Pro 2022 doesn't show the location path option at all when I am trying to export anything. Not sure where the issue is.

And of course when I click export, I get the following error which is obvious.

Anyone has a solve to this?

Correct answer Ann Bens

Issue has been fixed.

EDIT: this issue has NOT been fixed.

Show previous replies

jacoblees

Participant

This is still occurring - was successfully sending portions of timeline to media encoder when suddenly on one the location path disappeared and the same error message came up.

Y

Yominsane

Participant

It's because the path name was too long. Create a new folder and project with a shorter project name and folder name then copy and paste your current timeline to the new one. This should work

B

BalazsT

Participating Frequently

The latest version 23.3 seems to be even worse and doesn't let me export through the Media File OR You Tube option either which used to work. 23.1 was working okay and then suddenly it wasn't. I upgraded to see if it fixes the issue but it doesn't.

I already talked to Adobe via chat a few times about this and even had a technician remotely access my computer, no success and no solution. Yet still paying full premium for monthly subscription.

SOMETIMES copying and pasting to a new sequence helps temporarily but then it happens again.

D

default0tbkh4owiwwy

Participant

I've only had this just happen to me (V23.1.0) and I think it may have been due to a long path and/or long file name.
Selecting YouTube didn't work & creating a new sequence wasn't enough. I still had to shorten the file name for it to work.
I hope this helps somebody, somewhere.

B

BalazsT

Participating Frequently

Good tip but doesn't work for me.

B

BalazsT

Participating Frequently

TEMPORARY FIX

I spent a bunch of time chatting with Adobe support about this MISSING OUTPUT LOCATION issue, and they even had two different Adobe techs remotely access my PC to check Premiere. After a bunch of fiddling around they basically said the only solution is to make a new sequence, which seems to bring the output location option back.

It's not something you're doing wrong, it's an Adobe glitch.

If you have existing stuff in your sequence, just copy and paste it into a new sequence. It's hardly a permanent solution but it works. However note that after a few months of doing that, AGAIN the location ouput field disappeared and I had to make a new sequence and paste my stuff all over again.

Another trick that worked for me was to choose the YOUTUBE output option instead of the MEDIA FILE. You do not have to click the sign-in for it to work but it will give you an error after exporting that it can't upload. Just ignore that.
This hack was working for me up until March 2023 when it suddenly didn't.
However, the new sequence method seems to work consistently.

It's a quick solution but disappointing that Adobe can't get this fixed even after a few versions since I've had the issue, up to and including March 2023.

Dear Adobe: This is premium software and we're paying a notable monthly subscription for apps and services, should have been fixed a long time ago.

B

broderod

Participant

This happens to me when I try to change the location. I have replicated it 3x. And the only way around it is to create a new sequence... Today is the first time I have had the issue. I exported a file and changed the destination in the last couple of weeks of June 2024.

Adobe -- this is an issue. Please provide a solution. TIA!

F

FanciestPhoenix

Participant

Just came across this issue today with Premiere Pro v23.1.0 (Build 86). My problem started when I had to switch what hard drive I was editing on. I copied the folder structure of all the files and the Premiere Pro-generated files exactly as they were on the previous drive. Opening a new sequence and exporting from there worked for me!

B

benc90553918

Participant

I'm having this same issue in November 2022 with Version 23.0.0

M

MattG2390

Participant

Just had the same issue.

We created a new sequence and copied the old sequence into the new one.

Simple but it worked.