I never got around to really dialing this in - currently note and velocity are both mapped to intensity and notes are mapped through to a sampler. I taught myself Ableton for this as well as Blender so didn't get around to playing much with this.
I wonder if instead of black+repeating images (assumption here is that's the display and not an artifact of the firehose, the same unique image often repeats a lot in the same short instance) it'd be cleaner to have some sort of exponential backoff queue (the closer it is to empty the slower it empties like 0.5s/numInQueue, last element in queue will wait no less than 0.5s but also wait for the next element to queue). This would make the flow a bit more consistent, never blank, and never repeating.
Is there any way to make it flash less? I'm not epileptic, and I appreciate that you put a warning first, but it's still highly unpleasant after around 2 seconds. If I could look at it for a bit long it would be a cool experiment.
well, they knew most user would addicted to it (and would likely smoke while using them), so they chose to protect their hardware by providing a safe place to dump the ashes
The default "happy path" for new Samsung televisions is to be set up through an app. A mandatory step is to allow background location tracking permissions.
Sanity.io designer / co-founder here. We've been discussing how to explain what Sanity is and stuck with “CMS” to give people an everyday use case, casting a new product category in something old. There's the term «Headless CMS», but that doesn't capture the data modelling and query capability well either.
And for sure, this way of thinking about content isn't new. People have been building bespoke relational databases with custom forms on top since forever. But it has been time consuming and also pretty hard to get totally right. It's free form in data structure, but expensive to change.
Many who haven't needed to structure content in the past need to do so now. Both given content reuse across touchpoints, but also to be able to easily shift your content over to other services as structured data.
So we built Sanity to make this fast and easy while not compromising on the experience for the editor: real-time collaborative work on structured, interlinked data.
BTW – In order to make extending the editing UI clean we've built a system for build-time dependency injection. This gives a non-crufty way to override and compose components: https://www.sanity.io/docs/extending/parts
Looking over your landing page and docs it seems like really thought out product and a lot of effort being put in it. With that being said, I still can't understand the use cases for this. Who are your typical users? What do they use this for?
I agree. Strange phenomena at very small and very large scales seem like perfectly sensible optimization choices. Like the copenhagen interpretation of wave-particle duality (no need to simulate the particles until they are actually observed by an actant, just represent them as waves) or dark matter (no need to accurately simulate gravitational force at vast distances).
I'm glad you bring up the Copenhagen interpretation because the first time I watched a video of Richard Feynman explaining the duality of quantum particles [1] all I could think was "hey, that looks like an optimization you could put in a game engine or something".
