You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think actually our entire stack can be migrated to nodejs...
It's basically:
.MP3 -> .wav (can be done w/ https://www.npmjs.com/package/sox)
.wav -> .raw (can also likely be done w/ sox)
.raw -> .png (can hopefully be done with jimp - https://www.npmjs.com/package/jimp)
transformations (node-png - https://www.npmjs.com/package/node-png)
and then back up... what are your thoughts? Would definitely make it faster, a lot quicker to stand up, and better integrated!
The text was updated successfully, but these errors were encountered:
That's a great idea for the transformations, since it will greatly increase portability. However, wouldn't we want to keep the transformation logic in Python?
I think actually our entire stack can be migrated to nodejs...
It's basically:
.MP3 -> .wav (can be done w/ https://www.npmjs.com/package/sox)
.wav -> .raw (can also likely be done w/ sox)
.raw -> .png (can hopefully be done with jimp - https://www.npmjs.com/package/jimp)
transformations (node-png - https://www.npmjs.com/package/node-png)
and then back up... what are your thoughts? Would definitely make it faster, a lot quicker to stand up, and better integrated!
The text was updated successfully, but these errors were encountered: