Quentin Fuxa

Results 53 comments of Quentin Fuxa

Thank you for the issue. Do you get the error for the 2 streams or just for one ? A ffmpeg pipeline (`AudioProcessor()`) is created for each client, so I...

Hi, I am well aware of the problem, I am working on it. btw thank you for the screenshot @needabetterusername

You can try with the latest commit. Except if you have a different problem than mine, the issue is solved

Hi, last commit solves that. You can pull directly from github, or wait for the next 0.2.5 release

Hi @Aurora-6 According to the logs, your server is running on port 8080. However, the WebSocket URL on the front page is still set to its default value, which uses...

![image](https://github.com/user-attachments/assets/0eba644e-d38d-4067-adf3-403b2d9ff08d) When you click the button, you should see a pop-up asking for microphone permissions. The button will turn red when permissions are granted. ![image](https://github.com/user-attachments/assets/a9b6348b-26c4-4ce0-9bb3-86c392049021)

This is not a [whisper_streaming_web](https://github.com/QuentinFuxa/whisper_streaming_web) issue. You likely have restrictions on your machine or browser regarding the permissions that can be granted to webpages. Let me know if you’re able...

URL should be `wss://localhost:8000/ws` . `wss://` is the protocol. `/ws` is the endpoint, it does not change

Can you check in Chrome, in dev tools and network tabs, if the browser sends data to /ws endpoint, and if the server sends results back to the browser? ![image](https://github.com/user-attachments/assets/8164da77-297a-4f05-9763-82155988cb22)

Yes, I’ll take a look at it. I ran some tests, and it seems the VAC is indeed not stable. (The binary messages correspond to the mic audio. It’s normal...