News:

Latest versions:
Server plugin: 0.5.1
MVP dongle: 0.5.2
Raspberry Pi client: 0.5.2
Windows client: 0.5.2-1

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - kdeiss

#1
Vomp For Windows / VOMP and PPTP - no connect
September 28, 2008, 18:38:01
Maybe this problem is similar to that described here: http://forum.loggytronic.com/index.php?topic=196.0

But its a bit different - seen from the network side.
I'am user of an vdsl-line (50000 KBIT down/10000 KBIT up !!) and so I realised access to my homenetwork via ipsec/pptp.  Ipsec does not work with vomp, ok , in that case I'am on the other side in a different subnet and maybe the same problem described above.

But if I dial in with pptp I will have an ip adress of my home network and it does also not work. I tried different configurations (pptp dial in via original XP and alternativly pptp dialin via pptp addon running on ipcop) but in both cases this result:

09:52:27.000859 [debug]  Command - processing message 25
09:52:27.000859 [debug]  Command - Sending message to boxstack
09:52:27.000875 [debug]  Command - processing message 25
09:52:27.000875 [debug]  Command - Sending message to boxstack
09:52:28.000484 [debug]  UDP - Wait for packet
09:52:28.000484 [notice] VDR - Broadcasting for server
09:52:29.000984 [debug]  UDP - Wait for packet
09:52:29.000984 [notice] VDR - Broadcasting for server

and so on in an infinite loop. Of course vompclient is running fine at home on the same machine.

Theoretically it should run fine with that kind of vdsl-line. I connected an eeepc to my homenetwork (via pptp) and was able to use vdr-streamdev-client without any problem (via internet !!), even channelswitching was relatively smart. Seems to be a problem with that broadcasting/connecting code inside the vompclient, but I can't imagine what it could be......

Schade, sehr schade ....

greetz

klaus
#2

Quote from: MartenR on December 17, 2006, 17:31:02
Maybe the windows client log file would help.

My clients don't write a log by default. What have I to do to create a logfile ?

klaus
#3
Quote from: MartenR on December 17, 2006, 12:08:10

OK I see, on my computer it works at least with two screens. What kind of computer is it, how fast? What network connect, wlan might be to slow. And additionally what does the logs say.

It is a toshiba p20-s303, running xp sp2, pentium4 2,66 ghz, 1 gb ram, connected via 100Mbit lan interface.
It is possible to run simultaneously a dbox2 streaming client (videolan) and vompclient without stuttering any video, cpu usage around 70%. Should be enough for 2 vompclients ....

Anyway - this is category "nice to have", seems again to be a "private" problem, I think there are many things much more important to do .....

thanks chris + marten, vomp and its clients are really a very very good piece of software for the vdr community.

klaus
#4
Thanks for your detailed answer.

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

If it's so - ok we have to cleanup our systems - but at least it would be usefull to see which selected filter crashs the client (logfile).

Quote. 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?)

It is very usefull to see sport events (soccer formel1) which are transmitted simtaneously, for example the bundesliga konferenz. Theoretically it would be possible to see 2 or 3 or 4 games on a windows computer at the same time / and the conference on the main tv  ;)

thanks again

klaus

#5
Hi marten !

Quote from: MartenR on December 16, 2006, 17:35:01
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.

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.

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.

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 ?

thanks


klaus
#6
Quote from: MartenR on December 16, 2006, 15:50:05
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).

;D ;D ;D

wouldn't it be usefull to have a filtermanager ? could be realized with an external application. Target:list, select register, unregister external filter. If interested I would eventually contribute such an tool.

klaus


#7
hi marten,

I looked araund in my system and with help of graphedit I found the application MyDVD from sonic. This app brings 3 ligos ax files into the system (all from 2003).

c:\Programme\Sonic\MyDVD\lmpgad.ax
c:\Programme\Sonic\MyDVD\lmpgspl.ax
c:\Programme\Sonic\MyDVD\lmpgvd.ax

(version 4.0.0.90)

After 3x
c:\WINDOWS\system32\regsvr32.exe /u filtername.ax

vompclient is running fine !!!

TATA !!!

Would it help you if I send you these files ???

klaus
#8
hi marten,

On my crashing installation

Ligos MPEG Audio Decoder
.....
Ligos MPEG Video Decoder
.....
Ligos MPEG Splitter
BUMM!
#9
Hi Marten,

I'am sorry to bring you more bad news.

This evening I made some tests in my office. I installed the newest dongle bin and compiled the 0.25 plugin. With MVP all worked fine as expected.

I've tested your win client on 4 machines
Two of them with w2k, before test newest DirectX. On both machines only a white, froozen window - nothing more....

Then another XP machine (medion hassenichgesehn), very strange: click on the executable and nothing, really nothing, no window, no dialog box - nothing.

Finally I tested it on an acer t135 with a nagelnew original fresh XP image: First time I could enjoy you program - running very good now more then one hour.....

Yes - windows is really a nightmare, I hope that you don't give up. Vomp for Windows is a great idea !!

greetz


Klaus
#10
Two attachments regarding your questions


#11
hi marten,

ok i checked it 3x. Here is the output:

connect without mtype
next enter
next leave sucessfull
report 1
report 2
report 7
stage 1
next enter
next leave unsucessfull
stage 2
connect leave 3
connect enter

connect without mtype
next enter
next leave sucessfull
report 1
report 2

BUMM!

Seems to be a very very uggly bug .....

klaus
#12
additional info:

I read the thread on vdr portal and saw the graph output from poly (who had a working installation) and there is a difference, I have selected version 6.0.0.1424, which shows itself in graphedit as "cyberlink video /sp decoder (PCM4)", see attachment. The version from poly: "cyberlink video /sp decoder"
I scanned my system and I found 4 different versions of clsvd.ax.
I don't know if its usefull .....

klaus

#13
ok, stage version output

stage 2
stage 1
stage 2
stage 3
stage 9
stage 10
stage 1
stage 2
stage 3
stage 9
stage 10
connect leave 3
connect enter
connect without mtype
next enter
next leave succesfull

bumm !

hope this helps ....

Wouldn't it be more effective to write debug output to a file ?

klaus
#14
Hi Marten,

so early up in the morning .....
The second time I tried this version I had a blue screen with fatal error in awvid5.dll. But maybe its corrupted during out tests.....


sourcefilter added
next enter
next leave sucessf...
connect enter
connect without mtype
next enter
next leave sucessf...
got mtype
got meminput
connect leave 5
audio rendered
added vmr 9
vmr 9 config
vmr 9 complete
fg2
next enter
next leave unsucessf...
connect enter
connect without mtype
next enter
next leave sucessf...
next enter
next leave unsucessf...
connect leave 3
connect enter
connect without mtype
next enter
next leave sucessf...
next enter
next leave unsucessf...
connect leave 3
connect enter
connect without mtype
next enter
next leave sucessf...

bumm

Marten, today I'am very busy, but if it helps you: I could give you access to this machine here with pcanywhere. If you don't have this software you can download it from my homepage. Please call me: 49(202)751578

klaus
#15
hi,

took some time, saturday evening.....

sourcefilter added
next enter
connect enter
next enter
next leave sucessfull
connect leave 5
audio rendered
added vmr 9
vmr 9 config
vmr 9 complete
fg2
next enter
connect enter
next enter
next leave sucessfull
next enter
connect leave 3
connect enter
next enter
next leave sucessfull
next enter
connect leave 3
connect enter
next enter

bumm!

Perhaps you could write the output to a log-file, would be easier to handle.
Yes I already checked my system with filtergraph, I've installed the cyberlink filter.

klaus