3 ms·
These are all my scripts. They're object-oriented, self-documented, tab-completable and a `hg clone` away. They're simply more polished versions of what I could
by netmare 3y ago
These are all my scripts. They're object-oriented, self-documented, tab-completable and a `hg clone` away. They're simply more polished versions of what I could do on Windows with built-in PowerShell (and FFPROBE of course):
F:films> filter probe_format {
ffprobe $_.fullname -v error -show_entries format=duration -of json |
convertfrom-json | % format
}
F:films> ls -file -rec | ? extension -in .mp4,.avi,.mkv | probe_format |
measure -sum duration | % { New-TimeSpan -Seconds $_.sum } | % tostring
15.12:18:09 # same result as before (15days+12hours, etc.)
Even this makes much more sense to me than the Unix equivalent. I realize that Bash/AWK was better than CMD.EXE batch files, but, come on...
- forgotpwd16 3y agoThat looks pretty nice actually. But can be said the extra need to output and convert from json to object format introduce an extra complexity compared to the similar bash and fam command. Otherwise can see how the others parts (listing all files and choosing by extension, summing up a specific field from the output) can be more intuitive.