Can't you accept that someone who knows what they're taking about might have a different opinion than you? Bluetooth bitrate is once again a non issue for most situations. Unless you're listening to lossless audio (e: or the headphones are stuck in headset mode) Bluetooth has a higher bitrate than what you're listening to. And I'd argue with most headphones you hit the limits of the hardware way before you hit any bitrate limitations still. (Edit: what I meant is, if the hardware is capable of delivering better sound quality than what standard codecs can support the manufacturer will then include higher quality codecs)
I didn't know streaming services didn't have audio latency settings, that doesn't sound ideal. Latency is very situational in how much it matters to different people with different content (game streaming is a thing) so I'd still not write bluetooth off, but if it does bother you do use wired headphones
3%. Can't really find any higher. I haven't cared to investigate but there is a sweet spot in temperature and freshness that also massively changes the result
Either you never used a good wireless headphone or a bad wired one. Sure the best wired headphones might have higher quality than the best wireless ones but that's once again not something everyone will have lying around. In my personal experience every set of wired earbuds / headphones I've used (stuff my parents had lying around and ones bought for / gifted to me) sounded worse than all but one pair of wireless ones I've used.
Latency does not matter with audio and can be compensated for with video. Only place it would matter is gaming and even some of those might offer compensation options. Not to dismiss that it might be the decisive factor for some people but it hardly applies to everyone.
Why do these threads keep assuming everyone has high quality aux headphones lying around and nobody has wireless headphones, almost a decade after this trend started? Even assuming you don't have a prior investment in earphones, unless you're fine with the shitty bundled earbuds you need to buy new stuff regardless of the connection.
Is this an actual concern or a theoretical one? I think I heard that some nvidia specific features don't work out of the box in some games but never heard issues due to wine 'not implementing something'. I feel like that would just cause a crash, no?
It adds hdr support to vulkan drivers that don't have hdr support I think, it used to be a thing for all gpus but I assume nvidia's implementation is faulty somehow
I have no idea about c/c++ statics, does c even have statics? What kind of a scope could statics even have?
I'm very much novice myself and I never liked the idea of trusting the compiler with figuring out the correct overload and neither do I like not being able to tell which version of a function is being called at a glance. Named constructors ftw
Nevermind, I just tried it with proton-em and remembered what happened last time. It can be turned on but it looks like a grayscale filter on the screen so it's better left off.
Also tried control with proton-em but the hdr looks super wrong on that game now but not sure if it is because proton em or if the new built in hdr setting is not as good as the hdr mod that I used to use
Edit: just tried with witcher 3 too, never tried it before but it is also desaturated, maybe a bit less than crysis tho. Also with hdr enabled framegen started artifacting like crazy
Edit 2: Oh shame on me, should've rtfm. It requires enabling hdr wsi on nvidia drivers. Everything works now
I have and they are not addressed, that's why I commented as such. How would I know that one of the reasons you think <> are hard to read is because they are used as comparison and bitshift or that you intended () to be indexing syntactic sugar if I hadn't read them? As for the second, I didn't think how different languages managed to parse them matters as long as it doesn't impact compilation times significantly, hence my comment.
😭👋
Ayran 😋
Can't you accept that someone who knows what they're taking about might have a different opinion than you? Bluetooth bitrate is once again a non issue for most situations. Unless you're listening to lossless audio (e: or the headphones are stuck in headset mode) Bluetooth has a higher bitrate than what you're listening to. And I'd argue with most headphones you hit the limits of the hardware way before you hit
any bitrate limitationsstill. (Edit: what I meant is, if the hardware is capable of delivering better sound quality than what standard codecs can support the manufacturer will then include higher quality codecs)I didn't know streaming services didn't have audio latency settings, that doesn't sound ideal. Latency is very situational in how much it matters to different people with different content (game streaming is a thing) so I'd still not write bluetooth off, but if it does bother you do use wired headphones
Spot on
3%. Can't really find any higher. I haven't cared to investigate but there is a sweet spot in temperature and freshness that also massively changes the result
Either you never used a good wireless headphone or a bad wired one. Sure the best wired headphones might have higher quality than the best wireless ones but that's once again not something everyone will have lying around. In my personal experience every set of wired earbuds / headphones I've used (stuff my parents had lying around and ones bought for / gifted to me) sounded worse than all but one pair of wireless ones I've used.
Latency does not matter with audio and can be compensated for with video. Only place it would matter is gaming and even some of those might offer compensation options. Not to dismiss that it might be the decisive factor for some people but it hardly applies to everyone.
Na just meant that's a crazier taste than mine
You win
In my mouth
Why do these threads keep assuming everyone has high quality aux headphones lying around and nobody has wireless headphones, almost a decade after this trend started? Even assuming you don't have a prior investment in earphones, unless you're fine with the shitty bundled earbuds you need to buy new stuff regardless of the connection.
Is this an actual concern or a theoretical one? I think I heard that some nvidia specific features don't work out of the box in some games but never heard issues due to wine 'not implementing something'. I feel like that would just cause a crash, no?
How much money you have is about capabilities, no?
You too can get his by disabling history
It adds hdr support to vulkan drivers that don't have hdr support I think, it used to be a thing for all gpus but I assume nvidia's implementation is faulty somehow
Mister fantatic, iceman, spiderman, havoc, harry potter and cyclops
Apparently hdr wsi is still required on nvidia, my problems went away once I enabled that
I have no idea about c/c++ statics, does c even have statics? What kind of a scope could statics even have?
I'm very much novice myself and I never liked the idea of trusting the compiler with figuring out the correct overload and neither do I like not being able to tell which version of a function is being called at a glance. Named constructors ftw
Nevermind, I just tried it with proton-em and remembered what happened last time. It can be turned on but it looks like a grayscale filter on the screen so it's better left off.
Also tried control with proton-em but the hdr looks super wrong on that game now but not sure if it is because proton em or if the new built in hdr setting is not as good as the hdr mod that I used to use
Edit: just tried with witcher 3 too, never tried it before but it is also desaturated, maybe a bit less than crysis tho. Also with hdr enabled framegen started artifacting like crazy
Edit 2: Oh shame on me, should've rtfm. It requires enabling hdr wsi on nvidia drivers. Everything works now
I'm assuming static members are bad because globals are bad
"[] for arrays" is because they want to reserve it for generics once <> is retired
I think the oveloading thing is about the c/cpp thing where you can define the same function multiple times in the same namespace which yeah sucks imo
I have and they are not addressed, that's why I commented as such. How would I know that one of the reasons you think <> are hard to read is because they are used as comparison and bitshift or that you intended () to be indexing syntactic sugar if I hadn't read them? As for the second, I didn't think how different languages managed to parse them matters as long as it doesn't impact compilation times significantly, hence my comment.