Render your video in 720p before upload
Render your video in 720p before upload
Kcan't cf stream do this on its own?
1It wont if the source video is below that res
1Stream isnt a transcoding product
Kyah by default it won't but there should have been some option
1Ive been asking for that for a while lol
Kohh 
.
.1Like it does transcoding in the background, but you cant force it to render weird stuff like that
Kunderstood but they could do something like if its above 680 or something
Kin such cases 720 can be generated
Kor else there's kinda a huge difference
1where is your video coming from? Why the odd resolution
Kthe users are uploading it.
1Not sure who the Stream PM is but can someone more official confirm this?
KI thought you've confirmed it 
1As far as Im aware, but I dont work for CF
Knot much people are active in this channel
Kdid you read it somewhere in docs?
1I can't find a specific reference in the doc
KI'm not sure if they've even mentioned it in docs or not
1But I dont see any reason to waste transcode on upscaling a video very slightly. The pipeline would not be made to do so currently I would imagine
1Why would they? Its a very odd use case
Ki mean they should atleast mention that the streams will only be available in resolution <= resolution of original video
1Common sense would dictate that
Ktrue
1That specific resoluton you mentioned is an odd aspect ratio, how would you want it handled? Cropped to fit in the 720p frame, squeezed to fit, zoomed? Too many variables for what is wasted resources on tiny niche use case
Kokay, but then there should be an option to play the video in the original resolution as it was uploaded
Kapart from the degraded resolutions
1Could you link me to an m3u8 of one of your videos?
Kwe are using mpd
1Thats fine just curious what it shows
1PM if you cant share public
KI don't think I'll be able to share it since its not mine personally
Kwhat do you want to know specifically?
1I was going to try uploading my own video at 692P then compare the files
Kit just contains representation tags for 480, 360 and 240p
Kcan you try once as well?
1Will do, I wanted to compare bitrates of the encoded renditions. Lemme just encode something at that res
Kokay
Kbut there is no
Representation of the original videoKnot sure if thats how mpd files work
Ki think they have fixed set of supported resolutions
1videos aways get transcoded on Stream, no access to original as far as Im aware
Kohh
1I also only got a 480p stream max, encoded at 1.5mbps, the original was at 5mbps
1Tell your users to upload proper videos :lul:
K:face_holding_back_tears:
Sthe price for web RTC streaming is the same as stream? in the pricing page is not clear, it says
Delivery is counted by HTTP requests for video segments or parts of the MP4. Therefore:
Client-side preloading and buffering is counted as billable delivery.
Content played from client-side/browser cache is not billable, like a short looping video. Some mobile app player libraries do not cache HLS segments by default.
MP4 Downloads are billed by percentage of the file delivered.
HLS and DASH playback is rounded to the segment length. For uploaded content, HLS and DASH segments are four seconds. Live broadcast segments are determined by the keyframe interval or GOP size.
Delivery is counted by HTTP requests for video segments or parts of the MP4. Therefore:
Client-side preloading and buffering is counted as billable delivery.
Content played from client-side/browser cache is not billable, like a short looping video. Some mobile app player libraries do not cache HLS segments by default.
MP4 Downloads are billed by percentage of the file delivered.
HLS and DASH playback is rounded to the segment length. For uploaded content, HLS and DASH segments are four seconds. Live broadcast segments are determined by the keyframe interval or GOP size.
Sother technicall question, did't found a way to delete the web rtc published URL
Sin the rest API or docs
Scan anyone shrare that doc with me
