Search results

There was never any request to remove any archives, and we don't do so unless it's an archive file(s) that contains audio from someone's microphone and the feed provider themselves contacts us in a panic because they were beating their wife, or having an affair with someone, or they were...

Denny and I are working on this offline.

It is, of course, the R9000

I'm sorry that you and your fellow residents feel this way. But as you can imagine, this isn't going to be a place to debate this. This would be like walking into McDonalds and hosting a debate on whether or not french fries are good for public health. I would recommend you find another...

We can transfer it for you. Contact me at support@radioreference.com.

Give it a shot now. We were rolling out some changes this morning to the APIs. Should be OK now.

It’s something we can definitely look into. Thanks for the suggestion

Sounds like your Internet connection might be dropping.

We got this fixed this morning. We rolled out a bug in the interface yesterday. Another bug strikes... sorry about that.

Volume controls for iOS are all handled by the OS (the physical buttons) - we try to detect but it doesn't always work due to varying iOS versions

Given the disparity here between iOS versions for support for Web Audio API functions I'm disabling the panner for iOS devices for now. You ruined it for everyone GILLIG40 😂

I'm unable to reproduce this on my own iPhone and iPad. What versions of iOS are you running? Edit: Oh, I see you're using a 10 year old iPhone LOL. Ummmm. Hmm.. I'll look into this.

Are you guys still having this problem?

Go for it! We did make a change to calls for SDRTrunk users where their node was being "kept alive" by the periodic tests instead of actually receiving calls.

I'm guessing this is where you've run into trouble because you've assigned "100" as the talkgroup ID when Broadcastify calls is expecting "1" as the entry ID. Remember, for conventional channels we have to map your conventional channels to frequencies in the RadioReference database. When you...

There's your problem. For some reason you're sending 100 instead of 1 for the slot or entry ID or whatever it's called in SDRTrunk.

Everything looks fine on our end. For some reason it looks like you're sending to the wrong node.

Well, for one, during a major incident, people will turn on their radios and affiliate to that talkgroup from all over the system to hear what is going on. If a node that is a slightly better quality node gets promoted to providing that talkgroup on calls, you are NOT going to see that...

The problem is there are multiple nodes that could be providing the same talkgroup and we vote between nodes for individual talkgroups. If there is a node 250 miles away with a better quality ranking providing the talkgroup, trying to listen could result in you never seeing that talkgroup...

Yeah that’s long gone. You’ll have to probably find it on youtube or something