Can WavPack handle memory stream data?, or does it have to be file stream? |
Can WavPack handle memory stream data?, or does it have to be file stream? |
Aug 12 2008, 04:15
Post
#1
|
|
|
Group: Members Posts: 3 Joined: 12-August 08 Member No.: 56982 |
I couldn't find any specific instruction in the lib_use.txt about how to handle memory stream data. I would like to know if the library supports memory streams. Thanks.
|
|
|
|
![]() |
Aug 12 2008, 05:27
Post
#2
|
|
![]() WavPack Developer Group: Developer (Donating) Posts: 1219 Joined: 3-January 02 From: San Francisco CA Member No.: 900 |
Yes, memory streams are supported.
For decoding WavPack files, use the WavpackOpenFileInputEx() function. The callback functions provided by the WavpackStreamReader can get the WavPack data from anywhere (and they don't have to implement "seek" unless you want to be able to seek in the audio playback). For encoding WavPack files, you again provide a callback function that will accept the completed WavPack blocks and can do with the data whatever it wants. Hope this is what you were after... |
|
|
|
Aug 12 2008, 08:30
Post
#3
|
|
|
Group: Members Posts: 3 Joined: 12-August 08 Member No.: 56982 |
Yes, memory streams are supported. For decoding WavPack files, use the WavpackOpenFileInputEx() function. The callback functions provided by the WavpackStreamReader can get the WavPack data from anywhere (and they don't have to implement "seek" unless you want to be able to seek in the audio playback). For encoding WavPack files, you again provide a callback function that will accept the completed WavPack blocks and can do with the data whatever it wants. Hope this is what you were after... Thanks you for the swift reply. I'll experimenting around and come back if I got more questions. |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 25th May 2013 - 07:41 |