Date
1 - 14 of 14
metadata management
Patrick Perdue
Hi:
I have a system that incorporates ASL, XLX, HBLink and DVSwitch. I'm toying with the idea of adding P25. Currently, DStar is handled by XLX and a pair of transcoders connected to the XLX reflector, not DVSwitch. I would like to connect ASL directly to the XLX reflector in DStar mode, so that the audio to and from DStar to ASL is not transcoded through AMBE, but still pass metadata to DStar from the other digital modes. Is this at all possible? Similar question in regards to P25. Basically, I want to do the least amount of transcoding possible to and from analog, while maintaining the greatest compatibility across digital modes. What I have now works, but I'd love to get rid of that extra layer of transcoding between analog and DStar without sacrificing metadata. Thanks.
|
|
Patrick,
toggle quoted messageShow quoted text
Either way, you have to go through a vocoder to go from analog to D-Star Same for P25, you still have to go through a vocoder. Steve
On 11/25/20 6:28 PM, Patrick Perdue wrote:
Hi:
|
|
Patrick Perdue
Sure, but I'm currently going through two of them to get from Allstar to DStar.
toggle quoted messageShow quoted text
I'm just wondering if there's a way to drop one of them out and still maintain metadata. I could directly connect A_B and MMDVM_Bridge to the XLX reflector and only direct DStar traffic to the module, and audio between DStar and the other digital modes should be about the same as it is now, but audio from Allstar to DStar has one less generation of vocoding, but then I lose metadata between the digital modes. At least, this is how I understand it.
On 11/25/2020 6:55 PM, Steve N4IRS wrote:
Patrick,
|
|
I don't see how there are 2 vocoders to get from AllStar to D-Star. The flow would be:
toggle quoted messageShow quoted text
AllStar <-> AB <-> MB <-> ircDDBGateway <-> XLX for D-Star. You could drop the ircDDBGateway and go to XLX DMR. Steve
On 11/25/20 7:14 PM, Patrick Perdue wrote:
Sure, but I'm currently going through two of them to get from Allstar to DStar.
|
|
Patrick Perdue
I'm not great at writing out flows.
toggle quoted messageShow quoted text
My setup currently doesn't use ircDDBGateway, since that's all handled at the XLX reflector end. So, it goes like this. Allstar <-> AB <-> HBLink <-> MB <-> XLXD (DMR, since XLX is also handling a BM interlink and YSF traffic) <-> ambed (connected to the XLX reflector) <-> TGIF. I'm sure I screwed that up. So basically, native AMBE traffic is transcoded to analog using the MD380-emu vocoder back to Allstar. DStar is transcoded through the pair of ThumnDV's on the reflector, which is then sent to MD380emu and then Allstar. Between DMR or YSF and DStar, this is fine, but from Allstar to DStar, it's going through another AMBE transcode before A_B sees it, so more latency and lower quality audio. If I connect to the reflector directly as DStar, then use ASL to connect to the other modes, perhaps on another module of the reflector and HBLink, then DMR-YSF would only see the call specified in A_B, correct?
On 11/25/2020 7:18 PM, Steve N4IRS wrote:
I don't see how there are 2 vocoders to get from AllStar to D-Star. The flow would be:
|
|
So,
toggle quoted messageShow quoted text
you have D-Star, DMR and AllStar. If you used AllStar to mix you could keep the number of vocoders to two and only have one transcoder. For the audio, you would have 2 private nodes. The first node would be DMR and pointed at TGIF. The second node would be D-Star and pointed at XLX. As you said in your first message, you issue would then be metadata. Steve
On 11/25/20 7:32 PM, Patrick Perdue wrote:
I'm not great at writing out flows.
|
|
Patrick Perdue
OK, so things are pretty much as I thought they were. Just wanted to make sure I wasn't missing anything should I decide to redesign this system. I'll probably keep things as-is for now, then add another private node for P25.
toggle quoted messageShow quoted text
Thanks.
On 11/25/2020 7:51 PM, Steve N4IRS wrote:
So,
|
|
k7wby@...
Here's a bit of advice, take it for what it's worth.
If you're thinking of linking your other modes to a currently active P25 Reflector, don't. You will be chastised to no end and probably banned from that reflector for life. The only solution you have is a P25Gateway and P25Reflector with a private TG. I did that for a while and had 0 users. I provided instructions on how to update the P25Hosts.txt files on their hotspots but I guess that was more work than they wanted to do. In the end I took down the reflector and gateway and just told them to use their hotspots in P252DMR mode and connect to my XLX reflector. I have a interlink to BM3103 on the XLX. Now I have P25 users and the meta data is not an issue.
|
|
On 26/11/20 11:51 am, Steve N4IRS wrote:
So,This is where my system is at. I have it arranged around an instance of AllStar (except for DMR - YSF, which uses its own instance of MMDVM_Bridge, and no transcoding). Audio wise, my system works well and maintains good quality (because I transcode as few times as possible, regardless of path), but it would be nice to have a way of passing metadata "around" AllStar when going between digital modes that are using different vocoders, without handling audio, to account for cases like mine. -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
On 27/11/20 5:42 am, k7wby@arrl.net wrote:
Here's a bit of advice, take it for what it's worth.I setup my own P25 reflector for my DVSwitch system to connect to, so I wouldn't upset anyone else. Got it registered and it can be reached by any hotspot with up to date hosts files. Or do as I did and get G4KLX to put your reflector into the public hosts file. Just takes a "feature request" in the right Git repository. more work than they wanted to do. In the end I took down the reflectorHmm P252DMR - that sounds like it would only work on an OpenSpot 3. This isn't possible on a Pi-Star based hotspot, because it requires transcoding. -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
Patrick Perdue
As I understand it, you can set up a private P25 reflector which
is available to anyone who uses the pi-star host files, thus, no
need to link to a public reflector. This is what I plan to do. I
will probably also get zero users, but at least I know that coming
in.
On 11/26/2020 1:42 PM, k7wby@...
wrote:
Here's a bit of advice, take it for what it's worth.
|
|
On 27/11/20 8:20 am, Patrick Perdue wrote:
You can do that, or you can setup your own public reflector. You just have to ask to get it listed in the public P25Hosts file. I did this for 50535. -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
Patrick Perdue
Yes, that's what I was referring to. I don't know what the process is for having your reflector listed, only that it can be done.
toggle quoted messageShow quoted text
On 11/26/2020 4:22 PM, Tony Langdon wrote:
On 27/11/20 8:20 am, Patrick Perdue wrote:As I understand it, you can set up a private P25 reflector which isYou can do that, or you can setup your own public reflector. You just
|
|
On 27/11/20 9:05 am, Patrick Perdue wrote:
Yes, that's what I was referring to. I don't know what the process isIt's quite simple, you just have to put in a feature request on the right (P25Gateway I think) Git repository, after setting up your reflector. I'll see if I can find it. Yep, here's the Git repository. You just need to make your request for a new gateway number as an issue here. https://github.com/g4klx/P25Clients/blob/master/P25Gateway/P25Hosts.txt -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|