Skip to main content


FFS, GNOME! Just wasted a day of editing video because the built-in screen recorder records screencasts at such a low quality that I ended up with keyframe artefacts / ghosting in my captures.

Bloody hell…

And is there any way to set the quality? Is there ever!

[Edit] Use OBS. (Thanks everyone in the replies.)

(Don’t use GNOME’s built-in screen recorder if you’re posting HD+ videos.)

https://vimeo.com/957970626

#gnome #video #screenRecorder #quality #linux #foss

This entry was edited (4 days ago)
in reply to Cykonot

@cykonot Thanks; donno why I didn’t think of that – I used to use it for my streams a while ago before the Atem. I guess I still associate it with streaming.

So I just tried it and the recordings are pristine even with default settings (but I set them a little higher anyway).

:)

in reply to Aral Balkan

OBS is very full featured, but I've also had a great deal of use from SimpleScreenRecorder. Both in the repos of most distros, I think.
in reply to Aral Balkan

OBS Studio has worked well for me in the past. I mostly use it for webinars now, but it's got good recording capabilities
in reply to Aral Balkan

I didn't actually read any further than FFS, GNOME! because I couldn't stop laughing 🤣 🤣 🤣 🤣
in reply to Aral Balkan

I haven't used it on Linux, but I love OBS and it is available for Linux.
in reply to Aral Balkan

I concur with the OBS and SimpleScreenRecorder suggestions.

I've happily used SSR on Debian Testing for years, but for my newest install switched to OBS for recording because IIRC SSR doesn't (or didn't) support Wayland yet.

in reply to Aral Balkan

So, thanks to all the replies, I’ll be redoing a bunch of my work tomorrow using OBS.

So, in short: if you want to record screencasts and you care about the quality of your work: DO NOT USE THE BUILT-IN GNOME SCREEN RECORDER. It outputs low quality videos and you cannot change the qualiy.

Use OBS instead.

*le sigh*

G’night!

#gnome #screenRecorder #screenRecording #warning #OBS #FOSS #Linux #fedora #education #design #communication #presentations #video #editing #nle #videoEditing

in reply to Aral Balkan

The best thing about open source projects is that I got Linux software like OBS on Windows... and it works more or less perfectly. I'm still afraid to switch to Linux, but it's great to know I've got more than one option, including one out of the box.

(There's no way you can re-encode the video to salvage it, is there?)

in reply to Aral Balkan

I tried Simple Screen Recorder and produce AV1 videos

https://www.maartenbaert.be/simplescreenrecorder/

Finding the correct encoding was not simple since there are several AV1 implementation (I use libsvatv1).

in reply to Aral Balkan

Awesome! I like it partly because it does seem pretty solid, with all the basics working most reliably. But another reason is that it doesn't try to do everything. It does stick to the basics, which keeps the (re)learning curve reasonably flat.
in reply to Professor_Stevens

Yeah, I used to use it early on for streaming, before I got the Atem. Just never thought of it as a recording tool (mostly because of how large an app it is and because GNOME comes with one. Albeit one that’s clearly not fit for purpose.)
This entry was edited (4 days ago)
in reply to Aral Balkan

kooha what I have used and been pretty happy with for short screen recordings. Has options for quality and frame rate and file type output - Gif webm MP4 etc.

OBS is way more full featured, of course

in reply to Aral Balkan

I am under the impression that the GNOME Shell screen recorder is optimized for variable framerate recording with minimum amount of information encoded, resulting in very small filesizes compared to other screen recorders.
It is light on resources (I suspect it is much more efficient for encoding) and great for quick partial recordings to attach to bug reports (small filesizes), which is my primary usecase for it; it does not seem to be meant for files intended for editing in a NLE.
in reply to Jeff Fortin T.

@nekohayo Hi Jeff, thanks for taking the time to reply and for providing background but I hope you realise this is exactly why I stopped filing bugs for issues like this on #GNOME projects. It makes perfect sense for a tool made for the GNOME team to be for “quick partial recordings to attach to bug reports” where quality doesn’t matter. For anyone else who uses a screen recorder, quality is what matters. But were I to report it, my issue would be closed with this justification.
in reply to Aral Balkan

@nekohayo (Case in point: the exact issue that made me lose a day of work was reported three years ago: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3371 and the reason it’s still an issue is not because of an inability to fix the issue but a reluctance to see the problem as an issue since, given the use case you stated above, the low quality isn’t a bug but a feature as the tool is optimised for a different use case to one that people outside the GNOME dev team have.)
in reply to Aral Balkan

@nekohayo > he reason it’s still an issue is not because of an inability to fix the issue but a reluctance to see the problem as an issue

perhaps if you sent a merge request you'd get different results?

in reply to Aral Balkan

I think you misunderstand.

I'm not a GNOME Shell developer, it was just my educated guess of the probable practical performance+legal tradeoff that occurred a decade ago.

Nobody closed nor opposed @YaLTeR's issue 3371 that you linked there, nor other issues AFAIK. It's just impossible without HW encoding for VP9/AV1, IMHO.

VP8 is the only usable "in software" Free codec out there. I know because (from experience) you typically can't encode VP9 realtime "in software".

in reply to Jeff Fortin T.

As a user, I remember the era between 2015 and 2020 where GNOME Shell's video screen recorder was *literally unusable* because the VP9 encoder could never keep up and would lock up your computer by filling up the RAM within a minute. I'm not making things up; this commit proves it: https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/c61685e617

So, *very much* a technical limitation.

I would have appreciated if you had simply asked politely to begin with, & assumed good faith, rather than immediately publicly smearing #GNOME

in reply to Jeff Fortin T.

@nekohayo And this is the other reason why I don’t file bug reports any longer.

Me: this feature is not fit for purpose.

Someone on GNOME team: actshaully, according to technical reason #3096… why are you publicly smearing GNOME!

Ok, pretend I didn’t say anything. And you heard nothing.

in reply to Aral Balkan

@nekohayo So... you just ignore everything they said and not only continue to ignore but mock their explanation of why it isn't currently feasible to do so. Shame.
in reply to Aral Balkan

@nekohayo lots of FOSS seems to me to be technology-centric, rather that user-valie-centric.

Software is designed around what (selected) tech can do, rather than making tech to do what user needs.

With that focus in mind of programmers, FOSS often contains lots of options and features, but fails to let user do the most value task(s) efficiently (or at all).

in reply to Aral Balkan

@nekohayo Turns out doing real time encoding in software is a hard problem to solve, and turns out most of the good codecs out there are patent encumbered and can't be shipped by default.

Maybe instead of directing rants at volunteers, you could ask *why* things are as they are instead of expecting every feature to be on-par with commercial OSes.

in reply to Aral Balkan

No vertical screen?

Do you rotate a screen while coding or you actually feel better with an horizontal setup?

in reply to Shamar

@Shamar Tried vertical, never really worked for me. Found myself straining my neck more often than not.
in reply to Aral Balkan

You really use that DIY/Lego keyboard you built a while ago!? It's that good?

I'm impressed!