Bug report--Crashing
Tzvi Merczynski-Hait <[email protected]>
| Newsgroups | gmane.comp.audio.mp3.lame |
|---|---|
| Message-ID | <[email protected]> |
When running lame with the input being a pipe from arecord, and piping the output to ezstream (http://icecast.org/ezstream/) after a few hours the LAME process dissapears (dies). For example, arecord -f dat -c 1 | /usr/bin/lame -r -s 48 --resample 22.05 -m m -b 16 --cbr --lowpass 4 - - | /usr/bin/ezstream -c /etc/ezstream_bcfy.xml > var/log/bcfy.log 2>&1 & Runs fine, until some point where it stops working, (presumably) because Lame has stopped running, while the other 2 commands continue, with ezstream running with high CPU (links below suggest because waiting for input from LAME). A temporary fix is to frequently check whether LAME is running, and if it quit restart the above commands, but that's not a permanent solution. This person had the same issue, and reccomended the fix--http://ohnosec.org/pipermail/app_rpt-users/2016-May/014103.html as well as here http://wiki.radioreference.com/index.php/Raspberry_Pi_RTL-SDR_Broadcastify#Verify_System_is_running_and_connected <http://wiki.radioreference.com/index.php/Raspberry_Pi_RTL-SDR_Broadcastify#Verify_System_is_running_and_connected> Running LAME 32bits version 3.99.5, on Ubuntu 16.04 Linux kernel 4.4.0-65-generic I created this on sourceforge too—not sure what’s most updated contact method. Tzvi Merczynski-Hait ------------------------------------------------------------------------------ Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford _______________________________________________ Lame-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lame-dev