Don’t know anything about software development and third-party dependencies then? They probably cannot fix it on their own.
If a problem with software arises, and it’s not clear whether the problem lies with one’s own software, or the third-party one, then it requires some joint, and separate, discovery processes.
Now if one is a relatively small fry dealing with a mega enterprise that may not necessarily have a vital interest in your software working with their product, then you are largely, if not totally, at the mercy of that enterprise’s timing priorities.
And one cannot always isolate by oneself exactly what it is an OS is doing that may be upsetting the cart. While your software may be doing the same calls to the OS it always has, if the ‘magic’ happening in the called OS function’s logic has changed, and it doesn’t provide a return code that indicates why the difference in the treatment of the call, then you are TOTALLY dependent upon the OS maker for resolution.
This is what happened with Windows 10 and MS changing how MCSS operated. MS fixed it, and suddenly everything across all SBs programs is OK, and SB gives the thumbs up. Even though the MS audio team lead is highly engaged in making things work, it still took the time it took to discover where the problem lay, work out the solution, and get the fix through their patch process, all nothing SB could do a thing about, until it was a fait accompli.
Certainly, once the patch dropped, SB was able to quickly test and certify that all their programs were compliant, which probably means they had already done all the rest of their regression testing, except for those bits affected by the outstanding issue. I suspect that SB would have done much the same with El Capitan, and once the issue is fixed, things may well move quickly here as well. That is, unless Apple has done one of their ‘line in the sand’ ideological cutoffs (such as with Firewire audio), for which SB may have to redesign the program to achieve its same functionality in other ways, with its consequent delays, though at least they could then have something to report to us.
Of course, MS might need to have, for their own priorities, not ‘fixed’ the changes in MCSS functionality, and SB would also have just had to do a functional redesign around it.