Black Hole
May contain traces of nut
Update: This problem is now cured by a new firmware release. See HERE (click).
As you may know I am using the standard built-in DLNA server to stream to an HD-FOX. A couple of times I have experienced cut-offs before the end of a HiDef streamed play-back - of course one of the key values of the HD-FOX is its ability to stream HiDef direct from the HDR-FOX without any of our interventions.
I have not rigorously tested it, but the pattern that is emerging is there is a 4GB limit on the accessibility of the data. Would this be a limitation of the DLNA protocol, and if not is it an implementation bug in the server or the client?
I'm not expecting anybody to be able to answer these off the cuff, it is the aim of this topic to "seek the truth".
As you may know I am using the standard built-in DLNA server to stream to an HD-FOX. A couple of times I have experienced cut-offs before the end of a HiDef streamed play-back - of course one of the key values of the HD-FOX is its ability to stream HiDef direct from the HDR-FOX without any of our interventions.
I have not rigorously tested it, but the pattern that is emerging is there is a 4GB limit on the accessibility of the data. Would this be a limitation of the DLNA protocol, and if not is it an implementation bug in the server or the client?
I'm not expecting anybody to be able to answer these off the cuff, it is the aim of this topic to "seek the truth".