aironet@tigercomp.ro 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

Wolfgang Fritz schrieb:

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

OK, that tracing helped. VIA C3 Samuel processor does not support MMX2. I reconfigured without mmx2, recompiled and now it's working.

Hope this helps,

Hope it helps Istvan too.

Wolfgang

---

vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

On 15 May 2007, at 15:13, aironet@tigercomp.ro wrote:

I reinstalled ffmpeg-0.4.9 from rpm (and all the dependencies) but I have the same output. It doesn't matter if i start softdevice with dummy or xv video output. I will do some more investigations tonight.

If you did a system wide update, you might have gotten different xorg gfx drivers installed, that has a different setup for Xv overlays. Check if you can change the pixel value used for Xv overlays keying. Maybe also check if other Xv programs works as before.

Check what value you have for XV_COLORKEY, using eg. xvattr.

Thanks for reply. I've installed xvattr, I can't see any lines containing XV_COLORKEY. I use nvidia driver.

Port: 334 Name: XV_SET_DEFAULTS Flags: XvSettable Min value: 0 Max value: 0 Name: XV_SYNC_TO_VBLANK Flags: XvGettable XvSettable Min value: 0 Max value: 1 Current value: 0 etc...

tigervdr:/home/ifuley # xvattr -a XV_COLORKEY Found Xv 2.2 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 141 (XVideo) Minor opcode of failed request: 14 () Serial number of failed request: 11 Current serial number in output stream: 11

gdb says: [softdevice] Subplugin successfully opend [New Thread 1086622608 (LWP 15390)] [softdevice] Video Out seems to be OK [softdevice] Initializing Audio Out [softdevice] Audio out seems to be OK [softdevice] A/V devices initialized, now initializing MPEG2 Decoder

Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1076586704 (LWP 15386)] 0x403b7d31 in avcodec_init () from /usr/local/lib/libavcodec.so.51

Istvan