Hallo,
I would use the vompclient for windows on my computers. On some computers the client works well and on serveral other computers the client does not work. At all computers they have the some windows updates and powerdvd software. When I will start the client, the windows opens and the windows is closed. I can not the message "connecting to server" because the window is closed.
Can you help me to solve my problem? Can you give me the name of all DLL files that the client will use?
Thx.
DER KANZLER
Take a look at http://www.loggytronic.com/forum/index.php?topic=195.0 maybe this helps.
Marten
Quote from: MartenR on February 19, 2007, 18:21:14
Take a look at http://www.loggytronic.com/forum/index.php?topic=195.0 maybe this helps.
Marten
I have read this before, but it did not work. Is it a problem with a missing DLL?
All the computers have the same microsoft patch level.
Do you have an idea?
Look into the readme.win file and generate a log file after the instructions therein.
Marten
Hi,
here is the logfile information. I think the problem is the directx software, but why?
I hope you can solve my problem.
20:32:44.000859 [info] Core - Starting up...
20:32:44.000859 [info] Core - Remote module initialised
20:32:44.000859 [info] Core - LED module initialised
20:32:44.000859 [info] Core - Mtd module initialised
20:32:44.000859 [info] Core - Timers module initialised
20:32:44.000859 [info] Core - Read from MTD: PAL 720x576
20:32:44.000859 [info] Core - Video module initialised
20:32:44.000890 [WARN] OSD - Could not create Direct3D9 device!
20:32:44.000890 [EMERG] Core - OSD module failed to initialise
20:32:44.000890 [notice] Core - ViewMan module shut down
20:32:44.000890 [notice] Core - Command module shut down
20:32:44.000890 [notice] Core - VDR module shut down
20:32:44.000890 [notice] Core - OSD module shut down
20:32:44.000890 [notice] Core - Audio module shut down
20:32:44.000890 [notice] Core - Video module shut down
20:32:44.000890 [debug] Timers - Timers shutdown start
20:32:44.000890 [debug] Timers - Timers shutdown end
20:32:44.000890 [notice] Core - Timers module shut down
20:32:44.000890 [notice] Core - MTD module shut down
20:32:44.000890 [notice] Core - LED module shut down
20:32:44.000890 [notice] Core - Remote module shut down
20:32:44.000890 [notice] Core - Log module shutting down... bye!
Unfortunetely DirectX 9 is not equal to DirectX 9. Please install a DirectX runtime newer or equal to DX9 February 2006.
Marten
Now I have tried 2 other DirectX Patches. It does not work at all. When I start the client, the window from vompclient.exe is white but nothing happens. The client hangs up.
Here the logfile.
11:34:52.000754 [info] Core - Starting up...
11:34:52.000754 [info] Core - Remote module initialised
11:34:52.000754 [info] Core - LED module initialised
11:34:52.000754 [info] Core - Mtd module initialised
11:34:52.000754 [info] Core - Timers module initialised
11:34:52.000754 [info] Core - Read from MTD: PAL 720x576
11:34:52.000754 [info] Core - Video module initialised
That´s all.
I have used the directx version 2/2007 and 8/2006.
I hope you have another idea.
So the logs have changed after installing the runtime. So this part is fixed.
Now, I need to know the OS the graphics card for getting a better insight for this new error.
Marten
At this time, I tried out the vompclient at WinXP on 2 different computers. The both graphiccards have the Intel815 chipset (Dell Optiplex GX150, HP Vectra VL400). What are the minimum requirements for computers to use vomp?
This might be the reason. Unfortunetely this graphics card is not on my compatibility list. Maybe a can do a fix in Vomp maybe not, it depends on the graphics card capabilities. I'll send you a tool for determineing the graphic cards caps.
Btw, maybe using a newer driver might help!
Marten
I have tried to get a newer driver version for my graphics card, but unfortunetely I use the newest one.
Ok. I will wait for you.
I have already send a mail to you at 8 o'clock using the mail address in your forum profile.
Did it arrive your inbox?
I have on one computer exactly the same behaviour as described by the topic starter; on other computers all works well.
When starting vompclient it creates a white window and immediately exits. I installed directx9 from feb 2007. The log file says:
Could not create Direct3D9 device!
When I start graphedit.exe, it displays MPV decoder filter connected to Video Renderer, not Video Mixing Renderer 9, so this is obviously my problem.
Removing the connection MPV -> Video Renderer is ok, but when I try to connect MPV Decoder to Video Mixing Renderer 9 it says:
These filters cannot agree on a connection. Verify type compatibility of input pin and output pin. (Return code 0x80040217)
I don't understand, because on two other computers (all win xp sp 2) this all installed perfectly well.
Anybody any clue?
@dingo35
If it already exists at Direct3d device creation, some thing of your DirectX installation might be wrong, thus a not 3d capable graphics card or switched of 3d acceleration etc. .
So what type of graphics card are you are using, what os (also xp) , did you turn off graphics card accelaration in the control panel?
Marten
Quote from: MartenR on March 31, 2007, 16:00:37
@dingo35
If it already exists at Direct3d device creation, some thing of your DirectX installation might be wrong, thus a not 3d capable graphics card or switched of 3d acceleration etc. .
So what type of graphics card are you are using, what os (also xp) , did you turn off graphics card accelaration in the control panel?
Marten
Hi Marten, thx for your quick response. Graphics card is onboard Sis 730 chipset, on Windows XP sp2, Directx9,0c redist feb 2007 . Dxdiag reports hardware accell is active and all tests are working fine. Direct3d is reported active and test is working fine.
I am not an expert, but this is my only PC having this graphics chipset, so I agree with your suspicion that this probably is a compatibility issue. The main question is: why does this pretty "standard" chipset does not match Video Mixing Renderer 9 ? Any idea where to look/what to look for?
Thx, Hans.
Hi,
the error has nothing to do with the VMR9. It is some graphics card incompatibility.
It might be, that it is impossible to run vomp for windows on it, but this points you can check:
1) vomp windows version should be 0.2.5-2 or higher better 0.2.6, there is one comptability issue fixed for older cards.
2) Update your graphic cards driver on sis webpage is one from 2003 (http://www.sis.com/download/download_step1.php), this might be to late for DirectX 9 support, but check this.
3) It might be that memory of graphics card is insufficient for vomp, if it is possible increase amount of mem that the graphics card can use.
If this does not work, you have to buy a new graphics card.
Marten
Quote from: MartenR on April 01, 2007, 17:46:55
3) It might be that memory of graphics card is insufficient for vomp, if it is possible increase amount of mem that the graphics card can use.
This was the golden tip, I increased memory assigned to graphics card from 8M to 64M, and now vompclient started ok, but now only sound, no picture. Now in graphedit.exe I can connect MPV decoder to VMR 9, restart computer --> still no picture.
Updated my vga drivers, now I cannot start vompclient anymore. Graphedit.exe does not enable loading VMR9, says perhaps its resources are in use elsewere.
So downgraded vga drivers again, now I can start vompclient, have sound, but no picture.
Logfile attached, it says a.o.:
TS Demuxer - Packet overflow, pid 517 .
Is it possible in this old driver sis730 chipset reports VMR9 capability, which it actually hasn't, and this is corrected in later driver versions?
How can I check for VMR9 capability (other than by graphedit.exe)?
Thx in advance, Dingo.
I really don't know, but if adding the VMR9 fails already on graphedit, it would not work on vomp.
Can you play back with graphedit and the VMr9 a dvd or an mpeg2 file, using the older driver?
Marten
Thx Marten, this was the kind of check I was looking for.
First I reverted to old drivers.
Then, when I insert a dvd, I can play it with windows media player, but I think this doesn't mean anything since it perhaps isn't played through WMR9.
When I open graphedit, choose "render media", and open a vob file on a dvd, graphedit points to MPEG-2 Demultiplexer, then to both MPA and MPV decoderfilter (does all look fine!). But then, the MPV decoder links to "Video Renderer", not to VMR9.
I can however reconnect MPV decoder filter to VMR9, so that all seems to work fine. But then, the proof of the pudding would be playing "trhough" graphedit, but I cannot find any option? This probably is a very dumb question, but how can I replay a media file being sure the graphedit config is used?
Hans.
P.S.: After "rewiring", vompclient still runs with sound but gives black screen; also mediaplayer keeps playing dvd... not sure whether this means anything...
It would be better to choose a dvd navigator filter for testing playback and not a vob, they might be encrypted and the dvd navigator initiate decryption. Playback inside graphedit is simply started with the play button under the menü bar.
QuoteP.S.: After "rewiring", vompclient still runs with sound but gives black screen; also mediaplayer keeps playing dvd... not sure whether this means anything...
Does that mean you can see the whole film with only audio?
Or does it stop after some seconds of playback?
If you can see the whole film, the graphics card does not support converting video pictures in yuv to rgb in the way vomp does i, do you use 0.2.5-2 or 0.2.6, since audio only was a bug on some grapphics adapters on 0.2.5-1
Marten
With mediaplayer I can see dvd with audio and picture, plays fine. I use vompforwindows-0.2.6-1.
As for graphedit.exe, that was really dumb of me, scanned all the menu-items but missed the buttons right under them.
Playing with graphedit.exe gives black screen with sound, not even a few seconds of picture, when VMR9 is selected. When I select normal Video Renderer, fine picture with audio.
So conclusion is sis730 chip does not support vmr9 correctly, and therefore it is blocked in later driver versions. I also can find some remarks on the internet that there is sis730 "only has limited support on vmr9", so that confirms the conclusion... :(
Marten, thanks for your fine support, I hope this thread can help others if they have videoproblems with vomp: the step-by-step approach is in this thread..
Best to all and keep up the good work! :)
P.S.: For those looking how to install the MPV and MPA decoder:
regsrv32.exe "c:\Program Files\vompclient/Mpeg2DecFilter.ax"
regsrv32.exe "c:\Program Files\vompclient/MpaDecFilter.ax"
Uninstall:
regsrv32.exe /u "c:\Program Files\vompclient/Mpeg2DecFilter.ax"
regsrv32.exe /u "c:\Program Files\vompclient/MpaDecFilter.ax"