Closed damechen closed 3 years ago
Thanks @damechen if you create the Mux asset directly like the request below, does the same issue happen? Curious if this is an issue with UpChunk or if this issue should be tracked somewhere else.
curl https://api.mux.com/video/v1/assets \
-H "Content-Type: application/json" \
-X POST \
-d '{ "input": "{URL_TO_FILE}", "playback_policy": ["public"] }'
-H "Content-Type: application/json" \
-u ${MUX_TOKEN_ID}:${MUX_TOKEN_SECRET}
Would you be able to send me a video file that reproduces the issue? I'd love to dig in more.
Thank you so much Dylan!!!
I tried stream.new and the same issue occurred.
Since it's one of my customer's file, I can't make it public here. Let me send you the link to your Twitter DM.
Also, for the curl
command, what if the video file is on my local machine, and I don't have URL for it, how to use it to upload the file?
Yep, please DM or email me the file. If you can get it on Dropbox then a Dropbox URL will work!
Just sent you the Twitter DM, pls check
Closing because this is not an Upchunk specific issue, confirmed it happens when passing this video file as an "input"
param
Step to repro: