• 0 Posts
  • 293 Comments
Joined 2 years ago
cake
Cake day: June 30th, 2023

help-circle



  • Years ago, I played with AWS then contacted their support to make sure any AWS billing to my account was disabled.
    I thought I’d try it again recently, and couldn’t log in.
    I still don’t think I’m missing anything.

    I’d rather have VPS or server providers where I know exactly what I’m getting per month no matter what, tho I’ve ran near data transfer surcharges.


  • Oh, it’s expected costs.
    Like, figure out the compute requirements of your code, multiply by the cost per compute unit (or whatever): boom, your cost.
    Totally predictable.
    Compared to suddenly having to replace a $20k server that dies in your data center.
    So much easier.

    Except when your code (let’s be honest, the most likely thing to have an error in it… At least compared to some 4+ year old production hardware that everyone runs) has a bug in it that requires 20x compute.
    But maybe that is a popularity spike (the hug-of-death)! That’s why you migrated to the #cloud anyway, right? To handle these spikes! And you’ve always paid your bills so… Yeh, here’s a 20x bill.


  • The amount of software that is limited free self-hosted but the next tier of “self hosted” is enterprise and thousands per year is ridiculous.
    Absolutely ridiculous.

    Like, you have self hosted. I like your software, I use it personally and that’s why I’m using it for (and recommending it to) small businesses. They could afford your 10-100 per month for whatever extra features, but they don’t want to rely on 3rd party hosting. They want to host it themselves.
    But the only way to get those features is to go for some “cloud” bullshit they don’t control, or to pay “enterprise” prices.

    It’s why I make part of what I make/charge a contribution to the products and projects I use and recommend.
    I’ll set all that up and tailor it to your company, but anything and everything I recommend/implement is standing on the shoulders of giants. So pay those giants.
    Although I think I’m lucky with the people I work for, in that that are interested in the tech, but not the detail.



  • 250ohm isn’t louder.

    This is my understanding. Audiophiles love to shroud things in mystery. And it’s been decades since I did reactive/imaginary electronics at university.
    Please someone correct me:

    80 ohm is fine from a phone or a laptop headphone jack. Basically everyday consumer not-special devices.
    80ohm can covert the small power output to a higher magnetic field, so the voice coil can move more (or with more force) which moves more air, which is louder.

    But to make 80 ohm coils, it requires a thicker wire in the voice coil (thicker wire lowers resistance. I know its impedance, but I feel like wire resistance is probably higher than the imaginary component). Which makes it heavier. Which makes it slower to change direction (heavier has higher intertia, so larger momentum once it’s moving in one direction). So you get less definition (high frequency/fidelity/detail/whatever, basically).

    P = I²R : as resistance increases for a given power amp, the current has to drop. And magnetic field (which drives the voice coils) is related to the current.
    So for a given power amp, low impedance phones will generate more magnetic field.

    So a low impedance headphone can do more with less, at the expense of fidelity/high-frequency/detail.

    A higher impedance coil is made with thinner wire, so is lighter which reduces its intertia.
    But it requires more power to produce the same amount of magnetic field (which relates to the amount of air moved, which relates to loudness).


    I feel like the whole thing is a rule-of-thumb thing.

    Generally low impedance has heavier components which move slower, so can’t do the higher frequency things.
    But they can move more air for a given power, just slower.

    High impedance things are lighter and can move quickly. But they require more power to produce the same amount of magnetic field.
    So they can move air faster for a give power, just less of it.

    So a high power headphone amp will be able to “drive” 250 ohm headphones.


    I have a FiiO k7 with my DT770 250 ohms.
    It’s a dac, nice big volume knob, usb, DAC (spdif copper and glass), unbalanced inputs and unbalanced outs.
    My hatred (and I wish I knew this before buying) is that inserting headphones does not mute the analogue outputs. So plugging I. headphones doesn’t mute my speakers.
    Other than that, I have no issues with it. Sure, I’d love a Benchmark. But my budget says FiiO is good enough, and my 770s sound lovely



  • I hope the Chinese company isn’t just buying the brand name, but actually buying the company.
    IE, will continue to do excellent beyerdynamic things.
    But I doubt it. I don’t know if an audio company that got better after an acquisition. Cheaper, maybe. Better bamg-for-buck, yup. But actually better? Not that I can think of.

    As opposed to what Behringer/Music Tribe did to Midas: Midas made extremely well respected kit; Behringer buys them (except it was Music Group, now Music Tribe); midas stuff becomes shittier; behringer stuff becomes a little bit better.
    Sucks for anyone that bought a Pro series console. Pretty much a boat anchor after 5 years.







  • Trying to disable the windows key hotkey that opens the start menu, so the game The Witness can pause stuff, minimize, open the start menu and release the block on the windows key (IE do a more controlled start menu hotkey, instead of having windows rudely interrupt everything and break the game).

    Started with a 5 second hang whenever a debug breakpoint was reached. The dev started digging into the issue.

    Games use RawInput to get better mouse interactions, but that breaks the Microsoft recommended way of disabling windows key (as all input goes through RawInput instead of whatever the other windows API is).
    In the documentation for RawInput, it specifically states the flag to disable the windows key doesn’t work. So the Dev that was debugging the issue didn’t try it. Until the next day when they had the realisation that MSDN windows API docs are garbage, tried the supposedly not-working flag and it actually did work.

    The linked article is quite a good read, actually.
    I had to use one of the mirrors in the SO answer

    Edit:
    The mirror I used https://caseymuratori.com/blog_0006