I'm streaming video a lot in the PiP breakout window while reading other web pages. I think it's a great feature and I've seen some improvements in the UI over time. I was hoping this problem would have been fixed in the latest update or noticed by someone either in development or another user at some time, but I could find no reference to it when searching the help pages. When the video is playing in the window, everything works fine. Except when I'm watching something like a live broadcast that has breaks in it for commercials. My practice is to keep an eye on the video playing when I've muted the tab, while I continue my reading in other tabs. When the program comes back on in the PiP, I unmute (demute??) the tab and usually return the picture to the host tab, then go full screen. At least half the time I do that, the navigation bar - where you can stop/start the play, go forward/back 10 seconds, and where you see the red "LIVE" notification or how many minutes/seconds you are behind the LIVE stream - shows that my program is now minutes behind the LIVE point. The funny thing is, it doesn't do it consistently and I have tried several things to figure out if it's something I'm doing. But there is no rhyme or reason why it's happening. It did this when I had Windows 8, and continued after I installed Windows 10. For a three or four minute break, I will lose perhaps two or three minutes. I suppose that if I left it in the PiP configuration and just let the program play for the two or three hours it would take for the duration, the time would slip maybe as much as forty five minutes to an hour. Typing this statement now is going to push me to try it next time for an observable result. Again, though, it doesn't happen every time. My guess is that, for some reason, video frames are being dropped when it's in PiP mode and instead of 30 fps it's only delivering 15 fps. (If 30 fps is what's normal.) I do not have this slippage when I maintain the picture in the standard size video box or when it's full screen. So yeah, as I'm thinking more about it, a distinct possibility is that the frames per second is reduced for the PiP, because it is not able to keep up with the higher frame rate. But then the question is why doesn't it do it 100% of the time. So thank you all for thinking about it, and multiple thanks to the ones who can help this one be marked "solved". Later -