Building ffmpeg can be simple or complex, depending on how you configure the dependencies and if it's dynamic or static and of course it's target outputs.
I'm currently working on a cross-platform builder that runs within Github Actions runners, but the Mac and Windows builds take up so many of my monthly minutes.
I had to build from source because of that CVE that dropped, couldn't do it so I just wrapped the whole thing and injected my own -version command, passed the scanners cleanly
For anyone vaguely familiar with ffmpeg, don't sleep on this video. Quite funny, and everything from `yadif` (which I dealt with today!) to mkvtoolnix to "But then it will explode if you have an apostrophe in your file name. Because it doesn't understand that."
Building ffmpeg itself from source is actually quite easy.
The hardest part IMO is getting the necessary codecs to work; this can take a little while. If you know what audio and video codecs you want and need, and if you get them installed properly, then compiling ffmpeg is really simple and straightforward. It works almost always for me, and I have compiled ffmpeg from source for like +10 or even +15 years.
For reference purposes, my current configure options are:
Probably more codecs could be added, and some options may not be necessary anymore (I changed this last ... years ago, too), but this works for the most part fairly well.
One focus I have is mostly on a few .mp4 files, and for these I think you kind of want x264 x265 and so forth (I think one more codec from google too or so). But it is really quite trivial once you are past the codecs step. You can also start simple with just a few codecs, e. g. one good audio codec and one good video codec. One reason I like to have ffmpeg support many codecs is so I can use mpv, which in itself is really awesome; I like it more than vlc, which is also ok though.
getting the stock ffmpeg to compile/build might be "easy", but once you start adding on additional codecs and other features that get you into dependency nightmares "easy" is not the word I would use. I have not been able to use the stock ffmpeg since forever. for example, i see no openssl enabled in your config. I see no freetype. I see you've disabled openjpeg. clearly, you and i use ffmpeg differently which just goes to show your "easy" is very misleading
Say you have to pick a flight and you take the train to the airport. You can bet your train will be delayed, so if it ever happens at least you'll get a payout.
This is interesting because it is largely a set of good writing advice for people in general, and AI likely writes like this because these patterns are common.
Not least because a lot of these things are things that novice writers will have had drummed into them. E.g. clearly signposting a conclusion is not uncommon advice.
Not because it isn't hamfisted but because they're not yet good enough that the links advice ("Competent writing doesn't need to tell you it's concluding. The reader can feel it") applies, and it's better than it not being clear to the reader at all. And for more formal writing people will also be told to even more explicitly signpost it with headings.
The post says "AI signals its structural moves because it's following a template, not writing organically. But guess what? So do most human writers. Sometimes far more directly and explicitly than an AI.
To be clear, I don't think the advice is bad given to a sufficiently strong model - e.g. Opus is definitely capable of taking on writing rules with some coaxing (and a review pass), but I could imagine my teachers at school presenting this - stripped of the AI references - to get us to write better.
If anything, I suspect AI writes like this because it gets rewarded in RLHF because it reads like good writing to a lot of people on the surface.
EDIT: Funnily, enough https://tropes.fyi/vetter thinks the above is AI assisted. It absolutely is not. No AI has gone near this comment. That says it all about the trouble with these detectors.
These patterns overlap with formal writing advice because AI was trained overwhelmingly on academic papers, journals and professional writing so it inherited this style.
I completely understand - and do not intend to disparage - the use of these tropes. With the vetter and aidr tools I try to focus more on frequency analysis. I've tried to minimise false positives by tuning detection thresholds to match density rather than individual occurrences e.g. "it's not X, it's Y" is fine but 3x in one paragraph and suspicions flare.
But other tropes like lack of specificity and ESPECIALLY AIs tendency to converge to the mean (less risk, less emotion, FALSE vulnerability) are blatantly anti-human imo.
I'd argue most of them I overlap less with academic writing advice than high school level writing advice. Most people don't transcend that because they have no need to, and it's where most people learn to write essays.
Audio and video surveillance via robot vacuum is a feature: you can control the vacuum, see and hear the world from its perspective, and spy on your cats. I wish I were kidding.
lol, I just assumed this was a reference to the old workflow for bypassing code-signing on OS X, which was you had to click 'Cancel' in the popup then right-click and select "open" (no indication in the UI that this did something different than double-clicking).
I'm like you, and a big fan of Pigallery2 precisely for its simplicity. But it turns out that Immich does support external libraries, so you can keep your manual file management in your filesystem and still use Immich for efficient indexing, face recognition, quick picture retrieval by year, location, people etc...
I'd recommend you try Immich (there's a docker compose version) and if you don't like it, you can just remove it and move on.
> If there's one that I really need to be on, I'm going to spin up a VM on my computer so that it has no idea of the other files laying around, such as my ~/passcodes.csv. If you are such a negligent bullhead as to get me onto your call, you'll be unable to see me because my VM cannot access my camera! By design! Same for my microphone, so I'll plug in a USB mic if I really need to speak up. More likely than not though, I'm exhausted by now. I'll spend the full duration of the call eeking a small echo of pleasure from the continuation of this rambling alarm, for your sheepish audience to rub their enablist shame in.
This is written in an edgy tone but it's pretty much SOP with QubesOS. Why would you install _anything_ in your main VM? Not just Zoom, but anything you import in a deep dependency graph can access your figurative ~/passcodes.csv anyway.
furthermore why would you give ~/passcodes.csv access to ~/nuke_launch_codes.csv and ~/incriminating_evidence.csv let alone connect the computer they are on to the internet
I agree with Dijkstra on this one: “The question of whether a computer can think is no more interesting than the question of whether a submarine can swim.”
I really wish all these LessWrong, what is the meaning of intelligence types cared enough to study Wittgenstein a bit rather than hear themselves talk; it would save us all a lot of time.
https://www.youtube.com/watch?v=9kaIXkImCAM
reply