Yeah, you’ve pretty much hit the nail on the head. After hearing the dev’s justification I can see what they were going for, but it’s really poorly handled in-game IMO.
They way it plays out in the story feels neither darkly comic nor a poignant commentary on parents going though a divorce; instead it just comes across as unnecessarily cruel, and the player has no choice but to go along with it.
The issue isn’t the use of conflict as a dramatic device per se; it is essentially forcing the player(s) to perform a seemingly unnecessary and unpleasant action against their will.
The fact that both main characters in the game appear to immediately decide that violently murdering their child’s favorite toy is the only course of action and that no alternative is offered is really jarring. Giving the player some agency in choosing an alternative way to to go about it would have solved the problem completely.
Thanks for the explanation, although I don’t find it a particularly acceptable one. The sequence wasn’t funny enough to justify the dramatic shift in tone in an otherwise family-friendly game, IMO. Also, making the protagonists unlikable in a game where you’re supposed to find them sympathetic is a very weird design decision.
Yeah, that part was a distinct bum note in an otherwise enjoyable game. Why the developers thought it was good idea, I’ll never know.
I use FLAC for long-term storage, 256kbps Ogg when transcoding for mobile devices.
Opus is the best lossy codec in terms of efficiency, but many devices/apps don’t properly support it.
Except Debian is neither interesting nor innovative.
This didn’t happen to OP, and it isn’t recent - look at the report date.
This happened back in 2021 and apparently blew up on Reddit and Twitter, causing OpSec to release a public statement that claimed that the DMCA notice was a fake.
https://news.itsfoss.com/ubuntu-download-dmca-notice/
https://torrentfreak.com/opsec-says-dmca-notice-system-was-spoofed-to-target-ubuntu-download-210527/
Nah they got it right the first time.
For your use case, I’d go with Lossless Cut as opposed Shotcut, Openshot, etc.
The reason being that it is much simpler and faster to use, and generally results in smaller filesizes because you aren’t having to re-encode from scratch.
Going from 192kbps to 320kbps would be audibly negligible unless you used a really bad codec to begin with, in which case adding AI into the mix would likely just compound the problem.
Probably not even worth it, tbh.
The difference is my six-year-old daughter isn’t going to be playing Spec Ops: The Line or Call of Duty.