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'm sending buffers generated by speech-synthesis, using WriteableBufferingSource, then NotiticationSource and finally WaveOut.
When I get the event from the NotificationSource, the Position of the WriteableBufferingSource is always 0.
After looking in CSCore, it seems it's on purpose.
What could be a workaround to get an approximation (~100ms) of the current playback position ?
Is there an alternate to WriteableBufferingSource accepting buffers and giving the Read position ?
Any hint appreciated
The text was updated successfully, but these errors were encountered:
lzanoni-stm
changed the title
Getting playback position with WriteableBufferingSource ?
[Question] Getting playback position with WriteableBufferingSource ?
Feb 20, 2023
You could write some kind of counting source which just reads from a base source and incremenrs its position by the number of read samples or bytes.Am 20.02.2023 um 12:30 schrieb lzanoni-stm ***@***.***>:
Hello,
I'm sending buffers generated by speech-synthesis, using WriteableBufferingSource, then NotiticationSource and finally WaveOut.
When I get the event from the NotificationSource, the Position of the WriteableBufferingSource is always 0.
After looking in CSCore, it seems it's on purpose.
What could be a workaround to get an approximation (~100ms) of the current playback position ?
Is there an alternate to WriteableBufferingSource accepting buffers and giving the Read position ?
Any hint appreciated
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
Hello,
I'm sending buffers generated by speech-synthesis, using WriteableBufferingSource, then NotiticationSource and finally WaveOut.
When I get the event from the NotificationSource, the Position of the WriteableBufferingSource is always 0.
After looking in CSCore, it seems it's on purpose.
What could be a workaround to get an approximation (~100ms) of the current playback position ?
Is there an alternate to WriteableBufferingSource accepting buffers and giving the Read position ?
Any hint appreciated
The text was updated successfully, but these errors were encountered: