IMS3000s and Doremi IMB ingest scans not populating content

[Skyler Hunt]

Hi, friends. I'm in the process of setting up a new site and, for the most part, things have gone smoothly. However, I'm having trouble getting all three cinema servers--two shiny new IMS3000s and an old reliable Doremi IMB--to communicate properly.

I successfully set up each server as an ingest source for the other servers. The Dolby web UI tells me they're talking to each other when I hit the Test button in config. However, when I run ingest scans, few or no results appear. When IMS A scans IMS B, no content appears, and vice versa. When IMS A scans Doremi, all I get are two show playlists.

The good news is that all three servers are communicating properly with our Dolby E-delivery server, so we can get by, but, in my experience, cross ingesting over the media network is much faster than having each server individually retrieve DCPs from the Deluxe server.

Networking is my Achilles' heel and our equipment vendor who installed the site is away at a training this week. Any troubleshooting assistance y'all can provide would be very helpful.

[Ryan Gallagher]

Having only two screens that never show the same film here, I’ve only dealt with this on doremi targeting a local NAS for festivals.

But assuming they are all using FTP methods, I would check that you can connect to each using a desktop ftp client like FileZilla. If you use the same info as configured perhaps it is working but dumping you into a sub-folder and not scanning above that. In FileZilla you can more easily navigate to determine the correct folder path?

Just a hunch since the test is working.

[John Thomas]

Different ftp users have different home directories and permissions, for different purposes. When connecting to any doremi family cinema server via ftp, make sure you are using the "manager" login and its usual password if you want to access the /data directory for remote ingest.

Also make sure "composition playlist" has been selected as a category to be scanned for those entries in the Content Feed Manager. It would be on by default, but worth a look while you're in there.