search

bitmovin / bitmovin-javascript

DEPRECATED: JavaScript client for the Bitmovin API, see https://github.com/bitmovin/bitmovin-api-sdk-javascript
MIT License
67 stars 23 forks source link

After running the node file to run encoding on bitmovin cloud I get error 404? #100

Closed svidata closed 3 years ago

svidata commented 5 years ago

So I am using the client node js to run the encoding of the test mp4 provided by bitmovin, I followed the demo that is presented by bitmovin. But after running the node js file I get an error 404 http. The error starts after I set the input path and at the part where I start adding the streams.

Now I have this issue can someone please help?

I have other questions as I don't know where to ask the bitmovin team:

1) Why I cant just encode a mp4 file without implementing a client code?

2) after I encoded test file using the UI provided by bitmovin to test encoding, I cant find anything in output tab.....it seems broken (has a 404 error)?

Thanks for your help.

SInCE commented 5 years ago

Hi Svidata,

thanks for reaching out!

Why I cant just encode a mp4 file without implementing a client code?

There is no UI available at the moment to handle the encoding in the same as with our API clients at the moment. Our service is API based in order to be integrated your current workflow or new project. Therefore we offer many API clients in different languages so the development and integration can start right away.

after I encoded test file using the UI provided by bitmovin to test encoding, I cant find anything in output tab.....it seems broken (has a 404 error)?

Outputs listed in the dashboard are configurations that are used by an encoding to know which Storage of yours it should use and how to access it in order to push the encoded content to it. Typically cloud storages like AWS S3, Google Cloud Storage are used and highly recommended as they provide a really good performance especially in terms of upload and download performance.

It would be great if you can share the ID of the encoding and the example you used (please strip your private credentials) with our support team, either via the chat in the bottom right corner of the dashboard, or via email to support@bitmovin.com. Then they can check further what could have caused your failed encoding attempt :)