Are they saying this stimulation that apparently cures tinnitus also causes depression?
166 karma · joined June 17, 2014
Are they saying this stimulation that apparently cures tinnitus also causes depression?
> we developed a guinea pig model of tinnitus induced by noise exposure ...
> choosing a stimulus interval known to induce long-term depression (LTD). Twenty minutes per day of LTD-inducing bimodal (but not unimodal) stimulation reduced physiological and behavioral evidence of tinnitus in the guinea pigs
https://stm.sciencemag.org/content/10/422/eaal3175
I'm not anti-science and I understand the need for animal testing to reduce risks to humans but this raises serious ethical concerns where no such risk to humans exists.
How on earth do they know if guinea pigs have tinnitus and if this method shut it off in them?
And thanks but I'm happily using my patch on a pure alsa system without pulse audio, and don't really have the time to spend on adding the equivalent to yours sorry. But I'd want to if only to spread awareness about clipping - it's not just music, there are also many Youtube channels that I unsubed from because of it (I did tell them but they didn't care).
Actually preventing clipping instead just detecting it (which mine does) is a lot of work - it would need to find the loudest frequency, then find the closest band and reduce that (while loudly informing the user, and oviously with an option to control it).
If the audio clips, and the meter doesn't "blow out", then in my opinion that is a defective meter.
ALSA already has an eq plugin (http://quitte.de/dsp/caps.html#Eq10) and I added this to it:
if ((s > +0.99 && x[z1] > +0.99 && x[z2] > +0.99) ||
(s < -0.99 && x[z1] < -0.99 && x[z2] < -0.99) ) {
//clipped audio isn't exactly 1.
printf ("dsp/Eq.h:process(): input clipped :(\n");
}
.... if (
(r >= 1.0 || r <= -1.0) &&
(r < 20 && r > -20)) { //uninited memory?
printf ("dsp/Eq.h:process(): output clipped :( %0.16f\n", r);
}
(one day I should try to get upstream to accept that or something like it...)No it's not, it's just widespread incompetence and has ruined lots of music I would have liked. Having better software tools that alert when clipping is happening would be a good thing (i.e. it needs to alert when crossing over from 0dB to a distorted wave form, not just hitting 0dB without distorting, which is fine).
https://www.wolframalpha.com/input/?i=black+hole+horizon+rad...
shows a black hole of mass 1×10^29 kg (which is about 1/20 of one solar mass) has a radius of 148.5 meters which is asteroid size.
https://www.wolframalpha.com/input/?i=gravity+of+1%C3%9710%5...
says at one earth's radius away that it has an escape velocity of 1447.5 km/s (kilometers per second), so yeah I think that will either destroy part of Earth or completely consume it, depending on how fast it's passing though.
For OP's question, whether it's detectable or not, it possibly is if it warps the light from background stars (same effect as https://en.wikipedia.org/wiki/Eddington_experiment).
Youtube-dl should be architected to allow many other people to own the site-specific support (i.e. via a plugin system, with the main "distro" of yt-dl including some popular plugins, which other people or themselves are responsible for), if it was like that then probably this fork wouldn't be necessary.
Certified food safe epoxies exist but are expensive, e.g. ArtResin is one.
Some of the projects on https://github.com/reHackable talk about having to be re-installed after upgrades, and other unfriendly vendor behaviour (e.g. https://github.com/reHackable/scripts/wiki/webui_invincibili...), which is slightly worrying, it'd be more assuring if they had better support for 3rd party software, or at least just a webpage saying "yes you can install 3rd party software, but note that it's not preserved over upgrades". The company I work for also sells a linux box, allows 3PS, and does have such a web page. Such a webpage might also cater to all the other people here commenting that their marketing dept is ignoring us.
This isn't good advice for trying to show someone their messages aren't being sent in clear text. It could be encrypted using a weak cipher or have other implementation bugs that make it trivial for a nation state to decrypt it. You need to be able to look at the application's source code to tell what encryption it's using and if it's secure enough.
So, no more "use the system python" for me...
I wish I could also disable those lightbox image loaders on web pages that slowly fade in images, as if the webmaster was worried that displaying it too quickly might give someone a heart attack or something.
The public has been duped into accepting slow interfaces, and it pisses me off!
I just upgraded to 2.0 and was so damn impressed with upgrade code. I run Zulip in a VM with an NFS root, and hit some random NFS bug that resulted in this error:
... Found existing installation: cryptography 2.3 Uninstalling cryptography-2.3: Successfully uninstalled cryptography-2.3 Could not install packages due to an EnvironmentError: [Errno 16] Device or resource busy: '.nfs00000000016cef5200000f9e'
... `pip install` failed; retrying... ...
Then it succeeded, all by itself.
I work in tech support myself (L3) and am constantly shocked at the brain-dead, useless and actively unhelpful things the lower level staff say to customers.
Even if the actual efficiency is no where near that, a 1080p jpg fits in that so it's not like people would want the IIIF functionality on images that small anyway.
Trying to load an image sends 50 separate requests, when the entire image is less than 400kb. This is the exact opposite of what web optimizers try to do, which is combine lots of small images into 1 large one and use clever CSS to show small parts of the image in the right places on the webpage..
The analogy applies to computing in 2 ways: they're hidden, and it's something desirable. Niether of those ways apply to what Mozilla did. Therefore it wasn't an easter egg and you trying to pretend otherwise is just confusing.