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.

Sign up for GitHub

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

Jump to bottom

Subsequent requests to the same node makes concurrents audio outputs #1

Closed
mudler opened this issue Mar 31, 2014 · 1 comment
Closed

Subsequent requests to the same node makes concurrents audio outputs #1

mudler opened this issue Mar 31, 2014 · 1 comment
Assignees
@mudler
Labels
bug

Comments

@mudler
Copy link
Contributor

mudler commented Mar 31, 2014

This was already know, should provide a syncronized and mutually exclusive shared LILO for the node threads that handles the voice output
@mudler mudler added the bug label Mar 31, 2014
@mudler mudler self-assigned this Mar 31, 2014
@mudler mudler changed the title Subsequent requests to the same node makes concurrents output files Subsequent requests to the same node makes concurrents audio outputs Mar 31, 2014
mudler added a commit that referenced this issue Apr 1, 2014
@mudler
[fix] Fixing #1 - Sox in quiet mode, removed useless -b 32 and using …
efc6f6f 
…standard fork
mudler added a commit that referenced this issue Apr 1, 2014
@mudler
[fix] enabling the load of the Node schema with the current backend a…
36fb1e5 
…nd making the socket blocking for #1
@mudler
Copy link
Contributor Author

mudler commented Apr 1, 2014

making the socket blocking for now, in tests, having speech recorded in queue seems not very useful

@mudler mudler closed this as completed in f69c8cd Apr 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mudler mudler

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mudler