Skip to main content
Known Participant
December 8, 2017
Answered

Publish to Youtube setting in Encoder is no longer working. Anyone else have this issue?

  • December 8, 2017
  • 2 replies
  • 1782 views

Hello!

I publish directly to Youtube a lot in Media Encoder. It used to work like a charm but ever since installing CC 2018, it fails almost every time.

When I look at the Error Log, it tells me that its because I wasn't logged in or had invalid credentials which isn't true. I have logged in and out and even re-installed 2018 Encoder.

Anyone else have this issue and or have a solution?

Thanks!

This topic has been closed for replies.
Correct answer kulpreet singh

Hi Da Volcano,

We found an issue here that using old preset from previous version cannot keep you logged into YouTube.

The workaround is either not to use old preset or to create new preset NOT based on old preset.  If you are creating a new preset in the Preset Browser, please make sure you are not selecting any old YouTube preset under "Based on Preset" menu.

Hope this helps!

Thanks,

Kulpreet Singh

2 replies

kulpreet singh
Inspiring
January 5, 2018

Hi Da Volcano,

Can you please confirm if the issue that you were facing has been resolved or not?

Thanks,

Kulpreet Singh

Participating Frequently
April 18, 2018

Kulpreet Singh, do you have an answer to Da Volcano's latest question? I am still unable to upload to YouTube even with your suggestions.

kulpreet singh
kulpreet singhCorrect answer
Inspiring
December 8, 2017

Hi Da Volcano,

We found an issue here that using old preset from previous version cannot keep you logged into YouTube.

The workaround is either not to use old preset or to create new preset NOT based on old preset.  If you are creating a new preset in the Preset Browser, please make sure you are not selecting any old YouTube preset under "Based on Preset" menu.

Hope this helps!

Thanks,

Kulpreet Singh

Participant
August 3, 2018

I'm also facing this issue with Premiere Pro CC 2018. Has this been resolved in an update or will this be resolved in an upcoming update? Looking forward to your response.