Uploaded/scanned the voxcall.exe at VirusTotal and it showed 9 different AV programs will call the file out as malicious. Not sure if there's some way to adjust the coding so it doesn't catch it.
voxcall beta - VOX recorder and uploader for Broadcastify Calls
- Thread starter aaknitt
- Start date
- Status
Unfortunately, I'm not able to get VoxCall to work on my Windows machine. The same selected audio device, if that is the one that is being reported as unavailable, worked fine with ProScan and ScannerCast.
I'm getting the following error logged.
Traceback (most recent call last):
File "voxcall.py", line 183, in start_audio_stream
File "site-packages\pyaudio.py", line 750, in open
OSError: [Errno -9985] Device unavailable
heartbeat OK at 1590964596.1749234
Any ideas?
I'm getting the following error logged.
Traceback (most recent call last):
File "voxcall.py", line 183, in start_audio_stream
File "site-packages\pyaudio.py", line 750, in open
OSError: [Errno -9985] Device unavailable
heartbeat OK at 1590964596.1749234
Any ideas?
I've only tested on a Pi 3. It should be fine on a Pi 4, not sure about a 2 or Zero.
voxcall gets audio from pulseaudio so yes you can use a single audio input device to feed multiple applications as long as they're all set up to use 'pulse' as the input (rather than alsa).
Andy
Not unusual for new programs and programs that aren't widely used by the general public. If the AV programs haven't seen it before they assume it's bad. TwoToneDetect still gets hits occasionally even though it's been out for years...it's just not widely used enough compared to "consumer" programs.
Yes generally speaking should work, in my experience.
Every once in a great while I've found that pyaudio has issues with the onboard sound card on some Windows machines. I haven't been able to figure out the rhyme or reason. Do you have a USB sound card you can try?
Andy
This one is a USB device. The onboard soundcard is being used by my 436HP with ProScan. This is one of those small USB sound cards that plugs in like a USB memory stick. Both ProScan and ScannerCast didn't have an issue and both worked/are working fine with it. I tried stopping ProScan and relaunching VoxCall with nothing else using the input device, just as a test, and it returned the same error message in the log.
Any ideas to try? Any other debugging I could try?
That's strange, those usually work well. I've confirmed it works on Windows 10 with ones that look like this:
I happen to be using this one. https://www.amazon.com/gp/product/B00IRVQ0F8/ . There are many like the one I have and are likely the same one just rebranded. I don't know if the majority of folks that will use the new Calls platform and would look to VoxCalls so maybe I'm in the 10% or 90%.
Maybe irrelevant but it looks like pyaudio hasn't been touched in 3 years. I saw some StackOverflow comments about pyaudio not working past Python 3.6. Not that you are using 3.7 but maybe pyaudio isn't the most optimal approach if it's no longer being updated.
Maybe irrelevant but it looks like pyaudio hasn't been touched in 3 years. I saw some StackOverflow comments about pyaudio not working past Python 3.6. Not that you are using 3.7 but maybe pyaudio isn't the most optimal approach if it's no longer being updated.
- Joined
- Jul 19, 2016
- Messages
- 13
Is this using the latest version that I posted earlier today? Are there any errors in the log.txt file?
Andy
- Joined
- Jul 19, 2016
- Messages
- 13
I grabbed Audacity which, at least at some point, used the same cross platform portaudio library that voxcall is using. When I launch Audacity, it detects the USB device and i can see the input audio level fluctuating as expected. Is there a different app interface from pyaudio that could be considered?
Any way to throw together a quick troubleshooting program that doesn't use pyaudio on Windows and see if that is the problem area?
Any way to throw together a quick troubleshooting program that doesn't use pyaudio on Windows and see if that is the problem area?
@aaknitt - Any other options to try on my end or your end? The voxcall app doesn't seem to recognize my internal soundcard (realtek) or USB soundcard "dongle". When I launch voxcall it sees the devices but there's no movement of the on-screen Audio Level signal bar. Both audio inputs are recognized by the ProScan app on the same computer.
Voxcall issues - Running 2 instances of Voxcall in seperate folders and uploading to Broadcstify Calls. Two comments - One instance appears to work fine, the other instance seems to stop working after a certain amount of time (Time unknown). Is there any way to tell if it is frozen and or not working? Second - Sometimes the recordings get saved in the main folder and not the audiosave folder. There is no "heartbeat ok" in the log file after the last recording. failed at 8:07 this morning and no email from Broadcastify indicating voxcall was down. Attempting to add a third instance with the same issue. Windows 10 Pro/voxcall file downloaded June 5th. How do I tell what version I have. Any thoughts and suggestions?
I take it there's nothing in the log file that's offering any clues?
The file is initially created in the main program directory and then gets moved to the /audiosave folder after uploading. For some reason that move isn't happening all the time, though I'm not sure why. I've seen it happen here as well but so infrequently that I haven't been able to track it down. It can certainly happen if the program gets shut down before the move takes place, but I'm not sure that accounts for all instances.
It only does the heartbeat if there hasn't been a recent upload. An upload "counts" as a heartbeat to Broadcastify.
Is it continuing to heartbeat but not recording/uploading audio? That's the only scenario I can think of that wouldn't trigger an email from Broadcastify.
Andy
Additional info - I have 3 instances of Voxcall running, two are uploading to Broadcastify and one is just recording. One of uploading instance made it past 24 hrs and still has a heartbeat in the log. The other stopped working after an upload at 5:30am this morning, no additional heartbeats and the audio level was frozen above the squelch level. Save and Exit and restart gets it working again. No other clues to offer.
John
John
- Status
Similar threads
