my profile | my password | search | faq & rules | forum home

» Film-Tech Forum ARCHIVE   » Operations   » Digital Cinema Forum   » Importing Ethernet automation cues on Dolby DSS

Author Topic: Importing Ethernet automation cues on Dolby DSS Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 12-03-2019 03:39 PM                     A friend was trying to follow the short instructions in the Dolby DSS 4.9.1.22 release notes to import a file containing ethernet automation cues. In order to apply the file after import, one has to execute a script ./listAutomationConfigurations.sh localhost However - when he does that, he sees a long list of various *sys-package-mgr*: processing new jar, 'usr/share/java/xxx.jar' and similar lines Not what he expects in order to choose the ethernet automation file following: --- 3. Enter ./listAutomationConfigurations.sh localhost to display an ordinal numbered list of all ingested configurations. 4. Enter ./importAutomationConfiguration.sh localhost <name of file> <store> where name of file is your most recently ingested file and store is MainStore. (Alternatively, you can type the displayed ordinal number of the desired configuration file.) The system imports and automatically applies the configuration. --- This is in 4.9.4(5) - Carsten  |  IP: Logged Pete Naples Phenomenal Film Handler Posts: 1565 From: Dunfermline, Scotland Registered: Feb 2001 posted 12-03-2019 04:05 PM                     It hasn't sucessfully imported I think. Or the xml file contains some error, the DSS line processing of these xmls isn't very friendly. If there's an error it won't tell you, it just fails. FTP into the automation folder off the root directoy and see if the ethernet xml files is there at all.  |  IP: Logged Steve Guttag We forgot the crackers Gromit!!! Posts: 12814 From: Annapolis, MD Registered: Dec 1999 posted 12-03-2019 04:52 PM                     Always use the ordinal number. So if they just FTPed 1 automation config file over...its ordinal number will be 1. The command (from the scripts directory) will be: ./importAutomationConfiguration.sh localhost 1 MainStore If you are unsure of the ordinal number, then executing the ./listAutomationConfigurations.sh localhost will get you the number to the associated names.  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 12-03-2019 06:35 PM                     There is no such file/number visible in the list. screenshot - Carsten  |  IP: Logged Pete Naples Phenomenal Film Handler Posts: 1565 From: Dunfermline, Scotland Registered: Feb 2001 posted 12-04-2019 05:08 PM                     Nothing is imported. Was the xml FTPed into the root directory? Many people make the mistake of importing into the automation folder. The software does that as part of the import process.  |  IP: Logged Steve Guttag We forgot the crackers Gromit!!! Posts: 12814 From: Annapolis, MD Registered: Dec 1999 posted 12-04-2019 06:49 PM                     What Pete said  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 12-05-2019 10:33 AM                     Yup. Ingesting into root solved the problem (this one is dealing with a JNIOR). The 4.9.1.22 release notes are not entirely clear on this method. Are there other documents explaining it better? - Carsten  |  IP: Logged

All times are Central (GMT -6:00)

Printer-friendly view of this topic

Hop To: Select a Forum: Category: Operations -------------------- Digital Cinema Forum Film Handlers' Forum Large Format Forum Ground Level Feature Info, Trailer Attachments & REAL Credit Offsets Category: Community -------------------- Film-Yak Film Handlers' Movie Reviews The Afterlife Bob Maar's Joke-A-Thon Category: Classified -------------------- Equipment and Supplies Wanted/For Sale Help Wanted/Seeking Employment Category: System -------------------- Software Beta Testing Forum

The Film-Tech Forums are designed for various members related to the cinema industry to express their opinions, viewpoints and testimonials on various products, services and events based upon speculation, personal knowledge and factual information through use, therefore all views represented here allow no liability upon the publishers of this web site and the owners of said views assume no liability for any ill will resulting from these postings. The posts made here are for educational as well as entertainment purposes and as such anyone viewing this portion of the website must accept these views as statements of the author of that opinion and agrees to release the authors from any and all liability.