mbg wrote: 
> Thanks - the log I attached previously was from before I put your
> updated PM file in place. I've attached another log from after
> installing it, again covering a period that had two rebuffering
> attempts.

The new log is much better - it gets rid of the "noise" but shows up a
few different instances of odd behaviour.  Trying to figure out which
one is significant.

At a few places LMS is trying to write data to the transcode chain of
processes but cannot and this soak up LMS processing - this usually
because the player's buffer is full and cannot take any more data from
transcoders but the looping can stop LMS processing other comms.


Code:
--------------------
    
  15-12-22 08:47:18.4063] Slim::Player::Pipeline::sysread (304) Attempting to 
write to pipeline writer
  [15-12-22 08:47:18.4069] Slim::Player::Pipeline::sysread (304) Attempting to 
write to pipeline writer
  [15-12-22 08:47:18.4211] Slim::Player::Pipeline::sysread (304) Attempting to 
write to pipeline writer
  [15-12-22 08:47:18.4340] Slim::Player::Pipeline::sysread (304) Attempting to 
write to pipeline writer
  [15-12-22 08:47:18.4343] Slim::Player::Pipeline::sysread (310) Wrote 12346 
bytes to pipeline writer
  
--------------------


Shortly afterward player often runs out of data and so get rebuffering. 

How is the player connected to LMS wired or wireless ?


------------------------------------------------------------------------
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread: http://forums.slimdevices.com/showthread.php?t=104672

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to