I’m swiftly moving into the sparsely populated camp which holds that it’s not actually in our interests. Maybe the bell labs people were the good path and were walking parcs bad path now. We’re gonna find out for sure!
Idk how kde missed it, they’re probably taking fixes, why not whip something up?
In my experience a lot of non it people have used computers with text interfaces and don’t have any problem with things like fstab but I understand what you’re saying.
Does adding them to fstab not work?
See if you have qsv decoding support enabled. The Intel CPUs in those little mini pcs usually have a video card that will do the heavy lifting using a system called quick sync video but if you’re isn’t set up to decode in hardware then it’s gonna have to do all the work in software and that’s slow.
For sending a file to print, share your plugged up printer over the network.
For sending a torrent file most of the time people use their torrent clients web interface. A person suggested using qbittorrent and that’s a perfectly fine one, but if you’re a fellow or lady of girth swishing brandy around in a snifter, might I recommend rtorrent+rutorrent?
Well I’m American so idk how far away that is and it’s incredibly racist of you to assume I would.
Even if you stay with external drive backups, consider a kind of total loss copy.
You could easily end up being in a fire or some natural disaster and lose both your server and your backups.
An easy way to add this in your life if you’re already going there is a safe deposit box at the bank. You just gotta remember to take a weekly copy over there for safekeeping.
The usual way is called a low pass filter.
If you listen to electronic music you probably know what I’m talking about even without knowing it by name. It’s the sound in breakdowns where nothing really changes about the patterns or the music being played, but the sparkle and definition goes away and all you can really hear is the baseline and kick drums. The high hats are still playing and “in the mix”, their high pitched sound is just being filtered out electronically when the person playing turns a knob.
In everyday life it’s the sound of music through a closed door or rolls up window, muffled and low pitched. When the person opens their door or rolls down the window suddenly you hear more than the subs.
Waves propagating through a medium follow the inverse square law so the more dense or thick the “door” that sound has to go through, the quieter the blocked frequencies on the other side will be.
Since ultrasonic waves will be higher in frequency than audible ones, they’ll be scattered and absorbed much more readily than low frequency ones. Something that will absorb them well would be a flexible damping layer between the microphone and air, like the material of a disposable glove stuck over the top of the microphone hole.
This solution is better than a software one, because instead of relying on your software to correctly intercept and filter input from the microphone, you’re preventing it from ever reaching the mic in the first place!
Now you still need to be worried about solid objects. They can transmit sounds just like the air and are even better at high frequencies! Someone could have an ultrasonic exciter mounted on the bottoms of a table and vibrate your phones mic directly through its own chassis! So maybe stick your whole phone in the glove instead of just cutting out a little diaphragm for the chassis mic hole.
Don’t.
You like the user experience, you like the hardware, you don’t need to switch to linux to become independent from big tech.
Even if you needed to switch your operating system, what computer are you gonna use it on that isn’t under the control of big tech (however you choose to define that)?
Even if you had a computer you understood the hardware of and ordered in a group buy from a small manufacturer, and therefore wasn’t under the control of big tech, the linux operating system has thousands of core components maintained or developed by people who are in the employ of big tech to do just that! Are you really out from under the thumb of big tech when they’re paying the people that do the lions share of work in key components of your operating system who just so happen to always seem to make choices in that role which align with their bosses needs?
What might be better than switching from mac to linux would be considering exactly what big tech you’re trying to get away from and why, then doing so on the system you already understand and feel comfortable with.
You didn’t explain how I’m wrong, you just repeated it a bunch of times.
My brother or sister, this thread is literally about how the “solutions” to the “problem” you describe break one of the most common expectations users have of computers.
The fact that python (and javascript!) create terrible dependency clashes is not a defense of static linking, it’s an indictment of those languages and the people who develop, maintain and use them.
“Oh yeah? Try using the terrible software that breaks the computer!” Isn’t the powerful argument you think it is.
Users hated Java because seeing the splash popup for it was the loading screen to what would inevitably be a barely functional pile developed by the lowest paid person in the company and because it was confusing to deal with, not because there were version conflicts. I remember Java being decent about that once the 0s hit at least, that you would need to upgrade the jre but never downgrade.
Ah, so back2nt4 like I said earlier?
You don’t need to insult and attack in every reply. This isn’t reddit.
It doesn’t make any sense to bring up avoiding dependencies in the context of personal computing (the context of this thread), because nowadays the user never sees it. Either deps are handled by the package manager or they’re shipped with the target software except shipping static libraries breaks the environment now so it’s a worse option.
People don’t care if dependencies are installed, they care if the environment breaks. They care if the thing you just described, potential interference with normal operation, happens!
Again: this was a solved problem for decades and now people are opening up the wound to implement stuff that’s only appropriate for use cases narrower than general purpose personal computing. It’s astounding and truly hard to explain.
And no one but the poor schmuck computer janitor cares about making IT work easier. Shes being paid to do that work and the total extent of concern given to making the work easier is an equation that accounting solves each quarter. It’s the same as the countertops in the bathrooms: first, are they what the company wants? Second, do they meet the requirements, distant, unconsidered third: are they gonna cost too much to clean?
Rather than doing what you are asking about, why not swap them over to the 21h2 ltsc iot version of windows 10 that will receive updates till 2032?
Doing that will improve their lives by rolling the computer back to what they expect and are familiar with, avoid the problems 11 is having and still keep them up to date.
It’s probably best to do something like that instead of evangelizing linux to people who only want the computer to function in expected ways as opposed to learning a bunch of new stuff.
I’m gonna go out on a very stable limb here and recognize that containers, immutability and atomic(ism?) are solutions to wildly different problems and the set of circumstances that allowed them to be viewed as acceptable approaches stem from the costs and reliability of storage and bandwidth and not from some form of correctness.
Now that at the very least storage and the memory required to page it are getting expensive, you can expect people to become more vocal about how badly implemented these solutions are, weather or not they’re able to actually articulate it in the face of you stamping your feet and saying “nuh-uh”, as I have, or not.
I can tee you up, holy warrior of containerization, immutability and atomicisation: any vague gestures towards security from the aforementioned technologies are made redundant by two frameworks and invalidated by the compromised web of trust our entire world relies upon using identity as authentication.
Static linked libraries shipped with software exchange dependency hell for environment inconsistency.
Extensive handlers and api calls can work around that, but then you start building the windows nt system all over again.
The reason atomic/immutable became popular is because two generations looked out upon the plains and wept because there were no more useful programming problems to solve but had to suck it up and manufacture some so they could solve them to pad their resumes in order to get faang internships.
Not to get too awful off topic, but you can do that and it doesn’t work good.
There are two problems with what you’re suggesting being fast: the first is that there are elements of motion or color change in the video that you don’t wanna trigger on, like the shadows of leaves blowing in the wind or the colors slowly getting orange because the sun is setting and afaik there’s not a good method to figure out if the change in bitrate you’re catching is because an imperceptible swarm of gnats moved under a street lamp and caused the sidewalk underneath to move exactly one bit down the chroma scale or because a man in a trenchcoat stepped out from behind the pole that lamp is mounted on. The second is that the video is already compressed so you gotta uncompress it to figure out what is on the frame to then figure out if the change from that frame to the next is enough to call “motion” and start flagging.
It’s one of the reasons why you super want to be working with raw or minimally compressed video when you’re editing something because simple things are much harder from a computation perspective.
E: the script to use ffmpeg another person posted checks every few seconds so it doesn’t actually crunch through all the frames, so sort and path finding techniques like that can be used to make it faster.
Op one of the reasons it’s frustrating for me to see so much focus put on flat packs, snaps, docker images and the like is that they manage to excel at doing their one expected thing, but throw everything else out by the wayside.
Frankly I think their prominence is a direct result of the way their goal is structured: make sure the “🚀getting started” section of the git/wiki works 100% of the time.
It’s a distillation of the poison ethos of technology companies dripping into the open source world. We are now moving fast and breaking things. Oh, the things we broke are the users environment? Well, it just so happens that we sell a premium product that integrates properly for a small subscription fee.
Yeah it’s always sucked and tbh the only place drag and drop has ever worked close to predictably is on the mac.
As someone who uses linux, mac and windows, if you rely on drag and drop working right you’re probably best served by using macos. Windows is a distant second but if you get familiar with its eccentricities then it’s doable too.
Hey, someone already gave you the right answer, which is ffmpeg.
I handle dozens of cameras and their video. I may be able to help you set your expectations appropriately.
You do not need a gui. You would not feel more comfortable with a gui. There are so many options, methods and process available just within the ffmpeg package that you would be overwhelmed.
“Reasonably fast” to me is seven times faster than the source material. That means it would take ffmpeg a day to go through a weeks worth of footage and dump out the parts with motion. That takes a very fast computer with lots of ram.
Consider locating some footage with a few different sections of motion, feeding it into ffmpeg and making sure you get the output you want (files appropriately sized, time stamped, etc) then calculating how long it would take to do all your footage that way.
Not only will working with a smaller, “known” section help you figure out how to do it and get it right, it will help you figure out if you need to rent time on a server or something to get the whole job done faster.
E: I am trying to get you to do a test section in order to find out how fast your system will perform. Different factors like media speed, ram size, hardware acceleration and system load will have a significant impact.
More users of a system has never meant more driver support. The two don’t correlate on windows, mac or linux. Hell, the kernels been shedding drivers during the last few years! I also don’t think more users means more main applications, no matter what you mean by that, but it’s neither here nor there because neither one of us can pull things in the direction we want.
What are the kde people saying it’s a dupe of? Is there a number?