We have a beautiful saying in my country: Dumb head is a burden for the body.
The french understand this, too, deciding to relieve poor old Marie of that burden.
We should all be more like french people. Wine, cheese and good medical care system.
Shurimal
joined 2 years ago
Set up Tailscale as exit node to your local network.
Make sure that your network is not standard 192.168.0.x or 192.168.1.x IP address range, but something like 192.168.101.x so you don't have IP conflicts when accessing from a friend's house or workplace wifi.
Set up Nginx to redirect your home server IP (eg. 192.168.101.5) to the correct port for your dashboard like Heimdall or Dashy.
That's it. Works like a charm for me if set up this way.
Addendum: if you have trouble on Android, disable MagicDNS.
It's good, but in the name of the Galaxy, those hour-long dialogues and exposition dumps!
Power over Ethernet
Perl Object Environment
PowerOpen Environment
Product of Experts
Platform for Open Exploration
Post Occupancy Evaluation
Port of entry
I'm sure there are more.
As it should be #DynamicRangeIsLife
The first HL had surprisingly good sound with great dunamic range. HL2 felt wimpy, guns never had the same oomph to them.
Do you have the Tailscale's "Magic DNS" enabled? I had problems with Tailscale on Android, too, and disabling their DNS solved it.
No, it isn't. OS and app volume controls are not implemented on driver level, but in each application individually, or you wouldn't be able to change OS volume and in-app volume independent of each other. It's simple math, multiplying audio sample values with a coefficient, best done in 32 bit floating point.
The question is not whether to do the math at driver level or in the userspace. The question is: if the user sets their volume slider to the middle, what value that coefficient should be? Most apps use simple linear correlation (middle point halves values which is 6 dB of attenuation or -6 dB(FS)) which is not how human hearing works. Log volume control would have the middle point at, eg, -40 dB(FS) and zero point at -80 dB(FS), giving psychoacoustically useful range in both halves of the bar. This is how analog volume controls on amplifiers work (not exactly so, but pretty close).
Driver level volume control can be done, but then you'd need to open your sound card control app and set it there. It would be an addition to OS and app volume controls. It would not be tied to OS or in-app volume controls or affected by standard multimedia keys on your keyboard. And if you decide to do OS volume control at driver level, in-app volume controls would still need to exist and be at the mercy of the app devs competency at implementing it.
Implementing proper logarithmic volume controls and defaulting them to -20 dB(FS) would be great. But the math involved is slightly more complicated* than the simplistic "multiply everything with a coefficient between 0 and 1" so devs won't bother (if they even know about logarithmic volume controls at all).
*I did logarithmic volume slider in Jscript for foobar2000 using a Jscript GUI plugin and it was not too difficult, but not straightforward either. Getting the button states and scaling to work correctly was more difficult and I never solved some annoying bugs. That was the first and the only "programming" I've ever done in my life.
Volume sliders never sound linear to me
Ironically that is because (with very few exceptions) every application from OS-s to streaming service webapps to games to mediaplayers uses linear volume slider. Human hearing is logarithmic.
The way typical volume slider works is multiplying the audio sample values with a coefficient that is ≤1. Ie, if you set volume to 50% the input is multiplied by 0.5 and as a result the signal voltage level on the analog output to your headphone or loudspeaker drivers is halved. The kicker—halving the voltage is just 6 dB less volume. This is why if you have sensitive headphones (or big, powerful speakers) you find that you have to keep the volume slider in your OS at 10% or even lower to not blast your ears off. And why the upper half of volume sliders is completely useless.
I have an unconventional speaker setup that makes classical analog volume control completely impractical. Since said setup has the maximum sound pressure level output of around 110 dB at full scale digital input, I have to keep the OS volume slider at 30% and in-app volume sliders at around 20%, resulting the total multiplier of 0.06 (or about -26dB full scale) to have comfortable volume levels. Only exception is Elite: Dangerous; with sound set to full dynamic range I can keep the main volume slider at maximum and enjoy glorious dynamics. Youtube is also surprisingly reasonable, probably because they normalize to -14dB LUTS or something similar.
Independence War and Independence War 2 remake by Aerovery Labs, or maybe Eagle Dynamics would be dapper.
The Mist.
Not movies, but Rifters series, Blindsight and Echopraxia by Peter Watts; and Killing Star by Zebrowski and Pellegrino. These will never become movies or TV, they're just too nihilistic and have some extremely heavy themes. Watts especially does not shy away from describing and closely analyzing the psyche of some truly horrible characters in Rifters series.
Wouldn't any off the shelf temperature+humidity sensor work? I use Sonoff and Aqara ones with Sonoff Zigbee coordinator and Zigbee2MQTT, both are somewhere around 15€ a pop, integrate painlessly and do the job. Aqara is a bit smaller and has air pressure sensor, too.