Announcement
Collapse
No announcement yet.
Error 702 with AV1 HDR10+ Content for MKV (The case for upgrading ffmpeg)
Collapse
X
-
Yeah!! Looks like they are using GPAC 2.5 (MP4Box), as well. Rev. 8349? The latest GPAC revision beta version is 1474. I guess that might be a good indication that SF has compiled their own version of the latest MP4Box. Things are looking up! Still need to check on aria2c, atomicparsley, mediainfo, and shaka. If it wasn't for the Peacock issue raised by 0xFeedBeef I'd have 6238 installed already and know if those were updated, too. If they are, that will be the first time in more than two years that I won't have to modify anything in a SF release.
Comment
-
Originally posted by Germania View PostMP4Box in SF 6238 is 2.4-rev0-g5d70253ac-HEAD ..
.. the shown 2.5-DEV-rev8349 is what NF used (different for releases)
Comment
-
Just checked the files that I routinely update, and it looks like I'm still going to be doing the updating myself for a while. Both Arias2c and AtomicParsley need to be updated in the YouTubeDL folder. The latest releases can be had at GitHub, https://github.com/aria2/aria2 and https://github.com/wez/atomicparsley, respectively. Then in the main StreamFab folder, you have shaka-packager which needs to be updated. That can be found at GitHub, also. https://github.com/shaka-project/shaka-packager It downloads as packager-win-x64 and needs to be renamed to shaka-packager.exe for SF. And lastly, MediaInfo needs updating. You can get mediainfo.dll at https://mediaarea.net/en/MediaInfo/Download/Windows.
I'm not totally happy with the update for FFmpeg. Not that it matters much, I like to use the builds put out by BtbN, and they like to use those put out by Gyan. The big issue is that they have decided to use the 7.11 Release build, whereas I always use the latest Master build. This is what Gyan says about Release vs. Master. The bold font is his, not mine.
FFmpeg's source code is maintained using a version control system called git. The git master builds are built from the master branch of the repository, which is where all development occurs whereas the release builds are built from the latest release branch. These are essentially a snapshot of the master branch at a given point of time. They are updated with bug and security fixes for a while but no new features. It is highly recommended to choose a git master build; unlike many software, releases are primarily made for the convenience of OS distributors and package managers and don't signify greater stability or maturity. For a bug report to be accepted, the issue must be reproducible using a very recent git master build.
They still have work to do.
Comment
Comment