3 ms·
I agree this could be very cool for low frequency events like @mik3y suggested. I know it's just a demo, but it would be nice to have a visual indication of wh
by BinaryBullet 13y ago
I agree this could be very cool for low frequency events like @mik3y suggested.
I know it's just a demo, but it would be nice to have a visual indication of which events made which sound.
Maybe at some point down the line, your api could expose an image as well (like maybe image/g/3 is the "g/3" waveform in green, while image/b/5 is the "b/5" waveform in red).
Anyways, good work!
- cortesi 13y agoYes, making that link clearer is one of the things we're thinking hardest about right now. The (inadequate) measure at the moment is the replay-on-hover when you scrub over the feed messages. I'm not sure how instantly recognizable a waveform might be, but something that indicates pitch and duration could work. Basically, this is the kind of thing we're playing with right now, and why we want a few brave users to join us very, very early on. If you've submitted an invite request, let me know which address you used, and I'll make sure you're in the first cohort of users.
- BinaryBullet 13y agoHere's some css that helps a little bit IMO (for newer browsers). It might be even better to scale the green/yellow/red values based on their 0-3 values. Anyways: tr[data-sound] { border-right: 5px solid; } tr[data-sound^="g"] { border-right-color: green; } tr[data-sound^="n"] { border-right-color: yellow; } tr[data-sound^="b"] { border-right-color: red; } I just signed up. Sent you my info via a different channel.