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.










share|improve this question


























    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.










    share|improve this question
























      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.










      share|improve this question













      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 8 at 9:54









      Mike Someone

      146414




      146414
























          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, loadVideoById or setPlaybackQuality functions.




          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.






          share|improve this answer





















          • 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













          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














           

          draft saved


          draft discarded


















          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
































          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, loadVideoById or setPlaybackQuality functions.




          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.






          share|improve this answer





















          • 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

















          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, loadVideoById or setPlaybackQuality functions.




          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.






          share|improve this answer





















          • 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















          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, loadVideoById or setPlaybackQuality functions.




          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.






          share|improve this answer












          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, loadVideoById or setPlaybackQuality functions.




          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.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 9 at 13:22









          droidBomb

          50115




          50115












          • 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


















          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




















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          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




















































































          Popular posts from this blog

          Schultheiß

          Verwaltungsgliederung Dänemarks

          Liste der Kulturdenkmale in Wilsdruff