Messages

I ran into this a while back - i believe that the MVP *firmware* bootloader successfully gets a DHCP address, but the newly booted MVP kernel asks DHCP *again* (now that linux is running), and *that* second DHCP request does not interact well with your setup - DHCP protocol problem we're guessing.

options - fix the MVP's linux DHCP, or get a different DHCP server that interacts better with the MVP's linux-based DHCP requests. or

we used a different router...

good luck!

--dbm

Coupla Quick Updates from here...

(BTW - thanks to the rest of the vomp contributors too - it's too easy to forget the rest of the mob)

Be sure and activate your Power DVD version, if required. (don't laugh... You didn't have to do that to get the decoders to work in previous versions      )

add to the keyboard commands "Alt-Enter -> full screen"

PowerDVD 7, vompclient.exe 2.5-1, xp-sp2 w/updates, dx9aug2006 .. werks fer me.

--dbm

Hi all,


(thanks to chris and martenr for vomp - it rocks)

For what it's worth, I was missing a few things that might save others some trouble.

I did not have directx on this machine (xp-sp2, current updates), so googled and got the redistributables from Microsoft at:

  http://www.microsoft.com/downloads/ - search for directx, i got the aug2006 redists and installed

I also did not have the msvcr71.dll - looks like a visual-c runtime dll - googled and got it at:

  http://www.driverskit.net/dll/get/2373.html - put in same folder as the vompclient.exe

Nor did I have the msvcp71.dll - also probably related to visual-c - also got it at:

  http://www.driverskit.net/dll/get/2371.html - also works if in the same folder as the vompclient.exe

your mileage may vary, but PLEASE check ALL downloads for viruses! Don't trust anything out there... I also cannot guarantee that having these MSV* DLLs is legit without the visual-c environment, so I'm willing to remove them if they ask me to.

Now I get the VOMP interface (nice!) and radio works (yay!), along with keyboard commands, etc. My mpeg2 decoder is from the cyberDVD 4.0 and (as advertised) doesn't work, so I'm digging for a newer copy. so close!




cheers,

--dbm

hello,

I recall a post of some low level (ASM) code for AC3 (it assumed the HW mods were done) on the SHS site a while back. The implication being that it *can* being done, but integrating that into the vomp, esp the player mods and the user interface tweaks to allow choosing audio channels...  will all be a bit of a task. Doable, but not trivial.

vomp rocks,

--dbm

Would it be possible/practical to create the desired static binary during the end-user's installation process, using compiled vomp objects and pulling any MS object segments directly from the end-user's own machine?

Even if a link-editor were sent as an EXE with the installer, it could be a custom/one-shot snip/glue engine, good only for melding exactly the right versions of the various parts...

Doing this might appropriately migrate the licensing issue to the end-user/owner of the OS/MS-software, rather than the vomp team.

So long as the GPL code for parts vomp distributes were available to the end-user, the spirit/intent of the GPL might be intact, and the MS distribution issues would be up to the end-users ("i accept", etc.).

I believe the direct-X stuff is freely available from MS - even as a redistributable bundle for vendors to send with their products (ala acrobat reader)


--dbm

Thanx MarkC,

you were on the money with the versioning. It looks like the APIVERSION tweaks in the 1.4.x makefiles created an unversioned ".../vdr/PLUGINS/lib/libvdr-vomp.so." file in my 1.3.34 vdr tree and it never got properly copied into my active PLUGINS directory. The build and installs ran with no noticeable errors, for this *and* the 2.3 vompserver... so I was *two* versions off. Impressive that it ran as well as it did.

all functions seem to work as intended - quick-skip, resume, OSD progress, etc. it even 'mostly works' on an edited/remuxed vdr file! (but that's not vomp's problem)

I guess it's time to bite the 1.4.x bullet...

FYI - finding the .../vdr/PLUGINS/lib/*.so. files with no version (libvdr-vomp.so. vs. libvdr-vomp.so.1.3.43) was the indication that something wasn't right. of course a quick look at the startup log/messages file would have helped too. Thanks again MarkC - I'll be more careful before posting in the future.


thanks again to all,

dbm

howzit,

thanks for the 2.4 fixes. esp rewind.

Welcome; glad it now works for you... apart from the problems below, of course

side effects for me:

  when navigating, the progress indicator frame shoes up, but the numbers
  and yellow percentage indicator are no longer visible.

  the quick jump feature, where pressing a number would jump to that
  number*10 percentage (e.g. 5 = 50%) into the program now just
  sends me to the start. I really got to liking that feature...

Sounds like the server isn't able to tell the client how long the recording is. The % skipping now works by frame numbers, with the help of the index.vdr file.

Are you definitely running the 0.2.4 vompserver as well as the 0.2.4 client? Could it be that your VDR recordings have missing or corrupted index files (perhaps they've been edited in some way?)

What about resuming a recording from the point you last stopped it: does that work? (I'd expect it to fail if the % skipping does).

howzit,

thanks for the 2.4 fixes. esp rewind.

side effects for me:

  when navigating, the progress indicator frame shoes up, but the numbers
  and yellow percentage indicator are no longer visible.

  the quick jump feature, where pressing a number would jump to that
  number*10 percentage (e.g. 5 = 50%) into the program now just
  sends me to the start. I really got to liking that feature...

appreciating your efforts. dbm

FYI - vdr 1.3.43.

----- UPDATE ------

I didn't notice the previous conversation in the nearby "CVS compile errors" that appears to ID/address the same issue/symptoms. Anyone with similar issues may want to track that thread too.

tnx all.

Thanks again for a way-cool package.

I'm with lodda, and guessing his skipping problem is intermitent/content-specific. starting in 0.2.2, my skip/rewind ( |< using the original (old?) remote) on recordings didn't work right, and would often skip forward.

My current version sometimes rewinds correctly, 'quick-skips' in place, or skips forward. Oddly, this is repeatable in any given spot, but I can't tell which effect it will have at any arbitrary point in the recording.

I would guess it's related to the GOPs frames in the particular recording...

I only mention it so that it's still considered for possible review when you're in that code-section, etc.

Note that it never did this in 0.2.1.

thanks for all,
dbm

FYI - vdr-1.3.43, lnx 2.6.15-rc6, MVP Ver D3A, original hauppauge style remote, vomp client/dongle 0.2.3, US-NTSC