Hey all
I've been running two Icecast2 streams for a few years that are fed by a Pd patch. Those patches use [readanysf~] to playback MP3 and other audio media, partially from URL. The result is sent through [mp3cast~] to an Icecast2 server.
Since a few weeks, the patch segfaults after a few hours/days of running. This is the backtrace (not much useful info, libraries from Debian seem not compiled with debug symbols):
#0 0x00007ffff757be96 in ?? () from /lib/x86_64-linux-gnu/libgmerlin_avdec.so.2
#1 0x00007ffff756cf14 in ?? () from /lib/x86_64-linux-gnu/libgmerlin_avdec.so.2
#2 0x00007ffff75a64c7 in ?? () from /lib/x86_64-linux-gnu/libgmerlin_avdec.so.2
#3 0x00007ffff753f8e8 in bgav_open () from /lib/x86_64-linux-gnu/libgmerlin_avdec.so.2
#4 0x00007ffff78a42a7 in ?? () from /usr/lib/pd/extra/readanysf~/readanysf~.pd_linux
#5 0x00007ffff7bf41c4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#6 0x00007ffff7c7485c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
which indicates the problem is in the [readanysf~] playback and not in Pd or [mp3cast~].
I plan to run those streams for some more years and am looking for a sustainable way to play back the audio files. Thus, I'm evaluating possible options:
Fix [readanysf~] (if the problem is in readanysf~ and not in a library)
Switch to [mp3amp~] from unauthorized. However, it doesn't compile with current libmpg123
Use something else. Are there other mp3 playback externals?
Fixing [readanysf~] or adjusting [mp3amp~] to modern libmpg23 seem to exceed my coding capabilities and before I decide for a route, I'd like to check what else is around.
Having said that, [readanysf~] is a pretty neat external since it plays many audio formats and supports streaming from HTTP. However, it doesn't seem maintained upstream and is stuck at version 0.43 since 2012. Amazingly, it still works in Debian due to IOhannes' work (I cannot compile the original sources). What does it mean for the future of the object that the external doesn't have an upstream maintainer?
Before those issues arose, the streams have been running for years with minimal maintenance effort. That really speaks for Pd's quality and careful development practices. I can't quite figure out what changed in the system. I upgraded the server to Debian bookworm last year, but experience the issues only since a few weeks.
This is with:
- Debian bookworm (amd64)
- Pd-0.55.1 from bookworm-backports
- pd-readanysf 0.43-5 from bookworm
Thanks, Roman