buffer size problems
Brought to you by:
phintuka
Menu
▾
▴
#73 buffer size problems
I'm using latest git version xineliboutput and latest version of VDR, I have VDR backend and I stream to another box through wireless TCP, (I'm not aware why but it works better than UDP).
after the increase of buffer size to 2048 i have problems with dragging, I have also tried 1024 but after a while the dragging appears again.
Since I'm using the latest version I guess the buffer size should not be linked to the VDR version. Maybe it is better if it is configurable.
Also the code would not work as expected if you are not building inside VDR tree
I have investigated a bit more, and it seems that the increase of the buffer did not create my problems but changes in changeset df90d550cdf13d838e4e2d9c6946e152b987cebe
"Improved discontinuity handling"
previous than this commit I do not have dragging on my frontend. I also forgot to mention that I use VDPAU
Larger bufers can't be used with vdr 1.6.0 because of the way it handles trick speeds, still images and seeking.
Should be fixed in CVS.
> Also the code would not work as expected if you are not building inside VDR tree
Why?
VDR version must always be known at compile time (it is in vdr headers). It is used in several places where VDR API has been changed between versions. Compiling for different vdr versions would be impossible without knowing the version.