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
At first glance, at least how we're calling its API, Elemental Conductor doesn't seem to allow existing presets to be updated. When using the transcoding API to create/update existing presets in Elemental, we get the error Name has already been taken.
We should investigate if we're calling Elemental's API the wrong way. If not, we should mimic what Encoding.com does, which is to override the existing one.
The text was updated successfully, but these errors were encountered:
flavioribeiro
changed the title
Updating presets that already exist doesn't work for Elemental
Updating presets that already exists doesn't work for Elemental
Oct 26, 2016
flavioribeiro
changed the title
Updating presets that already exists doesn't work for Elemental
elemental updating presets that already exists is not working
Nov 1, 2016
flavioribeiro
changed the title
elemental updating presets that already exists is not working
elemental: updating presets that already exists is not working
Nov 1, 2016
flavioribeiro
changed the title
elemental: updating presets that already exists is not working
provider/elemental: updating presets that already exists is not working
Nov 15, 2016
At first glance, at least how we're calling its API, Elemental Conductor doesn't seem to allow existing presets to be updated. When using the transcoding API to create/update existing presets in Elemental, we get the error
Name has already been taken
.We should investigate if we're calling Elemental's API the wrong way. If not, we should mimic what Encoding.com does, which is to override the existing one.
The text was updated successfully, but these errors were encountered: