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

will try to pop it up later when I've had a chance to review it a bit. it started out well defined but I think it got a bit messy.


lunemercove
@lunemercove

seems to have worked, need to check nothing weird happened. have additional caveats for later, as well.


lunemercove
@lunemercove

https://gist.github.com/lunemercove/e4e9404b6a50478bceac05fb253df631
this solves the problem of a video file which is several separate videos concated together. this is a thing they do for runs of 7-8 episodes on the official JJBA blu-ray disks, and additionally I found it was done for the special features and trailers on my Journey to the West blu-ray. the argument parsing is like half the file because I wanted to have a lot of control over the resulting files, so that I could set this loose and be 99% done with the resulting files.

hope it's helpful, I got through the last three episodes of Battle Tendency with it, and am now setting it loose overnight on episodes 1-8 of Diamond is Unbreakable.

Embedded under the break if you want to see it in post. it's 300 or so lines I wrote mostly in a Heightened State yesterday.


known improvables:

  1. could stand to have it fork intentionally and with parameters (previously it forked per split, which wasn't intended behavior and which got fixed trying to see ffmpeg's output)
  2. it could better show ffmpeg's output. initially it didn't capture it at all, now it outputs it with extra newlines. Ideally it would give you an option of direct output (without extra lines), or catching the frames line in ffmpeg's output and summarizing that for you (per thread, maybe).
    2a) bonus points to do readline stuff so it's not taking up huge amounts of console. https://pypi.org/project/clint/ could help.

You must log in to comment.

in reply to @lunemercove's post:

the biggest outstanding Mess is it doesn't capture the ffmpeg output (not sure why, it should. think it's a stderr/stdout distinction thing), and that it kind of shotguns out various subprocesses because I didn't quite think about what I was writing. but it does appear to work.