Hi: I have Analog_Bridge currently set up to send unity gain from DMR to ASL, and ASL to DMR at TLV gain factor 0.34. Over all, this works pretty well, but I would like to raise quieter DMR audio into

If you can get raw PCM to stdout, you can pipe that audio to lame, then pipe lame to ezstream. No sound card, virtual or otherwise, required. You could perhaps do this with ffmpeg as well. Going the D

Well, the root cause has been identified and fixed. Apparently, Brandmeister did actually give me that interlink I asked for months ago, but I never got a notification about it. This was breaking thin

XLX log: I: 2019-12-01 19:02:46.038 MMDVM_Bridge: I: 2019-12-01 19:02:46.038 Portions Copyright (C) 2018 DVSwitch, INAD. I: 2019-12-01 19:02:46.038 Hacks by Mike N4IRR and Steve N4IRS I: 2019-12-01 19

Oh, doink. My clipboard must not have gotten updated. XLX log for real this time: I: 2019-12-01 18:45:51.187 MMDVM_Bridge: I: 2019-12-01 18:45:51.187 Portions Copyright (C) 2018 DVSwitch, INAD. I: 201

XLX log: I: 2019-12-01 18:45:51.187 MMDVM_Bridge: I: 2019-12-01 18:45:51.187 Portions Copyright (C) 2018 DVSwitch, INAD. I: 2019-12-01 18:45:51.187 Hacks by Mike N4IRR and Steve N4IRS I: 2019-12-01 18

I have now updated to v2.3.2. How does this interlink without talkgroup conversion work in this version as opposed to older ones?

I: 2019-12-01 18:38:59.097 MMDVM_Bridge: I: 2019-12-01 18:38:59.097 Portions Copyright (C) 2018 DVSwitch, INAD. I: 2019-12-01 18:38:59.097 Hacks by Mike N4IRR and Steve N4IRS I: 2019-12-01 18:38:59.09

Here's that version. First transmission is from Brandmeister, second is from the reflector. I transmitted from Brandmeister again but it isn't in the log. I: 2019-12-01 18:22:43.822 MMDVM_Bridge: I: 2

Here is the full log from the XLX MMDVM_Bridge. There was only one transmission sent from the reflector itself other than MMDVM_Bridge quick keying to connect to 4001. I: 2019-12-01 18:02:37.822 MMDVM

Hi: I've been trying to set this up all day, and am stumped by the following situation. Now that I've sorted my XLX problems (I hope,) I have two instances of MMDVM_Bridge connecting a BM talkgroup to

The local ports are already different -- BM instance local port is 62032, XLX is 62034. I have them both running in console. Traffic passes fine from BM to XLX, but as soon as anyone transmits from D-

This is XLX679 module A. FWIW: I copied the exact configuration over to a machine on my LAN, and it works there. Don't know what the difference is. I have two instances of MMDVM_Bridge running -- one

Right. I wasn't referring directly to the INI file at the time. My machine is on a VPS, so the IP of ETH0 is a public IP address. So, it looks like this. [DMR Network] Enable=1 Address=<Public_IP_Of_T

Currently, I have the address in the DMR Network stanza pointed to the XLX reflector <IP_ADDRESS:62030). I assume this is the network address you're referring to? If so, then the reflector isn't doing

Oh yes, I forgot to mention that the MMDVM_Bridge is in its own directory with different rx and tx ports in DVSwitch.ini to avoid conflict with the existing bridge.

That was actually the first configuration I tried. Same result either with the Interface IP address, or local loopback. I’ll mess with it some more later. The MMDVM_Bridge part looks easy enough once

I downloaded the latest MMDVM_Bridge earlier today. My current issue is getting MMDVM-Bridge connected to XLXD on the same machine. I'm sure I've directly connected a hotspot to the reflector before,

OK. I just tried setting up an instance of MMDVM_Bridge to point to 127.0.0.1 on port 62030 (MMDVM) using the DMRNetwork. I thought XLXD responded to that, but apparently it doesn't, as the connection

Hello: I found an old docc referring to using two instances of MMDVM_Bridge and DMRGateway to bridge DMR to XLX. Is this necessary anymore, or can we now just use two instances of MMDVM_Bridge, since