VDR User wrote:
...
> Logic still says that if mplayer can play vdr recordings just fine
> without losing sync, but vdr can't, the problem is with vdr, not the
> firmware.
That's only correct if you ignore specifications.
Maybe VDR is behaving according to the specified interface
and the firmware
Frank Schmirler wrote:
Although it's very unlikely that the server is filtering outbound connections,
you should also take a look at the server's iptables configuration. But AFAIK
the connect call on the server would rather return with an "operation not
permitted" instead of hanging forever.
Petri Helin <[EMAIL PROTECTED]> wrote:
> Now there are some problems that have come up with the HD OSD. Font
> rendering and the way fonts and OSD are used by plugins are the main
> distractions. I bumped in to this Utf8-patch
> (http://www.vdr-wiki.de/wiki/index.php/Utf8-patch) which looks
Has so
Am Donnerstag, 30. November 2006 15:52 schrieb Harald Milz:
> Has somebody got a pointer to where the actual patch is located,
> especially v0.1.2 (I'm running vdr-1.4.1)? The link to the homepage at
> free-x.de seems to be gone, and http://www.free-x.de/vdr/ contains a lot
> of stuff except this p
You make things sound promising again, thanks for the reply! And of course
I agree with your points fully. At any rate the issue still remains and has
once again seemed to be left unresolved.
A question for Oliver Endriss (if you read this).. Can you confirm that the
firmware abides fully to s
Hello to all UTF-8 user and naturally to others 8 and 7bit user also. ;-)
Please look at http://www.free-x.de/utf8/
The last version of utf8 patch is for vdr 1.4.3 the next version for 1.4.4 will
be soon there.
P.S.
Would be also interesting to know whether someone Antialiasing uses, otherwi
VDR User wrote:
> Can you confirm that the firmware abides fully to specification?
I'm pretty sure that it doesn't. Neither do mplayer, vdr and the DVB
driver. All complex programs have bugs... ;-)
CU
Oliver
--
VDR Remote Plugin 0.3.8 ava
Carsten Koch wrote:
> Maybe VDR is behaving according to the specified interface
> and the firmware fails.
> Maybe mplayer is working around firmware bugs by behaving
> differently - which may or may not be according to the
> specified interface.
>
> What we can agree upon is the fact that the pro
