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
I know this is possible as WarpStream does it just fine. This would also resolve timeouts when some clients try to play long videos over the API. Effectively, data would be served as it was written to the file. If playback caught up to conversion, the instance would serve data at a lower rate or stop serving data if conversion had (for some reason) halted entirely. Any good gdata-based client would perceive this as a slow connection and show a loading screen accordingly.
The text was updated successfully, but these errors were encountered:
realistically this would only work with 360p and newer android versions (4.4+) as it's the only itag that still has audio & video in a single file. gdata apps (and most yt flash players) didn't support DASH.
older android versions (around 4.2) also need the video to be reencoded to actually start playback (h264 main profile -> h264 baseline profile). such encoded videos aren't sent by youtube servers, thus the need to do that locally after downloading the video first.
multiple attempts were carried out at streaming over this project's existence with mixed results, such as broken seeking.
I know this is possible as WarpStream does it just fine. This would also resolve timeouts when some clients try to play long videos over the API. Effectively, data would be served as it was written to the file. If playback caught up to conversion, the instance would serve data at a lower rate or stop serving data if conversion had (for some reason) halted entirely. Any good gdata-based client would perceive this as a slow connection and show a loading screen accordingly.
The text was updated successfully, but these errors were encountered: