Automatic filename change in Media Encoder (sent from AFX)

New Here ,
Jun 25, 2018 Jun 25, 2018

Copy link to clipboard

Copied

Hi there,

when I have a composition in AFX titled for example "composition15.0_test" and I send that to render to Media Encoder, the output filename automatically changes to "composition15-0" (hyphen instead of dot). Why and how can I disable this? Thank you.

Views

619

Likes

translate

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 18, 2018 Jul 18, 2018

Copy link to clipboard

Copied

Hello? Anyone?

Likes

translate

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Sep 28, 2018 Sep 28, 2018

Copy link to clipboard

Copied

Miorota,

That sounds odd but I can definitely reproduce it. Can you file a bug here? After Effects: Hot (895 ideas) – Adobe video & audio apps

Sorry about that.

Thanks,
Kevin

Likes

translate

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Sep 29, 2018 Sep 29, 2018

Copy link to clipboard

Copied

I confirmed that this does not happen when queuing to AME from Premiere Pro (2018.1.2). And AME will happily process the original filename once you edit it back.

Likes

translate

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Community Professional ,
Sep 29, 2018 Sep 29, 2018

Copy link to clipboard

Copied

While a period changing into a dash is unexpected, it's probably worth mentioning that unless you have a closed post production workflow (that is, your files remain internal from start to finish) that special characters of any king should be avoided (including periods).

And, yes, as long as the period is not at the beginning or the end of the filename it shouldn't cause any trouble, but I would not allow it to be used in any workflow that I oversee.

The following would also be off limits:

  • # pound
  • % percent
  • & ampersand
  • { left curly bracket
  • } right curly bracket
  • \ back slash
  • < left angle bracket
  • > right angle bracket
  • * asterisk
  • ? question mark
  • / forward slash
  •   blank spaces
  • $ dollar sign
  • ! exclamation point
  • ' single quotes
  • " double quotes
  • : colon
  • @ at sign

One disclaimer: For Mac based workflows, I allow blank spaces.

miorota, I know this is probably more than you wanted to see in a response.  I wrote this more for others who might read the post.

Likes

translate

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines