Messages

OK in my case this helps as described in my last post (unregister) but in my opinion this is not a real solution. Before posting my first statement I checked the filters with graphedit and this did always show the cyberlink filter, if I connect Video Out and VMR Input. But in reallity vompclient tried to use the Ligos Splitter. So the user has no control over the selected filter, he does not even have an information about the selected filter and he can't correct it (without a bunch of knowledge).....

You gave me the hint to look for the Radlight Filtermanager - yes really a nice tool. I think their intention was to give the user some more control over the windows-directx-output system, and (very imortant) to blacklist some uggly, bad programed filters. Perhaps this could be a way to avoid such problems: a blacklist (ini file?), a logfile (from vompclient). In cases we run into GPF's the user can check his logfiles and than blacklist these kind of filters, or you could provide a default blacklist.

No, this can not be changed. It is also not the case, that vomp will use the ligos splitter.
Let we explain how Directshow works. Vomp say to DirectShow Filtergraph manager, hey please render this pin and then DirectShow will look into the registry and iterate thorugh all Filters in the registry. It will load one filter and then iterate thorugh all its input pins. Each input pin will be passed to vomps pin connect method and vomp will ask the filter pins, if he likes the ouput from vomp and the Ligos Pin crashes at this moment, instead of telling that he can handle the output ...

Well, I have said, that directshow iterate though the registry, all filter will be first sorted in order of their merit (ligos uses a a very high merit) and then alphabetically. So if you install a bad filter with a high merit, you will proably run into problems at a lot of DirectShow applications. (I have corrected a lot of pc of my friends, who messup their commercial DVD player with a codec pack).
This is the automated DirectShow behaviour. Well, you can also build the graph yourself in your app, but this will be really complicated, since you have to know allmost every filter, which is availible.
First,I have not assumed, that it is the filter, therefore it took so long to get the error.

So a blacklist is not possible, the user have to use a tool like these filter managers, since it is a system wide problem.

Now that my vompclient is running (thanks a lot again for this) I immediatly have some new questions. The output (in my case) needs to be deinterlaced, I already tried some settings in graphedit (filter properties) which let me select automatic/force bob/force weave but it does not have influence on the output from vompclient. Is there annother way to do this? Same question for saturation, brigthness etc, I can't even move these controls.

Well, this is planned. In the case of vomp, this would be done through the VMR9 interfaces ( deinterlacer etc.), but first we need for the main code a way to have device dependend options (other options on windows than on mvp).  So wait some revisions for this.

More than one instance? I tried to use the client twice (on the same machine), but after a while (10 seconds or so) both instances are freezing. With my MVP and vompclient this is possible (of course in the same bouqet), but two clients on the same machine is (in my case) seems not to be possibe. Would be such a strong feature - again only here on my machine ?

Well, it would be possible to run vompclient on to different computer simulataneously. On the same computer, this might work also, but this highly depends on your hardware and software, since some features are limited to be used only once at one computer. So this can work, but it does not have to. (and I personally see no use running it twice on the same computer, why do you need this?)

Marten

Ok, I checked it, it is division by zero somewhere internally in the Filter, far away from my code. I assume a fault in the filter since I can't get closer to the problem, also the filter tries to connect in a way that is not allowed for the mediatype vomp gives to the filter. Anyway I can't do anything against the crash, so I suggest to decrease this filter merit or to unregister it.

So now the intervideo problem remains, I really need the versioin number, for testing maybe it is something different.

@kdeiss:
There are lot of this tools around Radlight filter manager and DirectShow Filter Manager 0.5 . I suggest that you can use one of them, they provide all the functunality you propose. (We don't have to reimplement the wheel a second time)

Got a version 4.0.?? from an old demo version and yes it crashes! (Maybe it sounds stupid, but I'm really happy, that it crashes on my computer).

Marten

Ligos Mpeg Splitter is a little bit more confusing, since it is not the right type of decoder.
Nevertheless, maybe something in vomp directshow implementation is wrong, which most filters does not care, but some filter does care. So I ask also for the version number etc., so that I can try to get this filter may be it crashes than on my development machine also.
Btw how old are these filters?
I don't implement one now obsolete interface, maybe they ask for the interface and do not realize, that I do not support it.

What happens if you remove this filter?

Marten

Interesting, I have intervideo decoder sucessfully tested (but a new one from ulead moviefactory). Can you please determine which version, maybe the version of your intervideo product (windvd , windvr, ulead version ) or the decoder version you uses.
Search for ivivideo.ax on your computer, report  the paths where you find it and the file version, press in explorer right mouse button on the files, select properties and then go to version tab and report the versions.
After we managed to determine the version I'll try to get a demo version of the same version and see whats happening.

@other users with crash , is it also a intervideo decoder

Marten

Hi
to all with the crashes, I thought about it. It is probable, that all installations with this crash have a filter installed, which is causing the problems. If I know the filters name, I can propable get the same filter and reproduce what is going wrong.
So attached to this messages is again a testing version. This version report the filter names of the filter vomp tries to connect, so please execute it and report the last filter name.

Marten

I have checked, if the cut marks are compatible with the windows client. They are, no problems with the windows client.
The cuttings marks feature are a very nice addition to vomp (now I'm able to skip commercials  also on the vomp clients  ), thanks for that.

Marten 

@GTRDRIVER
Ok, for black screen issue, it is important for me to know your graphic card chipset and if the bugfix release 0.2.5-2 does also have this error, the black screen issue might be already fixed. (Btw the testing versions in this thread are only 0.2.5-1 based, because they address a different problem).

Marten

I have to add another filter. The intervideo filter shipped with "Ulead Filmbrennerei 5"(in english "Ulead Moviefactory 5") work perfect.

Marten

@GTRDRIVER
Was it crashed before on your laptop?
Does it crash on your laptop with 0.2.5-2 and do you have a picture with 0.2.5-2 ?
What graphics chipset?

The guess the crashes you reported before were always on your desktop?

@all
I have a new idea, it might be that not the finally selected filter crashes, but another filter, which is used during connect.
So I ask everyone with a crash to report the filter from graphedit that will be used by vompwin and the filter that would appear if you press the right button on the video pin at DVD Navigotor and select Render.

Marten

Hi,
I have found some bugs in the connected part of vomp. Don't report the messages, just report if it still crahes.

Marten

@kdeeis
regarding the screen shots:
1) Filterscreenshot:
Hmm, I think you should try to use the newest Filter in your list. 6.1....  There may be two ways (I think only one of them might work). If all Filter are registered with DirectShow (it might be that only one is registered, because they are more or less the same), than increase the Merit of the newest (look at the vdr-portal thread, how to do this), but maybe there is only one registred, then reinstall the application with the newest Filter. If they both don't work, there would be also a command line method.

2) Well this is catched by Visual Studio if you press ok the normal windows message would appear and maybe say the module in which the segfault appears. One other thing, you seem to have Visual C++ installed on your computer. Are you capable to debug it?, for error  finding I usually need only the line of the crash and the call stack, this might be  a lot faster than MessageBoxing

Regarding the problem I'm also going through the code to think what code might be crashing, but this is on going(and during the week my time is limited due to work).

The other computers:
W2k: Well I have no idea, what is happening, you can run vomp as in a console  "vompclient.exe >vomp.log" and logging will be written to vomp.log . It can be graphic card issue, too, so update your driver please. BTW graphics card chipset please. service pack number ?

wxp: even stranger than on w2k, please report the same things to get a hint. SP2 ?

Thank you for doing so much testing, I hope we will resolve all issues.

Marten

It is really ugly, it is inside receiveconnection, that means directshow or the filter calls another method of my pin and then crashes. I have to think about it, how to get closer. But one important question, does windows say in which module it crashes ? In vompclient.exe or other module ?

Regarding the different versions of powerdvd, a buggy mpeg2 filter can crash vomclient.exe also and then vomp is innocent.  I have powerdvd 6.0.0.1921 (but clvsd.ax, is it a typo). I have never seen a cyberlink filter with (PCM4). It maybe interresting, in which directory the different filters are located and to know their version. Maybe the crash is not vomps fault. But since I reimplement the interface formerly from streambase just three weeks ago and the crash is connect to them, it is more probable that vomp is the origin.

Marten

Hi, thanks for the input.
Regarding the log file, that isn't more effective, because the messagebox stops the executing thread. If it crashes always at the same place, I know that it is in right thread. With a log file this information will be lost, since there is no timing indepent of the programm like  a user pressing a button, second thing is that the bug seems to be inside the directshow code of vomp and this means it is not granted which thread (maybe processes) access the function and I don't know if file handles can be shared.

Unfortunetely I assumed that the crash is in another place and the stage message where in the wrong place to determine the place of the crash. So another round starts, now I need all report messages after the last ""connect without mtype" .
I know this is annoying (I have done this several times while developing vomp, if debugging was forbidden by mpeg2 decoder filter), but after the second test we know that the crash occurs inside connect method (several hundered lines), now I know that it crashes inside only 5 lines in connect and after this test I know in which line. (binary search algorithm=

One thing I was thinking C3PO seems to have the same problem, but he was no next leave sucessful at the end, so please look what happen if it  is executed twice, do you reproduce the same messages?

Marten

No, the target is not fiinding a freeware decoder. I think it is up to the user to choose, which mpeg2 decoder should be used for system-wide MPEG2 playback. I personnally hate it, if a programm installs some MPEG2 decoder, I want to choose the decoder myself. But what I want is to provide a compatibility list, that user can check before they buy or download in the case of freeware decoders, if it would work with vomp.
Also shipping a mpeg2 decoder can be problem regarding software patents.

Marten