You are not logged in.
johnraff wrote:I think your experiences do reinforce my argument that no vsync options at all should be applied to compton, do you agree?
...er, no.
[...]
While I agree with the decision not to enable vsync with compton by default in BL
I am confused.
My proposal is that in the stock BunsenLabs desktop compton should be run without any --backend or --vsync flags at all, do you agree with that?
I think this is the best option for us because applying any given set of flags uniformly may be advantageous for one set of hardware but deleterious for another.
YES
Agree completely.
This thread is not for discussion of what should go in the BL default config files - there is already another thread for that. (Which I am just about to revisit.)
This one is for individual users to share their specific hardware details and the settings that worked best in their case, so other users with similar hardware might try them.
Last edited by johnraff (2017-12-08 03:14:43)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
EDIT: ^The above is what I thought this thread was for, but-rereading the OP it seems to be a request for input to help with choosing BL defaults.
Apologies to HoaS and Tknomanzr - there seems to have been some talking at cross-purposes both here and in the other thread. Anyway, I think we're agreed that no tweaks should be put in by default, leaving it up to users to optimize things.
Considering how messy and complicated and just generally PITA all this is, I was thinking just a simple list of individual peoples' hardware and what compton settings they were using might be a nice resource for someone who didn't want to go over every single combination of settings in order to find something that might work for them.
Should we start another thread for that?
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
your NVIDIA card has the full force composition pipeline to deal with tearing
CompositionPipeline does not seem to be available with my card & driver. The gui shows no such option as described on the Arch Wiki, and using the terminal:
john@bunsen1:~$ nvidia-settings -V all --assign CurrentMetaMode="nvidia-auto-select +0+0 { ForceFullCompositionPipeline = On }" john@bunsen1:~$ nvidia-settings --query CurrentMetaMode Attribute 'CurrentMetaMode' (bunsen1:0.0): id=50, switchable=no, source=nv-control :: DPY-2: nvidia-auto-select @1440x900 +0+0 {ViewPortIn=1440x900, ViewPortOut=1440x900+0+0} john@bunsen1:~$ nvidia-settings --query all | grep -i composition john@bunsen1:~$
It's true that querying nvidia via the terminal showed no sign of composition pipelining after trying to apply it, but I have now found that it does in fact seem to improve display of that test video, without using compton's vsync: there is some flickering and stuttering but no tearing. I've set it in xorg.conf as per the Arch Wiki, and we'll see how it goes, but it seems to be an improvement. Apologies again for being too hasty.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline