The YouTube iframe API serves up streams at resolutions that will not playback over cellular
up vote
0
down vote
favorite
I sincerely hope that the YouTube API team will address this issue:
YouTube has disabled the ability to request a specific size using the setPlaybackQuality() method.
If i am correct, the YouTube iframe API automatically determines the appropriate resolution / size to serve up (small, medium, large, hd720 etc) depending upon the pixel dimensions of the embedded player.
This is a HUGE problem over cellular networks.
AT&T, Verizon, TMobile and others have all begun to throttle video streams and / or disable playback all together in some cases for streams above 480p.
In our case, we are seeing 1.5 - 2 minutes of buffering before playback in the embedded YouTube player at widths above 360px.
In portrait mode this limit would at least be somewhat acceptable, but in fullscreen landscape on mobile, the preferred method for watching video, YouTube changes the quality automatically and in most cases serves up HD720p which almost immediately becomes stuck in buffering mode over cellular connections.
TO FIX: We DESPERATELY need the ability to request a specific resolution, and/or we need YouTube to serve up video at 480p over cellular connections.
ANY HELP from YouTube on this would be greatly appreciated.
youtube-api asked Nov 8 at 9:54
Mike Someone
146414
add a comment |
up vote
0
down vote
favorite
I sincerely hope that the YouTube API team will address this issue:
YouTube has disabled the ability to request a specific size using the setPlaybackQuality() method.
If i am correct, the YouTube iframe API automatically determines the appropriate resolution / size to serve up (small, medium, large, hd720 etc) depending upon the pixel dimensions of the embedded player.
This is a HUGE problem over cellular networks.
AT&T, Verizon, TMobile and others have all begun to throttle video streams and / or disable playback all together in some cases for streams above 480p.
In our case, we are seeing 1.5 - 2 minutes of buffering before playback in the embedded YouTube player at widths above 360px.
In portrait mode this limit would at least be somewhat acceptable, but in fullscreen landscape on mobile, the preferred method for watching video, YouTube changes the quality automatically and in most cases serves up HD720p which almost immediately becomes stuck in buffering mode over cellular connections.
TO FIX: We DESPERATELY need the ability to request a specific resolution, and/or we need YouTube to serve up video at 480p over cellular connections.
ANY HELP from YouTube on this would be greatly appreciated.
youtube-api asked Nov 8 at 9:54
Mike Someone
146414
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I sincerely hope that the YouTube API team will address this issue:
YouTube has disabled the ability to request a specific size using the setPlaybackQuality() method.
If i am correct, the YouTube iframe API automatically determines the appropriate resolution / size to serve up (small, medium, large, hd720 etc) depending upon the pixel dimensions of the embedded player.
This is a HUGE problem over cellular networks.
AT&T, Verizon, TMobile and others have all begun to throttle video streams and / or disable playback all together in some cases for streams above 480p.
In our case, we are seeing 1.5 - 2 minutes of buffering before playback in the embedded YouTube player at widths above 360px.
In portrait mode this limit would at least be somewhat acceptable, but in fullscreen landscape on mobile, the preferred method for watching video, YouTube changes the quality automatically and in most cases serves up HD720p which almost immediately becomes stuck in buffering mode over cellular connections.
TO FIX: We DESPERATELY need the ability to request a specific resolution, and/or we need YouTube to serve up video at 480p over cellular connections.
ANY HELP from YouTube on this would be greatly appreciated.
youtube-api asked Nov 8 at 9:54
Mike Someone
146414
I sincerely hope that the YouTube API team will address this issue:
YouTube has disabled the ability to request a specific size using the setPlaybackQuality() method.
If i am correct, the YouTube iframe API automatically determines the appropriate resolution / size to serve up (small, medium, large, hd720 etc) depending upon the pixel dimensions of the embedded player.
This is a HUGE problem over cellular networks.
AT&T, Verizon, TMobile and others have all begun to throttle video streams and / or disable playback all together in some cases for streams above 480p.
In our case, we are seeing 1.5 - 2 minutes of buffering before playback in the embedded YouTube player at widths above 360px.
In portrait mode this limit would at least be somewhat acceptable, but in fullscreen landscape on mobile, the preferred method for watching video, YouTube changes the quality automatically and in most cases serves up HD720p which almost immediately becomes stuck in buffering mode over cellular connections.
TO FIX: We DESPERATELY need the ability to request a specific resolution, and/or we need YouTube to serve up video at 480p over cellular connections.
ANY HELP from YouTube on this would be greatly appreciated.
youtube-api youtube-api asked Nov 8 at 9:54
Mike Someone
146414
asked Nov 8 at 9:54
Mike Someone
146414
asked Nov 8 at 9:54
Mike Someone
146414
asked Nov 8 at 9:54
Mike Someone
146414
asked Nov 8 at 9:54
Mike Someone
146414
146414
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
The suggestedQuality parameter of player.setPlaybackQuality(suggestedQuality:String):Void determines appropriate playback quality not only depending upon the pixel dimensions of the embedded player, but actually varies for different users, videos, systems and other playback conditions.
Setting the parameter value to default instructs YouTube to select the most appropriate playback quality.
YouTube selects the appropriate playback quality. This setting effectively reverts the quality level to the default state and nullifies any previous efforts to set playback quality using the
cueVideoById,loadVideoByIdorsetPlaybackQualityfunctions.
I assume this also takes mobile connections into consideration, but if you believe there is an issue on this API feature, you can contact YouTube here.
answered Nov 9 at 13:22
droidBomb
50115
I could be mistaken, but i believe thesetPlaybackQuality()method is now ignored. Regardless, i have tried using this method anyway, and still i am seeing the player attempt to load HD720p over cellular, and testing has shown that AT&T and Verizon are blocking and/or throttling video streams above 480p. In testing we loaded the same player over AT&T and TMobile. Over AT&T the video is throttled and will not play, while over TMobile, the video played without issue. I did create an issue for this as well at YouTube. Hoping for a response.
– Mike Someone
yesterday
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The suggestedQuality parameter of player.setPlaybackQuality(suggestedQuality:String):Void determines appropriate playback quality not only depending upon the pixel dimensions of the embedded player, but actually varies for different users, videos, systems and other playback conditions.
Setting the parameter value to default instructs YouTube to select the most appropriate playback quality.
YouTube selects the appropriate playback quality. This setting effectively reverts the quality level to the default state and nullifies any previous efforts to set playback quality using the
cueVideoById,loadVideoByIdorsetPlaybackQualityfunctions.
I assume this also takes mobile connections into consideration, but if you believe there is an issue on this API feature, you can contact YouTube here.
answered Nov 9 at 13:22
droidBomb
50115
I could be mistaken, but i believe thesetPlaybackQuality()method is now ignored. Regardless, i have tried using this method anyway, and still i am seeing the player attempt to load HD720p over cellular, and testing has shown that AT&T and Verizon are blocking and/or throttling video streams above 480p. In testing we loaded the same player over AT&T and TMobile. Over AT&T the video is throttled and will not play, while over TMobile, the video played without issue. I did create an issue for this as well at YouTube. Hoping for a response.
– Mike Someone
yesterday
add a comment |
up vote
0
down vote
The suggestedQuality parameter of player.setPlaybackQuality(suggestedQuality:String):Void determines appropriate playback quality not only depending upon the pixel dimensions of the embedded player, but actually varies for different users, videos, systems and other playback conditions.
Setting the parameter value to default instructs YouTube to select the most appropriate playback quality.
YouTube selects the appropriate playback quality. This setting effectively reverts the quality level to the default state and nullifies any previous efforts to set playback quality using the
cueVideoById,loadVideoByIdorsetPlaybackQualityfunctions.
I assume this also takes mobile connections into consideration, but if you believe there is an issue on this API feature, you can contact YouTube here.
answered Nov 9 at 13:22
droidBomb
50115
I could be mistaken, but i believe thesetPlaybackQuality()method is now ignored. Regardless, i have tried using this method anyway, and still i am seeing the player attempt to load HD720p over cellular, and testing has shown that AT&T and Verizon are blocking and/or throttling video streams above 480p. In testing we loaded the same player over AT&T and TMobile. Over AT&T the video is throttled and will not play, while over TMobile, the video played without issue. I did create an issue for this as well at YouTube. Hoping for a response.
– Mike Someone
yesterday
add a comment |
up vote
0
down vote
up vote
0
down vote
The suggestedQuality parameter of player.setPlaybackQuality(suggestedQuality:String):Void determines appropriate playback quality not only depending upon the pixel dimensions of the embedded player, but actually varies for different users, videos, systems and other playback conditions.
Setting the parameter value to default instructs YouTube to select the most appropriate playback quality.
YouTube selects the appropriate playback quality. This setting effectively reverts the quality level to the default state and nullifies any previous efforts to set playback quality using the
cueVideoById,loadVideoByIdorsetPlaybackQualityfunctions.
I assume this also takes mobile connections into consideration, but if you believe there is an issue on this API feature, you can contact YouTube here.
answered Nov 9 at 13:22
droidBomb
50115
The suggestedQuality parameter of player.setPlaybackQuality(suggestedQuality:String):Void determines appropriate playback quality not only depending upon the pixel dimensions of the embedded player, but actually varies for different users, videos, systems and other playback conditions.
Setting the parameter value to default instructs YouTube to select the most appropriate playback quality.
YouTube selects the appropriate playback quality. This setting effectively reverts the quality level to the default state and nullifies any previous efforts to set playback quality using the
cueVideoById,loadVideoByIdorsetPlaybackQualityfunctions.
I assume this also takes mobile connections into consideration, but if you believe there is an issue on this API feature, you can contact YouTube here.
answered Nov 9 at 13:22
droidBomb
50115
answered Nov 9 at 13:22
droidBomb
50115
answered Nov 9 at 13:22
droidBomb
50115
answered Nov 9 at 13:22
droidBomb
50115
50115
I could be mistaken, but i believe thesetPlaybackQuality()method is now ignored. Regardless, i have tried using this method anyway, and still i am seeing the player attempt to load HD720p over cellular, and testing has shown that AT&T and Verizon are blocking and/or throttling video streams above 480p. In testing we loaded the same player over AT&T and TMobile. Over AT&T the video is throttled and will not play, while over TMobile, the video played without issue. I did create an issue for this as well at YouTube. Hoping for a response.
– Mike Someone
yesterday
add a comment |
I could be mistaken, but i believe thesetPlaybackQuality()method is now ignored. Regardless, i have tried using this method anyway, and still i am seeing the player attempt to load HD720p over cellular, and testing has shown that AT&T and Verizon are blocking and/or throttling video streams above 480p. In testing we loaded the same player over AT&T and TMobile. Over AT&T the video is throttled and will not play, while over TMobile, the video played without issue. I did create an issue for this as well at YouTube. Hoping for a response.
– Mike Someone
yesterday
I could be mistaken, but i believe the
setPlaybackQuality() method is now ignored. Regardless, i have tried using this method anyway, and still i am seeing the player attempt to load HD720p over cellular, and testing has shown that AT&T and Verizon are blocking and/or throttling video streams above 480p. In testing we loaded the same player over AT&T and TMobile. Over AT&T the video is throttled and will not play, while over TMobile, the video played without issue. I did create an issue for this as well at YouTube. Hoping for a response.– Mike Someone
yesterday
I could be mistaken, but i believe the
setPlaybackQuality() method is now ignored. Regardless, i have tried using this method anyway, and still i am seeing the player attempt to load HD720p over cellular, and testing has shown that AT&T and Verizon are blocking and/or throttling video streams above 480p. In testing we loaded the same player over AT&T and TMobile. Over AT&T the video is throttled and will not play, while over TMobile, the video played without issue. I did create an issue for this as well at YouTube. Hoping for a response.– Mike Someone
yesterday
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53205246%2fthe-youtube-iframe-api-serves-up-streams-at-resolutions-that-will-not-playback-o%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
