Messages

hello martenr,

the memory incrase dynamicly. 16m are using at the moment of generating report. if any layers
defined it catches the memory from the mainmemory. 8m means that the smales block to use
(and i think the memory only changed at 8 mb block-size). and the maximum of usable memory
for grafik are 224 mb.

If you don't object i woud try to implement sdl and ffmpeg. if it's work i can send you the result.

bye woodym

now i have updatet driver (newest from intel). the result is the same.

here the report:

Intel(R) Graphics Media Accelerator Driver Report
Report Date:      12/09/2007
Report Time[hr:mm:ss]:   02:29:37
Driver Version:      6.14.10.4864
Operating System:      Windows XP* Professional, Service Pack 2 (5.1.2600)
Default Language:      German
DirectX* Version:      9.0
Physical Memory:      2039 MB
Minimum Graphics Memory:   8 MB
Maximum Graphics Memory:   224 MB
Graphics Memory in Use:   16 MB
Processor:      x86 family 6 Model 15 Stepping 6
Processor Speed:      2319 MHZ
Vendor ID:      8086
Device ID:      2772
Device Revision:      02
*   Accelerator Information   *
Accelerator in Use:      Intel(R) 82945G Express Chipset Family
Video BIOS:      1295
Current Graphics Mode:   1280 x 1024 True Color (75 Hz)
*   Devices Connected to the Graphics Accelerator   *
Active Monitors: 1
Active Digital Displays: 1
*   Monitor   *
Monitor Name:      Plug und Play-Monitor
Display Type:      Analog
Gamma Value:      2,20
DDC2 Protocol:      Supported
Maximum Image Size:   Horizontal: 14,0  inches
         Vertical:   11,0  inches
Monitor Supported Modes:
640 x 480 (60 Hz)
640 x 480 (67 Hz)
640 x 480 (72 Hz)
640 x 480 (75 Hz)
720 x 400 (70 Hz)
800 x 600 (56 Hz)
800 x 600 (60 Hz)
800 x 600 (72 Hz)
800 x 600 (75 Hz)
832 x 624 (75 Hz)
1024 x 768 (60 Hz)
1024 x 768 (70 Hz)
1024 x 768 (75 Hz)
1152 x 864 (75 Hz)
1280 x 1024 (60 Hz)
1280 x 1024 (75 Hz)
Display Power Management Support:
   Standby Mode:   Not Supported
   Suspend Mode:   Not Supported
   Active Off Mode: Supported


*   Digital Display   *
Monitor Name:      Plug und Play-Monitor
Display Type:      Digital
Gamma Value:      2,20
DDC2 Protocol:      Supported
Maximum Image Size:   Horizontal: 14,0  inches
         Vertical:   11,0  inches
Monitor Supported Modes:
640 x 480 (60 Hz)
640 x 480 (67 Hz)
640 x 480 (72 Hz)
640 x 480 (75 Hz)
720 x 400 (70 Hz)
800 x 600 (56 Hz)
800 x 600 (60 Hz)
800 x 600 (72 Hz)
800 x 600 (75 Hz)
832 x 624 (75 Hz)
1024 x 768 (60 Hz)
1024 x 768 (70 Hz)
1024 x 768 (75 Hz)
1152 x 864 (60 Hz)
1152 x 864 (70 Hz)
1152 x 864 (75 Hz)
1280 x 960 (60 Hz)
1280 x 960 (70 Hz)
1280 x 960 (75 Hz)
1280 x 1024 (60 Hz)
1280 x 1024 (75 Hz)
Display Power Management Support:
   Standby Mode:   Supported
   Suspend Mode:   Supported
   Active Off Mode: Supported

*   SDVO Encoder Report   *
** Encoder 1 **
Vendor ID:   Silicon Image
Device ID:   170
Device Revision:   3
Major Version:   1
Minor Version:   1
* Other names and brands are the property of their respective owners.

hello martenr,

1.) I think we may ran into software patent issues for the binary version. This is no issue for linux since, most software is there distributed in source code form.

for this i have used external dll. so ffmpeg (and sdl) isn't part of binary.

2.)
I know DirectShow and Direct3D very well and this is was the reason beside the legal stuff to use it. (I have no time to learn a new framework).

yes you'r right... but only if direct3d and directshow is configured well. if you install any software it's posible this damage your good install.

3.) With DirectShow I have not to care about time and synching, because it cares about it. This very important for DVB Streams because they are not synched like mpeg files or DVD content with ffmpeg I have to this on my own.

yes, you must do sync yourself. but this is here at sourcecode. the test i made was with vdr-files witch stored by vdr. so this is async like the stream.

4.) I want to make the windows port better in detail not to do an entire rewrite.

and this is the point why so many people loves vompclient !

yes i know it's costs mutch time to reimplement the decoding-core. if you say: 'let's try' i can help you to build a version with ffmpeg. if ffmeg isn't any option than it makes not sens to spend time for this. on a short look to source i havn't find the posible entry for ffmpeg. but this is only a question of time.

The dual screen issue: This is really interesting! This does not have something to do with the codecs, but with the selected surface type and your graphics card. Because some video scaling options are only availiable on the primary screen on most cards, so that in a dual screen configuration maybe something had to be simulated in software.

i have testet this situation with sdl and cpu-time not incrased.
at vompclient the cpu-time are incrased at any sitution (like only display stream or if menu is on).

@a i extend my desktop
@b prozessor 82945G (intel onboard chipset), it uses shared memory, the memory-size are max 224m for grafik, the total memory 2g, resolution 1248*1024 on both screens (32 bit).
@c this system is an new system install 1 month ago with (i mean) new driver. but after sending this i try to update the driver and report the result.
@d which config you mean? hardware-accelorator is set to maximum i can give the report:

Code Select Expand


Intel(R) Graphics Media Accelerator Driver Report
Report Date: 12/09/2007
Report Time[hr:mm:ss]: 02:12:30
Driver Version: 6.14.10.4764
Operating System: Windows XP* Professional, Service Pack 2 (5.1.2600)
Default Language: German
DirectX* Version: 9.0
Physical Memory: 2039 MB
Minimum Graphics Memory: 8 MB
Maximum Graphics Memory: 224 MB
Graphics Memory in Use: 16 MB
Processor: x86 family 6 Model 15 Stepping 6
Processor Speed: 2319 MHZ
Vendor ID: 8086
Device ID: 2772
Device Revision: 02
*   Accelerator Information   *
Accelerator in Use: Intel(R) 82945G Express Chipset Family
Video BIOS: 1295
Current Graphics Mode: 1280 x 1024 True Color (75 Hz)
*   Devices Connected to the Graphics Accelerator   *


woodym

hello,

i have testet vompclient 2.6 and 2.7 on my win-xp.
the vompclient is one of the rare programs that works on dual-screen with video.
the codec-select are very hard to get the right codec. one codec works great but hangs after time. othe let flickering the video. other have long startuptimes. other problem... if i start, vompclient gets 2%-6% cpu-load. if i move the vompclient to dualscreen, it works but the cpu-load incrase to 40%-50% (6600 dualcore cpu).

4 weeks ago i have testet sdl on windows with ffmpeg. i have made a simple movie-player. the results are great. cpu-load like 4%-6% on both screens. able to play htdv (mpeg4 codec works with ffmpeg). layers (for menue) can build.

have you planed to use sdl and ffmpeg? the benefits are vompclient works on linux and windows. no codes must be installed an system. hdtv can be used with vompclient. very stable client.

hello,

i have try mahlzeit 3 and mahlzeit4. on mahlzeit4 it's not posible to add dhcpd (apt-get dont'n work; a lot of config files not there). to setup developing-system for mahlzeit is very time-intensiv (i can't find any packages for the old woody-sytem), so i have made a new server based on gentoo with vdr 1.4.7 and vompserver 2.7. the changes i have posted is to give developer of vompserver any idea where the h3 problem is. this can help to build , let me say 2.8 of vompserver. if i have time i try to find the problem myself and post the info about the changes.

to help running vompserver with h3 the posible way are to use external dhcp (means other dhcp, not build in from vompserver).
on one system i have tested dns-masq and it works.
on my created gentoo-system i use Internet Systems Consortium DHCP Server V3.1.0
the config are easy:

Code Select Expand


option domain-name "mydomain.de";
option domain-name-servers 192.168.1.99;

default-lease-time 600;
max-lease-time 7200;
ddns-update-style none;
authoritative;
subnet 192.168.1.0 netmask 255.255.255.0 {
  range 192.168.1.180 192.168.1.185;
  option broadcast-address 192.168.1.255;
  option routers 192.168.1.99;
}

host mpv1 {
  fixed-address 192.168.1.181;
  hardware ethernet 00:0d:fe:0c:4b:cc;
  filename "dongle.bin";
  server-name "192.168.1.37";
#  allow bootp;
}


to get the hardware ethernet you can use the logfile of dhcpd or get the mac from the mvp (sticker on bottom of mvp). other way is to disable dhcpd, start vompserver with bootp and start mvp. vompserver generates one file with the hardwareaddress in the folder with the vomp.conf. then you can disable the bootp on vomserver and starts the dhcpd with the hardware-adress (mac-adress) set.

the config for vompserver:

Code Select Expand


#Log file = /var/log/vompserver.log
Server name = GenVdr
#Bootp server enabled = yes
TFTPD server enabled = yes
TFTPD directory = /tftpboot

(!! use TFTPD without D at end... if i post without d the forum crashes)

in dir /tftpboot are
dongle.bin
dongle.bin.ver

dongle.bin.ver are generatet with:
dd if=/tftpboot/dongle.bin of=/tftpboot/dongle.bin.ver bs=1 skip=52 count=40

at the moment i use the tftpd-server build in from vompserver 2.7 it works. i don't know if vompserver 2.6 tftpd works but i think it must because older mvp like h3 works with build in tftpd.

the flow of requests are (simplified):
mvp starts an send broadcast-request to the network (0.0.0.0:67).
the dhcp-server catch this request and look of any configs for the requesting mac.
if any config are defined the dhcpd send one answer to the requesting device (255.255.255.255:68)
the answer holds the defined ip for the device and other information like the ip and file to request the dongle.bin
mvp connect to tftpd (if acticated the build-in from vompserver) and gets the dongle.bin.ver
the mvp gets the dongle.bin and (*) starts the dongle.bin

(*) at this point mvp h3 requests other dhcp-request and gets no answer if dhcp from vompserver are activated. normal dhcp-server answer this correct and dongle.bin can started. with vompserver-dhcp the mvp requests 5 time the dhcp-request and hangs.

hello,

yes, i have read this. and try this. but it dosn't work.
this topic is the initition to look for the real problem (why it works on one server and not on other).
the real problem is the newle request to dhcp with the wrong (or uncomplete) answer.
it's not a problem if the dhcp is on the same server. i vae try it out with two differnt dhcp-server (software)
on two servers. where the dchp-server runnig dosn't matter. the dchp must run with port 67 (vompserver dosn't)
and the request after loading dongle.bin must answer with the right protokoll. one of the dhcp-server i tryed is
dnsmasq (great dns-cache with dhcp-server build in). this says on log-files the dhcp-request after loading dongle.bin
are class 5-requests.
for a long time ago i have read about dhcp and class-request and i think the request are adition options i have to send.
vompserver have a realy simple dhcp implementation without aditional options about router, dns and domain.

Hello,

i read in many borads h3 dosnt work.
i got one mediamvp h3 and want to play with vompserver. i used Mahlzeit 4.0beta2 and it dosent work. mahlzeit uses 2.6.1 of vompserver. i read i must update to 2.7 to work with h3. i setup a new vdr and try it out. it dosnt work to.  but anybody wrote it's work.
first the actions on mvp...
he gest the dongle.bin.ver
he gets the dongle.bin
the mvp is pingable for 5 seconds.
the led of lan are off after the 5 seconds.

ok,  i sniff the tcp and look about the problems.

the mvp try to get the bootp-info from bootp-port
he try it another one
than he try port 16867 to get the dchp-infos
vompserver answer with the ip and the dongle.bin
mvp gets from vompserver dongle.bin.ver and than dongle.bin

on this point it's look like ok.
than h3 (and i think this is the differnt) send another dchp request (i think class 5-request). but this request only goes to bootp-port.
vompserver isn't bind to this port and the mvp requests many times without answer.
i have change vompserver to listen to 16867 (i'ts a wook ago, i dont know is this the right port) and 67. the changes are simple (i change the server to start to threads with differnt ports).
now vompserver answer to the dhcp-request after transfer the dongle.bin .
but the h3 dosnt work.

at this point i switch bootp off (vompserver) and use dhcp-server.
all are the sam, but answer the dhcp-request (after transfer from dongle.bin) the mvp works.

i anlayse the differnt about the answer from vompserver and dhcp. the only seen differnt is tha dhcp-server sends options with the name-server, rooter and domain-name.

i think h3 uses other boot-firmware and try to set (after transfer dongle.bin) the network-address. only if this sends correct it starts the loaded bin.
i think every one that uses dhcp-server wrot about working h3.

at the moment i dont have time to anlayse the different about the dhcp-requests. the first step is to listen on default bootp-port. the other to
change the response in the right way.

here my changes:
note!!! to use ports <1027 vdr have to run as root. if initialize of port 67 fails the vompserver don't stop, only log this fault.

the changes are:
bootpd.h:
-    int run();
+    int run(int port, int aport);
    int shutdown();

+    int answer_port;
    DatagramSocket ds;

bootpd.c:
-int Bootpd::run()
+int Bootpd::run(int port, int aport)
{
  if (threadIsActive()) return 1;
  log->log("BOOTPD", Log::DEBUG, "Starting bootpd");

+  answer_port=aport;
-  if (!ds.init(16867))
+  if (!ds.init(port))
  {
    log->log("BOOTPD", Log::DEBUG, "DSock init error");
    shutdown();
    return 0;
  }

mvpserver.h
    UDPReplier udpr;
    Bootpd bootpd;
+    Bootpd bootpd67;
    Tftpd tftpd;


mvpserver.c
  bootpd.shutdown();
+  bootpd67.shutdown();
  tftpd.shutdown();


-    if (!bootpd.run())
+    if (!bootpd.run(16867,16868))
    {
      log.log("Main", Log::CRIT, "Could not start Bootpd");
      stop();
      return 0;
    }
+    if (!bootpd67.run(67,68))
+    {
+      log.log("Main", Log::CRIT, "Could not start Bootpd 67");
+    }