Problems with DVArchive Client

Philip Van Baren

2004-07-15 01:39:54 UTC

Rob,

I have not tried running on 1.5.15, only on 1.5.18. I don't know if this would
make a difference, though.

The script uses the "dirname" command to find the name of the executable
directory. With 1.5.18 this is in the /usr/bin directory, which is in the
default path. Perhaps with 1.5.15 this doesn't work the same. You can test
this by typing "dirname /test/this/out" which should then return "/test/this"

You can also manually run the program like this:

cd (insert-the-directory-with-dvaclient.app)
set LD_LIBRARY_PATH=.
./DVAClient.app 192.168.0.11 192.168.0.12

where the numbers after DVAClient.app are the IP addresses of your ReplayTV, or
the IP address of a DVArchive machine. You should then see a bunch of info
displayed on the console window, or at least some form of error message. If
you send me that log, then I can look it over and maybe get some insight to the
problem.

The DVArchive connection is done on port 8042, because this is the special
"Video Server" port that it uses. For this to work you don't have the
"streaming server" option enabled in the DVArchive program, on (the default)
port 8042. This is configured on the bottom of the "Server" configuration tab
in DVArchive. The special port 8042 will give out information about all
ReplayTV units that DVArchive knows about.

DVArchive also emulates a ReplayTV "Server" on port 80, but on that port it
only gives out the listings local to that particular DVArchive machine, and not
for the full network.

I should also say that I have only tested with version 3.0 of DVArchive. With
that version there are some cases where DVArchive will not return any
information the first time you connect, but will work from then on. Also I've
found you need the "UPnP" support enabled in DVArchive for it to work. I don't
know if 2.1 or any beta version will work. What version of DVArchive did you
try?

Phil

Post by Rob DeMillo
Hi Phil -
Thanks for doing this.
Unfortunately, I played with it for about 30 minutes - but I was unable
o DVAClient seemed to ignore the REPLAYLIST setting
that I placed in the DVAClient.roku shell script
It kept trying to use "dvarchive" as the host name.
It wouldn't locate my Replays. (Yes, everything was
entered into /tmp/hosts
o Firing up a DVArchive on a PC and then trying to
force DVAClient to read from that did nothing either.
DVAClient was constantly looking for access to the
server on port 8042... DVArchive itself has a bug
that was preventing me from changing the port to
anything other than 80... and DVAClient wouldn't
allow me to change from port 8042 to 80. So, no good
there.
o Nothing was written to the /tmp directory. Nothing.
Not the log from DVAClient or CinemaSix. (I resorted
to firing it from the command line)
o It wouldn't fire from the onscreen icon. After a little
investigation, it was because it didn't seem to be
accepting the LD_LIBRARY_PATH variable, so it couldn't
find the .so library. (Could this be related to the
first point? It isn't reading from DVAClient.roku?)
I am on version 1.5.15 of the Roku OS.
Um...that's about it. Sorry man - I couldn't get it to go.
- Rob

Message: 1
Date: Mon, 12 Jul 2004 06:45:38 -0700 (PDT)
Subject: [Roku-tech] Announcing: new release of DVAClient
I've release a 0.2 version of the DVAClient program which
supports direct ReplayTV access, without requiring the use of
DVArchive. It also includes a version of the CinemaSix
executable which streams the video directly from the ReplayTV unit.
http://www.geocities.com/flipflop7146/roku.html
Phil

_______________________________________________
Roku-tech mailing list
http://lists.rokulabs.com/mailman/listinfo/roku-tech

__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail