Nobody is aggressive Skander36, but it's an offended way to reply when people trying to help you on ways to get your issue across, - then to second guess one's motives, - as the aspect of what is "realtime" in a given webOS can vary a lot from one to the next - when it's down to something as relative as an individual perception of real-time - and what each of us finds acceptable.
yeah clasic ...show us a movie, but whatever you show your scope is broken, or you may have network problems ... Then what for ... ?
..
I'm good at networks ...
I get that your first reply to me, #455, - its likely not directed at me in full, but still its a precarious offended attitude to meet other people who are trying to help you, and then second guess my motive.
It's like you feel I'm attacking you and you need to excuse yourself upfront for whatever your mind can summon of possible attacks, but there is nothing in my first posts #453 that do anything other than try to help you, visualize the issues you're experiencing, that you claim are far from what other users are indicating.
I get' that your offended attitude could be down to other clashes you have had previously, with other users, but maybe not the right approach when users are trying to help you.
As I explained in my first pots, #453 there is both lag (ms delay) and there is the update rate..
It's not the same, and both factors can be a problem when not having a "real-time" experience.
* Lag, as in the timely ms-delay from when things unfold on the screen to it is shown on your WebOS.
* Update rate, the frequency that the WebOS updates your screen content, as it can be close to useless in practise, if it is only a few times per second as we saw in the past on some models..
And you keep referring to "lag", and it ain't real-time, the data that takes place on your scope to when it enters your WebOS, but both your two videos, are with consistent waveforms, that makes it somewhat difficult to tell, what lag you're having, as there could be seconds of lag, or it could be close to instant but with no reference point it's difficult to tell, - its mostly the update rate, your video gives an idea off - but its still better then nothing and other users can relate and inform you if it matches what they are encountering.
Why I showed the old example in #453 as you can sense how far the lagging on the tablet is behind the actual scope, alongside the update rate.
In plan ms-values, its a tad under 1/3 of a sec... web-stopwatch with granular ms-details
https://tinyurl.com/4vymssfp I get that approach ain't relevant on your scope, and why I showed the rolling/tail as a crude example for that timespan of lag delay
https://i.imgur.com/L2IxS2b.mp4Anyway, let's move forward, I don't have any horses in this race, don't have this scope you imported from China, but you can put up a small campfire for the future, as there is a big chance that it will be optimized five ways to Sunday, and many of these aspects that you find far from ideal, will only get better.. its very early days for SDS1000X HD.