Well atleast its working at all. 
Can anyone post an updated ntruehd v3 build that we peasants can download?
I can compile and upload a new ntruehd v3 build later today.
2 Likes
True. True 
I have learned a lot building mpv using your modified build instructions so thank you I think I’m going back to using MPV by itself because Plex HTPC seems to be going down a path that is reducing performance. But I will still be using your build until ffmpeg is sorted
Just wanted to start off by thanking you for your commits and builds I appreciate the work it helps a lot.
You can auto build and release on github with github actions. Public repos are allotted 2000 build minutes monthly. You can check how many minutes you’ve used this month :
https://github.com/settings/billing/summary
You already are running actions on your fork:
https://github.com/mitzsch/mpv/actions
Which builds for multiple platforms and you haven’t come close to hitting the limit. So you could remove some of these platforms to save on minutes if you want while also adding a few github actions to your repo to auto build and release.
https://github.com/actions/create-release
&
https://github.com/actions/upload-release-asset
There is also other free public options for auto release with actions:
https://github.com/marketplace?category=&type=actions&verification=&query=auto+release
Either way if you add auto build/release actions or not I’d love for you to post releases on github and not just on gdrive if possible, I want to setup a RSS feed for your releases so I can auto fetch them with scripts and such. 
Thanks again.
2 Likes
Thanks for the tips on GitHub action - I will definitely take a look at it!
1 Like
New build:
Its based on the patched mpv branch => GitHub - mitzsch/mpv at plex-htpc-hdr-patches
3 Likes
Thanks!
Update
GitHub build/release system is wip and it looks promising!
I just found the repo from zhongfly (GitHub - zhongfly/mpv-winbuild: Use Github Action to build mpv for Windows with latest commit.), where everything about building with Github is already coded.
I made a fork and edited the files to initiate an mpv-plex-ntruehd compile process. It runs!
=> https://github.com/mitzsch/mpv-winbuild/actions/runs/9014283774
Hopefully, the automatic release process also works… If everything is working, I will do some polishing and we should have automatic builds.
2 Likes
Good job! I will probably continue with my local builds just to keep up the practice but this is good news.
The first build release is up!
=> Release 2024-05-09 10:58 · mitzsch/mpv-winbuild · GitHub
I will do some polishing when I have more time… wip…
1 Like
Just tested this build. the ntruehd works properly here with no drop outs unlike my local build which is strange because they should be the same. Anyway good job
Great to see this! Can your same builds be made for the non-v3 version? It looks like the source you are forking from includes those.
Non-v3 will also be available. In fact I don´t need to change anything to also get non-v3 builds… for initial testing, I started with v3 builds… The next workflow run will also include non-v3 builds.
The new workflow run with also non-v3 builds is up => you can download the builds after the workflow finishes (3h from now, the non-v3 build env needs to be compiled from source…) from the workflow overview
2 Likes
New release:
The repo already works perfectly fine but still needs polishing.
3 Likes
Sad that I am no longer use Plex HTPC but your builds and notes keep me interested in future progress
1 Like
Thank you so much for the github builds, this is greatly appreciated :).
@Mitzsch, Great job on the work patching the ffmpeg truehd passthough issue. I grabbed your git project back in Dec 2023 and was able to build mpv locally with both gcc and clang. Since then shinchiro updated that project (the one you are forked from) to use static libs and now there is an issue building llvm. During the last stage of “ninja llvm” when it links the executables it is using libstdc++.so (dynamic lib) instead of libstdc++.a (static lib) which causes a link error. I fixed this locally by adding the “-static-libstdc++” in the linker options. Building the gcc toolchain works fine.
Just curious if you are experiencing the same issue?
OS: Ubuntu 22.04 LTS
CMake: 3.29.3
Meson: 1.4.0
Target: x86_64-w64-mingw32
I’m not facing such an issue, but I don’t use Ubuntu. I have used Ubuntu in the past, it worked for a bit, but then the packages got out of date and completely broke the building environment. That’s why I switched to Arch Linux. The GitHub action workflow also uses Arch Linux. No problems there.
My system neofetch output:
[root@anarchy:~]# neofetch (05-12 09:10)
-` root@anarchy
.o+` ------------
`ooo/ OS: Arch Linux x86_64
`+oooo: Host: VirtualBox 1.2
`+oooooo: Kernel: 6.8.9-arch1-2
-+oooooo+: Uptime: 2 mins
`/:-:++oooo+: Packages: 329 (pacman)
`/++++/+++++++: Shell: zsh 5.9
`/++++++++++++++: Resolution: 1280x800
`/+++ooooooooooooo/` Terminal: /dev/pts/0
./ooosssso++osssssso+` CPU: AMD Ryzen 9 3950X (6) @ 3.493GHz
.oossssso-````/ossssss+` GPU: 00:02.0 VMware SVGA II Adapter
-osssssso. :ssssssso. Memory: 136MiB / 15996MiB
:osssssss/ osssso+++.
/ossssssss/ +ssssooo/-
`/ossssso+/:- -:/+osssso+-
`+sso+:-` `.-/+oso:
`++:. `-/+/
.` `/
meson: 1.4.0
cmake version 3.29.3
Target: -DTARGET_ARCH=x86_64-w64-mingw32 -DGCC_ARCH=x86-64-v3
Have you tried Arch?
