waigl @ waigl @lemmy.world

Posts

3

Comments

173

Joined

2 yr. ago

Thanks for pointing that out, I found the setting on my laptop and tried it out. I do like the jiggle approach better, though, simply because that is something many people (myself included) instinctively do when losing track of the mouse cursor.

If it was, I don't think it was a default. I had been using Windows 7 for quite a while back in the day, and I cannot remember ever seeing something like this. On the other hand, I can certainly remember losing track of where on my monitors my mouse cursor was on various occasions...

FWIW, this entire comment section:

https://lemmy.world/post/1940961?scrollToComments=true

Back to the to the topic, yes, Linux is not technically Unix by pedigree. In practice, it doesn't matter that it isn't and it wouldn't matter if it were, both for this issue in particular and for most others you are likely to encounter.

The actually relevant technology here is the graphics subsystem, and MacOS's Cocoa has always been radically different from anything else in the Unix/Linux space. There is no relation whatsoever to either X11 or Wayland. The only thing worth "porting" here is the basic idea. Which is pretty neat, though. Let's hope Apple hasn't patented it.

Ever since Donald Trump was elected, I always had the impression that he just doesn't properly understand that being elected president is a fundamentally different thing from being crowned king.

Using "they" when you haven't yet established the group you are referring to in context feels weird and kinda wrong, especially if it's about a group of inanimate objects. It really looks like the word should have been "there", but they just mistyped and then didn't catch the error in the editing process or didn't bother to correct it.

That's what I think is wrong here. I'm not 100% sure that this grammatically wrong, but it sure feels like it. Might depend on what the page before this one said.

One of the advantages of being on old reddit like a hopeless geezer is not getting to see that shit.

Too bad this windows firewall dialog is really sparse on details. We really have no way have telling whether that is normal permissions or not.

I've read that article. It is complete garbage and doesn't explain anything at all. It's just standard cookie cutter fear mongering to sell some random antivirus software.

In theory, that shouldn't even be possible with JavaScript. There's such a thing as same-origin policy for that exact reason...

I also wondered for quite some time why my Logitech C920 webcam seemed to be using much lower framerates (which could be perceived as "laggy") in Linux as compared to Windows. It turns out it was transmitting uncompressed YUV frames by default, and for that, the bandwidth of my USB port just wasn't enough. (Maybe in USB C it would be enough, but this webcam isn't USB C.)

It worked like a charm after I manually set the format to H.264 in OBS. ("Like a charm" meaning it was transmitting 1920x1080 at 30 fps.) Unfortunately, I don't know how to do that in an application-agnostic way, but maybe someone else here can enlighten us. Worst case, install https://github.com/umlaeute/v4l2loopback and pipe your webcam stream through OBS...

I think it's possible that this is the same problem that you have run into.

i

Graphics workloads are GPU bound.

This isn't a graphics workload, or at least not that kind of graphics workload. The GPU is irrelevant here.

As far as I know and could look up on short notice, libx265 does not make use of GPU computing (via CUDA or otherwise), so the answer to your second question

Would tight integration between amd cpu + gpu help in this case?

is almost certainly no.

Performance wise, the ffmpeg command you posted will be completely dominated by the video encoding part through libx265, to the point where everything else is pretty much negligable. Also, the rest of this does not use gpgpu computing either.

Yepp, that's a risk.

I have made it habit to put my laundry basket somewhere where I have to step over it to go to bed whenever I switch on my washing machine. Makes it easier to not forget. If I don't, I may as well wash the laundry a second time, because forgetting it in the machine over night means it starts to stink...

You messed up the formatting there, you put the URL where the visible text should go and the text where the URL was supposed to be.

In F/OSS, it is not unusual for software to stay below 1.0 version for a long time yet still get a lot of use. Just look at how long OpenSSL, for example, was at 0.9.something, while already being of crucial importance to a lot of internet infrastructure.

The reasons for this are varied, but the most important is probably simply that free software developers don't feel the pressure to call a product 1.0 when they don't believe it is ready to be called that.

Pipewire makes me feel like I'm a bit stupid. I keep reading about it, I read the introduction and FAQ on their website, yet I still couldn't tell you what that thing even does. All I know is it's a slightly less buggy drop-in replacement for pulseaudio, and pulseaudio is something I use because Firefox forces me to. (I would still be on plain old ALSA if it weren't for Firefox.)

Also, it definitely did not "just work" for me out of the box, I had to do quite some digging and some very non-obvious stuff to get it to a) start up and b) let me use my microphone. I still don't even know what "starting up" really means for pipewire (is there a daemon or something?), the website likes to pretend that isn't a thing, but without doing some stuff to start it up, audio just won't work for pulseaudio and pipewire applications...

AMD and nVidia on Windows: So your GPU is still very capable and useful for almost everything including most gaming tasks, but it's a couple years old and not making us money any more? Sucks to be you, have fun hunting for unmaintained legacy drivers with likely security holes from questionable sources.

Linux: Your video card is from a long bygone era of computing, before the term "GPU" was a thing, and basically a museum piece by now? We'll maintain a long-term support version for you for the next ten years.