qyot27
@qyot27.bsky.social
Stubbornly clinging to physical media. Sometimes I help build stuff.
Yeah, if we called it anything other than a VCR, the word wasn't 'player', it was 'deck'.
A VHS tape was still housed in a cassette, and you used audio cassettes in a cassette deck/tape deck, so 'VHS deck'. But that also tends to conjure up images of rack-mounted hi-fi equipment.
A VHS tape was still housed in a cassette, and you used audio cassettes in a cassette deck/tape deck, so 'VHS deck'. But that also tends to conjure up images of rack-mounted hi-fi equipment.
January 11, 2026 at 11:49 PM
Yeah, if we called it anything other than a VCR, the word wasn't 'player', it was 'deck'.
A VHS tape was still housed in a cassette, and you used audio cassettes in a cassette deck/tape deck, so 'VHS deck'. But that also tends to conjure up images of rack-mounted hi-fi equipment.
A VHS tape was still housed in a cassette, and you used audio cassettes in a cassette deck/tape deck, so 'VHS deck'. But that also tends to conjure up images of rack-mounted hi-fi equipment.
AviSynth has nothing to do with the .NET framework? It's purely C++ (with both C++ and C APIs for 3rd party apps/plugins) and was initially targeted to VC6.
VapourSynth did have platform agnosticism as a boon for a while, but AviSynth+ has been cross-platform since March 2020.
VapourSynth did have platform agnosticism as a boon for a while, but AviSynth+ has been cross-platform since March 2020.
December 22, 2025 at 1:28 AM
AviSynth has nothing to do with the .NET framework? It's purely C++ (with both C++ and C APIs for 3rd party apps/plugins) and was initially targeted to VC6.
VapourSynth did have platform agnosticism as a boon for a while, but AviSynth+ has been cross-platform since March 2020.
VapourSynth did have platform agnosticism as a boon for a while, but AviSynth+ has been cross-platform since March 2020.
I thought that might have been it. The dependency on nnedi3 is probably the only *core* blocker from allowing the native Mac version of AviSynth+ from using QTGMC.
September 28, 2025 at 6:54 PM
I thought that might have been it. The dependency on nnedi3 is probably the only *core* blocker from allowing the native Mac version of AviSynth+ from using QTGMC.
Which plugins are the issue?
September 28, 2025 at 6:26 PM
Which plugins are the issue?
So was I. ccextractor is for extracting EIA-608 captions (amongst others) from video streams. FFmpeg can extract them by using a video filter, but it's much much slower.
Although looking at the help now, extracting captions from DVD might require stitching the video stream together in TS first.
Although looking at the help now, extracting captions from DVD might require stitching the video stream together in TS first.
May 29, 2025 at 2:35 AM
So was I. ccextractor is for extracting EIA-608 captions (amongst others) from video streams. FFmpeg can extract them by using a video filter, but it's much much slower.
Although looking at the help now, extracting captions from DVD might require stitching the video stream together in TS first.
Although looking at the help now, extracting captions from DVD might require stitching the video stream together in TS first.
ccextractorwin -nobom "input.mp4"
ffmpeg -i "input.srt" "output.en.ass"
sed -i 's/PlayResX: 384/PlayResX: 512/' "output.en.ass"
Edit/resample to 1080p with Aegisub. For DVD, you'd probably need to give it the correct .ifo for the title, since the video can be spanned across multiple .vob files.
ffmpeg -i "input.srt" "output.en.ass"
sed -i 's/PlayResX: 384/PlayResX: 512/' "output.en.ass"
Edit/resample to 1080p with Aegisub. For DVD, you'd probably need to give it the correct .ifo for the title, since the video can be spanned across multiple .vob files.
May 28, 2025 at 12:09 AM
ccextractorwin -nobom "input.mp4"
ffmpeg -i "input.srt" "output.en.ass"
sed -i 's/PlayResX: 384/PlayResX: 512/' "output.en.ass"
Edit/resample to 1080p with Aegisub. For DVD, you'd probably need to give it the correct .ifo for the title, since the video can be spanned across multiple .vob files.
ffmpeg -i "input.srt" "output.en.ass"
sed -i 's/PlayResX: 384/PlayResX: 512/' "output.en.ass"
Edit/resample to 1080p with Aegisub. For DVD, you'd probably need to give it the correct .ifo for the title, since the video can be spanned across multiple .vob files.
One of these days I'll rewatch Code Geass.
May 7, 2025 at 10:11 PM
One of these days I'll rewatch Code Geass.
My only weird reaction was that graphic at 8:13. Three different flavors of Ubuntu (using the really old logos, at that), and three¹ *very* dead distros.
¹I had to look up the third one (Foresight), though. I knew Sabayon and Mandriva were long gone.
¹I had to look up the third one (Foresight), though. I knew Sabayon and Mandriva were long gone.
April 27, 2025 at 9:16 PM
My only weird reaction was that graphic at 8:13. Three different flavors of Ubuntu (using the really old logos, at that), and three¹ *very* dead distros.
¹I had to look up the third one (Foresight), though. I knew Sabayon and Mandriva were long gone.
¹I had to look up the third one (Foresight), though. I knew Sabayon and Mandriva were long gone.
But I shudder to think about trying to wield an AviSynth filter chain as a CLI argument like with libavfilter, instead of as a normal script.
March 29, 2025 at 7:23 PM
But I shudder to think about trying to wield an AviSynth filter chain as a CLI argument like with libavfilter, instead of as a normal script.
It was completely replaced in 2013 with a proper demuxer that interfaces directly with the AviSynth library through the C interface, using LoadLibrary (on Windows) or dlopen (on all the other OSes) in a similar fashion to how x264 does.
March 29, 2025 at 7:23 PM
It was completely replaced in 2013 with a proper demuxer that interfaces directly with the AviSynth library through the C interface, using LoadLibrary (on Windows) or dlopen (on all the other OSes) in a similar fashion to how x264 does.
Fun fact, AviSynth support in FFmpeg (2006) existed before libavfilter (2008).
Although that's maybe not the best comparison, because the 2006 version was really just a Video for Windows demuxer that only handled *.avs scripts as input.
Although that's maybe not the best comparison, because the 2006 version was really just a Video for Windows demuxer that only handled *.avs scripts as input.
March 29, 2025 at 7:23 PM
Fun fact, AviSynth support in FFmpeg (2006) existed before libavfilter (2008).
Although that's maybe not the best comparison, because the 2006 version was really just a Video for Windows demuxer that only handled *.avs scripts as input.
Although that's maybe not the best comparison, because the 2006 version was really just a Video for Windows demuxer that only handled *.avs scripts as input.