philippe_44 wrote: > Yes, as said, check that your friend has not set pacing_size at more > than 1M and if it's still 1M, reduce it to 500k. > > [edit]: this pacing_size parameters tells the plugin to stop gathering > data from the source if the player has not accept the latest N amount of > bytes. It's not exactly the same than the buffer_size because it governs > how far ahead the bridge can be from the CC. > > There is really two buffering levels happening here. CC can be greedy > himself and tell the plugin "give me more" while, on top of that, the > plugin will eat all can from the source till buffer_size is met. Setting > pacing_size might not fully solve the problem in a sense that if CC eats > a lot of data when starting, then there will still be a large amount of > data buffered in (CC buffer + pacing_size) at the beginning then a long > silence before CC starts to ask for more. You can set the pacing_size > value to a super small value, it should still work. > > Doing something different would mean starving the CC and guessing what > has been exactly consumed and I don't want to do that (lots of > timer-based programming and I always feel its wrong)
Thanks Touch, Logitech Radio, Logitech UE Radio, O2 Joggler + SqpOS UPnPBridge - 2 paired Sonos Play1 speakers; Rocki - Sony SRS-BTM8 speaker; Pioneer WX-SMA1 speaker; - PURE One Flow internet radio: PURE Jongo S3x ; Jongo T2; Libratone Zipp Castbridge - Chromecast 1 + Chromecast Audio AirplayBridge - Loewe Airspeaker SB Player - Fire TV ------------------------------------------------------------------------------------ ------------------------------------------------------------------------ castalla's Profile: http://forums.slimdevices.com/member.php?userid=15624 View this thread: http://forums.slimdevices.com/showthread.php?t=104672 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
