Menu

#102 libshout-idjc 2.4.5 disconnects from server when sending metadata.

v1.0 (example)
closed-fixed
nobody
None
5
2023-09-18
2021-02-10
No

If you set a stream to use MPG3 and either Latin or UTF8 for encoding, the stream disconnects from the server (tested with Icecast) when the metadata is sent. Turning off metadata and the stream works. This does not happen if using Vorbis. I've downgraded libshout-idjc to 2.4.2 and MPG3 with metadata works.

Discussion

  • Stephen Fairchild

    Please test libshout-idjc version 2.4.4 on the file release system which works OK for me. Also I did a bad thing to the git repo basically just deleted it and rewrote some stuff so please delete and re-clone libshout-idjc. Note master is at 2.4.5 one commit ahead of the metadata friendly 2.4.4.

     
    • Brian Millham

      Brian Millham - 2021-02-14

      2.4.4 works. I can't use the git repo, I had to download the tar.gz. When trying the git, it complains about missing modules when running autogen.sh, I get:

      ERROR: Submodules missing! Ensure you git cloned with '--recursive' or run:
               git submodule update --init
      

      And if I try that, I get:

      Cloning into '/home/brian/Develop/idjc-libshoutidjc-code/m4'...
      fatal: repository 'https://git.code.sf.net/p/idjc/libshoutidjc/icecast-m4.git/' not found
      fatal: clone of 'https://git.code.sf.net/p/idjc/libshoutidjc/icecast-m4.git' into submodule path '/home/brian/Develop/idjc-libshoutidjc-code/m4' failed
      Failed to clone 'm4'. Retry scheduled
      Cloning into '/home/brian/Develop/idjc-libshoutidjc-code/src/common'...
      fatal: repository 'https://git.code.sf.net/p/idjc/libshoutidjc/icecast-common.git/' not found
      fatal: clone of 'https://git.code.sf.net/p/idjc/libshoutidjc/icecast-common.git' into submodule path '/home/brian/Develop/idjc-libshoutidjc-code/src/common' failed
      Failed to clone 'src/common'. Retry scheduled
      Cloning into '/home/brian/Develop/idjc-libshoutidjc-code/m4'...
      fatal: repository 'https://git.code.sf.net/p/idjc/libshoutidjc/icecast-m4.git/' not found
      fatal: clone of 'https://git.code.sf.net/p/idjc/libshoutidjc/icecast-m4.git' into submodule path '/home/brian/Develop/idjc-libshoutidjc-code/m4' failed
      Failed to clone 'm4' a second time, aborting
      

      I've run into this before, but never mentioned it as downloading the tar.gz has always worked.

       
  • Stephen Fairchild

    You will need an upstream branch with a remote set to the correct upstream repository if you want to recursively obtain those files and possibly a gitlab account too since that is where they keep their most up to date code. I got mine from a download page - cheating.

    Bug report regarding upstream libshout 2.4.5 here (including test program):
    https://gitlab.xiph.org/xiph/icecast-libshout/-/issues/2328

     
  • Brian Millham

    Brian Millham - 2021-02-15

    Thanks to Moonbase, I got a copy of SC 1.9.8, and sending Metadata still fails to the SC server. I reverted back to libshout-idjc 2.4.2 and sending Metadata (in Latin) works. So it looks like 2.4.4 is not compatible with Shoutcast 1.9.8. If I suppress Metadata 2.4.4 will connect to SC (MP3) and stream. Just without metadata. I also noticed that when connecting to SC using 2.4.4 that I always get an invalid password error. When connecting with 2.4.2 I don't see that error.

     

    Last edit: Brian Millham 2021-02-15
  • Moonbase

    Moonbase - 2023-02-10

    Has this ever been followed up and probably even fixed? Upstream libshout talk about 2.4.6 working correctly (see Stephen’s bug link above).

    I’m facing having to switch some friends (and myself, actually) to Arch-based distros (ArcoLinux & Manjaro) and the AUR provides IDJC 0.9.4-1 and libshout-idjc 2.4.4-1. All seems to work except sending metadata to SC 1.9.8, and I’m unable to manually rebuild libshout-idjc, exactly like Brian.

    Unfortunately, most commercial stream providers over here only offer Shoutcast 1.9.8 or 2 (even worse), not Icecast, and stations aren’t willing to switch.

    Staying on old Ubuntu 14.04 and Linux Mint 17 or sending no metadata aren’t an option. Any ideas or solutions?

     

    Last edit: Moonbase 2023-02-10
    • Brian Millham

      Brian Millham - 2023-02-10

      You can still get the 2.4.2 tar.gz and use that to replace 2.4.4

      Has Arch switched to Pipewire yet? If so you will need the newest version of IDJC as there were some issues with Pipewire.

       
      • Moonbase

        Moonbase - 2023-02-11

        I must admit I have to learn more about Pipewire yet… It is running, as are PulseAudio & Jack2, which I still use (bridged), with Cadence for easy setup and either Catia or Patchage (where available) for patching. Also a2jmidid, for my KORG nanoPAD2 to control the IDJC cartwall.

         
  • Moonbase

    Moonbase - 2023-04-06

    Just FYI: I downgraded to libshout-idjc 2.4.2-1 on my Arch, and can connect to SC 1.9.8 again. No metadata update problems anymore.

     
  • Stephen Fairchild

    Announcing libshout-idjc-2.4.6.

     
  • Stephen Fairchild

    • status: open --> closed-fixed
     

Log in to post a comment.

MongoDB Logo MongoDB