Regarding a feed on radio reference

[Bullwinkle043]

Yes I have talkgroups I listen to from radio reference linked to my broadcastify as a playlist and only have one problems one of the talkgroups repeats itself St. Joseph County Sheriff Dispatch (TGID:12275 what can I do to fix this problem please help thank you

 

[a417]

Yes I have talkgroups I listen to from radio reference linked to my broadcastify as a playlist and only have one problems one of the talkgroups repeats itself St. Joseph County Sheriff Dispatch (TGID:12275 what can I do to fix this problem please help thank you

Can you expound on what you mean "the talkgroup repeats itself"?

 

[Bullwinkle043]

I'm not sure what you mean by expound but I have some talkgroups that I've added to a playlist I made using broadcastify I got my talkgroups though radio reference all the talkgroups work perfectly except for one which is St. Joseph County Sheriff Dispatch (TGID:12275 I'm not sure what the problem is all I can say that this particular talkgroup has a problem repeating itself the problem needs to be addressed

When you add talkgroups to listen too and make a playlist and you go to play the playlist that you have created and try to listen to the talkgroups that you've added and listen to it one particular talkgroup it repeats itself meaning everytime they transmit and say something it repeats as saying it says the same thing twice

Sheriff Dispatch/St. Joseph County (71) Group Calls Live

12275 Group Calls Live

www.broadcastify.com

If you click on the link that I posted listen to it you'll see what I mean by repeating itself more than once

 

[a417]

I'm not sure what you mean by expound

expound.

 

[mciupa]

On this link: St. Joseph County Public Safety Live Audio Feed Click on Report a Problem and detail clearly what is happening in case the Feed Provider doesn't read your post.

 

[Bullwinkle043]

Okay the problem is not coming from a feeder from broadcastify this is a problem coming from radio reference to a talk group by the local law enforcement or whoever put the talk group on radio reference

It's definitely a problem with the talkgroup on radio reference

 

[INDaviation]

You'll have to contact the owner of the SAFE-T St. Joseph County Simulcast node on Broadcastify Calls. Go to the list of nodes, click on the SAFE-T node, and click the little blue button with "i" on it. It will tell you who owns that node.

 

[AB5ID]

I was able to duplicate the issue by going into the calls platform and creating a temporary playlist with the 12275 talkgroup. The same problem happened here in Kansas City when there was 2 feed providers uploading the same talkgroup to the calls platform.

 

[INDaviation]

I'm hearing it too, listening on the page for that talkgroup.

 

[Bullwinkle043]

Need help reporting the problem thanks

 

[AB5ID]

Need help reporting the problem thanks

Try support@broadcastify.com tell them that you're hearing duplicate back to back calls on talkgroup 12275 that is possibly coming from two different feed providers uploading the same talkgroup to the calls platform.

 

[Bullwinkle043]

Sent thanks

 

[Bullwinkle043]

I sent a message to the person that owns the node as well I still haven't received a response

 

[Bullwinkle043]

 

[n0esc]

Here is what looks like is happening as others have hinted at.

There are at least three volunteers uploading Calls nodes to the system that are monitoring TG 12275 from seperate towers. The times are slightly off between systems so the calls are being treated as separate, thus the duplication.

Node	Owner	Site
1894	mark3871	St. Joseph County Simulcast
201	FrostTheFox	Elkhart County Simulcast
766	ajcoll5	Plymouth (Marshall County)

 

[Bullwinkle043]

What needs to be done to fix the problem or is there another link that I can click on that has no problems

 

[n0esc]

I don't know that there is any one specific fix to resolve this, at least not a simple one.

As a Calls volunteer, you are encouraged to upload all TGs captured by whatever tower, control channel, whatever you are monitoring and the system will filter out the stuff it needs to in a perfect world. Two of the three people who are providing Calls feeds I linked above are super inactive on the site, and not likely to respond. FrostTheFox is relatively active. Making sure all of them are keeping times as accurate as possible will help the site to know which calls are duplicates. The sites for surrounding counties could drop 12275 from their feeds. Not desirable from a personal standpoint if they are monitoring St Joseph as well personally. Broadcastify itself and the developer are aware that this can/is an issue and are working on some fixes, both to encourage providers to make sure their equipment and connection is up to date and to help the system be smarter about picking up these duplicates more accurately. There have been several posts over the last couple of years since Calls was launched.

 

[SurgePGH]

I sent a message to the person that owns the node as well I still haven't received a response

You have to understand that the feeds are supplied by volunteers with their own money and time. Sometimes it may take them some time to reply.

 

[Bullwinkle043]

I understand thanks for the support

 

[FrostTheFox]

Hi, thanks @Bullwinkle043 for bringing this to my attention. It looks like to me that my node is running on an average skew currently of about 0.635 secs, which should be perfectly adequate. The machine I feed from is already being NTP synced with NIST.

I noticed some instances of duplicates where the SJC site had a skew in the range of 16-17 seconds. The Plymouth site has been better on the duplicates, at around 2 seconds. 2 seconds doesn't strike me as particularly large but I guess it might be enough to throw the system off if mine is coming in at under a second. So perhaps they need to check their time syncs.