Sure, that's called audio super resolution, there's a few papers/projects doing that. Haven't really seen models which are robust and have good generalization though.
This is also very important in many global illumination techniques which requires sampling the hemisphere around a point.
As case in point a simple Monte Carlo path tracer uses this to sample random directions, see e.g. [0]. In addition to this there are many 'tricks' one can use to reduce the variance/noise using a differently weighted sampling (to help the converge of MC).
A nice technique to get a cosine-weighted hemisphere sampling is to generate a random point on the unit disc and then project them onto the (hemi)sphere.
Seems somewhat relevant here.
That definitely sounds like some predisposition.
The whole idea around intermittent fasting revolves around eating in a specific time window, outside of that you don't consume any calories at all.
Many people I know of do this, in order to lose some weight or gain muscles without adding too much fat, never heard of this problem.
Great question. I think it stems from the origin of robotics itself. The desire to build a machine that is "alive" and get it to obey at all our commands. Sometimes I think that robots are slaves 2.0, and as such, they will have human traits.
I'm running on Wayland at this moment (Gnome 3 on Fedora), and just tested on the terminal. It has two: I can copy something with Ctrl-Shift-C, then select something else, then paste with Ctrl-Shift-V, then paste with middle-click; the selection didn't override what I had copied, and middle-click pasted what was selected.
So you still have two, at least with Gnome 3 on Wayland.
Well, for me at least, I always recognize if a button click/UI interaction doesn't force a visible and immediate UI response. That's one of the main reasons why I switched a couple of years to Chromium and now back to Firefox. It really responds fast. I totally agree that there were _very_ few instances where I noticed a rendering time difference.
I switched to it yesterday from VimFX. Basic stuff works the same as in VimFX, but:
- Yanking does not work at all.
- "Follow in new tab" (F) does not work. (EDIT: Working now, so maybe I did something weird yesterday.)
- "Open" (o) does not respect search keywords. "wikipedia Test" gives me a search for "wikipedia test" instead of the Wikipedia page for "test".
- Most of the shortcuts don't work on a blank page, or on "about:" pages. For example, when I open a new tab with "t", then change my mind and press "[Esc]x", it doesn't work. Nor does any other letter command.
I filed a bug for the first one, and it seems to be related to shortcomings in FF's clipboard API for WebExtensions, so I suppose that at least the last issue in my list is also related to what the browser allows WebExtensions to do. But at this point, I don't really care about filing more bug reports. I'm looking for alternatives instead. (Any suggestions?)
There's a checkbox to control smooth scrolling in about:preferences#advanced , but I just tried both options and didn't notice any difference, neither when using the touchpad nor with j/k in Vimium-FF.
I just found "Use smooth scrolling" under Vimium's advanced options. Might be this page: moz-extension://78ac0671-3b7c-4a05-8771-f46ecdb2b65c/pages/options.html#advancedOptions unless that random string is unique per-user and I just broadcast my password.
I've been running Nightly and experienced the same thing with inbox. If I attempt to interact with it before fully loaded, inbox will freeze up for minutes at a time. Love everything else about nightly, this is my biggest issue.
Seriously, when we talk so much about the Web's portability, why is a major feature from a major website not even working on identically on the two biggest browsers? Since it's Facebook we can't accuse them of browser favouritism as they're browser neutral. I wonder what APIs are missing from Firefox that makes FB Live Video broken?
> Favoritism isn't the only reason for these things. What often happens is that the website devs all use one browser and nobody tests it.
That is exactly the point the GP post makes. These things are supposed to be standardized and the standards well described, so basic things should work everywhere without any testing. But somehow for web, it is acceptable and accepted as status quo, even after years and years of smashing our heads against the wall of nonstandard, browser-specific features.
Yeah. Well, it's not just "features", it's also stuff like minor differences that the spec allows for (the spec doesn't spec everything). For example, assuming the order of elements in the indexed getter of getComputedValues().
There are also cases like where Google's U2F library doesn't work with Firefox's U2F implementation because Firefox's window.u2f is immutable, as a newer (IIRC draft) spec dictates, whereas it isn't in Chrome, and the library does `var u2f=u2f||{}` which errors in Firefox.
Works in Nightly but the video quality is beyond garbage. 1080p webcam should not look like 320p. Chrome properly sees my camera resolution and uses it.
