Hey Bill, Well, I sit here looking at the code and I just don't know exactly what that message means - and more specifically what changes when it encounters this situation. But again, as I said we see this all the time, and none of our carts skip. Let me be more clear (my earlier estimate was a bit off). We run 4 simultaneous servers here at RFA, 24/7. Each server has these messages - 997,1190,624,1632 times respectively (this last log number is since Jul 4th). Some days there are literally hundreds of carts playing out. Not a single one has skipped.
So, yes the message would tend to make you wonder what it means (I know I always have wanted to know why this happens). I guess Fred could shed some light on what happens when you see that. But, I don't think it's the smoking gun. A script might be a good idea to see which carts create the message(s)... Here is something I tried - just for giggles.... My operating system keeps messages in the directory /var/log/messages A quick one liner gives me the list of all carts... and I actually sort them so duplicates are really obvious... I type at the command line: cat /var/log/messages | grep "position out of bounds on signal" | cut -f7 -d: | cut -f2 -d" " | sort This gave me a list of all cart numbers, in order... So maybe you can detect if there is a pattern in your environment. Not sure what else to do here, but yeah, if putting the same cart back into the log and it plays fine then markers is NOT the problem. Sorry I can't help more. Todd -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bill Putney Sent: Friday, August 26, 2011 10:31 AM To: User discussion about the Rivendell Radio Automation System Subject: Re: [RDD] Debugging log? Or "position out of bounds"? Todd, Sometimes we find a cart that always (we think) makes this happen. Sometimes it seems that it's the cart that precedes the one that skips is causing the problem. If someone is standing there and catches it happen, they can always add the cart that skipped back into the running log and it will play. I've never quite convinced myself it was related to a specific cart. If it was misplaced start/end markers it would seem like if you added it back in to the log it would not play again. The fact that the "position out of bounds" warnings stop after it skips a cart makes me think that there is some pointer that is fouled up and gets overflowed (or underflowed) when a big cart comes along and that takes care of things for a while. But I'm not sure of that either. Does anyone know what "position out of bounds" means? Seems like it was a big enough issue for someone to give it some error handling or at lease it's own warning message. I guess it might be interesting to go write a script that hunts through the syslog and looks to see if there is a specific cart or event that starts the "position out of bounds" messages in the first place. Bill Putney - KPTZ Port Townsend, WA On 8/26/11 4:56 AM, Todd Baker wrote: > Dear Bill, > > Hmm..very strange. I am not sure what is going on there. It is always > the same cart ? > > The out of bounds errors happen here all the time - well - 977 times > since Aug 11th, but it doesn't cause us to skip carts (we are using a > older version though ...) > > If it is always the same cart(s), I would look at those for end marker - > start markers , etc. if it's random I really don't get it... > > Todd Baker > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Bill Putney > Sent: Friday, August 26, 2011 1:57 AM > To: User discussion about the Rivendell Radio Automation System > Subject: Re: [RDD] Debugging log? Or "position out of bounds"? > > At 17:03:50 in the following /var/log/syslog excerpt, Cart 80145 Cut 2 > should have played. It is an hour long program. It skipped and did not > play. . I don't know what "position out of bounds" means but it seems > that everything is playing out of bounds. The items before and after the > > cart that failed played normally. I see that the cart that started after > > (cart 80133) did not have a position out of bounds associated with it. > Has anyone got an idea what that is or what I can do to get rid of it? > > Any ideas? Anybody? Please! > > Thanks, Bill Putney - KPTZ Port Townsend, WA > > Aug 24 17:00:11 auto-mc rdairplay: *** position out of bounds on signal: > > Line: 24 Cart: 14418 Pos: 250025 *** > Aug 24 17:00:11 auto-mc caed: alsaStopTimerData(16) > Aug 24 17:00:11 auto-mc rdairplay: finished event: Line: 24 Cart: > 14418 Cut: 1 Card: 1 Stream: 0 Port: 0 > Aug 24 17:00:11 auto-mc caed: UnloadPlayback - Card: 1 Stream: 0 > Handle: 166 > Aug 24 17:00:11 auto-mc caed: LoadPlayback Card: 1 Stream: 0 Name: > /var/snd/045103_001.wav Handle: 167 > Aug 24 17:00:11 auto-mc rdairplay: started audio cart: Line: 25 Cart: > 45103 Cut: 1 Pos: 0 Card: 1 Stream: 0 Port: 0 > Aug 24 17:00:11 auto-mc caed: PlaybackPosition - Card: 1 Stream: 0 > Pos: 78 Handle: 167 > Aug 24 17:00:11 auto-mc caed: Play - Card: 1 Stream: 0 Handle: 167 > Length: 7863 Speed: 100000 Pitch: 0 > Aug 24 17:00:12 auto-mc caed: FadeLevel: 0 > Aug 24 17:00:19 auto-mc rdairplay: *** position out of bounds on signal: > > Line: 25 Cart: 45103 Pos: 7801 *** > Aug 24 17:00:19 auto-mc caed: alsaStopTimerData(16) > Aug 24 17:00:19 auto-mc rdairplay: finished event: Line: 25 Cart: > 45103 Cut: 1 Card: 1 Stream: 0 Port: 0 > Aug 24 17:00:19 auto-mc caed: UnloadPlayback - Card: 1 Stream: 0 > Handle: 167 > Aug 24 17:00:19 auto-mc caed: LoadPlayback Card: 1 Stream: 0 Name: > /var/snd/070003_001.wav Handle: 168 > Aug 24 17:00:19 auto-mc rdairplay: started audio cart: Line: 26 Cart: > 70003 Cut: 1 Pos: 0 Card: 1 Stream: 0 Port: 0 > Aug 24 17:00:19 auto-mc caed: PlaybackPosition - Card: 1 Stream: 0 > Pos: 0 Handle: 168 > Aug 24 17:00:19 auto-mc caed: Play - Card: 1 Stream: 0 Handle: 168 > Length: 210372 Speed: 100000 Pitch: 0 > Aug 24 17:00:20 auto-mc caed: FadeLevel: 0 > Aug 24 17:03:50 auto-mc rdairplay: *** position out of bounds on signal: > > Line: 26 Cart: 70003 Pos: 210278 *** > Aug 24 17:03:50 auto-mc caed: UnloadPlayback - Card: 1 Stream: 0 > Handle: 168 > Aug 24 17:03:50 auto-mc rdairplay: finished event: Line: 26 Cart: > 70003 Cut: 1 Card: 1 Stream: 0 Port: 0 > Aug 24 17:03:50 auto-mc caed: LoadPlayback Card: 1 Stream: 0 Name: > /var/snd/080145_002.wav Handle: 169 > Aug 24 17:03:50 auto-mc caed: alsaStopTimerData(16) > Aug 24 17:03:50 auto-mc rdairplay: started audio cart: Line: 27 Cart: > 80145 Cut: 2 Pos: 0 Card: 1 Stream: 0 Port: 0 > Aug 24 17:03:50 auto-mc rdairplay: finished event: Line: 27 Cart: > 80145 Cut: 2 Card: 1 Stream: 0 Port: 0 > Aug 24 17:03:50 auto-mc caed: PlaybackPosition - Card: 1 Stream: 0 > Pos: 0 Handle: 169 > Aug 24 17:03:50 auto-mc caed: Play - Card: 1 Stream: 0 Handle: 169 > Length: 3594892 Speed: 100000 Pitch: 0 > Aug 24 17:03:50 auto-mc caed: UnloadPlayback - Card: 1 Stream: 0 > Handle: 169 > Aug 24 17:03:50 auto-mc caed: LoadPlayback Card: 1 Stream: 0 Name: > /var/snd/080133_001.wav Handle: 170 > Aug 24 17:03:50 auto-mc caed: FadeLevel: 0 > Aug 24 17:03:50 auto-mc rdairplay: started audio cart: Line: 28 Cart: > 80133 Cut: 1 Pos: 0 Card: 1 Stream: 0 Port: 0 > Aug 24 17:03:50 auto-mc caed: PlaybackPosition - Card: 1 Stream: 0 > Pos: 0 Handle: 170 > Aug 24 17:03:50 auto-mc caed: Play - Card: 1 Stream: 0 Handle: 170 > Length: 1740094 Speed: 100000 Pitch: 0 > Aug 24 17:03:50 auto-mc caed: FadeLevel: 0 > Aug 24 17:04:00 auto-mc caed: ****** ALSA Capture Xrun - Card: 0 ****** > On 8/24/11 8:04 PM, James Harrison wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Check rd.conf for your own system specific logging configuration, but >> check both the daemons and syslog logfiles; alternatively, configure a >> specific log path or syslog logfile/service. Not sure if automation >> decisions are logged there, but playout system stuff certainly gets >> logged to those locations from caed... >> >> Cheers, >> James Harrison >> >> >> On 25/08/2011 02:49, Bill Putney wrote: >>> This is driving us crazy! At least once a day, a cart that is > scheduled >>> to play (usually a long one like a prerecorded show) is skipped in > the >>> middle of a log. >>> >>> I can't figure out why this happens but I know somewhere there has > got >>> to be a system log file (like syslog or something) that should tell > me >>> everything the automation system is doing and I should be able to see >>> the skip happen. >>> >>> We're using RRAbuntu 1.7.2... >>> >>> Help! >>> >>> Thanks, >>> >>> Bill Putney - KPTZ Port Townsend, WA >>> _______________________________________________ >>> Rivendell-dev mailing list >>> [email protected] >>> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.9 (MingW32) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >> >> iEYEARECAAYFAk5Vu9YACgkQmJV2s0zjsDgKfACdF1W8W/2O4K3X/YPWlu9L97WY >> d/EAnAjIMV5eprpuHmorOECFzaEyTyEp >> =mo9i >> -----END PGP SIGNATURE----- >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
