Can you revert back to the version that worked before and see if it does the same thing?
ProScan: Official Software Thread
Regarding the audio issue in the last few post:
The audio model hasn't changed in years. Something could have broken but I doubt it at this point. I would try to determine where the audio is getting lost. If using the sound card (not the Ethernet) method then start with the Win Mixer and see if audio appears there. If not then trace the audio back towards the scanner. If using the BCD536HP or SDS200 Ethernet audio then click the URL Setup button to see if data is being received from the scanner. I would revert back to the version that worked before to verify a later version caused the problem. If you're confident that it is a ProScan problem then submit a bug report so I can spend time on it.
Bug Reporting
If you discover a bug, send an email to support@proscan.org. The advantage of email is so I can ask questions and send you production quality files with additional testing to help fix the bug. The person reporting the bug will get the fix sooner than waiting for the next release. Put "bug" in the Subject line.
Bug Reports - Advise on the following:
The audio model hasn't changed in years. Something could have broken but I doubt it at this point. I would try to determine where the audio is getting lost. If using the sound card (not the Ethernet) method then start with the Win Mixer and see if audio appears there. If not then trace the audio back towards the scanner. If using the BCD536HP or SDS200 Ethernet audio then click the URL Setup button to see if data is being received from the scanner. I would revert back to the version that worked before to verify a later version caused the problem. If you're confident that it is a ProScan problem then submit a bug report so I can spend time on it.
Bug Reporting
If you discover a bug, send an email to support@proscan.org. The advantage of email is so I can ask questions and send you production quality files with additional testing to help fix the bug. The person reporting the bug will get the fix sooner than waiting for the next release. Put "bug" in the Subject line.
Bug Reports - Advise on the following:
- Product (ProScan, Free Client, or RadioFeed):
- Version:
- Scanner type:
- Scanner firmware version (if applicable):
- OS type:
- Options pertaining to the bug:
- Describe in detail what the bug is doing or not doing:
Decided to check my audio files. Nothing. I have a small HP computer like a nuk. Had no issues before so someth happened in recent updates.
audio playback device not found. Just checked. Cannot listen to any of my recordings.
audio playback device not found. Just checked. Cannot listen to any of my recordings.
Last edited:
I don't think you saw my post 8,882. Can you do some more troubleshhoting and provide better info. At least:, advise on the scanner type, if using ethernet audio, recorder turned on, audio control recorder tab shows audio present, audio files shows zero bytes or no audio files at all, etc.
Will do. Can tell you it is recording because it’s showing how many seconds the recording is. My guess, an update changed the audio settings. Will have to wait until I get back Saturday afternoon to reset proscan up according to your directions.
Will do. I've recently set ProScan to restart every few hours but I'll remove that and do some tracing the next time it occurs.
Same issues here using WIndows 11, SDS200, ethernet. Audio plays through computer speakers fine. Recorded audio does not. After work I'll check the mixer. As of now it shows activity on the scope and bar during non recorded transmissions. LAST day recorded audio will play was 3/20/24. Hope this helps a little.
Did the recorder work before using the SDS200 ethernet audio? If so, what version worked and can you revert back to the version that worked?
The Win mixer has nothing to do with the SDS200 ethernet audio.
Regarding the audio issue in the last several post:
I don't believe there's a problem with the last few updates causing the recorder not to record audio. I could be wrong. That's why it's best to send a Bug Report so I can send tests to see exactly what is going on.I have thousands of users and the Recorder is a popular feature so I would have heard about it from many many users. I compared version 21.0 with the latest and I see no changes in the audio nor the recorder code files.
Many things can cause the recorder not to record such as:
Audio
Control (No recording file)
I think it's best to send me an email so I can ask questions to get a better idea of what's going on. I'm not getting feedback here so It's difficult to diagnose the problem. I see in at least 2 posts where the end result is the same "not recording" but actually then are not the same. One is a file is created but 0 bytes and the other no file created.
@justlen, @03msc, @bearcatrp, @mr10pt
I don't believe there's a problem with the last few updates causing the recorder not to record audio. I could be wrong. That's why it's best to send a Bug Report so I can send tests to see exactly what is going on.I have thousands of users and the Recorder is a popular feature so I would have heard about it from many many users. I compared version 21.0 with the latest and I see no changes in the audio nor the recorder code files.
Many things can cause the recorder not to record such as:
Audio
Level control turned down in ProScan or the Win Mixer
Microphone Privacy Settings. I believe this affects the Line In input too
Win Mixer input disabled or wrong input set to default
Channels not marked for recording, If using the Rec. jack
Intermittent audio cable
BCD536 WiFi signal issue
Control (No recording file)
Recording time less then the option "Delete X Seconds From Grid And File"
Recorder turned off
Recording filename more than 260 characters.
I think it's best to send me an email so I can ask questions to get a better idea of what's going on. I'm not getting feedback here so It's difficult to diagnose the problem. I see in at least 2 posts where the end result is the same "not recording" but actually then are not the same. One is a file is created but 0 bytes and the other no file created.
@justlen, @03msc, @bearcatrp, @mr10pt
Last edited:
I will leave mine running and reach out to you via email when the condition arises again.
I round think it was a settings thing except it will be recording and then just stop. When I experienced the issue, it had been running a few days and recorded some and then just went to no audio.
As stated, I did not investigate extensively but will if it happens again. For that reason I am not going to guess what was or wasn’t the issue. I’ll let you know if I have the issue again, though.
As stated, I did not investigate extensively but will if it happens again. For that reason I am not going to guess what was or wasn’t the issue. I’ll let you know if I have the issue again, though.
ProScan Version 22.10 Just Released!
ProScan is the most powerful and feature rich scanner software in the world !!!
- Changed - Web Server - Using a reverse proxy now shows the client IP address and not the proxy IP address.
- Fixed - Web Server - The playback of mp3 recordings were intermittent when serving files using Chromium based browsers e.g., Chrome, Edge, Opera, etc.
- Fixed - UBCD3600XLT, UBCD436PT, & UBCD536PT scanners weren't writing the favorites to the scanner when the option "Erase Favorites Lists In The Scanner" was unchecked.
- Fixed - SDS100E, SDS200E, & USDS100 scanners weren't showing the scanner waterfall display.
ProScan is the most powerful and feature rich scanner software in the world !!!
Downloaded new version. Still no audio. Dug into sound settings. Dam windows update shut down my audio. Couldn’t hear anything besides proscan. After adjusting my settings, audio is back. Suggest everyone with audio issues check you sound setting if you received an update in last 30 days.
as i read everyone's audio issues, I wanted to add this to the thread. I don't even use PROSCAN, but at the same time all of you were having issues, I too noticed audio not working on my windows 11 machine all of a sudden. Couldn't play audio from web browser or any source... did windows update again and rebooted a couple times and now all is working... seemed to me windows had an issue with an update and microsoft patched it. If I'm wrong, it was a heck of a coincidence. I do plan to start using proscan soon tho 
That's one of many reasons why I use Linux at home. I only have one windows machine at home, which has Proscan on it because I haven't been able to get it to work with Wine. I blocked auto updates and reboots on it and on my Win computers at work, but Microsoft still forces them sometimes and I occasionally find that my Win machines have rebooted to the login screen without my permission. 🤬
Unusual display. I have been using ProScan (currently v.22.8) 24/7 for over a year on an older Dell desktop running Windows 10.
On a few recent occasions, after running overnight with the computer monitor screen turned off, I have turned the monitor screen on and I see the attached image. ProScan is still running and logging history.
Power cycling the SDS100 restarts the logging, but without changing the red "X." Disconnecting/reconnecting the USB cable yields the same result.
After opening the Comm Port tab menu, changing the Port to none, then running Auto Detect shows
port 11 Available SDS100 115200
Highlighting and selecting available port restarts the logging with no change in display.
The only solution I have found is to exit and restart ProScan.
Yes, I'm not running the latest version of ProScan, and updating might eliminate the problem, but I'm the type that likes to know why something's gone wrong. I'm running two other instances of ProScan (v. 22.8), for a BCD396XT and a SDS200 (for less than a month), with no issues. All three are connected via an Anker 10-port powered USB hub, along with three SDR dongles running two instances of UniTrunker v2.
On a few recent occasions, after running overnight with the computer monitor screen turned off, I have turned the monitor screen on and I see the attached image. ProScan is still running and logging history.
Power cycling the SDS100 restarts the logging, but without changing the red "X." Disconnecting/reconnecting the USB cable yields the same result.
After opening the Comm Port tab menu, changing the Port to none, then running Auto Detect shows
port 11 Available SDS100 115200
Highlighting and selecting available port restarts the logging with no change in display.
The only solution I have found is to exit and restart ProScan.
Yes, I'm not running the latest version of ProScan, and updating might eliminate the problem, but I'm the type that likes to know why something's gone wrong. I'm running two other instances of ProScan (v. 22.8), for a BCD396XT and a SDS200 (for less than a month), with no issues. All three are connected via an Anker 10-port powered USB hub, along with three SDR dongles running two instances of UniTrunker v2.
After the last Windows 10 update, mine started doing the same thing over night.
I found the the Power and Sleep setting for the computer had changed after the update. And the computer was set to go into SLEEP mode after 5 hours and the screen was set to blank out after 10 minutes. Set them to 30 minutes on screen saver and NEVER sleep like I had it before and all works OK now. When Windows go in sleep mode it messes up ProScan.
Don't know if this is the problem you are having, but computer should be set to NEVER sleep.
I found the the Power and Sleep setting for the computer had changed after the update. And the computer was set to go into SLEEP mode after 5 hours and the screen was set to blank out after 10 minutes. Set them to 30 minutes on screen saver and NEVER sleep like I had it before and all works OK now. When Windows go in sleep mode it messes up ProScan.
Don't know if this is the problem you are having, but computer should be set to NEVER sleep.
You may think the problem is with ProScan because it works after restarting ProScan. I think it works after restarting ProScan is because the Windows API WaveIn closes then reopens. If it happens again, Set the Input device to none then back to the device using. That will close the WaveIn and reopens it. I think something in your OS is doing it. You may want to look into a USB audio device to solve the problem.
All good suggestions.
Under Power Options, I just checked and both "Turn off the display" and "Put the computer to sleep" are set to Never.
Also, USB settings → USB selective suspend setting is Disabled.
I do see that Hard disk → Turn off hard disk after is set to 20 minutes. However, that setting appears not to be affecting my other two instances of ProScan nor my two instances of UniTrunker.
