- Joined
- Aug 28, 2019
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
HmmmmmmmnOne feature that is not yet merged for FFmpeg 8.0 but could potentially make it in time is this recent work on adding OpenAI Whisper audio filter support to FFmpeg. This could provide AI-driven live subtitles/transcription support with FFmpeg.
Forumers have already been using Whisper.Hmmmmmmmn
Interesting
I wonder how it's supposed to be run
I mean specifically how they're going to make it runnable in ffmpegForumers have already been using Whisper.
It is, at the very least, one of the most used and most useful, really only falling behind GNU/Linux... although if GNU/Linux weren't a thing, we'd probably still have a lot more Unix boxes in production environments (or even modern OS/2 successors, especially if Microshit decided to prop OS/2 up instead of Mac to avoid becoming a monopoly)Ffmpeg is probably the best FOSS project ever.
I mean specifically how they're going to make it runnable in ffmpeg
No need to inform me, I have a large-v2 right here on this machine
But how do they want to make it run across so many platforms? Use a teeny tiny model?
Maybe they aren't including the model yet (or ever) and it's Bring Your Own Model. But if you use one that's too large it could be too slow for real-time transcription.+It runs automatic speech recognition using the OpenAI's Whisper model.
+
+It requires the whisper.cpp library (https://github.com/ggml-org/whisper.cpp)
+as a prerequisite. After installing the library it can be enabled using:
+@code{./configure --enable-whisper}.
+
+The filter has following options:
+
+@table @option
+@item model
+The file path of the downloaded whisper.cpp model (mandatory).
+
+@item language
+The language to use for transcription ('auto' for auto-detect).
+Default value: @code{"auto"}
+
+@item queue
+The maximum size that will be queued into the filter before processing the audio
+with whisper. Using a small value the audio stream will be processed more often,
+but the transcription quality will be lower and the required processing power
+will be higher. Using a large value (e.g. 10-20s) will produce more accurate
+results using less CPU (as using the whisper-cli tool), but the transcription
+latency will be higher, thus not useful to process real-time streams.
+Consider using the vad_model option associated with a large queue value.
+Default value: @code{"3"}
There are probably missile/bomb guidance systems in current use by the US military that use FFMPEG because many processors natively support it.Ffmpeg is probably the best FOSS project ever.
wtf I hate ffmpeg nowThere are probably missile/bomb guidance systems in current use by the US military that use FFMPEG because many processors natively support it.
it is part of the holy trinityFfmpeg is probably the best FOSS project ever.
Do they all have rootkits?it is part of the holy trinity
ffmpeg, curl and sqlite.
Best and FOS in the same sentence...Ffmpeg is probably the best FOSS project ever.
They're open source retard.Do they all have rootkits?
And my 54 yo friend cant obfuscate a rootkit inside... dont make me laugh please... nobody is checking open shource (FOS) trash they js blindly trustThey're open source retard.
If there was something as deep as a rootkit, it would be hard to hide and likely any attempts to put such in would have been found by now. I don't think there's ever been any cases of a rootkit being in an open source project and not being detected.And my 54 yo friend cant obfuscate a rootkit inside... dont make me laugh please... nobody is checking open shource (FOS) trash they js blindly trust
People have looked over it, but that doesn't mean it's free of security vulnerabilities (Heartbleed) or even intentional backdoors (xz). But I feel like a rootkit would be especially tough to hide from people looking at the code.Didn't heart bleed show that just because a project is open source it doesn't mean someone has looked over it?
- 2013 to 2021, arbitrary code execution on pretty much anything running a Java server. 93% of enterprise clouds affected.a rootkit would be especially tough to hide from people looking at the code.
One factor you’re forgetting is that the folks who know about exceptionally long-lived backdoors in software don’t want to reveal them, because 1) they are useful and 2) the longer they sit undetected, the funnier the situation becomes.If there was something as deep as a rootkit, it would be hard to hide and likely any attempts to put such in would have been found by now. I don't think there's ever been any cases of a rootkit being in an open source project and not being detected.