Yes, RAM is like that because DSound has to be decentralised... So all the processing has to be done in the browser, meaning the decoding of the entire file and processing to extract the audio peaks required to generate the waveform... The longer the sound, the higher the RAM needed. :)
You are viewing a single comment's thread from:
That makes perfect sense. I forgot about waveform generation when wondering what was so inefficient when it comes to RAM usage. Could this possibly be remedied with a browser extension (or CLI uploader or something)? With a user defined IPFS node, I could just use a VM with enough RAM defined for the upload to an IPFS node on my local network without having to jump through extra hoops to keep the data online after uploading.
Thanks for the ideas, noted down! :) This will have to be improved, so will put some thoughts on that soon...