Not to be an "idea guy" who comes up with things for other people to do; however,
At this stage I'm thinking it would be nice if WineHQ had a specialized wine-audio branch that was more predictable (slow-to-change) and focused than wine-staging, which could serve as a single target for current Windows plugin developers.
Maybe then more Windows plugin devs could coordinate with CodeWeavers and WineHQ devs even if just to say: "These are the dlls and functions that we target for audio and graphics in our plugins" -- instead of volunteer fans poking the various black-boxes to see what works and what doesn't.
[On a side-note, I imagine CodeWeavers already has analysis tools that could help with such determinations, but it might be a matter of getting written permission from the devs to analyze their plugins that way.]
Maybe as a parallel to Proton and ProtonDB for games, even before a wine-audio branch is realized, there could be a Wine-AudioDB where results of what works (i.e., winetweaks and overrides) could be collected, and maybe those could also be collected in a way that commonalities and other patterns could be easy to discover.
But sure, it would be fair for Linux-interested Windows plugin devs to say, "It has been reported that our plugins work well with wine-music through yabridge (or other bridging apps) on Linux in some cases, but we can't guarantee success in all cases" (or similar).
At this stage I'm thinking it would be nice if WineHQ had a specialized wine-audio branch that was more predictable (slow-to-change) and focused than wine-staging, which could serve as a single target for current Windows plugin developers.
Maybe then more Windows plugin devs could coordinate with CodeWeavers and WineHQ devs even if just to say: "These are the dlls and functions that we target for audio and graphics in our plugins" -- instead of volunteer fans poking the various black-boxes to see what works and what doesn't.
[On a side-note, I imagine CodeWeavers already has analysis tools that could help with such determinations, but it might be a matter of getting written permission from the devs to analyze their plugins that way.]
Maybe as a parallel to Proton and ProtonDB for games, even before a wine-audio branch is realized, there could be a Wine-AudioDB where results of what works (i.e., winetweaks and overrides) could be collected, and maybe those could also be collected in a way that commonalities and other patterns could be easy to discover.
But sure, it would be fair for Linux-interested Windows plugin devs to say, "It has been reported that our plugins work well with wine-music through yabridge (or other bridging apps) on Linux in some cases, but we can't guarantee success in all cases" (or similar).
Statistics: Posted by havran — Mon Oct 07, 2024 2:51 am