Chris0516
Active Member
Bob, My System Tray indicates that, Proscan is using my microphone. I know muting Proscan won't stop it from using microphone. I tried to find the answer in the Proscan Manual. But I can't find the answer anywhere.
Go to the Audio Control tab then Recorder, Source Client, Web Server, & RSOIP tabs. See if the microphone is selected in the Input Sound Device box.Bob, My System Tray indicates that, Proscan is using my microphone. I know muting Proscan won't stop it from using microphone. I tried to find the answer in the Proscan Manual. But I can't find the answer anywhere.
Good morning Bob,
- Added - Favorites Editor - Circle to rectangle converter button.
Ahh the location tab. Thanks Bob!Good morning.
View attachment 120837
Did you upload to the 15X or write to the SDS200? If you did then just download to the 15X or read from the SDS200.Fav/Scan list HELP
I set up a List for my BCT15X in ProScan. Unfortunately I had my SDS200 running in ProScan at the time, so everything is for the SDS200 and not compatible with the BCT15X.
They are conventional systems (Air/MilAir) systems only.
Is there a way to export/import the list, or do I have to remake it?
Fav/Scan list HELP
I set up a List for my BCT15X in ProScan. Unfortunately I had my SDS200 running in ProScan at the time, so everything is for the SDS200 and not compatible with the BCT15X.
They are conventional systems (Air/MilAir) systems only.
Is there a way to export/import the list, or do I have to remake it?
Also change the scanner typeDid you upload to the 15X or write to the SDS200? If you did then just download to the 15X or read from the SDS200.
You can import from the SDS200 to the 15X. Ensure that the scanner type is set to 15X. Go to the menu - Database - Import Sentinel hpd (Favorites).
You also can import from the 15X to the SDS200. Ensure that the scanner type is set to SDS200. In the Favorites Editor, go to the File - Import ProScan DMA menu
Each instance of ProScan needs to be in separate folders just in case you didn't know that.
I appreciate any input on this. I don't have any ideals at the moment."Bob, how can we insure that users of this will be sending one slot per receiver, and not scanning? That's my main concern here...
Lindsay C. Blanton III"
Folks, A few request came in to add support to the Broadcastify Calls platform in ProScan & RadioFeed. I looked into this and it's easy to do. One potential show stopper.
I appreciate any input on this. I don't have any ideals at the moment.
Regards
Thanks for the info. I'm not really sure this is a good idea after all. I'm learning that a dedicated scanner is needed to provide the feed and the scanner needs to hold onto a channel. If this can be implemented, it will require the user using one scanner per feed and the scanner has to hold on the channel.No different than voxcall really. The user should only be sending a single channel but there are no checks in place to ensure they are not (that I'm aware). If they choose to use the calls platform, they should be following the rules just like a traditional feed and agreeing to the terms of their application.
If they're providing a single channel call node with ProScan/RadioFeed (whether it be analog or trunked) they're responsible to ensure they're only sending that single channel and nothing else or their node may be terminated.
Well, basically, its a recording on a per call basis. So, instead of one big recording of a single TG, its little snippets which could be uploaded through RadioFeed to Broadcastify Calls platform.Thanks for the info. I'm not really sure this is a good idea after all. I'm learning that a dedicated scanner is needed to provide the feed and the scanner needs to hold onto a channel. If this can be implemented, it will require the user using one scanner per feed and the scanner has to hold on the channel.
I know it's not one big recording but each transmission. Let me ask. If the scanner is set to ID Scan and another TGID is being received, won't the call of the intended TGID to be uploaded get missed?Well, basically, its a recording on a per call basis. So, instead of one big recording of a single TG, its little snippets which could be uploaded through RadioFeed to Broadcastify Calls platform.
True. I didn't think of that. I guess that's the advantage of software like SDRTrunk that can monitor several channels at once. A scanner has a single receiver.I know it's not one big recording but each transmission is a call. Let me ask. If the scanner is set to ID Scan and another TGID is being received, won't the call of the intended TGID to be uploaded get missed?
That answers that. ThanksTrue. I didn't think of that. I guess that's the advantage of software like SDRTrunk that can monitor several channels at once. A scanner has a single receiver.
I know it's not one big recording but each transmission. Let me ask. If the scanner is set to ID Scan and another TGID is being received, won't the call of the intended TGID to be uploaded get missed?
{edit} The Broadcastify Calls docs specifically mentions "SDR". Is that because the apps that supports SDRs, supports multiple SDRs so each SDR can receive a different TGID (VC) simultaneously?
Thanks for the info. I decided to scrap the Broadcastify Call feature. I can't see a user wanting to tie up a scanner just for one channel. If the scanner is scanning multiple channels and the scanner is stopped on another TGID then the intended TGID to upload will be a missed call.Primary target is SDR's for their functionality but using a scanner for a single frequency or talkgroup is very doable.
If the user is scanning multiple channels then any recorded audio is going to be sent to calls tagged as what they should be sending. This would obviously make the audio unmatched to the description of what they are providing.
However, there are conventional calls nodes that provide multiple frequencies on a single node (similar to trunked). Not sure how that is done.
I have never been a fan of Broadcastify.Thanks for the info. I decided to scrap the Broadcastify Call feature. I can't see a user wanting to tie up a scanner just for one channel. If the scanner is scanning multiple channels and the scanner is stopped on another TGID then the intended TGID to upload will be a missed call.