I have a question when I listen to DPD on the NTIRN on broadcasting call platform / nodes I hear this annoying ( burp, hiccup, digital whiny noise about every 6 calls or so , however when I listen to calls on open Mhz I don't hear this noise ? Is this because broadcasting is not as good rebroadcasting these transmissions as on Open mhz site ? Or is it the feed provider ? Listening to DPD on the call's platform is difficult even though free it seems that when a priority call is dispatched that's when the noise starts ?
Broadcasting vs open mhz
- Thread starter kmartin
- Start date
- Status
- Joined
- Jan 4, 2003
- Messages
- 142
I upload a calls node and another person feeds the same system. Broadcastify dedupes the calls that come in and whoever gets there first is kept. IMHO the other person providing the same system has worse digital decode than mine, but theirs normally is uploaded first so most of my audio is rejected. I am not sure if the same thing is happening for the system you are listening to, but it is possible. Another possible explanation is someone totally different provides the Broadcastify feed vs the openmhz feed and has different audio quality.
🤔
The thing is this technology sucks. I say this because time and time again I start to hear a call being dispatched on Galveston PD 1 channel and half way through the call notes as the dispatcher is reading them off suddenly you hear this horrible noise and it completely blocks out what was being said so you are left completely in the dark on what the call was about. And it seems to happen when a crucial moment of something of importance is being said and it happens quite frequently. It's very aggravating ! So for us who pay for a premium subscription makes me wonder if it's really worth it.
There has to be a better way to ensure a decent quality of audio , quality control or something I feel I have a right to complain if I pay for this
All of these feeds, both traditional as well as Calls nodes, are provided by volunteers. There is not, nor has there ever been, any guarantee of service when you purchase a premium membership to RR/BCFY. Feeds/nodes come and go, the quality of the audio varies due to myriad reasons, and that's just how it is.
So instead of complaining about it, perhaps you should either a) just listen to OpenMHz if you feel that's superior and don't bother with BCFY, or b) setup your own feed/node that you can listen to and improve the situation rather than moaning about it
At the very least, if listening to your local stuff is really this important to you, then buy a scanner or setup software so that you have full control over what you're hearing, rather than depending on others.
So instead of complaining about it, perhaps you should either a) just listen to OpenMHz if you feel that's superior and don't bother with BCFY, or b) setup your own feed/node that you can listen to and improve the situation rather than moaning about it
At the very least, if listening to your local stuff is really this important to you, then buy a scanner or setup software so that you have full control over what you're hearing, rather than depending on others.
Go ahead and spring for either an SDS100 or 200. Yup, they aren't cheap but will likely be your best bet when keeping simulcast distortion at bay that you'll undoubtedly experience in the greater Galveston area, as well as from that big city just to the north of you. RR/BCFY is an awesome resource but you shouldn't be reliant on any one particular source to satisfy all of your listening needs. Especially when that law enforcement agency (GPD) is in your own back yard. Lol! Seriously, pick up one of the two (or both if your feeling adventurous) scanners mentioned above and once you get over the discomfort of having to part ways with some (ok, more than some) scratch, you'll appreciate both the convenience and flexibility that having both platforms provides you with. Just do it!
Last edited:
You people on here are idiots ! plain and simple
Uh-oh...
Are you running node 2908? If that's the node and it's competing against node 4121, the reason why 4121 is preferred is likely because of the time. Node 2908 calls seem to show 3.2-3.3 seconds, whereas node 4121 calls seem to show pretty much less than 2 seconds. Are you running a time sync app like DImension 5 or something like that on your calls feed computer?
And the audio from 4121 is mediocre at the best of times. Wonder if that calls provider has issues with CPU overload or PPM problems on their devices.
Ah, someone has read How to Win Friends and Influence People by Dale Carnegie
Hey now...only people that work with me, or know me personally, or have seen me post online, or have heard vague details about me are allowed to call me an idiot.
If you're going to resort to name calling, at least get it right...I'm an asshole, not an idiot. An idiot implies low intelligence; for example someone who can only resort to name calling rather than crafting a clever, witty response.
I agree....GTR is indeed an azzhole. I can call him this because I am one myself and we know and respect our own kind. We even have a secret handshake....you REALLY don't want to know what it consists of.
I think you're both awesome guys.
Yes, because everyone here who gave you solid answers multiple times, even solutions to overcome your problems, and helped you understand how Broadcastify Calls work are an idiot. Yeah, it makes perfect sense. Good job!
If you don't like the service being offered, you are not obligated to continue paying for it. Plain and simple.
- Signed a fellow *******
I am actually the provider for 2908. My machine is capturing 5 sites though, so it’s probably a second behind 4121, but the audio in very clear from my node, even though it’s a temporary setup until the renovations are complete at my house in Dallas.
Anyway, it doesn’t appear 4121 is broadcasting now. So, audio might be better.
- Status
Similar threads
