Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Icecast metadata updates in scan mode" seems not to work #203

Closed
ger-pakon opened this issue Dec 4, 2020 · 13 comments
Closed

"Icecast metadata updates in scan mode" seems not to work #203

ger-pakon opened this issue Dec 4, 2020 · 13 comments

Comments

@ger-pakon
Copy link

Hey,

first thank you very much for your great work!
I tried to configure, that the labels for the frequencies are shown by my own icecast server, but this din't work.

Is there any point, where i can troubleshoot this?

Thank you,
Pakon

@szpajder
Copy link
Collaborator

szpajder commented Dec 5, 2020

Can you post your config file (without passwords, etc)?

Which version / branch of the program are you using?

@ger-pakon
Copy link
Author

Hey, I'm using the latest stable.

devices:
({
  type = "rtlsdr";
  index = 2;
  gain = 200.0;
  mode = "scan";
  multiple_demod_threads = true;
  channels: (
      {
      freqs = ( freq1, freq2, freq3, freq4, freq5);
      labels = ( "Label freq1", "Label freq2", "Label freq3", "Label freq4", "Label freq5");
      modulation = "am";
      afc = 0;
      squelch = 425;
      lowpass = 3200;
      highpass = 200;
      outputs: (
        {
          type = "icecast";
          server = "192.168.X.XX";
          port = 8000;
          mountpoint = "XXX.mp3";
          name = "ATC";
          genre = "ATC";
          description = "Tower and Ground";
          username = "<hidden>";
          password = "<hidden>";
          send_scan_freq_tags = true;
          shout_metadata_delay = 1;
        }
      );
    }
  );
});

@szpajder
Copy link
Collaborator

szpajder commented Dec 5, 2020

Works fine for me. I can see metadata updates and frequency labels displayed in the player.

Does your player actually display icy-info updates as they happen? It might be worth taking a traffic dump with tcpdump to verify if the updates are sent to the server and then back to the client.

@ger-pakon
Copy link
Author

Hey,

thanks for testing. I even can't see something with tcpdump on the local interface. For which keywoards should I grep? I tried to grep for the labels. Which player do you use? I use VLC and an "auna" Internet Radio.

Thanks

@szpajder
Copy link
Collaborator

szpajder commented Dec 5, 2020

I use mpv, but just checked VLC and it works equally well.

When the source sends metadata update to the server, it does that with a HTTP GET request to /admin/metadata?mode=updinfo&mount=<mount_name>&song=<label> . The server in turn sends updates to client with StreamTitle=<label>, so grep for that. For example you can do something like this on the client machine:

tcpdump -As0 -lni <interface_name> host <icecast_server_ip> and port 8000|grep --line-buffered StreamTitle

@ger-pakon
Copy link
Author

Hey,

I could do some tests:

  1. Update the Streamtitle with curl is working and will shown on all my clients.
  2. the /admin path is protected with basic auth, but i never set credentials
  • I tried the same password and user as for user source (admin renamed to source) - nothing happened
  1. I could see in tcpdump, when curl send the request to update the metada,I also could see this in the icecast access.log
  2. I can't see any update from the rtlsdr-airband (lan/loopback interface) to the icecast server (of course after someone's speaking for serveral seconds)

So I think the problem is between icecast (2.4.4.) and the rtlsdr-airband. :-(

Thank you

@szpajder
Copy link
Collaborator

szpajder commented Dec 5, 2020

I'm also on icecast 2.4.4 and it works fine.

Which libshout version are you using on the machine where rtl_airband is running? If it's 2.4.2 or later, then can you please try downgrading it to 2.4.1?

@ger-pakon
Copy link
Author

Hey,

its the following installed by ubuntu:

dpkg -l | grep libshout
ii  libshout3:amd64                                             2.4.3-1                             amd64        MP3/Ogg Vorbis broadcast streaming library
ii  libshout3-dev:amd64                                         2.4.3-1                             amd64        MP3/Ogg Vorbis broadcast streaming library (development)

It seems, I have to compile it for myself. Or will it been supported, soon?

Thanks,
Pakon

@szpajder
Copy link
Collaborator

szpajder commented Dec 5, 2020

2.4.3 is buggy, don't use it. See here: #143

2.4.4 is still buggy, but less. 2.4.1 works best as of now.

@ger-pakon
Copy link
Author

I use:

Distributor ID: Ubuntu
Description:    Ubuntu 20.04.1 LTS
Release:        20.04
Codename:       focal

I downgraded to:

- http://ftp.de.debian.org/debian/pool/main/libs/libshout/libshout3_2.4.1-2_amd64.deb
- http://ftp.de.debian.org/debian/pool/main/libs/libshout/libshout3-dev_2.4.1-2_amd64.deb

I will post, if it works with it. :-)

@ger-pakon
Copy link
Author

Hey,

just wanted to let you know, that it is working with the downgraded packages, I mentioned before on Ubuntu 20.04.

Thanks for your help.

@hypeARM
Copy link

hypeARM commented Dec 20, 2022

How to downgrade libshout packages?

I'm in: rpiv3 armhf

@feelingwalnut
Copy link

feelingwalnut commented Dec 20, 2022

@hypeARM this is a question for the package manager of your distribution, which will likely be covered by their help/man files.
likely several other packages will need downgraded, then they will have their own dependencies that also need downgraded.

usually with something like sudo apt install package =version
or manually download the *.deb and sudo dpkg --install filename.deb
that'd be instructions for debian based linux distros.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants