Previous working script now failing

[mike....@gmail.com]

I'm just getting back into ODR software and a previous ODR-AudioEnc script invoking ODR-PadEnc to add DLS that used to work now won''t work.

The script is:-

rm /tmp/shoutb.fifo
mkfifo /tmp/shoutb.fifo
odr-padenc -r -o /tmp/shoutb.fifo -t ./shoutb
odr-audioenc -v http://stream.dnsgb.net:8XXX -C 8000  -b 48 -c 2 -r 48000 --edi=tcp://127.0.0.1:9200 -l -D -p 58 -P /tmp/shoutb.fifo

(stream port blanked on purpose)

Reading the 'help' files seems to suggest one programme is expecting data from the other and vice versa in defining the size of the DLS. 

odr-padenc is v3.0.0, odr-audioenc is v3.5.0.

Running the odr-audioenc line without reference to odr-padenc parameters is fine but running the odr-padenc line gives this:-

ODR-PadEnc encoding DLS from './shoutb' to '/tmp/shoutb.fifo'. No Slideshow.
ODR-PadEnc using charset UTF-8 (15)
ODR-PadEnc converting DLS texts to Complete EBU Latin
ODR-PadEnc failure: PAD socket bind failed No such file or directory

and running the whole script gives the reason for odr=audioenc fail:-

2024-07-26Z12:11:08       ODR-AudioEnc failed to start: PAD socket bind failed No such file or directory
Initialising default TAI Bulletin URLs.

Is there a new parameter that I am missing?

.

[Rashid Mustapha]

If it was made for a very old version of odr-audioenc, it could be that there is a difference in the command line switches.

Things have moved on from fifos as both odr-audioenc and odr-padenc now communicate via unix sockets, which is much better.

R

--
You received this message because you are subscribed to the Google Groups "mmbtools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to crc-mmbtools...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/crc-mmbtools/6b38de6e-c5b0-4aed-a0a9-6005cbb9661an%40googlegroups.com.

[mike....@gmail.com]

Through trial and error(not being a Unix guru or Linux guru for that matter) and getting many (but helpful) error messages on the way I have a working syntax. This lesson seems to fit what I've always said about Linux's learning ladder that the bottom rung is missing. I can take out the references to FIFO's in the script now. 

Cheers Rash.

Mike D

[Matthias Brändli]

Hi Mike

> many (but helpful) error messages

Thanks, glad to hear that those messages are useful!

> This lesson seems to fit what I've always said about Linux's learning
> ladder that the bottom rung is missing.

For getting the Opendigitalradio tools to work, some linux proficiency
is indeed required.

The bottom rung is less close to the ground than other operating
systems, but the ladder is much longer :-)

Cheers
mpb

[mike....@gmail.com]

Yes the error messages gave guidance as to the way the syntax was going. Is this having to read between the lines a tactic to avoid updating the PDF? (only joking) It would obviously be a big job to document every command line switch in the upgraded main programmes. I'm sure I had the MUX GUI programme running 4 years ago but there seems to have been some significant changes there as well. 

MD

[Matthias Brändli]

On 29/07/2024 14:46, mike....@gmail.com wrote:
> Is this having to read between the lines a tactic to avoid updating the
> PDF? (only joking)

Oh! wait, does the mmbtools guide still contain examples with old
command line arguments? If so, where?

mpb

[mike....@gmail.com]

No it does refer to socket identifier between odr-padenc and odr-audioenc but the explanation of syntax is vague.

Where's my ladder?

MD

[mike....@gmail.com]

Just had a tussle with odr-audioenc probably due to the order I did things. I'm setting up two PC's to create the MUX EDI stream for our proposed transmitter(when we get the licence in Ofcom's good time). I have one setup and ready to go. The second standby PC(identical model) has been troublesome. I couldn't get Supervisor to behave at first in either Deb12 or Ubuntu 24.04 so re-loaded Ubuntu from scratch and played it straight using the Supervisor Deb package and it behaved. I knew I had found I needed VLC so used the version in the Ubunty software store. The ODR packages then got installed seemingly without incident but when it came to reading internet streams in odr-audioenc, failure with a VLC error occurred. This was strange as all the streams could be checked in VLC as OK. Reloading and recompiling the package was not successful. Suffice to say a command line re-install of VLC solved the problem. Ho hum, such is life.

Mike D.

[mike....@gmail.com]

I'm slowly working towards clean, i.e. no unwanted baggage due to misinterpreting error messages and going down blind alleys, installs of our main and standby MUX generating PC's and the recent attempt threw a wobble with the audio encoder. I didn't want 'Jack' or 'Gstreamer' so didn't download the files they apparently needed. Bootstrap was ok but configure, disabling 'Jack' and 'Gstreamer' but enabling 'Alsa' and 'Vlc', failed. I just went for broke and downloaded the Jack and Gstreamer components and  configure with the same rules worked fine.