lunemercove

witchy girl/virtual snep

^ computer witch ^
^ self-taught 3D modeller ^
^ 🏳️‍⚧️, fan of girls ^
^ old enough ^
^ anarchist 🟥⬛^


see them uncombined here


you can always find me here
lune.gay/
the blog specifically
lune.gay/blog/

lunemercove
@lunemercove
made with @nex3's grid generator

gonna see if I can browbeat plex into counting them separately later, but I at least am going to register my displeasure in [bracketed additions].

also: we meet again, ffmpeg timestamp cutting, my oldest foe. I think doing an encoding in the process will make it easier but ughhhhhhhhhhhhh. I should also be doing shorter samples to test the encoding quality before committing, but: I don't wanna. I wanna just send off a whole command and then see in the morning if I like it. also I'm starting with 18 which is "effectively lossless", so what's mostly going to matter in terms of quality is when I try again with 20 later and see the results of that.


lunemercove
@lunemercove
made with @nex3's grid generator

and yes I spend a lot of time on Wikipedia or TVDB copying these titles out and will continue to do so. I like being able to know what I have on the CLI level.


You must log in to comment.

in reply to @lunemercove's post:

ffmpeg timestamp cutting is my oldest foe because you can't cut exactly on timestamps without re-encoding, generally. because it comes down to where the frames are because [this is where I lose the ability to explain video encoding]. bane of my existence trying to snip out bits of game clips before getting Vegas and then Davinci to do that. and part of the reason I could never get my project to put vtuber and giant bomb commentary tracks into my movie files off the ground.

(though hey, maybe I'll give that another try if I can go dig up those commentary files. but only after all the other media cleanup I gotta do)