The VideoLAN Forums

I printed directx.c source code, both 1.0.6 and 1.1.1 versions. This is insane!!!

Well, let's dig out!!! (I somebody tells me that I'm not trying to solve the issue by myself, I could explode! )

Not yet, I'm working with directx.c . So far I detected a bug, is really strange. As you can see in this piece of code inside Open : /* FIXME */ sys->use_overlay = false; //var_CreateGetBool(vd, "overlay"); /* FIXME */ overlay mode is broken. I uncommented that line and yes, it is broken. ...

Well, the patch works ok but it did not solve the issue, after about 3500 iterations the player crashed as always. I'll take a deeper look at the code, let's see if I can see anything.

Right now the video is playing for 9 hours, I'll check again tomorrow, but I can say that the patch IS working. I changed your patch from if (sys->resource.p_sys->front_surface != sys->resource.p_sys->surface) DirectXDestroySurface(sys->resource.p_sys->surface); to if (sys->resource.p_sys->front_sur...

Well, these are the results from yesterday (without the patch). As expected, after 8 hours the player crashed (well, not crashed, just stopped showing anything)... but now I have more info. This is the log output of the crash: . . . [GENERIC] [MAIN] ---------------> VoutDisplayEvent 'resize' 316x252...

What are you missing in the logs?? I have them just here, would you like me to post anything else? Anyway, I'm compiling now with the diff applied, let's see the results.

Thanks

Well, I have some news, I noticed some differences between 1.0.6 and 1.1.1 involving closing directX: First, let's go with 1.0.6 . This is the log involving video opening (just the directX part): [VIDEO OUTPUT] [VOUT_DIRECTX] --> creating DirectXEventThread [GENERIC] [MAIN] ---------------> thread (...

Upgrade to 1.1.0, there is a working delphi wrapper in this forum.

In win32,I achieved the same by reparenting not the widget component (a panel in my case), but its parent. If you reparent the widget component the video stops, but if you reparent the owner everything works fine. As in X11, I'm not setting fullscreen mode, just reparenting.

I'm on holiday, until monday I'll not start again. As my fiancee thinks that programming is "job", I had to slow down a bit. On monday I'll begin again, but now I can get log messages, so maybe this can help a lot. I'll post the results of the debugging around tuesday.

Yes, you have to do by yourself, reparenting the video widget to a fullscreen window.

Well... I made logging work, maybe with a debug output I can see anything. Thanks for the piece of code XilasZ, I had everything solved... but if I get a log iterator just before the creation of the libvlc instance... there is a really BIG chance that there are no logged messages, that's why I did n...

Yes, I supossed that. Can I use the libvlc logging functions or they are broken in win32?? I tried some of them but they seem a little buggy.

Yes, I found myself the modules involving win32 video output. I'll try to understand the changes involved in 1.1.0, comparing the new functions with those functions in 1.0.6. Should I ask questions regarding those modules to you or to someone else? Besides, it would be so helpfull knowing how the fu...

Compiling myself is not a problem, I compiled 1.0.6 twice when I needed it. What I'm talking about is about log messages in win32, those obtained with libvlc_iterator_next() . I'm totally uncapable of obtaining any message under win32, but libvlc_log_count() returns me the total log messages everyti...

Well, I'll be glad to help. I don't know if we should be speaking in this post or somewhere else. Anyway, with no debugging in win32 it's nearly impossible to fix anything, can anyone solve that or should I do it myself?? Getting to understand such a large amount of code is frigthening. Once this is...

The computer froze before obtaining any OpenGL results, now I'm running the test again.

Besides, are the logging API functions working well under win32?? libvlc_log_open, libvlc_log_count and similar are working well, but I'm uncapable of obtaining messages with libvlc_log_iterator_next.

Yes, yes, dummy works fine with 1.1.0, 1.1.1 and 1.2.0. I tried SDL but libvlc_media_player_set_hwnd doesn't work, the video is not rendered in the HWND selected, another window is created and destroyed each iteration ( VLC (software YUV SDL output) ). Should I configure anything else? I'm now tryin...

Well, I have news, the last test I run obtained the same results, after 8 hours the system got out of resources. I tried with 1.1.1 and 1.2.0, even I set the hwnd to null before stop the video and reset the hwnd to the panel where I play the video just before playing again (another crazy test). This...

Damn it, I was answering but I closed the session without noticing. Well, let's explain it another time. First of all, I'm not using 1.0.X neither, it's useless. Right now, and with 1.1.X, it seems that the vlc instance uses all the graphics resources of the system after a bunch of start-stop cycles...

I realize that is nearly impossible to catch that issue for you, I don't know how many people is running start-stop iterations in such a short time (6-8 seconds), but for sure we're not a lot. If you want me to run some other test, or info about anything, just tell me. Right now I'm running a crazy ...

Well... I don't know if the results can help you: dummy ouput was still running this morning without problems after about 20 hours. On the other hand, wingdi output crashed after about 3000 iterations (8 hours).

Tomorrow I'll post the results of the test, just started the playback (both dummy and wingdi) this afternoon and for the moment everything is fine.

Bye.

Well, maybe the results with wingdi and dummy can bring you some enlightment, but until monday I will not have them.
If this can help you, with 1.0.5 and 1.0.6 the player hangs after 48 hours, with directx vout filter, and only because of the huge memory comsumption.

Yes no prob. I'll post the results as soon as I get it.

Bye.