Re: [vdr] softdevice crash
Thanks for your reply. On Sat, 12 May 2007, Stefan Lucke wrote: That's only 16bit per pixel. Please try 32bpp. Done, same result Can you try to change the OSD drawing mode in setup.conf ? softdevice.OSDalphablend = 1 I tried, no success. Three more things: 1. I do not have any softdevice. starting line in my setup.conf (The one with OSDalphablend I added manually.) 2. I tried to start softdevice with -vo dummy: and I have the same output [softdevice] A/V devices initialized, now initializing MPEG2 Decoder Segmentation fault 3. When I start with -vo xv: I can see a black X window appearing for a fraction of a second. Now I'm also stuck with connecting my Mobo (asus M2NPV-VM) via DVI-HDMI to my TV set, but that's a different story. On RGB it works fine on 1360x768. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] softdevice crash
[EMAIL PROTECTED] schrieb: Thanks for your reply. On Sat, 12 May 2007, Stefan Lucke wrote: That's only 16bit per pixel. Please try 32bpp. Done, same result Can you try to change the OSD drawing mode in setup.conf ? softdevice.OSDalphablend = 1 I tried, no success. Three more things: 1. I do not have any softdevice. starting line in my setup.conf (The one with OSDalphablend I added manually.) 2. I tried to start softdevice with -vo dummy: and I have the same output [softdevice] A/V devices initialized, now initializing MPEG2 Decoder Segmentation fault 3. When I start with -vo xv: I can see a black X window appearing for a fraction of a second. I have the same crash. If I try -vo dummy: it does not crash anymore but then I get a message that my ffmpeg is miscompiled due to a compiler bug and may be slow or crash. I don't have the exact message at hand because VDR is in use just now (with a FF card). Maybe you can try and look if you get that message too. System here is SuSE 9.3, gcc --version shows gcc (GCC) 3.3.5 20050117 (prerelease) (SUSE Linux) Regards, Wolfgang Now I'm also stuck with connecting my Mobo (asus M2NPV-VM) via DVI-HDMI to my TV set, but that's a different story. On RGB it works fine on 1360x768. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] softdevice crash
Stefan Lucke schrieb: [Cut] Can you try to change the OSD drawing mode in setup.conf ? softdevice.OSDalphablend = 1 If that doesn't help, we need the gdb backtrace of the segfault. Meanwhile I got a precompiled ffmpeg version for SuSE 9.3 which does not show the erreor message in my other mail, but I still get the segfault. I tried with softdevice.OSDalphablend = 1 and without and get the same crash. Here is gdb output: Program received signal SIGILL, Illegal instruction. [Switching to Thread 1076229824 (LWP 10441)] 0x402d3b36 in cSoftOsd::AYUV_to_AYUV420P (PY1=0x40ecd008 , PY2=0x40ecd2e8 , PU=0x91363e0 '\177' repeats 200 times..., PV=0x911c5d0 '\177' repeats 200 times..., PAlphaY1=0x40f35008 , PAlphaY2=0x40f352e8 , PAlphaUV=0x91501f0 , pixmap1=0x4381f008, pixmap2=0x4381fb88, Pixel=720) at SoftOsd.c:601 Backtrace: (gdb) bt #0 0x402d3b36 in cSoftOsd::AYUV_to_AYUV420P (PY1=0x40ecd008 , PY2=0x40ecd2e8 , PU=0x91363e0 '\177' repeats 200 times..., PV=0x911c5d0 '\177' repeats 200 times..., PAlphaY1=0x40f35008 , PAlphaY2=0x40f352e8 , PAlphaUV=0x91501f0 , pixmap1=0x4381f008, pixmap2=0x4381fb88, Pixel=720) at SoftOsd.c:601 #1 0x402d489d in cSoftOsd::NoVScaleCopyToBitmap (this=0x91ac978, PY=0x40ecd008 , PU=0x91363e0 '\177' repeats 200 times..., PV=0x911c5d0 '\177' repeats 200 times..., PAlphaY=0x40f35008 , PAlphaUV=0x91501f0 , Ystride=736, UVstride=368, dest_Width=720, dest_Height=576, RefreshAll=true) at SoftOsd.c:1133 #2 0x402d6406 in cSoftOsd::OsdCommit (this=0x91ac978) at SoftOsd.c:205 #3 0x402d649f in cSoftOsd::Flush (this=0x91ac978) at SoftOsd.c:293 #4 0x080e18ec in cSkinSTTNGDisplayChannel::Flush (this=0x91ac0c0) at skinsttng.c:322 #5 0x080accfb in cDisplayChannel (this=0x917c958, Number=301, Switched=true) at menu.c:3043 #6 0x080f3422 in main (argc=10, argv=0xbfeffb34) at device.h:240 This i vanilla softdevice 0.4.0 with vanilla vdr-1.4.0-1 Hope this helps, Wolfgang ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Best settings..
Hi! I have very simple and still hard question.. At vdr pluging setup - xineliboutput - Video. Post processing (ffmpeg) and Deinterlaceing. What ARE best values (to select) when you have HD LCD (via DVI) as TV and enough CPU power (Intel Core 2 Duo) to use. I think that I'm not only one who thinks that there is too many choices.. ;-) -- JJussi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Best settings..
JJussi wrote: Hi! I have very simple and still hard question.. At vdr pluging setup - xineliboutput - Video. Post processing (ffmpeg) and Deinterlaceing. What ARE best values (to select) when you have HD LCD (via DVI) as TV and enough CPU power (Intel Core 2 Duo) to use. I think that I'm not only one who thinks that there is too many choices.. ;-) I use vdr-sxfe with --video=xv --aspect=16:9 --post tvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=1. -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Best settings..
JJussi wrote: Hi! I have very simple and still hard question.. At vdr pluging setup - xineliboutput - Video. Post processing (ffmpeg) and Deinterlaceing. What ARE best values (to select) when you have HD LCD (via DVI) as TV and enough CPU power (Intel Core 2 Duo) to use. I think that I'm not only one who thinks that there is too many choices.. ;-) There is a simple answer: the one that pleases your eyes the most... AFAIK ffmpeg post processing is for mpeg4 only. What comes to deinterlacing, I'd suggest to use tvtime with any greedy algorithm or TomsMoComp, disable cheap mode and use full framerate. My experience is that TomsMoComp or Greedy2Frame are needed for sports whereas other types of programs are not that demanding. Unfortunately none of the deinterlacing methods is perfect and they all produce some jagginess, especially with football in 16:9 aspect. -Petri ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
