You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error message: Unknown media processor: 'Windows Azure Media Encoder'
Parametername: mediaProcessorName
Code:
var job = _mediaContext.Jobs.CreateWithSingleTask(MediaProcessorNames.WindowsAzureMediaEncoder,
configuration, asset, $"{asset.Name}_encoded",
AssetCreationOptions.None);
I am using the MediaProcessorNames class with the already predefined media processor names (WindowsAzureMediaEncoder). I did not change any code and the code did work several months ago.
Did you change something?
The text was updated successfully, but these errors were encountered:
Also, can you please share the configuration preset that you are using
var job = _mediaContext.Jobs.CreateWithSingleTask(MediaProcessorNames.WindowsAzureMediaEncoder, configuration, asset, $"{asset.Name}_encoded",
AssetCreationOptions.None);
Media Encoder Standard (MES) uses a new encoding schema. You will need to change the encoding preset (“configuration” in the sample code snippet you shared) to use the new schema.
Thank you for your reply. I could fix the problem.
The question is why do you break running clients? What is the approach to run an Azure Media Service in production? Do we really need to subscribe your news feed and update our clients when you introduce breaking changes? (We were still running on 3.5.2)
Error message: Unknown media processor: 'Windows Azure Media Encoder'
Parametername: mediaProcessorName
Code:
I am using the
MediaProcessorNames
class with the already predefined media processor names (WindowsAzureMediaEncoder
). I did not change any code and the code did work several months ago.Did you change something?
The text was updated successfully, but these errors were encountered: