Dmitry Iv.

Results 343 comments of Dmitry Iv.

Possibly color temperature also may give an insight, tbh I imagined it more in this way ![image](https://user-images.githubusercontent.com/300067/118002909-151ff380-b316-11eb-9564-2bd3ab730684.png)

It seems to be some data for the translator https://uwdata.github.io/color-naming-in-different-languages/vis/color_translator.html#term=pink&start_lang=en&dest_lang=en As you see some colors have 9 nodes others 4 ![image](https://user-images.githubusercontent.com/300067/118023078-1ad40400-b32b-11eb-96c8-0d6b9a2a4843.png) Btw, I'm not sure their work is a reliable...

@meodai that is _so nice and fun_ ![image](https://user-images.githubusercontent.com/300067/132969875-97a479bf-ad25-4784-94f9-a1808ce481b6.png) As an idea: showing neighbor colors

Yes, hue and maybe saturation. I mean names are so fun but dense, picking is not precise, same time there are many almost-symonymic colors nearby with very different names- would...

I'm thinking something simple: ![image](https://user-images.githubusercontent.com/300067/133106342-e3c7a08c-6b1d-4db0-b646-a5fdc5f3ff6a.png) Basic directions: -h, +h, -s, +s, -l, +l, -h-s, -h+s, +h-s, +h+s etc.

I'm in a bit different context now, tbh it will take some time to switch.

Unfortunately there's no easily available good implementation of decoder in JS/WASM ([here](https://github.com/orgs/audiocogs/repositories?type=all) ?), so if you find any - you're welcome to contribute. I'd recommend to use ffmpeg for now...

@LWTechGaming could you show the code you use to run player?

@LWTechGaming I added [a test](https://github.com/audiojs/audio-play/blob/master/test.js#L49), that seems to work fine in browser, run `budo test`. Is that possible that electron tries to use node version of package? Try `require('audio-play/browser')`

We're blocked by https://github.com/audiojs/node-cubeb, https://github.com/audiojs/audio-speaker/pull/44 or https://github.com/audiojs/audio-mpg123/pull/10. That needs a separate effort.