question

jhodges avatar image
0 Votes"
jhodges asked ajkuma-MSFT commented

BuiltInStandardEncoderPreset with custom output file name

I am using a transform to convert a source MP4 file ready for adaptive streaming. I am using the AdaptiveStreaming BuiltInStandardEncoderPreset. This is working well however I'd like to customise the auto-generated output file names. Is this possible?

azure-media-services
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JonPayne-8781 avatar image
0 Votes"
JonPayne-8781 answered
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

jhodges avatar image
0 Votes"
jhodges answered ajkuma-MSFT commented

I've tried specifying the filenamePattern when using the BuiltInStandardEncoderPreset and it doesn't work.

That example you've referenced uses the StandardEncoderPreset not the BuiltInStandardEncoderPreset. Using the StandardEncoderPreset forces me to define all the output resolutions myself. I just want exactly what BuiltInStandardEncoderPreset.AdaptiveStreaming is doing but with the ability to change the output file.

As a workaround is there some documentation on how to use StandardEncoderPreset to produce the same behavior as uiltInStandardEncoderPreset.AdaptiveStreaming?

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for the follow-up and sharing additional info. I'm checking on this internally and will follow-up shortly.

~I still leave this open for other community members/SMEs to share their insights.

0 Votes 0 ·

Thank you for clarifying this use-case. Unfortunately, custom output filenames are not currently supported when using the built-in presets.

0 Votes 0 ·

jhodges, Just adding to JonPayne-8781.

Built-In presets, as the name implies, were designed as readymade presets, and as such provide limited configurability options. Having said that, our product engineering team is working on filename customization for built-in presets, but there is no exact ETA to share on this yet.

Your feedback on this is much appreciated. Please be assured that your feedback has been shared internally to our teams.

If you wish you may also share your feedback on this on our Uservoice - All of the feedback, you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure. Also, users with a similar request, can up-vote you post and add their comments.



To benefit the community find the right answers, please do mark the post which was helpful by clicking on Accept Answer’ & ‘Up-Vote’.

0 Votes 0 ·