Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Media Services 3.5.2.0: Unknown media processor exception #178

Open
Rookian opened this issue Apr 27, 2017 · 3 comments
Open

Media Services 3.5.2.0: Unknown media processor exception #178

Rookian opened this issue Apr 27, 2017 · 3 comments

Comments

@Rookian
Copy link

Rookian commented Apr 27, 2017

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?

@Juliako
Copy link
Contributor

Juliako commented Apr 28, 2017

Hi, please switch to Media Encoder Standard, and update the preset.

Here is the documentation: https://docs.microsoft.com/en-us/azure/media-services/media-services-dotnet-encode-with-media-encoder-standard

@Juliako
Copy link
Contributor

Juliako commented Apr 28, 2017

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.

@Rookian
Copy link
Author

Rookian commented Apr 28, 2017

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants