Messages

I tried this patch but could not compile after patching. Propably my version was wrong Is this patch in git?

I have vdr-vompclient-mvp (0.3.1.3-0yavdr0~precise) whis does not work on my mvp. It does work on my windows vomp client. I happen to have a raspberry pi and compiled vompclient-raspi from git but it turned out that it needs another version of the server plugin. Which again is not so easy to compile on ubuntu with vdr from the repos Or I did managed to compile it but then my vdr installation complained about it not being compatible on binary level :/

But as said my mvp loads the windows dongle nicely from my vdr server and then connects on windows server. But it does not want to work with any other dongle. It leaves the last box white when loading. Logs shows it has loaded the dongle.

Seems quite same behaviour as I have seen. Could you also try to put the hauppauge donge.bin to your tftp server to see if your MediaMVP starts? Just download the setup from hauppauge.lightpath.net/software/mediamvp/mediamvpsetup_34_25345.exe and extract the exe with some zip extractor and find the dongle.bin. Put it in your server and change TFTP file name = vomp-dongle in your vomp-00-0D-FE-00-48-F1.conf file to reflect the file name. No reboot of any kind is needed (you will see the file name change on the "TftpClient - File: '/tftpboot/vomp-dongle'" line in the log).

We have different revisions of MediaMVP but maybe it would show that the problem is in the client software.

So now I have set up a windows server but the MediaMVP loads the dongle from my vdr setup and then connects to the windows server and everything works fine. But of course this is not the way I want But this proves (I think) that my setup should be correct. VDR is even found on the hauppauge software (but not playable).

To test more I used older dongles but the result was the same. I thought that maybe the dongle.bin was broken in Ubuntu repo.

The MediaMVP is still in the last stage leaving the last box white when using vomp-dongles

And I also tested with vomp for windows which also works fine.

What can I do ?

Hopefully someone is still reading this thread

Now I tested with putting the Hauppauge windows server dongle.bin to my vdr server and MediaMVP loads it as it should. Now it is trying to find a server in my network which it of course cannot find because I do not have any Hauppauge servers running.

Looks like there is something in the vomp-dongle which is not compliant with my MediaMVP (Model 86002 Rev E1 Lot 4703) Even though it should be.

No, do not believe so.
1. I have more than one devices in the network all working perfectly
2. The server shows the mediamvp on its list and shows its IP everytime I connect it
3. I installed Hauppauge software on my windows laptop and mediamvp worked fine with it

Had not tried before but now tried even to force an IP address for mediamvp. Normally my dhcp server does it. No change :|

Had not tried telneting but tried now. It does not respond. I did a clean install starting with an empty hd So I dont think there should be any problem with conf files. And as I said the 0.3 did not start either. Its bizarre??

It says in the bottom:
Model 86002 Rev E1 Lot 4703

And as said it did work before. It makes no sense what so ever. As I wrote I had VDR 1.6.0 with vompserver 0.3.0 and it was working. I do not use it daily (not even weekly). I moved and changed dvb cards (dvb-c to dvb-t). No software changes. Could not get it working.

Then I was anyways updating my vdr box so now I have vompserver 0.3.1-3 and still no luck

No, there is nothing wrong with mediamvp. I downloaded latest windows software and tested with it and mediamvp finds it and loads without problems.
Is there some restrictions about some hw version and dongle version?

Now I have vompserver 0.3.1-3 and still no luck

Does anyone have any suggestions?

Seems there might  be something wrong with the mediamvp. I downloaded vomp for windows and it works with my vompserver. Strange that mediamvp downloads the dongle and after that freezes

Checked and double checked.
The DHCP server does not have a region specified. It really seems to share addresses from the whole subnet. There is no mention of DHCP in the manual. In UI DHCP is mentioned in one place, when looking at configuration information of a network device "DHCP lease time: Infinite" and above that a checkbox "Always use the same IP address". Also I can see the MediaMVP in the router when i power it on and it shows an IP for it. The router even identifies it as Set top Box.

Doesn't it mean that the server is communicating with the MediMVP since firstly it knows the mac address and secondly it sends the dongle  per the request of the client?

Either the MediaMVP is somehow faulty or the router does something in between.

I also tried with the recommended IP forcing and nothing but the log changed.
23:19:58.554646 [debug]  BOOTPD - Wait finished
23:19:58.554774 [debug]  BOOTPD - Got request
23:19:58.554853 [debug]  Config - Opened config file: /var/lib/vdr/plugins/vompserver/vomp-00-0D-FE-00-65-F5.conf
23:19:58.554880 [debug]  BOOTPD - Opened config file: /var/lib/vdr/plugins/vompserver/vomp-00-0D-FE-00-65-F5.conf
23:19:58.555008 [debug]  BOOTPD - Found IP 192.168.1.110 for MVP
23:19:58.555090 [debug]  BOOTPD - Will enforce IP 192.168.1.110 on MVP even if it already has another
23:19:58.555121 [debug]  BOOTPD - Giving MVP IP from config
23:19:58.555322 [debug]  BOOTPD - Starting wait
23:19:58.686042 [debug]  Tftpd - Wait finished
23:19:58.686173 [debug]  TftpClient - Client handler started
23:19:58.686321 [debug]  TftpClient - RRQ received for vomp-dongle
23:19:58.686384 [info]   TftpClient - File: '/usr/share/vdr-plugin-vompserver/vomp-dongle'
23:19:58.687037 [debug]  Tftpd - Starting wait
23:20:05.885947 [debug]  TftpClient - Retransmitting buffer
23:20:08.057591 [debug]  TftpClient - Retransmitting buffer
23:20:08.209884 [info]   TftpClient - File transfer finished
23:20:08.210035 [info]   TftpClient - processMessage terminating connection

I am out of options

I have a DHCP server in local net givin adresses in 192.168.1.0 network (basically any address in the net is available). The devices in the network gets same addresses because of the way the network router just works. It always gives them same address (this is the behaviour by default). So basically they are dynamic but made static by DHCP server. As strange as it may sound there is no DHCP settings other than a checkbox on every device wether or not to reserve the address for that device in the future.

vomp.conf is as follows:
Log file = /tmp/vompserver.log
Server name = VDRBox
Bootp server enabled = yes
TFTP server enabled = yes
TFTP directory = /usr/share/vdr-plugin-vompserver

vomp-<client>.conf:
[Boot]
# IP = 10.0.0.100
# Override IP = 1
TFTP file name = vomp-dongle
[General]
Last Power State = Off
WSS = No
Channels = FTA only
LangCode = fi
Remote type = New
Remote keys = <snip>
# Override Video Format = NTSC
[TV]
Connection = S-Video
Widemode = Letterbox
Aspect = 16:9
[Timers]
Priority = 50
End margin = 10
Start margin = 1
[ResumeData]

Or in the new setup de vomp-<client>.conf was as simple as
[boot]
TFTP file name = vomp-dongle

And yes the MAC is the one in the log.

Also this is whats in the log (a bit more than in my previous post)
18:56:05.885552 [debug]  BOOTPD - Wait finished
18:56:05.885671 [debug]  BOOTPD - Got request
18:56:05.885743 [debug]  Config - Opened config file: /var/lib/vdr/plugins/vompserver/vomp-00-0D-FE-00-65-F5.conf
18:56:05.885769 [debug]  BOOTPD - Opened config file: /var/lib/vdr/plugins/vompserver/vomp-00-0D-FE-00-65-F5.conf
18:56:05.885882 [debug]  Config - Config error: Key IP not found
18:56:05.885914 [WARN]   BOOTPD - No IP found for MVP. Hopefully it has one already...
18:56:05.885989 [debug]  Config - Config error: Key Override IP not found
18:56:05.886020 [debug]  BOOTPD - Will not change MVP IP if it already has one
18:56:05.886043 [debug]  BOOTPD - Leave YI=0 as MVP already has good IP
18:56:05.886250 [debug]  BOOTPD - Starting wait
19:13:23.026393 [debug]  BOOTPD - Wait finished
19:13:23.026551 [debug]  BOOTPD - Got request
19:13:23.026629 [debug]  Config - Opened config file: /var/lib/vdr/plugins/vompserver/vomp-00-0D-FE-00-65-F5.conf
19:13:23.026655 [debug]  BOOTPD - Opened config file: /var/lib/vdr/plugins/vompserver/vomp-00-0D-FE-00-65-F5.conf
19:13:23.026770 [debug]  Config - Config error: Key IP not found
19:13:23.026803 [WARN]   BOOTPD - No IP found for MVP. Hopefully it has one already...
19:13:23.026879 [debug]  Config - Config error: Key Override IP not found
19:13:23.026911 [debug]  BOOTPD - Will not change MVP IP if it already has one
19:13:23.026934 [debug]  BOOTPD - Leave YI=0 as MVP already has good IP
19:13:23.027128 [debug]  BOOTPD - Starting wait
19:13:23.157188 [debug]  Tftpd - Wait finished
19:13:23.157296 [debug]  TftpClient - Client handler started
19:13:23.157425 [debug]  Tftpd - Starting wait
19:13:23.157449 [debug]  TftpClient - RRQ received for vomp-dongle
19:13:23.157650 [info]   TftpClient - File: '/usr/share/vdr-plugin-vompserver/vomp-dongle'
19:13:29.242405 [info]   TftpClient - File transfer finished
19:13:29.242541 [info]   TftpClient - processMessage terminating connection

Hi

I have VDR 1.6.0 with vompserver 0.3.0. Everything worked fine. Then I moved home and had to change dvb cards from C to T. But no other changes was made.
For some reason MediaMVP now seams to stop the loading procedure leaving the last box white on the boot up screen.
Log stops with:
19:25:47.072790 [debug]  BOOTPD - Starting wait
19:25:47.203282 [debug]  Tftpd - Wait finished
19:25:47.203397 [debug]  TftpClient - Client handler started
19:25:47.203510 [debug]  Tftpd - Starting wait
19:25:47.203544 [debug]  TftpClient - RRQ received for vomp-dongle
19:25:47.203626 [info]   TftpClient - File: '/usr/share/vdr-plugin-vompserver/vomp-dongle'
19:25:53.270532 [info]   TftpClient - File transfer finished
19:25:53.270669 [info]   TftpClient - processMessage terminating connection

So I wondered if there is something wrong in my setup and installed brand new ubuntu on another pc and installed vdr stuff from the repos. Ending up with VDR 1.7.16 with vompserver 0.3.1.
Using this new VDR box with MediaMVP the bahaviour is the same and the log stops:
19:30:47.223699 [debug]  BOOTPD - Starting wait
19:30:47.354311 [debug]  Tftpd - Wait finished
19:30:47.354400 [debug]  TftpClient - Client handler started
19:30:47.354540 [debug]  Tftpd - Starting wait
19:30:47.354713 [debug]  TftpClient - RRQ received for vomp-dongle
19:30:47.354759 [info]   TftpClient - File: '/usr/share/vdr-plugin-vompserver/vomp-dongle'
19:30:54.409469 [info]   TftpClient - File transfer finished
19:30:54.409698 [info]   TftpClient - processMessage terminating connection

As you can see its identical.

So is my MediaMVP somehow broken or am I missing here something?

I have not yet been able to reproduce the crash in the same position of the recording. There is also this resume problem while crashing and that is that sometimes resume starts from the beginning of the recording and sometimes from where it crashed. Can mpeg decoder have an impact on this?

\\Kartsa