Calls - Listening via Individual Nodes no longer available

[Outerdog]

The concept of nodes probably shouldn't even be presented to users who aren't providing a node. Particularly problematic seems to be the concepts of nodes and location presented together.

 

[K3HY]

I’m sorry but this isn’t how calls works, you can only listen to a playlist through your web browser.

additionally, the link above is to an individual feed, not a Broadcastify “node”

Thanks for your quick response. Luckily my internet radio also receives bluetooth, so I can send the web browsers playlist audio to the internet radio via bluetooth.

 

[blantonl]

The concept of nodes probably shouldn't even be presented to users who aren't providing a node. Particularly problematic seems to be the concepts of nodes and location presented together.

Agreed

 

[Napalm]

Someone earlier in this thread said you can't send DMR/TRBO to calls. This is absolutely wrong and I didn't see anyone correct the poster.

I have two DMR T3 nodes that I provide for the Indiana NIPSCO net in my area via SDRTrunk.

 

[blantonl]

Someone earlier in this thread said you can't send DMR/TRBO to calls. This is absolutely wrong and I didn't see anyone correct the poster.

I have two DMR T3 nodes that I provide for the Indiana NIPSCO net in my area via SDRTrunk.

You, I saw this earlier and wanted to chime in as well. I think for now we support everything that SDRTrunk can capture.

 

[blantonl]

Please see: Broadcastify Calls - New Playlist Management Features

 

[cadareev]

@blantonl , the Rattlesnake Round-up is this weekend. Just FYI. Come see some snakes, eat some good food, and have a good time!
Calendar of Events.....

 

[egftechman]

Appreciate all the efforts @blantonl has put into the Call platform recently!
just wondering if it's possible to add the speed control to the "all received calls" pages, like below. This is where the speed control could be most useful.

 

[blantonl]

We'll look at it for the next developer sprint that we do.

 

[rcid1971]

Collapse of the Francis Scott Key Bridge was a perfect example of me, the out of towner, wanting to hear the whole node at 3:30 in the morning versus struggling to build playlists to figure out which channels they were on. A major fail.

 

[egftechman]

Collapse of the Francis Scott Key Bridge was a perfect example of me, the out of towner, wanting to hear the whole node at 3:30 in the morning versus struggling to build playlists to figure out which channels they were on. A major fail.

Is there multiple nodes in the area? An area playlist will actually be more complete than listening to a single node (many SDR setups still have a limit to how many simultaneous decodes they can do, there can be network/power outages, local interference, etc - multiple nodes reduces the impact of those issues), and operate exactly the same (listing to a node vs a "Baltimore area" playlist is exactly the same). I'm having a hard time understand why so many here don't understand the concept. It brings the power and coverage of multiple "scanners" together. You can also listen to "systemwide" calls in Broadcastify calls, where you hear all calls on a TRS. (side note, events like this also underscore the need for conventional channel feeds into Calls, I'm sure many of them otherwise idle became active for specialized purposes)
I'll agree maybe there needs to be more playlist interface refining. I thought there was doing to be automatic "county" playlists based on DB entries, along with curated playlists from feed providers.
I think this is the right approach, just takes a higher level vision than a single scanner station to see its benefits. I you want to be stuck with the traditional limitations, you can go to openmhz, one of the many rdio scanner sites (most are limited membership), or find the "independent" streams in an area you want to listen to.

 

[rcid1971]

Is there multiple nodes in the area? An area playlist will actually be more complete than listening to a single node (many SDR setups still have a limit to how many simultaneous decodes they can do, there can be network/power outages, local interference, etc - multiple nodes reduces the impact of those issues), and operate exactly the same (listing to a node vs a "Baltimore area" playlist is exactly the same). I'm having a hard time understand why so many here don't understand the concept. It brings the power and coverage of multiple "scanners" together. You can also listen to "systemwide" calls in Broadcastify calls, where you hear all calls on a TRS. (side note, events like this also underscore the need for conventional channel feeds into Calls, I'm sure many of them otherwise idle became active for specialized purposes)
I'll agree maybe there needs to be more playlist interface refining. I thought there was doing to be automatic "county" playlists based on DB entries, along with curated playlists from feed providers.
I think this is the right approach, just takes a higher level vision than a single scanner station to see its benefits. I you want to be stuck with the traditional limitations, you can go to openmhz, one of the many rdio scanner sites (most are limited membership), or find the "independent" streams in an area you want to listen to.

How would an area playlist have enough capacity to include Tac 32?

 

[blantonl]

Collapse of the Francis Scott Key Bridge was a perfect example of me, the out of towner, wanting to hear the whole node at 3:30 in the morning versus struggling to build playlists to figure out which channels they were on. A major fail.

"A major fail."

Sorry bud, but this take is ridiculous and I take personal offense to your assertion. All you had to do was click on the "listen to systemwide calls" for the 3 systems and you would have been just fine.

If you would have listened to an individual node you would have almost certainly missed calls because some nodes were providing calls for some talkgroups and other nodes were doing so for others.

Really an offensive and obtuse take....

 

[rcid1971]

"A major fail."

Sorry bud, but this take is ridiculous and I take personal offense to your assertion. All you had to do was click on the "listen to systemwide calls" for the 3 systems and you would have been just fine.

If you would have listened to an individual node you would have almost certainly missed calls because some nodes were providing calls for some talkgroups and other nodes were doing so for others.

Really an offensive and obtuse take....

Apologies if my comment read as offensive. Never was the intention. That’s not how I roll.

 

[RaleighGuy]

Collapse of the Francis Scott Key Bridge was a perfect example of me, the out of towner, wanting to hear the whole node at 3:30 in the morning versus struggling to build playlists to figure out which channels they were on. A major fail.

"A major fail."

Sorry bud, but this take is ridiculous and I take personal offense to your assertion. All you had to do was click on the "listen to systemwide calls" for the 3 systems and you would have been just fine.

If you would have listened to an individual node you would have almost certainly missed calls because some nodes were providing calls for some talkgroups and other nodes were doing so for others.

Really an offensive and obtuse take....

Case in point, I built a playlist and was listening to traffic from two systems, with TGs gained from the thread in the forums, in under 5min and was hearing most traffic without the interruptions for traffic stops or other unrelated traffic I wouldn't care about.

The playlists worked perfectly for this incident the morning of.

 

[blantonl]

How would an area playlist have enough capacity to include Tac 32?

You just add it to the playlist? Why are you being obtuse? If you look at the system setup you'll notice that just because the channel is labeled "Tac 32" doesn't mean there's 30+ TAC channels you needed to monitor.

Good lord.

 

[blantonl]

Case in point, I built a playlist and was listening to traffic from two systems, with TGs gained from the thread in the forums, in under 5min and was hearing most traffic without the interruptions for traffic stops or other unrelated traffic I wouldn't care about.

The playlists worked perfectly for this incident the morning of.

Yeah, we had a playlist tactically generated and made available to the public within minutes later that morning with hundreds of listeners, covering 3 totally separate wide area trunking systems, and we had a new record for Broadcastify Calls users yesterday.

It might have been the best use of the calls platform and ease of use for monitoring such a complex incident in the history of the platform.

 

[rcid1971]

You just add it to the playlist? Why are you being obtuse? If you look at the system setup you'll notice that just because the channel is labeled "Tac 32" doesn't mean there's 30+ TAC channels you needed to monitor.

Good lord.

Now it reads as if you saw obtuse in Shawshank and get that keyboard warrior dopamine joy from using it on your customers? Good work!

 

[rcid1971]

Case in point, I built a playlist and was listening to traffic from two systems, with TGs gained from the thread in the forums, in under 5min and was hearing most traffic without the interruptions for traffic stops or other unrelated traffic I wouldn't care about.

The playlists worked perfectly for this incident the morning of.

TGs you found from the threads. But look deeper at those threads and see who was first researching where to find those talk groups. 🤦‍♂️

 

[blantonl]

Now it reads as if you saw obtuse in Shawshank and get that keyboard warrior dopamine joy from using it on your customers? Good work!

Every man has his breaking point rcid1971. It's not nice to come in and throw stones in peoples homes, all the while not really having a good leg to stand on.

I take to heart feedback, but those that have taken the stance that our decision to move away from listening to individual nodes are dying on the dumbest hill possible in the face of overwhelming information and contradicts all the evidence to the contrary. We've beat this to death. Your use of the phrase "Major Fail" is... obtuse. everything suggests otherwise.

I'll go back to your original reply and take that at face value and ignore the rest.

Apologies if my comment read as offensive. Never was the intention. That’s not how I roll.