Transcoder glitch

[riggs498]

Hi Tom,

I have been using your XLX version in an Oracle cloud. They have been having network issues. The transcoder runs through my VPN. The transcoder still shows it is transcoding. But XLX is not synced fully anymore? I can restart transcoder and get it back. I guess it resyncs again. No the problem. I am only transcoding 2 modules EP. That is how I have it setup in rconfig. If the above happens. I lose XLX on all modules. If shows we are keying up and text passes. But voice will not pass. Module C is D* only. We can not use it. No errors either F anywhere. Resync the transcoder fixes the problem.

Do you have any ideas?
I have a server at home the has FREEDMR and Allstar. Can I make a hidden server at my house, interlink them together and do transcoding at my house on the same computer and send it back in my XLX Reflector?
Also, if my transcoder is remote. Can I get radmin to bypass ambed server compile? But still keep it in the config. If it is okay, I can look at changing that script file.

Thanks,
Ryan (KB8PMY)

[n7tae]

Ryan, I replied to this via E-mail, but I don't see my response here. Did you get my Email?

[riggs498]

No Thanks, Ryan (KB8PMY) N8MFN Hamilton Wireless Radio Club

…

On Sat, Mar 16, 2024 at 8:09 PM Tom Early ***@***.***> wrote: Ryan, I replied to this via E-mail, but I don't see my response here. Did you get my Email? — Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADTNHB2HQ7Z2ZHN54GAIEZDYYTNMHAVCNFSM6AAAAABEZPNOZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGE4TOMRWGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[n7tae]

UDP is a terrible way to connect xlxd to ambed, especially if the connection is even slightly problematic. The only way UDP works well for this comm is over the loop-back device, 127.0.0.1 or ::1. Once packets start going AWOL, the only way to get the system back into sync is to restart xlxd or ambed, or both.

You could build a new couple of radmins, one for ambed and one for xlxd, but it probably would be easier to just use sudo make install and sudo make uninstall manually and use systemctl and journalctl to manage the two services and check the logs.
You can still use rconfig on the xlxd side and then after writing out the .h files and .mk files, rcp those for the ambed to its server build directory.

If I were you, I would buy a cheap, good SBC, like a RPi 5 or an Orange Pi 5 to run urfd and tcd. You only have to open incoming ports for protocols that you are going to support. You could then use local IP address for connection to your DMR server.

[riggs498]

See Below Thanks, Ryan (KB8PMY) N8MFN Hamilton Wireless Radio Club

…

On Sat, Mar 16, 2024 at 10:24 PM Tom Early ***@***.***> wrote: UDP is a terrible way to connect xlxd to ambed, *especially* if the connection is even slightly problematic. The only way UDP works well for this comm is over the loop-back device, 127.0.0.1 or ::1. Once packets start going AWOL, the only way to get the system back into sync is to restart xlxd or ambed, or both. Why does it take all the audio away? Even on the stuff that doesn't need the trascoder. I rebuilt the system with out the transcoder. I would have thought that the only module that would not have worked would have been the transcoded modules. You could build a new couple of radmins, one for ambed and one for xlxd, but it probably would be easier to just use sudo make install and sudo make uninstall manually and use systemctl and journalctl to manage the two services and check the logs. You can still use rconfig on the xlxd side and then after writing out the .h files and .mk files, rcp those for the ambed to its server build directory. If I were you, I would buy a cheap, good SBC, like a RPi 5 or an Orange Pi 5 to run urfd and tcd. You only have to open incoming ports for protocols that you are going to support. You could then use local IP address for connection to your DMR server. I could use this but you don't support interlink. I have two interlink connections. I have a 16 core 76GB blade server I have everything for Ham radio running on that. I think I will have to just move the whole xlx server to the house. urfd looks good but interlink in not there. I am doing away with Brandmiester. Bad issues there. — Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADTNHB4JWCSKCHVAN6OPBW3YYT5G3AVCNFSM6AAAAABEZPNOZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGI4DEOJVHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[riggs498]

sorry it has been a while. I have been having a lot of issues lately. I think I have them fixed. That being said. I have the transcoder and new-xlxd on the same vm. There is something still wrong. Here is what xlxd is saying. I used ./radmin to compile and run everything.

Apr 20 00:45:10 ambed xlxd[4528]: Closing stream of module E
Apr 20 00:45:10 ambed xlxd[4528]: ambed 1781 of 408 packets timed out
Apr 20 00:50:51 ambed xlxd[4528]: ambed openstream ok
Apr 20 00:50:51 ambed xlxd[4528]: Opening stream on module E for client BM3103 with sid 52907 by user N8EMA / DMR
Apr 20 00:51:01 ambed xlxd[4528]: Closing stream of module E
Apr 20 00:51:01 ambed xlxd[4528]: ambed 1994 of 462 packets timed out
Apr 20 00:53:13 ambed xlxd[4528]: ambed openstream ok
Apr 20 00:53:13 ambed xlxd[4528]: Opening stream on module C for client N8MFN E with sid 63126 by user KB8PMY P / RYAN
Apr 20 00:53:16 ambed xlxd[4528]: Closing stream of module C
Apr 20 00:53:16 ambed xlxd[4528]: ambed 586 of 98 packets timed out

If you notice the packet count is real high. It doesn't transcode very well either. Now here is the log for the transcoder.

Apr 20 00:50:51 ambed ambed[4350]: Opened stream 11
Apr 20 00:51:01 ambed ambed[4350]: Vocodec channel DVstick-33:1 -> DVstick-33:0 closed
Apr 20 00:51:01 ambed ambed[4350]: 0 of 462 packets lost
Apr 20 00:51:01 ambed ambed[4350]: Stream 11 closed
Apr 20 00:53:13 ambed ambed[4350]: Stream Open from XLX265
Apr 20 00:53:13 ambed ambed[4350]: Vocodec channel DVstick-33:0 -> DVstick-33:1 open
Apr 20 00:53:13 ambed ambed[4350]: Opened stream 12
Apr 20 00:53:16 ambed ambed[4350]: Vocodec channel DVstick-33:0 -> DVstick-33:1 closed
Apr 20 00:53:16 ambed ambed[4350]: 0 of 98 packets lost
Apr 20 00:53:16 ambed ambed[4350]: Stream 12 closed

They are nothing alike. I have not idea even where to start with this one.

[n7tae]

The "packets timed out" message showing up here, without any turn-around "ambed stats" being printed, along with the fact that the ambed log looks okay, would seem to indicate that nothing is being returned from the transcoder. Those messages are in the ctranscoder.cpp file in the ReleaseStream function.
Does this weird packet count start when it has first booted up, or does it work okay for a while and then start acting up?

[riggs498]

I switched back to XLXD for the time being. I was trying to bring it back up in the log. But Yes that would be correct. The weird part about lastnight was that I could hear E on C. Thanks, Ryan (KB8PMY) N8MFN Hamilton Wireless Radio Club

…

On Sat, Apr 20, 2024 at 8:45 AM Tom Early ***@***.***> wrote: The "packets timed out" message showing up here, without any turn-around "ambed stats" being printed, along with the fact that the ambed log looks okay, would seem to indicate that nothing is being returned from the transcoder. Those messages are in the ctranscoder.cpp file in the ReleaseStream function. Does this weird packet count start when it has first booted up, or does it work okay for a while and then start acting up? — Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADTNHB5WLTC6H6JX4K3N5ELY6JPNXAVCNFSM6AAAAABEZPNOZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRXGY3DENRXGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[riggs498]

Is there something I can try to see if it helps? Thanks, Ryan

…

On Sat, Apr 20, 2024 at 4:14 PM Ryan Collier ***@***.***> wrote: I switched back to XLXD for the time being. I was trying to bring it back up in the log. But Yes that would be correct. The weird part about lastnight was that I could hear E on C. Thanks, Ryan (KB8PMY) N8MFN Hamilton Wireless Radio Club On Sat, Apr 20, 2024 at 8:45 AM Tom Early ***@***.***> wrote: > The "packets timed out" message showing up here, without any turn-around > "ambed stats" being printed, along with the fact that the ambed log looks > okay, would seem to indicate that nothing is being returned from the > transcoder. Those messages are in the ctranscoder.cpp file in the > ReleaseStream function. > Does this weird packet count start when it has first booted up, or does > it work okay for a while and then start acting up? > > — > Reply to this email directly, view it on GitHub > <#12 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ADTNHB5WLTC6H6JX4K3N5ELY6JPNXAVCNFSM6AAAAABEZPNOZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRXGY3DENRXGM> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[n7tae]

Is XLXD working correctly for you?

[riggs498]

Yes, it is working.

…

On Tue, Apr 23, 2024, 7:08 PM Tom Early ***@***.***> wrote: Is XLXD working correctly for you? — Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADTNHBZNL23SSQZS6CZOPR3Y63SW3AVCNFSM6AAAAABEZPNOZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZTGYZTCOJQGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[n7tae]

Is ambed local or remote?

[n7tae]

Also, if xlxd is working, why do you want to replace it?

[riggs498]

AMBED is local on the same server. It is running on 127.0.0.1 I want to replace it cause you use more connections and support things easier. The other one is that I can only make a couple reflectors transcode not everything. I also would like to see if I can feed D-Star voice announcements to the Reflector instead of allstar. I want to figure that part out. Thanks, Ryan

…

On Tue, Apr 23, 2024 at 8:08 PM Tom Early ***@***.***> wrote: Also, if xlxd is working, why do you want to replace it? — Reply to this email directly, view it on GitHub <#12 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADTNHB4SROVI4E3X5VEZC63Y63ZYLAVCNFSM6AAAAABEZPNOZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZTGY4DOMRZGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[n7tae]

If xlxd is running okay with ambed local, then if you are having trouble with new-xlxd, then it must be a new xlxd configuration issue. Shutdown and uninstall both xlxd and ambed. Then in new-xlxd do ./rconfig and make sure the configuration looks okay, and write out the configuration with a 'w'. use ./radmin to compile ans install new-xlxd.

At that point, if there are problems with new/xlxd and or ambed, I will need to see the following files: reflector.cfg, src/configure.h, src/configure.mk, ambed/configure.h and ambed/configure.mk. You can post them here, or if it's easier, you can send them to me via email using n7tae (at) arrl (dot) net.

When you 'w'rite out your configuration in ./rconfig, it will print all these files to the screen. That might be a good time to grab them.