Re: Is ELMB-Sync Really That Bad? [Reviewer Consistency? / Model Differences?]
Posted: 15 Mar 2020, 04:59
Easy!
Both sides are getting a bit hot on this. Both of you, both sides, please re-read the forum rules on the "Be Nice To New Users" rule, even to users you disagree with or to users who are wrong.
I'm not going to close this otherwise useful thread. But I'm going to change the subject. This thread a "Consistency of Reviewer Tests" type of thread, and the thread stays open. I understand some of the reasons of the inconsistencies between reviewers.
From what I've seen of ELMB-SYNC on 1ms panels (TN or IPS), the use of ELMB-SYNC already looks reasonably good at max-Hz because it doesn't start multi-strobing. The strobe crosstalk in Hardware Canucks is roughly similiar to what I saw with my eyes in person. There's a bit of error margin going on with the tests, but it's reasonably small enough that it's representative of what I see go on in ELMB-SYNC at fps-Hz situation. So stop arguing about whether those YouTubes are authentic; they are. They're not exactly following the standard pursuit camera instructions (I'll have to ask them for more info), but as long as they're using 360-degree-shutter (no closed-shutter moments) during video pursuit camera tests, it's passable. I will contact them to make sure they're doing that, or to switch to long-exposure multi-refresh pursuit camera tests -- so that the ladder looks more accurate. But yes, I will talk to them so they're more experienced with pursuit camera -- I didn't even know they were using my free pursuit camera invention until recently --
The thing is that ELMB-SYNC (at least some implementations) go multi-strobe at framerates below Hz. But the fps=Hz strobe of ELMB-SYNC for screen middle is tolerable at least during 1ms panels.
What I am REALLY interested in, is how ELMB-SYNC behaves at fps below Hz on some of the newer ASUS models. Now, you launch CS:GO with ELMB-SYNC, it actually looks reasonably decent because it's always capping out at fps=Hz. But as soon as framerate fluctates, the sudden multistrobing effects starts to happen... More tests are needed for framerates below Hz.
As for the photos of ELMB-SYNC in this thread, the fake/not-fake should not be argued on (because they're real photos, I looked at them closely -- but that doesn't answer if they're perfectly identical to what was seen in real life), but "What are the camera parameters? And is he camera parameters accurate?".
The topic of reviewer consistency is a fascinating subject to me. But please, dial down the heat in this thread a bit, and follow the "Be Nice To New Users" rule (even those you disagree with / even those who are wrong). Even if this means this topic needs to get redirected to the reviewer-consistency discussion. I've changed the topic title to reflect this.
Both sides are getting a bit hot on this. Both of you, both sides, please re-read the forum rules on the "Be Nice To New Users" rule, even to users you disagree with or to users who are wrong.
I'm not going to close this otherwise useful thread. But I'm going to change the subject. This thread a "Consistency of Reviewer Tests" type of thread, and the thread stays open. I understand some of the reasons of the inconsistencies between reviewers.
From what I've seen of ELMB-SYNC on 1ms panels (TN or IPS), the use of ELMB-SYNC already looks reasonably good at max-Hz because it doesn't start multi-strobing. The strobe crosstalk in Hardware Canucks is roughly similiar to what I saw with my eyes in person. There's a bit of error margin going on with the tests, but it's reasonably small enough that it's representative of what I see go on in ELMB-SYNC at fps-Hz situation. So stop arguing about whether those YouTubes are authentic; they are. They're not exactly following the standard pursuit camera instructions (I'll have to ask them for more info), but as long as they're using 360-degree-shutter (no closed-shutter moments) during video pursuit camera tests, it's passable. I will contact them to make sure they're doing that, or to switch to long-exposure multi-refresh pursuit camera tests -- so that the ladder looks more accurate. But yes, I will talk to them so they're more experienced with pursuit camera -- I didn't even know they were using my free pursuit camera invention until recently --
The thing is that ELMB-SYNC (at least some implementations) go multi-strobe at framerates below Hz. But the fps=Hz strobe of ELMB-SYNC for screen middle is tolerable at least during 1ms panels.
What I am REALLY interested in, is how ELMB-SYNC behaves at fps below Hz on some of the newer ASUS models. Now, you launch CS:GO with ELMB-SYNC, it actually looks reasonably decent because it's always capping out at fps=Hz. But as soon as framerate fluctates, the sudden multistrobing effects starts to happen... More tests are needed for framerates below Hz.
As for the photos of ELMB-SYNC in this thread, the fake/not-fake should not be argued on (because they're real photos, I looked at them closely -- but that doesn't answer if they're perfectly identical to what was seen in real life), but "What are the camera parameters? And is he camera parameters accurate?".
The topic of reviewer consistency is a fascinating subject to me. But please, dial down the heat in this thread a bit, and follow the "Be Nice To New Users" rule (even those you disagree with / even those who are wrong). Even if this means this topic needs to get redirected to the reviewer-consistency discussion. I've changed the topic title to reflect this.