-
Notifications
You must be signed in to change notification settings - Fork 9
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
Streams implementation #11
Comments
Excuse my late reply, please. I don't see any use case where streams in node-lame would help me. If you want to implement streams as an alternative to promises I'm looking forward to your pull request :) |
A use case for streams: User is uploading recorded audio to send to google speech to transcribe as text.
I want to insert a step 2a, in which ctx.req is piped to a transform which converts the audio format to a format Google accepts, then the transformed output is piped to the Google speech client. The reason streams are important is that the server may not have a huge amount of memory or disk to work with. By streaming, we don't have to store the whole audio file in memory or on disk at once. This is even more important with many simultaneous requests. |
Streams would be very useful for on-the-fly transcoding to avoid user having to wait for transcoding to buffer before downloading. |
I'd second the request (the use case is conversion of a big mp3 to wav and streaming it further to a sound recongnition library that uses streams). I wasn't sure if this is possible, but it seems it is, at least frame-by-frame (but I don't know yet whether a file typically consists of just one frame or many, i.e. does this provide enough fragmentation to do any real streaming) |
A streams implementation will be great!
The text was updated successfully, but these errors were encountered: