Duet Image Viewer - any hints?

[RocketMan]

Hi
I recently spoted an under the radar new item on the Duet remote menu, "Image Viewer". It's a shame there is no easy mechanism, no "go to place" for reading what's new and, crucially, any documentation on how things work. I have played around with Image viewer and found one question/answer online and all this has helped me get precisely nowhere with it. Does anyone have answers to any of the following please?

1) I found a Q&A somewhere explaining the format of the URL list "controller.lst", but when the question was asked "Where do I create/keep the file controller.lst?" the question was ignored. Without knowing that, there is zero probability that that function will ever work. Anyone know where it goes?
2) Directly related to 1. above, I assume I can crate and locate a controller.lst file using windows and save it on my NAS under windows? If I need to access some obscure Linux folder using some Linux plugin for Linux geeks, then agan the entire enterprise is doomed, except for the Linux geeks out there.
3) If, instead of a URL list you opt for "Local Storage", how would I get it to look, for example, at my c/Media/photographs directory? When I 'type' that int the handset it disregards the capital M in Media and can't find the images. I have tried creating other directories especially for it (massively inconvenient when all the photos are actually on the Media path) and that doesn't work either.
4) Any plans to really document these things or will it always be up to the user to Google an ad-hoc paper trail of partial clues from disparate forum sites, especially now the Duet has been officially discontinued?

Yours saddly

Rocketman
I have a Netgear NAS that has a directory called c/Media (note the capital M)

[mherger]

> 1) I found a Q&A somewhere explaining the format of the URL list
> "controller.lst", but when the question was asked "Where do I
> create/keep the file controller.lst?" the question was ignored.

Where did you see this? Might be worth completing.

The file must go on a web server which is accessible from your controller.

> 2) Directly related to 1. above, I assume I can crate and locate a
> controller.lst file using windows and save it on my NAS under windows?

No, this is not supported. The list must be accessible using the http
protocol.

> 3) If, instead of a URL list you opt for "Local Storage", how would I
> get it to look, for example, at my c/Media/photographs directory? When

"Local Storage" means storage media on the controller itself. In the
battery compartment there's a slot which can hold a SD card.

> I have a Netgear NAS that has a directory called c/Media (note the
> capital M)

The ReadyNAS might provide the web server you need.

--

Michael

[RocketMan]

Hi

Thanks for the reply, but you told me little thatI can put into actual practice, and the message itself appeared to be self-contradictory, unless I am mistaken. Consider:

* I asked if the file could be stored on the NAS, you said:
"No this is not supported"
then later:
"The ReadyNAS might provide the web server you need."
- so, I CAN store the list on my NAS?

* Also, can it then refer to it's self as the location of the images?

Put the long way round can I refer to locations in my NAS' folder structure, write a list that looks like the following, and store the list (where???) in a folder on my NAS:

(The controller.lst file)
c/Media/Photgraphes/picture 1.jpg
c/Media/Photgraphes/picture 2.jpg
c/Media/Photgraphes/picture 3.jpg

and then save this, say on c/Media (because I still don't know where this should go.

If c/Media is not a location where the http server can 'see' (not part of it's /public path, where can it see?, and can I place controller.lst there by looking at the NAS from a Windows 95 machine or do I need some sort of Linux interface to find the web server's structure?

I guess the root question remains - is there any actual documentation on this anywhere, or are such features realy undocumented hence little understood and little used (except by Linux hackers)?

Cheers

Rocketman.

[mherger]

> * I asked if the file could be stored on the NAS, you said:
> "No this is not supported"
> then later:
> "The ReadyNAS might provide the web server you need."
> - so, I CAN store the list on my NAS?

I'm sorry for the confusion... the file needs to be on a web server. This
web server can indeed be on a NAS.

> * Also, can it then refer to it's self as the location of the images?

Yes, it can.

> Put the long way round can I refer to locations in my NAS' folder
> structure, write a list that looks like the following, and store the
> list (where???) in a folder on my NAS:
>
> (The controller.lst file)
> c/Media/Photgraphes/picture 1.jpg
> c/Media/Photgraphes/picture 2.jpg
> c/Media/Photgraphes/picture 3.jpg

It's not that simple, as c/Media/... is not available to the Controller.
The list needs to consist of http:// urls. Eg. if your NAS does publish
the media folder through http, this might be something like
http://yournas/Media/Photographs/Picture1.jpg.

> If c/Media is not a location where the http server can 'see' (not part
> of it's /public path, where can it see?, and can I place controller.lst
> there by looking at the NAS from a Windows 95 machine or do I need some
> sort of Linux interface to find the web server's structure?

Figure out what folders your http server can access. All the files (list
and photos) need to be accessible for the http server.

> I guess the root question remains - is there any actual documentation

I'm sorry, no more than these few threads...

--

Michael