• 0 Posts
  • 27 Comments
Joined 2 years ago
cake
Cake day: July 31st, 2023

help-circle
  • Creative labs made shit audio chips, at least post isa, they never figured out pci at all. Haven’t forgiven them for killing aureal either.

    Turtle beach was quality, but overpriced and they completely focused on the pro market after a while, ignoring gaming.

    Realtek makes garbage, I always bypass it with a good USB DAC (fiio usually) because the mobo manufacturers always route lines so it buzzed when the GPU started using power.

    You are right that they killed the market, but only for people who don’t care, and you can pick up a banging used mellanox for cheap that gives you excellent sriov.





  • I need to explain to people why this is so amazingly stupid:

    You are literally giving Europe an excuse to put tariffs on American goods and services, which they want to anyway, to encourage domestic producers.

    Also, you’re making it easier for them to buy directly from south Korea, Japan and even China, especially since those countries can’t sell as easily to the US.

    For Europe this is an absolute win/win.

    But honestly, this sounds like a way for Trump to put pressure on Europe to back off on Ukraine, as he probably thinks the EU is reliant on US LNG, which is kind of isn’t really.


  • It’s not Bluetooth - it’s WiFi, using a proprietary blob for authentication.

    You’ve literally missed my whole point.

    Playstation link is this exact same thing, and btw, both controllers are dual-mode bluetooth and “high-speed wireless interface”, which is basically wifi or wifi-direct or some proprietary variant.

    My point is, why isn’t it like Playstation link which just presents as HID devices and usb-audio devices, without a driver at all? Same low-latency, they even do LDAC.


  • if your input is barely too late for one 125Hz poll,

    So those polls are generally isochronous to the USB bus transaction state, not based on polling frequency of the CPU, what happens is:

    1. USB interrupt URB comes in to HCI controller,.URB descriptor written to descriptor chain.

    2. Controller adds to descriptor chain, once chain length > WAT (| Timeout), interrupt and start processing incoming URBs.

    3. In interrupt controller, follow chain, push URBs onto usb stack queue, trigger handler tasklet

    4. Stack processes URB, routes to proper class driver

    5. Class driver checks if URB has file handle open (or has open ref from drivers like HID/input).

    6. If so, poll or other input read() returns value.

    Now it’s possible there are multi-input poll reads in games, and I’m doing linux of course.

    For MSFT it’s URB -> IRP -> WDM filter driver stack -> kernel32/directinput or win32 input stack (WNDPROCs after routing).

    In any of these cases, I’m struggling to see how interrupts would come in faster with the same code on PC.

    See, the same code probably runs on both MSFT and normal hardware, so it’s going to have the same structure, unless you actually believe a dev team is optimizing input latency that much, that’s often the lowest priority, they’ll optimize video lag more because it’s more noticeable. The engines themselves use DirectInput, and that’s routed through to libinput in WINE, and the same for all devices.

    Btw, DirectInput has a device-based interface, so it couldn’t poll like this anyway, basically each controller has its own input queue that is round-robin and pluck stuff out of their input stream when available.

    In any case, you’re not getting the latency improvement, both because it’s so different in software and because nothing can appreciate this.

    I’m not trying to be extra autistic for no reason, I’ve just had to make these decisions before, and these are how we have to think.










  • What in the fuck are you even talking about?

    PS5 is bluetooth, standard bluetooth, and wired uses both standard HID and standard usb audio, my point is: Why isn’t MSFT?

    Also, since you clearly don’t know the first fucking thing you’re talking about:

    After 2016, when Bluetooth connectivity was introduced with the second controller revision (model 1708) alongside the Xbox One S, Microsoft rebranded its proprietary connection protocol as “Xbox Wireless”.[10] Xbox Wireless uses the same frequency range as Bluetooth (2.40-2.48 GHz), but has a higher transmit power, improving range and input latency. Starting in 2017, Microsoft began working with third-party manufacturers to produce additional accessories using Xbox Wireless, with the first class being headsets.[11]

    With a firmware update that began rolling out in September 2021, controllers with Bluetooth are able to pair with devices using both wireless protocols, allowing those controllers to switch connections by double-tapping the pairing button.[12]

    Drivers were released in June 2014 to allow Xbox One controllers to be used over a USB connection on PCs running Windows 7 or later.[69] The Xbox One Wireless Adapter for Windows is a USB dongle that allows up to eight controllers to be used at once wirelessly.[70]

    Look at how stupid broken this is! You need drivers to use it over standard USB!

    Everything about this design is broken, it should be kicked out of the kernel and MSFT should release firmware that actually implements HID like normal, non-stupid people.

    8bitdo has exactly this, same dongle system and pairing and again, it works perfectly without any drivers at all, because they’re not morons.