On Thu, Aug 20, 2009 at 08:31:43AM +1000, Torgeir Veimo wrote:
> In my experience, you just have to do deinterlacing in vdpau with
> interlaced content, even when displaying on an interlaced display. If
> you try to output interlaced material directly, you get ghosting since
> the weaved frames are
> the main reason why nvidia chooses to deinterlace always even if you use an
> interlaced video timing is not the scaling problem you mention. This could
> be eventually solved (albeit not perfectly) by scaling both fields
> independently.
>
> The main reason is: even with VDPAU there still exis
Is it AMD (ATI) have the same problem?
Vladimir
On Sat, 2009-08-22 at 13:12 +0400, Goga777 wrote:
> > the main reason why nvidia chooses to deinterlace always even if you
> > use an interlaced video timing is not the scaling problem you
> > mention. This could be eventually solved (albeit not pe
On Sat, Aug 22, 2009 at 01:12:43PM +0400, Goga777 wrote:
> is it possible to solve radically this problem with vdpau ? did you discuss
> with nvidia developpers about this
> issue ?
I don't know if nvidia hardware is capable of such things at all.
This issue (among others) once has been discuss
hi
I tried to use the gotox patch (thanks to Seppo Ingalsuo and Ales Jurik) for
vdr 178
http://www.linuxtv.org/pipermail/vdr/2009-June/020800.html
I have this scheme vdr with hvr4000 card ---> rotor >> 4x1 diseqc switch
---> LNB Ku band Linear + LNB Ku
band Circular + LNB С band Circular
Приветствую, Vladimir
> Is it AMD (ATI) have the same problem?
yes.
but for ati and intel there's solution from Thomas - see
http://www.forum.free-x.de/wbb/index.php?page=Thread&postID=2576#post2576
http://lowbyte.de/vga-sync-fields/vga-sync-fields/
Goga
__
2009/8/22 Thomas Hilber :
> On Thu, Aug 20, 2009 at 08:31:43AM +1000, Torgeir Veimo wrote:
>> In my experience, you just have to do deinterlacing in vdpau with
>> interlaced content, even when displaying on an interlaced display. If
>> you try to output interlaced material directly, you get ghostin
On Sat, 2009-08-22 at 13:54 +0400, Goga777 wrote:
> I have this scheme vdr with hvr4000 card ---> rotor >> 4x1 diseqc
> switch ---> LNB Ku band Linear + LNB Ku
> band Circular + LNB С band Circular
>
> my diseqc.conf (for Ku circular) is
>
> S36.0E 0 V 10750 t v [E0 10 38 F4] W150
Hi,
Are there cleaner or later patches somewhere for vdr (1.7.8) for xmbc?
The patch vdr-1.7.4-ext68-streamdev.patch from ticket
http://xbmc.org/trac/ticket/5595
could be applied but there could be some extra that I don't need from
some VDR extensions patch.
I'm also wondering if streamdev cvs i
On 22.08.2009 00:51, Simon Baxter wrote:
> Hi
>
> I use xmltv2vdr to process .xml EPG listings and populate VDR.
>
> VDR seems to be processing the EPG (via SVDRP) into and across two
> channels. There's no error in the xmltv2vdr - seems to be a VDR problem.
>
> Example:
> here's a snippet from
> > I have this scheme vdr with hvr4000 card ---> rotor >> 4x1 diseqc
> > switch ---> LNB Ku band Linear + LNB Ku
> > band Circular + LNB С band Circular
> >
> > my diseqc.conf (for Ku circular) is
> >
> > S36.0E 0 V 10750 t v [E0 10 38 F4] W150 G v t
> > S36.0E 9 V 10750 t v [E
On Sat, 2009-08-22 at 17:45 +0400, Goga777 wrote:
>
> honestly - I don't know because the dish is on the roof of my home - I don't
> have access to it currently
OK, that makes debugging more complicated.
> have you ideas about how can I see in the log the disecs commands from vdr to
> dish ?
On Saturday 22 of August 2009, Goga777 wrote:
>
> have you ideas about how can I see in the log the disecs commands from vdr
> to dish ?
>
You can add dsyslog command to each point in dvbdevice.c where this ioctl with
FE_DISEQC_SEND_MASTER_CMD is called (3 times) and print out the cmd buffer.
Be
My log files get so big it,s very hard to check them because of the ts error
messages that get flooded to it. I've had logs near 2gb
in size. I have a problem with xine crashing when there is a weak signal and
the ts loging bloating the log files is creating a lot
of problems. Need a way to turn
On Sat, Aug 22, 2009 at 10:12 AM, Timothy D. Lenz wrote:
> My log files get so big it,s very hard to check them because of the ts error
> messages that get flooded to it. I've had logs near 2gb
> in size. I have a problem with xine crashing when there is a weak signal and
> the ts loging bloating
> > honestly - I don't know because the dish is on the roof of my home - I
> > don't have access to it currently
>
> OK, that makes debugging more complicated.
I connected the ampermeter for measure the current in dish cable and found out
that no any problem with software - when I
are moving b
On Sat, 2009-08-22 at 14:31 +0300, Seppo Ingalsuo wrote:
> recording.h:66: error: ‘const cEvent* cRecordingInfo::GetEvent() const’
> cannot be overloaded
> recording.h:63: error: with ‘const cEvent* cRecordingInfo::GetEvent()
> const’
> make: *** [channels.o] Error 1
The duplicate due to patching
On 22.08.2009 00:51, Simon Baxter wrote:
Hi
I use xmltv2vdr to process .xml EPG listings and populate VDR.
VDR seems to be processing the EPG (via SVDRP) into and across two
channels. There's no error in the xmltv2vdr - seems to be a VDR problem.
Example:
here's a snippet from "./xmltv2vdr.pl
On 22.08.2009 23:03, Simon Baxter wrote:
>> On 22.08.2009 00:51, Simon Baxter wrote:
>>> Hi
>>>
>>> I use xmltv2vdr to process .xml EPG listings and populate VDR.
>>>
>>> VDR seems to be processing the EPG (via SVDRP) into and across two
>>> channels. There's no error in the xmltv2vdr - seems to be
19 matches
Mail list logo
