a pi4 shouldn't make any kind of performance problem for audio streaming... should be solved for a decade, but just for fun, what does dpkg --print-architecture say? the answer should be armhf...
for debugging, you could run darkice from the command line, in a screen (survives logout from the shell), with high verbosity 1-10, redirect output into a logfile, eg.
screen sudo darkice -v5 -c your.config.file > /tmp/darkice.log 2>&1
when these buffer overruns occur, something should be in the logs. If not, increase log levels. bests, u
civyiukkliu@thelab.blue:
thanks Udo for your help.
i'm using a Pi 4.
it's very curious but right now, at 345a, after a fresh pi boot, i'm not experiencing the problem; no silence every 34 seconds. i'm also not seeing any buffer overruns in the log, but at least for me, the log report doesn't seem to be real-time so may see reports of overruns later.
it's hard to imagine that rebooting the pi was the solution because i've done that of course many times hoping that might resolve things (somehow). but it's also hard to believe the solution was to do with the time of morning because i'm frequently working on things at like 4a when demands on my time are fewer :) (and fewer people are using the internet).
i'm happy if the problem just somehow resolved itself but we'll see!
any other thoughts about what might have caused / is causing this given the above?
-R
Aug 9, 2023, 03:28 by un@aporee.org:
hi Robert, silence on the stream can be network congestion or something in that chain. But buffer overruns on the encoder/pi side feels a bit like CPU/load related. On various pi zero I've seen buffer overruns when accessing the soundcard from more than one source at the same time, eg. darkice and arecord. which raspi is it? Udo
civyiukkliu@thelab.blue:
Hi all,
Does anyone have ideas re: how to fix a stream that goes silent (for about 4 seconds) every 34-35 seconds? I'm using a raspberry pi stream box. This problem is relatively new; it didn't seem to happen, what, a month or so ago (?) and I've not changed anything.
Thanks much,
Robert
Open Mic mailing list -- openmic@lists.locusonus.org To unsubscribe send an email to openmic-leave@lists.locusonus.org
Open Mic mailing list -- openmic@lists.locusonus.org To unsubscribe send an email to openmic-leave@lists.locusonus.org
does anyone know how to determine one's "Streambox login"?
for some reason when i set up my box (pi 4), i don't think i made a note of that login name and it doesn't appear to be the same as my login at Locus Stream.
when i try to type the suggested command below into the box, i get prompted for my Streambox login and password.
thanks!
-R
Aug 9, 2023, 06:11 by un@aporee.org:
a pi4 shouldn't make any kind of performance problem for audio streaming... should be solved for a decade, but just for fun, what does dpkg --print-architecture say? the answer should be armhf...
for debugging, you could run darkice from the command line, in a screen (survives logout from the shell), with high verbosity 1-10, redirect output into a logfile, eg.
screen sudo darkice -v5 -c your.config.file > /tmp/darkice.log 2>&1
when these buffer overruns occur, something should be in the logs. If not, increase log levels. bests, u
civyiukkliu@thelab.blue:
thanks Udo for your help.
i'm using a Pi 4.
it's very curious but right now, at 345a, after a fresh pi boot, i'm not experiencing the problem; no silence every 34 seconds. i'm also not seeing any buffer overruns in the log, but at least for me, the log report doesn't seem to be real-time so may see reports of overruns later.
it's hard to imagine that rebooting the pi was the solution because i've done that of course many times hoping that might resolve things (somehow). but it's also hard to believe the solution was to do with the time of morning because i'm frequently working on things at like 4a when demands on my time are fewer :) (and fewer people are using the internet).
i'm happy if the problem just somehow resolved itself but we'll see!
any other thoughts about what might have caused / is causing this given the above?
-R
Aug 9, 2023, 03:28 by un@aporee.org:
hi Robert, silence on the stream can be network congestion or something in that chain. But buffer overruns on the encoder/pi side feels a bit like CPU/load related. On various pi zero I've seen buffer overruns when accessing the soundcard from more than one source at the same time, eg. darkice and arecord. which raspi is it? Udo
civyiukkliu@thelab.blue:
Hi all,
Does anyone have ideas re: how to fix a stream that goes silent (for about 4 seconds) every 34-35 seconds? I'm using a raspberry pi stream box. This problem is relatively new; it didn't seem to happen, what, a month or so ago (?) and I've not changed anything.
Thanks much,
Robert
Open Mic mailing list -- openmic@lists.locusonus.org To unsubscribe send an email to openmic-leave@lists.locusonus.org
Open Mic mailing list -- openmic@lists.locusonus.org To unsubscribe send an email to openmic-leave@lists.locusonus.org
Open Mic mailing list -- openmic@lists.locusonus.org To unsubscribe send an email to openmic-leave@lists.locusonus.org
Im forever forgetting my pi password’s. This may be of use.
https://rpisounds.wordpress.com/2022/06/12/i-forgot-my-password/
On Thu, 10 Aug 2023 at 14:41, civyiukkliu@thelab.blue wrote:
does anyone know how to determine one's "Streambox login"?
for some reason when i set up my box (pi 4), i don't think i made a note of that login name and it doesn't appear to be the same as my login at Locus Stream.
when i try to type the suggested command below into the box, i get prompted for my Streambox login and password.
thanks!
-R
Aug 9, 2023, 06:11 by un@aporee.org:
a pi4 shouldn't make any kind of performance problem for audio streaming... should be solved for a decade, but just for fun, what does dpkg --print-architecture say? the answer should be armhf...
for debugging, you could run darkice from the command line, in a screen (survives logout from the shell), with high verbosity 1-10, redirect output into a logfile, eg.
screen sudo darkice -v5 -c your.config.file > /tmp/darkice.log 2>&1
when these buffer overruns occur, something should be in the logs. If not, increase log levels. bests, u
civyiukkliu@thelab.blue:
thanks Udo for your help.
i'm using a Pi 4.
it's very curious but right now, at 345a, after a fresh pi boot, i'm not experiencing the problem; no silence every 34 seconds. i'm also not seeing any buffer overruns in the log, but at least for me, the log report doesn't seem to be real-time so may see reports of overruns later.
it's hard to imagine that rebooting the pi was the solution because i've done that of course many times hoping that might resolve things (somehow). but it's also hard to believe the solution was to do with the time of morning because i'm frequently working on things at like 4a when demands on my time are fewer :) (and fewer people are using the internet).
i'm happy if the problem just somehow resolved itself but we'll see!
any other thoughts about what might have caused / is causing this given the above?
-R
Aug 9, 2023, 03:28 by un@aporee.org:
hi Robert, silence on the stream can be network congestion or something in that
chain.
But buffer overruns on the encoder/pi side feels a bit like CPU/load
related.
On various pi zero I've seen buffer overruns when accessing the
soundcard from
more than one source at the same time, eg. darkice and arecord. which raspi is it? Udo
civyiukkliu@thelab.blue:
Hi all,
Does anyone have ideas re: how to fix a stream that goes silent (for
about 4 seconds) every 34-35 seconds? I'm using a raspberry pi stream box. This problem is relatively new; it didn't seem to happen, what, a month or so ago (?) and I've not changed anything.
Thanks much,
Robert
Open Mic mailing list -- openmic@lists.locusonus.org To unsubscribe send an email to openmic-leave@lists.locusonus.org
Open Mic mailing list -- openmic@lists.locusonus.org To unsubscribe send an email to openmic-leave@lists.locusonus.org
Open Mic mailing list -- openmic@lists.locusonus.org To unsubscribe send an email to openmic-leave@lists.locusonus.org
Open Mic mailing list -- openmic@lists.locusonus.org To unsubscribe send an email to openmic-leave@lists.locusonus.org
thanks so much! i'll give it a try. -R
Aug 10, 2023, 11:14 by diarmuiddrew@gmail.com:
Im forever forgetting my pi password’s. This may be of use.
https://rpisounds.wordpress.com/2022/06/12/i-forgot-my-password/
On Thu, 10 Aug 2023 at 14:41, civyiukkliu@thelab.blue wrote:
does anyone know how to determine one's "Streambox login"?
for some reason when i set up my box (pi 4), i don't think i made a note of that login name and it doesn't appear to be the same as my login at Locus Stream.
when i try to type the suggested command below into the box, i get prompted for my Streambox login and password.
thanks!
-R
Aug 9, 2023, 06:11 by >> un@aporee.org>> :
a pi4 shouldn't make any kind of performance problem for audio streaming... should be solved for a decade, but just for fun, what does dpkg --print-architecture say? the answer should be armhf...
for debugging, you could run darkice from the command line, in a screen (survives logout from the shell), with high verbosity 1-10, redirect output into a logfile, eg.
screen sudo darkice -v5 -c your.config.file > /tmp/darkice.log 2>&1
when these buffer overruns occur, something should be in the logs. If not, increase log levels. bests, u
civyiukkliu@thelab.blue:
thanks Udo for your help.
i'm using a Pi 4.
it's very curious but right now, at 345a, after a fresh pi boot, i'm not experiencing the problem; no silence every 34 seconds. i'm also not seeing any buffer overruns in the log, but at least for me, the log report doesn't seem to be real-time so may see reports of overruns later.
it's hard to imagine that rebooting the pi was the solution because i've done that of course many times hoping that might resolve things (somehow). but it's also hard to believe the solution was to do with the time of morning because i'm frequently working on things at like 4a when demands on my time are fewer :) (and fewer people are using the internet).
i'm happy if the problem just somehow resolved itself but we'll see!
any other thoughts about what might have caused / is causing this given the above?
-R
Aug 9, 2023, 03:28 by >>>> un@aporee.org>>>> :
hi Robert, silence on the stream can be network congestion or something in that chain. But buffer overruns on the encoder/pi side feels a bit like CPU/load related. On various pi zero I've seen buffer overruns when accessing the soundcard from more than one source at the same time, eg. darkice and arecord. which raspi is it? Udo
civyiukkliu@thelab.blue:
Hi all,
Does anyone have ideas re: how to fix a stream that goes silent (for about 4 seconds) every 34-35 seconds? I'm using a raspberry pi stream box. This problem is relatively new; it didn't seem to happen, what, a month or so ago (?) and I've not changed anything.
Thanks much,
Robert
Open Mic mailing list -- >>>> openmic@lists.locusonus.org To unsubscribe send an email to >>>> openmic-leave@lists.locusonus.org
Open Mic mailing list -- >>>> openmic@lists.locusonus.org To unsubscribe send an email to >>>> openmic-leave@lists.locusonus.org
Open Mic mailing list -- >>> openmic@lists.locusonus.org To unsubscribe send an email to >>> openmic-leave@lists.locusonus.org
Open Mic mailing list -- >> openmic@lists.locusonus.org To unsubscribe send an email to >> openmic-leave@lists.locusonus.org
-
civyiukkliu＠thelab.blue -
Diarmuid Drew -
unosonic