🎞️ A developer managed to reverse pixelation in video using FFmpeg, GIMP and edge detection - no AI involved.

By analyzing motion and edges across frames, they could reconstruct original content from blurred areas.

It’s a reminder: pixelation is visual, not secure.

🛠️ Code & demo: https://github.com/KoKuToru/de-pixelate_gaV-O6NPWrI

#infosec #opensource #ffmpeg #linux #osint #devtools #technews

So I have hundreds of videos of ~1 minute recorded from my phone ~10 years ago, and they generally don’t have that great compression, nor they are stored in a modern and advanced video format.

For archiving purposes, I want to take advantage of my workstation’s mighty GPU to process them so that the quality is approximately the same, but the file size would be strongly reduced.

Nevertheless, compressing videos is terribly hard, and way more complex than compressing pictures, so I wouldn’t really know how to do this, what format to use, what codec, what bitrate, what parameters to keep an eye on, etc.

I don’t care if the compression takes a lot of time, I just want smaller but good looking videos.

Any tips? (Links to guides and tutorials are ok too)

Also, unfortunately I am forced to use Windows for this (don’t ask me why 🫠), but I know nothing about Windows because I hate it. Practical software suggestions are very much welcome, too!

#ffmpeg #help#askFedi #codec#AVI#H265#H264 #movie #video #videoCompression #compression #encoding#HandBrake #heif #heic #avif #mp4 #mkv#Wondows

> Client side content-id comparison.

That's a neat idea!

#transcoding #encoding #video #browser #ffmpeg #webassembly #clientside #videoconverter

awesome!
In the long run it might also make the online transcoding tools with the "Start now" [to download malware]-button obsolete.

Funnily I talked about this [soon solved] problem with my funder @clemensg by phone today.

#transcoding #encoding #video #browser #ffmpeg #webassembly #clientside #videoconverter

just et. al. too
please save us from uploading duplicate files or journalists from writing alt twice with clientside content-id comparison.

Just a thought, from a knuckle-dragging biology scientist. TL;DR: I believe there is scope to make the hosting of a peertube instance even more lightweight in the future.

I read some time ago of people using #webAssembly to transcode video in a user's web-browser. https://blog.scottlogic.com/2020/11/23/ffmpeg-webassembly.html

Since then, I believe #WebGPU has done/is doing some clever things to improve the browser's access to the device's GPU.

I have not seen any #peertube capability that offloads video transcoding to the user in this way.

I imagine, though, that this would align well with peertube's agenda of lowering the bar to entry into web-video hosting, so I cannot help but think that this will come in time.

My own interest is seeing a #Piefed (activitypub) instance whose web-pages could #autotranslate posts into the user's own language using the user's own processing power... One day, maybe!

Thank you again for all your hard work; it is an inspiration.

#mastodon#webVideo #HLS #transcoding #video #decentralization#edgeComputing#webGL#W3C #activitypub#AI #ffmpeg #selfhosted #degoogle #mathstodon

Dear sound/audio folks and engineers,

I have a directory with 3.5GiB of audio files (chiefly opus & m4a) which are spoken word recordings.

Some of them are quite low, and some of them are quite dynamic such that it's a whisper at times and nearly a shout at other times.

I've processed a lot of them with #audacity's compressor filter or #ffmpeg (ffmpeg -i audio.m4a -filter:a "speechnorm=e=50:r=0.0001:l=1" audio-normalized.m4a), but there are some unprocessed files in the collection, which are a pain to individually find and fix.

Is there a way from the #CommandLine to detect the loudness and/or dynamic range of audio files so that I can automatically flag them for processing with ffmpeg?

Thanks!!

#audio #sound #SoundEngineering #AskFedi #HiveMind