Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate stack to nodejs #9

Closed
Kkevsterrr opened this issue Nov 13, 2016 · 2 comments
Closed

Migrate stack to nodejs #9

Kkevsterrr opened this issue Nov 13, 2016 · 2 comments

Comments

@Kkevsterrr
Copy link
Collaborator

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!

@bekher
Copy link
Owner

bekher commented Nov 13, 2016

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?

@Kkevsterrr
Copy link
Collaborator Author

No actually! The node-png gives us the exact same control over the data as does the python libraries, and the code could easily be ported!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants