So how do you use that? Do video players like mpv need some special support for it? What about video in Firefox?
Announcement
Collapse
No announcement yet.
AMD Enabling FreeSync Video Mode By Default With Linux 5.18, Merging AMDKFD CRIU
Collapse
X
-
Originally posted by RejectModernity View PostFreesync is already enabled in KDE... or this is different?
For example I see this in /usr/share/drirc.d/00-mesa-defaults.conf:
Code:<application name="mpv" executable="mpv"> <option name="adaptive_sync" value="false" /> </application>
I'm not sure how that is handled in conjunction with what amdgpu is doing.Last edited by shmerl; 13 February 2022, 04:52 PM.
- Likes 2
Comment
-
Originally posted by user1 View PostI'm not sure I like the idea of FreeSync enabled by default. I might be in a minority, but I have a FreeSync monitor (which I didn't buy because of FreeSync), but I prefer to use regular Vsync (I like to have steady 60 fps and I reduce the input lag with framerate limiters in most of my games anyway). About 4 years ago I tried FreeSync on Windows out of curiosity and the experience wasn't good. It caused constant stutters every few seconds and didn't really reduce input lag. I also accidentally turned off my monitor while in game, so after I turned it back on, the image was frozen and I couldn't do anything but a hard reboot.
So yeah, FreeSync didn't leave a very good taste in my mouth. Will there be a kernel argument to turn it off?
Comment
-
Originally posted by Quackdoc View Postfreesync does nothing for input lag... I have a feeling you probably set something up wrong.
Input lag happens when there is some delay between starting to display available frame and when the frame is actually available (which can be the case in vsync scenario). Tearing reduces that, and syncing refresh rate to current framerate obviously reduces that too.Last edited by shmerl; 13 February 2022, 07:27 PM.
- Likes 3
Comment
-
Originally posted by shmerl View Post
Why not? It should help reducing input lag as long as your framerate is below max monitor refresh rate (i.e. in range of the adaptive sync). If it's above, to reduce input lag you need to prevent vsync (i.e. allow tearing).
Input lag happens when there is some delay between starting to display available frame and when the frame is actually available (which can be the case in vsync scenario). Tearing reduces that, and syncing refresh rate to current framerate obviously reduces that too.
the way it was said made it sound like to me none of these steps were taken. freesync does nothing unless additional steps are taken. and even with those steps taken, freesync would not contribute to a reduction in input lag (unless you consider screen tearing)
I tried FreeSync on Windows out of curiosity and the experience wasn't good. It caused constant stutters every few seconds and didn't really reduce input lag.
Comment
-
Originally posted by Quackdoc View Post
the only thing freesync does is sync monitor refresh rate with display rate
Obviously it only works when current framerate is within monitor's adaptive sync range. When it's above, as I said, to reduce input lag you need to simply allow tearing there.
So within the range - adaptive sync. Above the range - tearing. That's the best experience you get for minimizing latency.Last edited by shmerl; 13 February 2022, 07:57 PM.
- Likes 1
Comment
-
This is 6 years and 332 days after initial Windows support. I am not trolling or sarcastic. I'm actually glad, Here's why...
I have been playing competitive online games in a Windows VM for ~8 years. Having low-overhead low-latency vsync in Linux has not bothered me much personally.
That said, AMD and Linux should celebrate the only open implementation that it's good enough to be set to default.
This was a massive codebase that was rejected multiple times IIRC. Honestly, well done for not giving up.
The amount of work that was done to finish this project is probably beyond my comprehension.
- Likes 6
Comment
-
Originally posted by shmerl View Post
Which reduces any potential latency between readiness of the frame and it's appearance on the screen, meaning it reduces input lag.
Obviously it only works when current framerate is within monitor's adaptive sync range. When it's above, as I said, to reduce input lag you need to simply allow tearing there.
So within the range - adaptive sync. Above the range - tearing. That's the best experience you get for minimizing latency.
but yeah, my entire point was I don't think he setup freesync right, which could have caused some of the issues he was experiencing. freesync sure is nice though. don't think I could live without it lol
- Likes 1
Comment
-
Originally posted by Quackdoc View Post
even then freesync doesn't really lower input lag. as the frames are still displayed when they are ready
- Likes 1
Comment
-
Originally posted by shmerl View PostSo within the range - adaptive sync. Above the range - tearing. That's the best experience you get for minimizing latency.
- Likes 2
Comment
Comment