shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

261
active users

#ffmpeg

2 posts2 participants0 posts today
Replied in thread

@sotolf @joel

Millennial/Zoomer long-form podcast enjoyers vs. GenX Zero Attention Span dude. XD

(To be fair, I have had some audio things that were over nine hours long, but they were compilations of several sermons concatenated together (and audio-equalized) with #ffmpeg)

Replied in thread

@christianp

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. blog.scottlogic.com/2020/11/23

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.

Scott LogicIn-browser transcoding of video files with FFmpeg and WebAssemblyThe WebAssembly build of FFmpeg allows you to run this powerful video processing tool directly within the browser. In this blog post I explore FFmpeg.wasm and create a simple client-side transcoder that streams data into a video element, with a bit of RxJS thrown in for good measure.

Re: okla.social/@johnmoyer/1147381

rsok.com/~jrm/2025May31_birds_

ffmpeg -loop 1 -i IMG_3666cs_gimp.JPG -y -filter_complex "[0]scale=1200:-2,setsar=1:1[out];[out]crop=1200:800[out];[out]scale=8000:-1,zoompan=z='zoom+0.005':x=iw/3.125-(iw/zoom/2):y=ih/2.4-(ih/zoom/2):d=3000:s=1200x800:fps=30[out]" -vcodec libx265 -map "[out]" -map 0:a? -pix_fmt yuv420p -r 30 -t 30 video_IMG_3666c_2.mp4

Replied in thread

@snacks that's because #ffmpeg was built by more people and can utilize more acceleration options (from SSE-SSE4.2) beyond vendor- & generation-proprietary code (GPU-Encoders & Decoders expect to get a native bitstream fed like hardware in dedicaded CD-/DVD-/bluray players)

  • Add to that parralelization and thousands of micro-optimization from how it ingests files to transcoding to how to optimize codec settings for the best possible results and you get a better product.

Not to mention big players from Alibaba to Zoom, from Amazon to Netflix and from Apple to Sony have a vested interest in it's performance, because bandwith, storage and computational power are expensive for them.

Usually, I'm quite happy with #Linux:

It just works, and I don't have to think about it at all.

But sometimes, I reckon: If it sucks, it sucks badly.

I use the command line video editor #ffmpeg quite a lot, but yesterday, it just stopped working, first producing wrong results and then weird error messages.

Internet search for the error messages gave lots of results from the 2010s and Reddit threads where the issue remained unresolved.

"OK", I thought, "Let's do what everyone does":

1/3

Replied in thread

@jcrabapple I had a few stumbles with #JellyFin to start (around it needing a special - but sanctioned - build of #ffmpeg on my platform), but once I figured that out it has been smooth sailing and Im quite enjoying it. Although metadata success relies on proper media curation, but #Filebot has been super helpful there and worth its one-time cost.

If only there were #xbox and #ps5 clients for it; rn i use a low power linux box for playback on my TV.

Replied in thread

🧵 3/3 - The Making Of

I kept getting #HTTP 413 "Payload Too Large" errors on my instance - it's not actually mine-mine, i'm just a guest here - layer8.space is run by @Sammy8806. (thanks, mate 🖖)

👉 1st, there was 1080p60 with audio
👉 then i trimmed and rendered it out as 720p30 with audio on the Galaxy S7
👉 on the PC, using #ffmpeg, i've removed the audio and rendered it out at 15 fps
👉 i've cropped it to 5 seconds

ffmpeg -i src.mp4 -an -c:v libx264 -vf "fps=15" -t 5 out-15fps-noaudio-5s.mp4

Continued thread

Reference mix is on top; our mix is on bottom. These are normalized to -1 dB peak, because I am specifically evaluating the mix. (If I just wanted to compare how they sounded and which I preferred, then it would make sense to normalize to perceived loudness, the default for #ffmpeg-normalize.)

Our mix has more dynamic range, prob too much. That fits _my_ tastes, but it's not what the market prefers. You can see some limiting in the ref mix, but not excessive.

I was puzzling over why so many of my spoken word audio tracks were suddenly so muted, and I thought I was going to have to re-process all 70 of them.

Y'all, the bluetooth volume on my phone was set low.

XD

But at least now I know how to batch-detect quiet tracks with #ffmpeg!

Continued thread

#ffmpeg nachinstalliert. Das löste das Problem unter #Windows. Hat aber auch nicht geholfen. Wahrscheinlich bleibt mir nix anderes übrig, als extra dafür nun eine VM mit Windows aufzusetzen. Wollte ich eigentlich nicht.

Leider habe ich keine Video Schnittsoftware als #Opensource gefunden, die die Features von Cuttermaran bietet.
* Schnitt auch auf B-Frame
* Geschnittene Videos werden nur kopiert. Nur die Schnittstellen werden über den #Encoder geschleust.

Any idea?