Date
1 - 7 of 7
No audio from Windows DVSwitch dashboard
|
I'm a beginner with DVswitch, but I have it installed on a Raspberry Pi (on top of a working OS, I didn't use the .img), and it's working correctly both from a phone and from the Python program on a Windows PC.
However, when I press the RX Monitor button on the dashboard on this same Windows PC, the button turns green, but no audio appears. Using the same Firefox audio from the BBC Radio service is fine. I am using Firefox, but no audio with Chrome or MS Edge either. I've attached the Analog Bridge status in case that helps. I'm stuck on knowing how to chase this further. Thanks, David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@blueyonder.co.uk Twitter: @gm8arv
|
|
|
|
David,
toggle quoted messageShow quoted text
Here are a couple of things to check: In /opt/Analog_Bridge/Analog_Bridge.ini [GENERAL] pcmPort = 2222 ; UDP port to send to the WebProxy In /lib/systemd/system/webproxy.service [Service] ExecStart=/usr/bin/node /opt/Web_Proxy/proxy.js 8080 2222 Steve N4IRS
On 5/17/2021 6:33 AM, David J Taylor via groups.io wrote:
I'm a beginner with DVswitch, but I have it installed on a Raspberry Pi (on top of a working OS, I didn't use the .img), and it's working correctly both from a phone and from the Python program on a Windows PC.
|
|
|
|
On 17/05/2021 13:22, Steve N4IRS wrote:
David,Thanks, Steve. Both checked and correct. I tried using an iPad in case something in Windows was blocking the audio, but no joy there either. No restart attempted. So I thought I would confirm that the Python client still worked - and it did - and then trying the RX Monitor again it started working. Not sure I can explain that - somehow a path was opened. I then tried the iPad and it was producing audio as well, although the button was briefly red, and the received audio was several seconds behind that from a hotpot. At least I may have a work-round. 73, David GM8ARV -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@blueyonder.co.uk Twitter: @gm8arv
|
|
|
|
Check the webproxy log in /var/log/dvswitch.
toggle quoted messageShow quoted text
On 5/17/2021 9:38 AM, David J Taylor via groups.io wrote:
On 17/05/2021 13:22, Steve N4IRS wrote:David,Thanks, Steve. Both checked and correct. I tried using an iPad in case something in Windows was blocking the audio, but no joy there either. No restart attempted.
|
|
|
|
On 17/05/2021 16:05, Steve N4IRS wrote:
Check the webproxy log in /var/log/dvswitch.Steve, Thanks for that suggestion. Two extracts below - the first seems to have a backwards time step, but it's from a couple of months back. The second shows yesterday's tests (apparently using a server started an March-19) and apparently sending data (audio packets, I guess) correctly. Judging by the times in the log it seems that audio was being sent, and that my Web browser wasn't receiving or processing it until I ran the Python client once. Unfortunately I didn't keep a careful note of the times! Oh, well! 21-03-19 11:03:12 - Websocket Proxy: 21-03-19 11:03:12 - = 21-03-19 14:15:46 - Version: 1.6.0 21-03-19 14:15:46 - 21-03-19 14:15:46 - WebSocket server ready on port 8080... 21-03-19 14:15:46 - PCM client is listening at port : 2222 21-03-19 14:15:46 - Server ip :0.0.0.0 21-03-19 14:15:46 - Server is IP4/IP6 : IPv4 21-05-17 10:41:16 - Remote client 192.168.0.8 connected. sending data... 21-05-17 10:41:16 - -------- CONNECTIONS -------- 21-05-17 10:41:16 - Connected client: 192.168.0.8 21-05-17 10:41:16 - ----------------------------- 21-05-17 10:41:35 - Remote client 192.168.0.8 disconnected 21-05-17 10:41:35 - -------- CONNECTIONS -------- 21-05-17 10:41:35 - No connected clients 21-05-17 10:41:35 - ----------------------------- 21-05-17 10:41:38 - Remote client 192.168.0.8 connected. sending data... 21-05-17 10:41:38 - -------- CONNECTIONS -------- 21-05-17 10:41:38 - Connected client: 192.168.0.8 21-05-17 10:41:38 - ----------------------------- 21-05-17 10:41:38 - Remote client 192.168.0.8 disconnected 21-05-17 10:41:38 - -------- CONNECTIONS -------- 21-05-17 10:41:38 - No connected clients 73, David GM8ARV -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@blueyonder.co.uk Twitter: @gm8arv
|
|
|
|
On 18/05/2021 08:32, David J Taylor via groups.io wrote:
The second shows yesterday's tests (apparently using a server started anFirst log was missing? It /was/ in the outgoing e-mail, though. 21-03-19 11:03:12 - Websocket Proxy: 21-03-19 11:03:12 - = 21-03-19 11:03:02 - Version: 1.6.0 21-03-19 11:03:02 - 21-03-19 11:03:02 - WebSocket server ready on port 8080... 21-03-19 11:03:02 - PCM client is listening at port : 2222 21-03-19 11:03:02 - Server ip :0.0.0.0 21-03-19 11:03:02 - Server is IP4/IP6 : IPv4 David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@blueyonder.co.uk Twitter: @gm8arv
|
|
|
|
On 17/05/2021 16:05, Steve N4IRS wrote:
Check the webproxy log in /var/log/dvswitch.Something appears to be causing log lines to be lost (at least as seen in Thunderbird here), so here's the message again this time with the log extract attached. Steve, Thanks for that suggestion. Two extracts below - the first seems to have a backwards time step, but it's from a couple of months back. The second shows yesterday's tests (apparently using a server started an March-19) and apparently sending data (audio packets, I guess) correctly. Judging by the times in the log it seems that audio was being sent, and that my Web browser wasn't receiving or processing it until I ran the Python client once. Unfortunately I didn't keep a careful note of the times! Oh, well! 73, David GM8ARV -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@blueyonder.co.uk Twitter: @gm8arv
|
|
|