Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
But you're not using the same hardware as I am so not really relevant to my issue. As I said I have sorted the issue by disabling steams streaming drivers in device manager but that isn't a long term fix. Just a workaround. I have been using this same audio interface for 4 years alongside steam with no issue.
So first off... ASIO is a wide standard used throughout all professional audio interfaces and supported by nearly all DAW's, for well known reasons. The fact that you're not even addressing this.... tells me quite a lot.
Second... we're talking about external (dedicated) audio interfaces; if Steam would somehow interfere here it should be noticeable in related setups as well.
See, the #1 issue with bugs is that they need to be reproducible before you can conclude that you're dealing with a bug. And it's you who put the blame on Steam, therefor.. it should be reproducible with similar setups.
If this is something only happening with Focusrite setups then the previous issue immediate becomes a problem: you won't be able to determine if the issue lies with Steam or Focusrite, hence me also mentioning ASIO.
All in all, it's way too early to conclude that there's a bug somewhere, and judging from your response.... I'm still quite convinced that this was the result of a mis-configuration.
Enough to figure out what was causing it...
Again, that is a totally different hardware and drivers.
Why does everyone on here try to make everything a pissing contest? lol
I have been building PCs and making music a long time and have had this same setup for years with no issues or conflicts with Steam until this feature was added.
Why I think this is all about misconfiguration?
If this is meant to be a legit bug report then this is not the right place, this is a forum to discuss the Steam platform, it's even in the name. Ergo it has been discussed as much, what you perceived as a pissing contest is actually a healthy discussion, plenty of us could back up our arguments with attached facts.
For a true bug report you should contact Steam support directly.
Alas... I'll share a more detailed (less peeing contest) kind of reply.
So from the bat this makes no sense at all.
We're talking about a dedicated audio interface which is set up apart from your main interface. At this point in time I hope you do know about ASIO and such because it can improve your performance by... dozens, but alas.
Point of argument: why would Steam try to access a second audio interface? This is assuming that your Focusrite is set up next to a default interface within your computer. I assume as much because if it isn't... why assume you can get any proper results with a shared setup anyway? But granted: that's an unfair comment on my end... let's stick to facts.
Fact is that if your setup has 2 interfaces and you plugged in your Focusrite then it wouldn't automagically become the default interface for the OS to use, that would still be your embedded audio interface. Meaning that if Steam would access it it's because it was configured as much, by default Steam follows the default as set by the OS.
An danother issue: the sampling rate isn't a static setting; it gets set by software which - at that time - uses your audio interface. And claiming that Steam would use a sampling rate of 96kHz is ridiculous. Steam does a lot of weird stuff but 96kHz sampling rate for microphone input?
Niquist learns us that 96kHz would account for a frequency range up to 48kHz. Generally speaking the frequency range of the human voice sits between 300 - 3.4kHz. Applying Niquist again (and a safety measure) tells us that for the most optimal result you wouldn't need to set your sampling rate any higher than 8kHz. Make it 10kHz if you will...
Valve does a lot of weird stuff, but they do know their basics. Claiming that their software would try to sample stuff for voice input at a sampling frequency 9 times beyond is simply not realistic. That's way beyond HD quality.
And then there's this issue that you can't really configure stuff within the Steam client; it relies on your own drivers when it comes to configuring stuff such as the microphone input.
Then back to ASIO again... what sets ASIO drivers apart from consumer stuff is that they can access the hardware directly, thus circumvent any restrictions the OS may have applied. This is also one of the reasons why - by definition - supporting software shipped with an audio interface most commonly does not try to directly access it. The software monitors, it does not access with the risk of changing stuff.
Seeing your sampling frequency shift means software was trying to access it. First (a repeat) is the issue of software not "just" accessing secondary interfaces without being configured as such but the second, more compelling, argument: why do you assume any of this even matters?
See, you only talk about the change of sampling rate, you never bother to tell us why this caused you problems.
Thing is: if you know what you're doing this wouldn't cause you problems anyway.... There's a good reason why most DAW's try to lock your audio interface and deny any further access to "other software". Keyword being ASIO but in this day and age a lot of operating systems caught on and also provide exclusive access to audio interfaces as well.
A long read, so let me summarize:
Add all of that up and then I can only conclude what I already shared above, I sincerely doubt that this is a bug within Steam.
"BAH! WHY I NEVER! STEAM NEVER HAS ANY PROBLEMS! HURP DERP!" Seemingly just flat out ignoring that steam can't even make a steam sale game without it exploding.
It's funny when that legitimate issue is on the user's side and in no way part of Steam's problems.
You'd prefer we believe every chicken little who claims the sky is falling? Or just the ones you vet as legitimate?
If someone has strong enough evidence they can prevail. If they just have wild claims and disbelief that people don't accept their claims automatically, they can grow up.
These guys get it. I have been making music alongside gaming with steam for a very long time and this is the first conflict I have found..
I also got the impression that the guys above either didn't completely read or didn't understand what I wrote in the original post.
All most people want to do around here is show how superior they are to you by telling you that you're wrong.
Funny thing is since disabling the steam streaming mic/speakers in device manager my Pro24 hasn't dropped connection once...
Yo Bro... I was just trying to be nice and let you know I ran similar hardware with no issues. I didn't say anything about the validity of your gripe. Because that's what it is... A gripe.
I believe you are having the issue, but it's not Steams fault. It's an issue with your individual setup. It's not a steam bug and it's definitely not "a pretty big bug" as you have stated in the title of your thread. It's either your rig or the operator. Judging by your sensitivity, I'll take the latter.
*Tips Hat*