4 ms·
I think you have failed to comprehend what a DAW actually needs to do/render, quickly.
by trollied 3y ago
I think you have failed to comprehend what a DAW actually needs to do/render, quickly.
- wg0 3y agoYou're not wrong to assume so. I think I should have said that minus the DAW and otherwise generally speaking for let's say 95% of the use cases, the web is pretty OK. So instead of editing the comment above, I'd agree with your underlying point about DAW and complexity of the UI. It is no trivial. As a backend engineer, the progress on web platform certainly is dazzling from Web Assembly to Web GPU, Flex, Grid, Container queries and lately view transitions.
- yurishimo 3y agoCan you share some examples where a DAW/plugin would need to update that much visual data onscreen with almost zero latency? I'm genuinely asking someone who used to make music with orchestral/Pianos/Drum VSTs a ton a few years ago. I agree that the underlying audio should be as fast as possible, but I don't see why the UI couldn't "lag" behind by a few extra milliseconds for on screen rendering. Especially as a plugin. Again, not trolling; genuinely curious!
- bandrami 3y agoLive manipulatable waveforms. Think DJ decks, etc. It tends to be one of those "tearing is better than stuttering" situations so it goes against a lot of compositing assumptions.
- zorr 3y agoImagine your keyboard lagging a few extra ms before the character you typed is visible on the screen.
- thomashop 3y agoAverage keyboard latency is between 3-15ms depending upon the type of keyboard switches used and the connection type.