If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Avoiding Frame Jitter With GNOME's Mutter, Weston

Phoronix: Avoiding Frame Jitter With GNOME's Mutter, Weston

Owen Taylor has written a new blog post about avoiding jitter in composited frame display. Owen -- along with help from Kristian Høgsberg -- made improvements to the algorithm for compositor frame timing as used by GNOME's Mutter compositing window manager and also Wayland's Weston...

Keep up the good work guys. I'm tired of naysayers that Linux will never pass muster as a desktop OS. You are making it happen. Thank God for your team, Intel, Canonical and other pioneers in the Linux world!

I like the idea of having applications give their expected frame display time to the compositor. Alternatively, video players could be given more information about the compositor's frame display times, allowing them to resample the audio as necessary to maintain sync with a strictly 2-2 or 2-3 video frame/compositor frame cadence.

Keep up the good work guys. I'm tired of naysayers that Linux will never pass muster as a desktop OS. You are making it happen. Thank God for your team, Intel, Canonical and other pioneers in the Linux world!

i'm tired of evangelists that promote linux fully knowing that its a not good desktop OS YET, but it might after wayland becomes good, gimp stops sucking balls, there is a autocad alternative, pulseaudio gets fixed, steam final is released, lightworks gets released, gnome 3 stop sucking balls, kde stops being buggy garbage, KMS doesn't cause kernel panics, wifi doesn't drop connections from sleep/wake and you don't have to paste things into the terminal to make your computer work.

+1 for applications giving the expected frame display time.
But this should be complemented by other things.
This way applications that work best with one method can use it while others that work best with another method can use the other one.

pulseaudio has latency issues, gstreamer also sucks balls, just check their bugzilla page. kms does cause kernel panics. the kernel also has a lot of regressions every time because the kernel devs are too cheap too hire code testers. the fact that you can't run useful apps is not linux's fault, but it renders the platform useless for the end-user.

pulseaudio has latency issues, gstreamer also sucks balls, just check their bugzilla page. kms does cause kernel panics. the kernel also has a lot of regressions every time because the kernel devs are too cheap too hire code testers. the fact that you can't run useful apps is not linux's fault, but it renders the platform useless for the end-user.

Linux doesn't have a single HW company that will push it on the desktop. So app developers are not interested in porting their apps. Also many of the bugs that the end user sees are HW related and cannot be solved on the kernel space. Even if the devs want they cannot do anything about it in many cases. (nvidia GPU, AMD PM etc etc) Also the kernel devs do a damn fine job IMO with regresions. I am on a rolling release distro and so far -apart from minor glitches- it works damn fine. My problems so far have been HW related (Intel POS).