Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
cocoggu
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
by
cocoggu
11y ago
Yeah the auto scroll feature may be lagging on huge scores. My best advice would be to switch the display in horizontal mode with the button on the top right toolbar.
62.
▲
by
cocoggu
11y ago
An offline version is about to be released, and if you ask why a web-based version, it can be very useful for Chromebooks for example.
63.
▲
by
cocoggu
11y ago
Hey! I'm head of audio and MIDI at Flat. In fact, latency and audio quality (because of file sizes for sampling and because of available resources for synthesis) are two big limitations in a browser. We have big expectations about the
64.
▲
by
cocoggu
11y ago
Here are some demo GIFs about how to use the editor: https://flat.io/support/editor
65.
▲
by
cocoggu
11y ago
That's not specifically a DAW but here is a web based music sheet editor I'm making with some friends. https://flat.io
66.
▲
Secret of happiness and success from a 75 years study
(ted.com)
3 points
by
cocoggu
11y ago
|
0 comments
67.
▲
by
cocoggu
11y ago
I agree it's a lot about luck and work, but I think you are missing an essential key to success: relationships.
68.
▲
by
cocoggu
11y ago
For people concerned, I asked the Smartflix team if it will impact their service. Here is their answer: "Hello! Yes, we are aware about the recent statement that Netflix has published, and needless to say we are upset about it! However
69.
▲
by
cocoggu
11y ago
I just asked the Smartflix team about it and here are their answer: "Hello! Yes, we are aware about the recent statement that Netflix has published, and needless to say we are upset about it! However this does not mean the end of Smart
70.
▲
by
cocoggu
11y ago
A domain name is sheep anyway!
71.
▲
How Product Hunt drastically changed our day off
(blog.flat.io)
3 points
by
cocoggu
11y ago
|
0 comments
72.
▲
by
cocoggu
11y ago
I think it is more how any JS script works, Chrome and Firefox (at least) slow down the process (for CPU consumption, to save battery... etc). Since that script is working using a setInterval to look ahead, he needs to wrap the setInterval
73.
▲
by
cocoggu
11y ago
In Chrome too, it is due to the JS engine working slowly when the focus is not on the tab anymore. To get around that issue he needs to wrap the setInterval function in a Web Worker, so the thread runs independently of the tab.