Skip to content
  • 0 points on The Way to the Wormhole in !tenforward@lemmy.world ·

    Glad that it worked for you!

    I have no detailed knowledge of how to suppress specific information output of ffmpeg. I actually like that it vomits out so much information; I have my terminal scroll back set to essentially infinite and can so better analyze what went wrong or not quite right.


    Okay, now I know more: svt-av1 apparently pipes all its info as stderr, and that’s why -loglevel error doesn’t suppress it and why >/dev/null also doesn’t suppress it since this only redirects stdout to the void. You could do 2> /dev/null and suppress all stderr, or you could append it to a temp file with 2>> /tmp/ffmpeg-error.txt.

    But I found a better solution in a superuser answer:
    You can use the SVT_LOG environment variable like so:

    SVT_LOG=1 ffmpeg -y -hide_banner -loglevel error -i *.mp4 -an -c:v libsvtav1 -crf 34 -preset 6 -svtav1-params fast-decode=2 -g 300 -pix_fmt yuv420p -vf "fps=25, scale=-1:480" 'test4'.avif
    

    SVT_LOG=1 only gives actual errors, and you can make it permanent by adding export SVT_LOG=1 to your shell profile.


    Another thing: -quality 80 doesn’t do anything, and ffmpeg even gives a warning, which you suppressed. Quality is being controlled by -crf 34, see the wiki.

  • 0 points on The Way to the Wormhole in !tenforward@lemmy.world ·

    Change -preset 0 to a higher value; this is the lowest setting and it should in most cases severely slowdown encoding. A value of -preset 6 should be way faster. According to the ffmpeg wiki you can choose between 0 and 13 (13 only for debugging). Higher value → faster encoding. A lower value should give, in most cases, a smaller file (sometimes not; I had cases where 4 was smaller than 0).
    I only used 0 here since it was such a small clip of low-ish resolution and encoding with -preset 0 and -preset 4 were both nearly instantaneous. (size comparison here -preset 0 128K and preset 4 135K)

  • 1 points on The Way to the Wormhole in !tenforward@lemmy.world ·

    lemmy-ui doesn’t support JPEG XL; see this Github issue.

    I can upload JPEG XL images to my instance (lemmy.zip), but they get automatically converted to avif.

    example

    JPEG XL converted to avif
    This was originally a JPEG XL image

    I can embed external JPEG XL images from a file host

    JPEG XL external catbox.moe


    Just realized you both aren’t on lemmy but on piefed and pylova respectively. I actually don’t know the support status of JPEG XL with those two and a quick search of their issues on codeberg didn’t reveal anything.

  • 0 points on The Way to the Wormhole in !tenforward@lemmy.world ·

    I messed around a bit with avifenc and it gave me generally larger encodes with worse quality than just svt-av1 and rav1e with just ffmpeg. Also I remember getting numerous errors with ffmpeg complaining about piping this or that format. I wouldn’t even know which commands in my shell history actually worked. I have to try again with avifenc and experiment more with rav1e too both in ffmpeg and avifenc.

  • 0 points on The Way to the Wormhole in !tenforward@lemmy.world ·

    I made it myself. Here is the ffmpeg command for anyone interested:

    ffmpeg -ss 00:22:47.700 -to 00:22:51.745 -i  *S05E14*  \
        	-filter_complex "[0:v][0:s:0]overlay" \
        	-an -c:v libsvtav1 -crf 34 -preset 0 -svtav1-params fast-decode=2  \
        	-g 300 -pix_fmt yuv420p -loop 0 \
    	'DS9 Way to the Wormhole (small)'.avif
    
    
    • -filter_complex "[0:v][0:s:0]overlay" hardcodes the dvd subs
    • -an -c:v libsvtav1 -crf 34 -preset 0 -svtav1-params fast-decode=2
      • no audio, svt-av1, fast-decode=2 for better playback (maybe just placebo)
    • -g 300 keyframe interval, should probably be higher since we don’t need any
    • loop 0 loops infinitely; for avif, in contrast to gif, you can actually specify how often it should loop.

    Funny thing, the low-quality webp thumbnail that lemmy generated is nearly twice the size of my encoded avif.
    236KiB webp thumbnail vs. 128KiB avif

  • 0 points on Apple is shuttering its 28-year-old online community forum in !technology@lemmy.world ·

    I always wait for the .1 updates or in this case .2 update. The .0 updates are always far to unstable.

    They did add a slider in the settings for their so called “Liquid Glass” so you can eliminate most of the tranparency.

    iOS26 is still getting security updates for a good long while; maybe not for as long as other older iOS versions since all devices that supported iOS26 also support iOS27.

  • 2 points on Apple is shuttering its 28-year-old online community forum in !technology@lemmy.world ·

    Damn that’s terrible. My old iphone still functions the same as before; mine is far to old for any AI feature so I don’t get bothered by it. I did need to reset some bluetooth devices in the last year, but so far I did have any major problems in that area.

    I didn’t realize that accessibility had gotten so bad. For me ios is now still visually more or less the same as ios18, despite all the buzzwords. I also was under the impression that ios played rather nice with hearing aids, but I don’t need those personally so I don’t have any first hand experience.

    Yeah, every new ios reelease has just a bunch of buzzword stuck together and nothing most people want.

    I hope you have better luck with your next phone, which from the sound of it won’t be an iphone.

  • 1 points on Apple is shuttering its 28-year-old online community forum in !technology@lemmy.world ·

    What exactly offended you about ios26 and ios27?

    I’m out of the loop. For me it seems like the same as before. There weren’t any interesting features in these updates, but that’s pretty par for the course with ios updates.