torkell: (Default)
Here, have a random scientific paper: The Effects of Latency on Live Sound Monitoring.

I keep mentioning this paper to friends and can never find it, so to solve that I'll blog about it! It's a fairly readable paper on how much latency you can get away with for foldback speakers or in-ear monitors before the performers start to complain.

If you just want to skip to the results, have a look at the graphs on pages 13-15 - these plot the likelihood that a performer would rate the setup as good/fair against the latency. The highlights are vocalists will notice as soon as there's any delay, particularly if they're using in-ear monitors, while on the other extreme of the scale keyboardists can tolerate an awful lot, and other instruments fall somewhere in the middle. The paper theorizes that it's down to a mixture of how far the instrument is physically from the performer (each foot of distance is about 1ms of latency just from the speed of sound in air!), and how quickly the instrument produces sound (singing is effectively instant, while a keyboard could have a fairly laid-back synth patch).
torkell: (Default)
This took a little longer to write than I was hoping for. I did at least start typing before midnight...

While chatting with [livejournal.com profile] elemnar earlier we ended up discussing P versus NP (not quite sure how we ended up on that topic), and she came up with a surprisingly good analogy for it: proving P ≠ NP is like proving that there are no teapots orbiting Mars.

In a nutshell, P versus NP is about splitting problems in Computer Science into Easy and Hard problems. Problems in class P are Easy to solve, while problems in class NP are Hard to solve. Except we don't know for certain that NP problems are Hard because no-one's managed to come up with a proof for this. The best we've got is that we've only been able to find Hard algorithms for NP problems.

Note that this is very oversimplified. Some Hard problems are quite quick to solve in practice. Some Easy problems take ages to solve. Some Hard problems can be done in an Easy way to give a "good enough" answer for most purposes. But in general, Hard problems take longer than Easy problems and the difference becomes more significant as the problem becomes larger.

The general thinking in Computer Science is that P ≠ NP, i.e. there is a class of problems that will always be inherently Hard to solve. Indeed a large chunk of modern computing relies on this assumption.

Anyway, what has this got to do with teapots and Mars? Well, how do you know there isn't a teapot orbiting Mars? There aren't any giant teapots as someone would have spotted them by now, but all that gives is an upper bound on the potential size of any teapots (similar to how we've found various algorithms for NP problems and so have an upper bound on how Hard they are). No-one's come up with a formal proof for a presence or absence of a teapot, similar to how there's no formal proof either way for P versus NP. So all we know is no-one's seen a teapot, and there probably isn't one because it all makes much more sense that way... but there could be one out there somewhere that we've just not found yet. And P = NP might be true after all.

[Poll #2074983]

SCIENCE!

Dec. 31st, 2016 03:31 pm
torkell: (Default)
SCIENCE!

torkell: (Default)
Today's discovery while randomly bouncing round TVTropes and Wikipedia is two truely mind-blowing things about Young's double slit experiment.

The first is that the experiment still holds true if you use individual electrons.

The second is that the experiment still holds true if you use larger particles. Like, for example, buckyballs.
torkell: (Default)
Sharing is Caring: Day three
For one week, recommend/share:

torkell: (Default)
Raymond Chen (of The Old New Thing blog) recently linked to a post asking, "How much does a gigabyte weigh?" The original poster had gotten confused (or is an excellent troll) and thought that as he installed stuff on his laptop it actually got heavier. Obviously that's not the case.

But it got me wondering. Does reading from or writing to something actually change the mass of it? See, if you apply a charge to something you do actually change the mass of it by a really tiny amount, as you're adding or removing electrons from the object. This probably means that flash memory will actually get heavier as you write to it, since it stores binary ones by trapping a charge on the chip.

I'm not sure if the same principle applies to hard disks (since they operate by storing a magnetic field rather than a charge), but nonetheless it's an interesting thought

December 2025

S M T W T F S
  1 2 3 4 5 6
78910111213
14151617181920
21222324252627
28293031   

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Dec. 27th, 2025 05:52 am
Powered by Dreamwidth Studios