Announcement

Collapse
No announcement yet.

Streamfab 6.2.1.9 Win10, all Peacock videos showing "Can't play Right now" page

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    peacock.com will be also added to the support list in next version.
    Great! /s
    That means that Peacock will be out of action for the next few updates. Typical, one step forward, two steps back. Why fix something that nobody (except one New Member with a depreciated Windows version) is having a problem with? Peacock has been downloading perfectly since 6.2.1.3.

    Comment


      #17
      Did we go into our peacock account via a web browser and log out of all devices? Is that a thing any more?
      Wilson.Wang does that mean we may get h265 in the next version? That would be nice!

      Comment


        #18
        Originally posted by MrGrackle View Post
        Did we go into our peacock account via a web browser and log out of all devices? Is that a thing any more?
        Wilson.Wang does that mean we may get h265 in the next version? That would be nice!
        h265 will require L1 so you can forget about this being supported.

        Comment


          #19
          While some are gung ho about my deprecated version of 10 (21H2) being a factor, it's not. I use Firefox 128.7.0esr and stream Peacock on this very same PC daily, all the time. Streaming a show as I type in fact. And everything plays in FF perfectly... with 21H2. Amazing, right? I have never seen that "Can't play right now" message in FF on this PC. Also, double checked, and pretty sure actual build info not part of browser's useragent info sent reported to sites. It's just O/S, browser brand, version, o/s architecture, etc. That... "Can't play message"... is something I'm getting pretty much randomly, only through SF's internal "chrome" browser (yet another reinforcer as to why I sort of loathe chrome). Anywhooo... I've been using SF for 2 years now ("new user"). All on this PC. And this is first time I've had this hiccup redirect issue with Peacock. Based on their track record, I'd bet dollars to donuts, it's something within the SF code. All in the name of progress....

          Comment


            #20
            peacock.com is also redirected to the peacocktv.com, normally to say, it should be supported as the VIP services.

            Coding glitch

            ​​​​​​​Wilson
            Please post your logs the default location is:
            For DVDFab 13: C:\Users\User Name\My Documents\DVDFab\DVDFab13\Log
            For StreamFab: C:\Users\User Name\My Documents\DVDFab\StreamFab\log
            Please use attachment button and attach your most recent, Internal log and post right here.
            If it's the burning issue, please also attach burn log.

            Thanks!

            Comment


              #21
              Also, double checked, and pretty sure actual build info not part of browser's useragent info sent reported to sites. It's just O/S, browser brand, version, o/s architecture, etc.
              You'd better triple check. How do you think I knew you were using a depreciated Windows version? Your StreamFab.log. See last line.

              2025:02:07-07:38:38 0x0000076c [Info]: Root Domain: "dvdfab"
              2025:02:07-07:38:38 0x0000076c [Info]: Platform: winx64
              2025:02:07-07:38:38 0x0000076c [Info]: app: system_type= Windows [Windows|macOS]
              2025:02:07-07:38:38 0x0000076c [Info]: app: system_architecture= x86_64 [x86_64|i386|arm64|arm]
              2025:02:07-07:38:38 0x0000076c [Info]: app: system_version= Windows 10 (10.0)
              2025:02:07-07:38:38 0x0000076c [Info]: app: machine_id= 00-50-b6-61-f9-2b:68-f7-28-f2-93-e8
              2025:02:07-07:38:38 0x0000076c [Info]: app: app_platform= x64
              2025:02:07-07:38:38 0x0000076c [Info]: app: app_client_id= cry_s//YRgquLx+/SsnosHdLcQ==_cry
              2025:02:07-07:38:38 0x0000076c [Info]: app: app_version= 6.2.1.9
              2025:02:07-07:38:38 0x0000076c [Info]: app: app_launch_id= "b1ac55a4-0774-43b1-9c14-e0a24c912540"
              2025:02:07-07:38:38 0x0000076c [Info]: app: applicationFilePath= "C:/Program Files/DVDFab/StreamFab/StreamFab64.exe"
              2025:02:07-07:38:38 0x0000076c [Info]: app: app_args= ("C:\\Program Files\\DVDFab\\StreamFab\\StreamFab64.exe")
              2025:02:07-07:38:38 0x0000076c [Info]: app: cmd_line: "C:\Program Files\DVDFab\StreamFab\StreamFab64.exe"
              2025:02:07-07:38:38 0x0000076c [Info]: app: QLocale::system QLocale(English, Default, United States)
              2025:02:07-07:38:38 0x0000076c [Info]: app: QLocale::c QLocale(C, Default, Default)
              2025:02:07-07:38:38 0x0000076c [Info]: app: fabApplication compiled time Jan 29 2025 22:55:38

              2025:02:07-07:38:38 0x0000076c [Info]: System: 64bit System Windows 10 Build 19044

              Click image for larger version

Name:	Screenshot 2025-02-11 8.27.40 AM.png
Views:	131
Size:	11.7 KB
ID:	458977 Depreciated almost 2 years ago.​

              Besides, not all streamers use user-agent anymore. They can learn a lot more about you using Client Hints. Look it up.

              Comment


                #22
                Originally posted by Wilson.Wang View Post
                peacock.com is also redirected to the peacocktv.com, normally to say, it should be supported as the VIP services.
                Please don't screw it up if you are going to do it, otherwise I'll sic my wife on you. She'll rip you apart if she doesn't see her daily soap opera episode downloaded from Peacock.

                Comment


                  #23
                  Good job, Wilson.Wang! My wife is happy that she can still get her soap opera. It took me a while to figure out what you wanted to fix. You could have left it alone. It was not a biggie. There are still plenty of real issues that have been ignored for years.

                  Comment


                    #24
                    Wilson.Wang - I was wrong in thinking about what you were fixing on Peacock in 6.2.2.1. I thought you were going to fix the blank, white screen that appears the first time you click on the Peacock icon.
                    Click image for larger version

Name:	Screenshot 2025-02-14 11.22.21 PM.png
Views:	97
Size:	27.8 KB
ID:	459204

                    The problem was previously written about in the topic - https://forum.dvdfab.cn/forum/stream...-loading-pages. You always have to close the display and then have to click on the icon again to be able to load up Peacock. From the other topic, it might be happening with other modules as well. For right now, I am only running Peacock, and so I don't know what is going on with the other modules. Could you please have the Developer look into this? Thank you.

                    Comment


                      #25
                      Originally posted by Cats4U View Post
                      Wilson.Wang - I was wrong in thinking about what you were fixing on Peacock in 6.2.2.1. I thought you were going to fix the blank, white screen that appears the first time you click on the Peacock icon.
                      Click image for larger version

Name:	Screenshot 2025-02-14 11.22.21 PM.png
Views:	97
Size:	27.8 KB
ID:	459204

                      The problem was previously written about in the topic - https://forum.dvdfab.cn/forum/stream...-loading-pages. You always have to close the display and then have to click on the icon again to be able to load up Peacock. From the other topic, it might be happening with other modules as well. For right now, I am only running Peacock, and so I don't know what is going on with the other modules. Could you please have the Developer look into this? Thank you.
                      For me when this happens, if I just do a single left click in the url bar --- (anywhere in there, making it active), that somehow pushes the page load along so it loads 100%. Then I don't have to close it and open it a 2nd time. Might work for others too until fixed.

                      Comment

                      Working...
                      X