The Henery
Member
360 sound was all on CPU, Xbox One has dedicated hardware for it, so they can't exactly do it 1:1 to the original game.
This happened with Halo 2 as well. Halo 2 PC's "radio" filter was barely there compared to the original Xbox version. I imagine this change persists in H2A. The inconsistencies between hardware just results in stuff like that sometimes. But completely different directions wouldn't be a cause of that.
Well, maybe. Even if the dedicated hardware supports a wide variety of filtering options, it's likely possible to filter on CPU and hand off the results to audio output. Of course even this would have required some amount of porting, and although the Jaguar should be more capable than Xenon in just about every way, it's possible there's not a lot of headroom with Halo 3 at 60fps.
At any rate, overall the XB1 probably has the resources to do better, and obviously some things were just plain done incorrectly.
I suppose the answers probably aren't actually much more interesting than "we ran out of time."
So what's the likely outcome here? The botched audio on H3 is a HUGE issue that just cannot be left unattended. The way people are talking about the MCC of late, it sounds like many expect it to be patched to its most minimally functional state then be left by 343, a terrible nightmare to be put to the back of their mind while they stride to a new day with Halo 5. I know 343 are working 'round the clock' on the bugs but someone high up needs to come out real soon with a comprehensive statement assuaging the above fears because MCC looks so deep in the hole right now with the amount of bugs, it's looking pretty bleak. I'll say now, if MCC isn't properly cared for then I'll be cutting my losses on the Xbox One. I only bought the damn thing for the MCC on dedicated servers. I don't like the pad, the One UI is a laggy, sluggish labyrinth, twitch app is notoriously unreliable, party chat is buggy. Sprint and ADS Halo 5 sure aint gonna be enough to keep me around.