LAVFilters VS gron

Install lav filters on your pc because I think that the cutscenes use it. Get it from https://github.com/Nevcairiel/LAVFilters/releases. Try it and let me know what happens.

The first is that it's a codec issue. I don't know what codec they'd be using but you may need to install another decoder to get it to play cleanly. With a bit of luck it's part of the LibAV collection, so LAVFilters should include it and installing those may be enough on their own.

You could also install any DirectShow codec. Such as LAVFilters. (https://github.com/Nevcairiel/LAVFilters)

K-Lite is still around? I just use clsid's MPC-HC and LAVFilters now that CCCP is dead. I've seen some cases where this combination worked much better than VLC (video playback in VLC was choppy, while MPC-HC+LAVf worked fine).

is it this? https://github.com/Nevcairiel/LAVFilters/releases

If you have your speakers/av amp setup over HDMI then your best bet as others have suggested it to bitstream it. personally I always use LAVFilters with PotPlayer, they support pretty much every format under the sun and support bitstreaming as a per format option.

You could also try LAV filters.

Yes, and sadly yes. LAVfilters and clsid's MPC-HC are decent replacements.

gron (https://github.com/tomnomnom/gron) to transform it and query and then invert the transformation?

It buffers all of its output statements in memory before writing to stdout:

https://github.com/tomnomnom/gron/blob/master/main.go#L204

Have you tried `gron`?

It converts your nested json into a line by line format which plays better with tools like `grep`

From the project's README:

▶ gron "https://api.github.com/repos/tomnomnom/gron/commits?per_page..." | fgrep "commit.author"

json[0].commit.author = {};

json[0].commit.author.date = "2016-07-02T10:51:21Z";

json[0].commit.author.email = "[email protected]";

json[0].commit.author.name = "Tom Hudson";

https://github.com/tomnomnom/gron

It was suggested to me in HN comments on an article I wrote about `jq`, and I have found myself using it a lot in my day to day workflow

> So all I want is a tool to go from json => line oriented and I will do the rest with the vast library of experience I already have at transformations on the command line.*

The tool for that is likely https://github.com/tomnomnom/gron

If JQ is too much, see GRON &| Miller

gron transforms JSON into discrete assignments to make it easier to grep for what you want https://github.com/tomnomnom/gron

Miller is like awk, sed, cut, join, and sort for data formats such as CSV, TSV, JSON, JSON https://github.com/johnkerl/miller

And jless [1] and gron [2].

This is the first I'm hearing of gron, but adding here for completeness sake. Meanwhile, JSON seems to be becoming a standard for CLI tools. Ideal scenario would be if every CLI tool has a --json flag or something similar, so that jc is not needed anymore.

[1] https://jless.io/

[2] https://github.com/tomnomnom/gron