will resolve the weirdness that occurs when trying to access localhost vs 127.0.0.1 (as there is an OS-native *:5000 listener that the fava :5000 binding overlaps) and fix the bison build errors (once you've brew install'd bison).
Huh. Get out your red string and pushpins because this inspired a theory.
So if the correct pair of values there ends up being 445 / 216.27000197, then it'll be:
60 * 445 / 216.27000197 = 123.456789
Or, since one of those programs had four decimals:
60 * 445 / 216.27015788 = 123.4567
Or, if it's 444/446 rather than 445:
60 * 444 / 215.78415752 = 123.4567
60 * 446 / 216.75615823 = 123.4567
But I see that they cut the "whooshing intro" at the front, which I imagine is part of the beat — they're in the hands of the machine now, after all! — so if we retroactively construct 123.4567 bpm into the silence (which, they estimate, is 5.58s):
5.58s * (123.4567bpm / 60s) = 11.4814731 beats
Assuming that the half a beat of slop silence there has to do with format / process limitations with CD track-seeking rather than specific artistic intent, we get:
+11 intervals @ 123.4567 bpm = 5.346s
Which, when added to the original calculation, shows:
And so we end up with a duration of 221.616 seconds between the calculated 'first' beat, a third of a second into the song, and the measured 'last' beat from the post:
60 * 456 / 221.616 = 123.4567 bpm
Or if we use the rounded 123.45 form:
60 * 456 / 221.628 = 123.45 bpm
And while that 22+1.628 is-that-a-golden-ratio duration is interesting and all, the most important part here is that, with 123.4567bpm, I think it's got precisely 0.2345 seconds of silence before the first 'beat' of the song (the math checks out^^ to three digits compared against the first 'musical beat' at 5.58s!), and so I think there's actually 456 beats in the robotic 123.45 song!
:D
^^ the math, because who doesn't love a parenthetical with a footnote in a red-string diagram (cackles maniacally)
Not sure if it adds anything, but a factoid I know is that CD timing is expressed in minutes, seconds, and frames, where each frame is 1/75th of a second.
I'm not sure but I think this is also the smallest time resolution.
Then each frame is composed of samples, but they seem to be counted in groups of 1/75th os a second anyway.
In this song, which is also chapter four of the movie Interstella 5000 movie (spoilers from here!), the knocked-out singers are scanned, parameterized, brainwashed, uploaded into The Matrix, and then used in the following songs of the movie-album to robotically mass produce music.
It makes perfect sense that the BPM is 123.45 because that’s exactly the sort of thing you get when a manager (who’s shown at the end!) just enters some numbers on the keyboard into the bpm field. They don’t keysmash the numpad; they just hit 123456789 until the field is full!
So not only does the song itself convey what some boss thinks is music, robotically beating at 123.45 bpm, but it is itself about being endlessly-rotating brainwashed-boring cogs in a pop music production industrial machine. I’m pretty sure the movie scene cuts and animations are timed specifically to the beats of the song, but knowing that they’re timed to a machine-specific bpm that a human would never select at random with a metronome?
Absolute genius.
I had no idea. Thanks for posting this.
EDIT: At 123.4567bpm, I think the track has precisely 0.2345 seconds of silence before the first 'beat' of the song and actually has 456 beats total, which is either numerological nonsense or pure genius by Daft Punk. Math elsethread :)
> It makes perfect sense that the BPM is 123.45 because that’s exactly the sort of thing you get when a manager (who’s shown at the end!) just enters some numbers on the keyboard into the bpm field. They don’t keysmash the numpad; they just hit 123456789 until the field is full!
This seems like quite an assumption. Why wouldn't they keysmash? Or make up a fake number? And why bother to add a decimal point? What is meant by "robotically beating at 123.45 bpm"? Any fixed tempo beats robotically.
Your theory could be correct but it feels like connecting too many dots to me. 123.45 is a bizarre (and kind of human in that way) tempo that strikes me as more of a cheeky easter egg than a deeper connection to themes of corporate mass-produced roboticism (if they even did intend that as the exact tempo).
I have no counter argument prepared, but I thoroughly enjoyed exploring this all and making plausibly charming numbers. Most likely I’m wrong, of course; that’s an automatic likelihood for any numerology.
It surely adds a nice flavor to one of their best songs. There wont be one time when the song is played from now on where I wont proclaim the this specific trivia.
Urm, the release date of the movie is not actually an indicator wherever what he said was true or not.
It's more then likely the backstory he outlined, which is I believe a minor subplot non-essential to the main story of the movie - has been added like this precisely because that was the theme of the song.
Because this was actually made by humans, they frequently talk with each other when making art in collaboration
This particular sequence in the movie (which is actually named Interstella 5555) is one of the most important ones in the plot.
Discovery has been explained many times by DP to be about childhood, not having any specific "theme" besides mixing disco and rock. Hence the name "disco very" and the "pun" in Veridis Quo. (which also happens to be a major sequence in the movie. Although DP never cared to enter the details of that particular composition, most likely memory hole'd by the protagonists.)
So no, this is definitely not the theme of the song. There are several years between the actual songwriting and the release of the movie.
Heck, if you actually see the movie, the ending sequence kinda explains that this is "one" of many interpretations of the record...
Taking a look at past interviews, it is more likely that 5555 is about what surrounded the actual release of Discovery (hugely anticipated sequel to a magnum opus that was wildly different from expectations) rather than an idea that was here from the start; see also Human After All for a continuation on this theme.
And they accidentally made it 1.003713731707 times faster? They chose a number that contains only the digits 0, 1, 3, and 7? C'mon, this cannot be a coincidence!!!
Same reason Acura stopped making small cars like the Integra/RSX: costs scale more slowly than revenue as car size increases, so selling to the small car market segment results in unearned potential profits — even if the small car segment is a majority, it’s better to make a higher profit per unit on fewer unit sales if your most primary goal is to min/max labor/profit.
(Small phones, unlike small cars, also have costs in UI development to maintain their form factor’s OS support, which can create an additional pressure to withhold devices for a viable and profitable market.)
If you had read the link you posted you would know those are various historic proposals for language reforms not something that's widely used. Same way there have been various proposals for English spelling reforms. That's not the normal way for writing or reading Russian. Russian uses Cyrilic alphabet which if anything is closer to Greek alphabet than Latin. There are other slavic langauges which actually use Latin based scripts. If you don't read Russian it might look like some of the letters look similar but that's only less than half of alphabet and from those half have completely different meaning than Latin lookalikes.
Yes there are various schemes for transliterating Russian into latin script, which people occasionally use for various reasons like typing on a computer or phone which hasn't been fully configured for use with Russian language, in contexts where unicode isn't supported or to make street signs legible for tourists. That's different from the "Russian Latin alphabet". In most cases where proper Cyrillic is problematic dedicated "Russian Latin alphabet" that's based on Latin with extra diacritic marks would also be problematic.
Similar thing could be said about other languages like Japanese or Chinese, but I don't think anyone would describe them as "languages that use the Latin alphabet".
As for typing on keyboard the main Russian layout is nothing like qwerty. Computer keyboards sold in relevant regions often have dual labels. I personally never learned touch typing in Cyrillic and use the phonetic layout in the rare cases I need to do so since for me it was a second foreign language.
Which exact approach Click chose - who knows. Will it be possible to choose your preferred Russian layout like on a desktop computer? Likely not. If they supported that I would have expect them to also add layouts for more languages. Although maybe they didn't want to promise anything for languages for which they don't have OS UI translations.
Fortunately, I then assumed that I knew nothing and asked anyways. I'm glad I did — this thread is now much more interesting than the one-word comment conveyed to me at first.
Transliteration is certainly a thing but it's only ever used as a last resort when you really have to pass Russian text through a system that only supports the Latin alphabet, or when you can't input Cyrillic for some other reason. It used to be somewhat common for SMS 20+ years ago.
Palm Treo/Pre and BlackBerry users! And probably Clicks users too. It's not a matter of "Does Russian language use the Latin script?" (it doesn't), but rather "What is the least annoying method to input Cyrillic on a BB-style keyboard, which doesn't have enough buttons for the йцукен layout?". Phonetic layouts such as яверты or яшерты were very popular for such devices back in the day.
For anyone one confused, the first part is an approximate transliteration into Cyrillic of the English sentence “Much like how you can/could spell English in Cyrillic.”
As a point of validation, I would use this even though I have know about AHK for years. I don’t have any interest in developing an AHK hobby and I value the specific single feature “strip non-bold/italic/underline/hyperlink formatting”. Thanks for making it :)
That exact feature, keeping the structure (bold/italic...) but stripping the junk was actually the hardest part to build. It requires parsing the full object tree recursively to make it compatible with any app, instead of just doing simple text replacements.
I saw so many people looking for that "middle ground" that I basically built the whole app around it. Glad it resonates!
This is what I would do if my internal moral compass was exhausted to the bone and I felt like public disclosure mattered. Fortunately, public disclosure regarding my prior employment is already regularly made and ignored, so I didn’t have any compulsion to.
Libraries are a haven of safety for leaking material once only. Burnout does not imply incompetent opsec. Neither does drunk; after all, it would horrify non-tech folks to realize how often impaired / intoxicated workers are using root privileges to fix an incident.
reply