Hello Folks: Every now and then my ogg123 quits while loistening to the stream. It isn't a bandwidth problem because my ogg123 is on a machine which is just a few feet from the server and is in fact on the same machine with ices2 doing the streaming. It happened this morning and I decided to take a look at the log and found some curious messages and thought maybe I'd post them here and see if you Mike or someone else had an idea what causes these messages. I will include below a portion of the log for the entry which seems to have caused the entries. Kirk [2001-12-07 08:08:52] DBUG encode/encode_clear Clearing encoder engine [2001-12-07 08:08:52] DBUG reencode/reencode_page Reinitialising reencoder for new logical stream [2001-12-07 08:08:52] INFO encode/encode_initialise Encoder initialising at 2 channels, 44100 Hz, bitrate 64000 [2001-12-07 08:10:44] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:10:46] INFO playlist-builtin/playlist_read Currently playing /var/music/Larry_Pattis/Random_Chance/12-Track_12.ogg [2001-12-07 08:10:46] DBUG encode/encode_clear Clearing encoder engine [2001-12-07 08:10:46] DBUG reencode/reencode_page Reinitialising reencoder for new logical stream [2001-12-07 08:10:46] INFO encode/encode_initialise Encoder initialising at 2 channels, 44100 Hz, bitrate 64000 [2001-12-07 08:10:46] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (88640) [2001-12-07 08:10:46] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:10:51] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:10:52] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:10:52] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:10:57] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:10:58] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:10:58] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:11:03] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:11:04] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:11:04] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:11:09] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:11:10] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (89088) [2001-12-07 08:11:13] DBUG encode/encode_dataout Forcing flush: Too many samples in current page (88832) --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Kirk Reiser <kirk@braille.uwo.ca> said:> Hello Folks: Every now and then my ogg123 quits while loistening to > the stream. It isn't a bandwidth problem because my ogg123 is on a > machine which is just a few feet from the server and is in fact on the > same machine with ices2 doing the streaming. It happened this morning > and I decided to take a look at the log and found some curious > messages and thought maybe I'd post them here and see if you Mike or > someone else had an idea what causes these messages. I will include > below a portion of the log for the entry which seems to have caused > the entries.This will typically happen when the input file has a longish section of digital silence - there's code to prevent problems with clients that occur due to buffers running out because of the very low bitrate you get when this happens, which is being triggered here. It shouldn't be a problem - but it's not that well tested, so it might be being triggered incorrectly here, or this might be a symptom of a more severe problem. I don't have the source around to look at, so I can't really give any more specific advice. Michael --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> Hello Folks: Every now and then my ogg123 quits while loistening to > the stream. It isn't a bandwidth problem because my ogg123 is on a > machine which is just a few feet from the server and is in fact on the > same machine with ices2 doing the streaming. It happened this morning > and I decided to take a look at the log and found some curious > messages and thought maybe I'd post them here and see if you Mike or > someone else had an idea what causes these messages. I will include > below a portion of the log for the entry which seems to have caused > the entries.That does look curious. Thank god for good logging :) Michael (the real ices2 maintainer) is travelling about the US right now, and probably won't be able to deal with these things for about 2 months. I'm the interim maintainer. Can you reproduce this with certain files always? Does it happen randomly? jack. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
Hi Jack: I have gone back through the log looking for those flush statements. It seems fairly common to have one flushing buffer statement for a piece of music. The pieces which generate the statement seem to be the same yet there is not a statement for each occurrence of the piece in the log. A lot of pieces tend to generate the statement. Very few pieces generate multiple statements as in the log extract I posted this morning. The statement seems to occur either at the end of a piece or the beginning of the next piece. It's hard to tell which. The pieces which tend to generate the statements are not from the same ripping/encoding program although I only use two programs for ripping/encoding. I guess that means that both packages generate files which cause these statements. As far as I can tell the pieces play fine although that also is hard to tell because I'm usually working and not listening intently to the stream. Kirk -- Kirk Reiser The Computer Braille Facility e-mail: kirk@braille.uwo.ca University of Western Ontario phone: (519) 661-3061 --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.