this post was submitted on 02 Apr 2024
1067 points (95.9% liked)
Programming
17661 readers
246 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Hilariously the issue was just a setting change in the update, that you can easily change via a command option. They saw thing didn't work, and didn't read the change log at all before asking to pay a one time fee to guarantee it be maintained for them.
So ffmpeg gets a few thousand dollars for such a simple answer/solution? Sounds good to me?
The problem is that Microsoft wants to pay that for a permanent "never maintain in a way that breaks caption decoding in any default behaviour we use" with that one time payment.
Its a quick fix on Microsofts end to change a quick flag in ffmpeg. It's also quick on their end to maintain a fork that only changes the default. One time payments for maintenance make open source projects like ffmpeg subject to fail.
Yes, they should have read the update notes. But I don't see much in the way of documentation regarding the data_field cli option in their documentation even now.