How is it that loud? It's not tolerable even on minimum settings on my iMac.
Ultrafast single TCP packet audio/visual experience
41–50 of 79 posts
Re: Ultrafast single TCP packet audio/visual experience
#42How is it that loud? It's not tolerable even on minimum settings on my iMac.
They are producing a waveform that is constantly at the peak range of the digital-to-analog conversion. Most real-life audio recordings only very rarely, if ever, reach peak levels.
Some (older?) Hi-Fi equipment was in fact designed with this assumption and playing a constant sine wave at peak levels would very quickly burn something out.
Re: Ultrafast single TCP packet audio/visual experience
#43This will upset any cat in the vicinity
Cat freakout confirmed
Re: Ultrafast single TCP packet audio/visual experience
#44[deleted]
Re: Ultrafast single TCP packet audio/visual experience
#45Why is the tcp socket set to busy poll for 1 microsecond?
Re: Ultrafast single TCP packet audio/visual experience
#46How is it that loud? It's not tolerable even on minimum settings on my iMac.
Tip: Shift + Option + Volume(up/down) adjusts volume by 1/4 of a bar.
Re: Ultrafast single TCP packet audio/visual experience
#47For those you are wondering, this is a webserver that serves an HTML page in a single TCP packet. I guess ≤ 1500 bytes to avoid fragmentation - shows as 1.1KB in Chrome's network view. The HTML contains embedded JavaScript that runs a simple demo with animated ASCII and playing a LOUD changing audio tone. You can visit the demonstration website here: http://packet.city/ You can see a screenshot of the demo here: http…
The limit is 1460 - the IP and TCP headers occupy 40 bytes. Out of those another 63 are consumed by the HTTP headers. The full TCP payload is only 1226 bytes though, and the full HTTP payload 1163 bytes. The decoded HTML document is 1546 bytes.
>"Out of those another 63 are consumed by the HTTP headers"
I am curious how you ended up at 63 for that, can you elaborate?
Re: Ultrafast single TCP packet audio/visual experience
#48For those you are wondering, this is a webserver that serves an HTML page in a single TCP packet. I guess ≤ 1500 bytes to avoid fragmentation - shows as 1.1KB in Chrome's network view. The HTML contains embedded JavaScript that runs a simple demo with animated ASCII and playing a LOUD changing audio tone. You can visit the demonstration website here: http://packet.city/ You can see a screenshot of the demo here: http…
Wow how'd it autoplay audio on my mobile chrome
Re: Ultrafast single TCP packet audio/visual experience
#49Earlier quoted context omitted.
The limit is 1460 - the IP and TCP headers occupy 40 bytes. Out of those another 63 are consumed by the HTTP headers. The full TCP payload is only 1226 bytes though, and the full HTTP payload 1163 bytes. The decoded HTML document is 1546 bytes.
>"Out of those another 63 are consumed by the HTTP headers" I am curious how you ended up at 63 for that, can you elaborate?
Viewed the http headers and counted?
Which you can do with curl, Chrome/Safari/FF dev tools, and lots of other tools besides.