|
|
Author
|
Topic: Question about dolby ims 2000
|
|
|
|
|
|
|
|
|
Leo Enticknap
Film God
Posts: 7474
From: Loma Linda, CA
Registered: Jul 2000
|
posted 11-24-2019 11:53 AM
quote: Steve Guttag ...it is the best way to get a fix, if there is indeed a problem and who knows, they might just be able to diagnose what was causing it.
In many ways, Dolby's technical support is superb; but one of my few grouses with them is that I have found that they tend not to give priority to coming up with bug fixes for user-reported software issues. I have encountered this three times in the last year.
Case 1 - Dolby TMS running on DSL200 hardware - the tms.exe service crashes when a DSS220 connected to it on the theater LAN is rebuilding a RAID. When I reported this, it was quickly escalated to their development team. Someone spent about two hours on Teamviewer to the affected installation and eventually figured out that this was the cause of the tms.exe crashes. Sure enough, when I disconnected the DSS220 in which I had just replaced a RAID drive, the problem went away. Dolby told me that they were working on a bug fix and would let me know when the patch was issued. No patch so far.
Case 2 - TMS again, same installation, same hardware. If a SPL on any of the connected DSS220s contains the & character, the TMS cannot see any content on that server, or push to or pull from it (so Hobbs & Shaw FUBAR-ed the whole setup). Same process again - Dolby techs went in on Teamviewer, established what the bug was, but so far, no patch. Incidentally, this place consists of 11 screens, ten of which have DSS220s and the other one an IMS2000. The TMS continued to be able to communicate with the IMS, thereby establishing that this was a specific bug affecting interaction between the TMS and DSS220s.
Admittedly the DSS220 is now considered EOL, and so this might be why they are not prioritizing this. But the TMS is still current and they are still accepting money for license renewals. Given that this bug affects currently supported software as well as legacy equipment (in fact, it doesn't affect the operation of the legacy equipment, only the TMS), I am a little disappointed that these bugs have not yet been fixed.
Case 3 - bug in Show Manager version 4.9.4 (5) that affects the DSS220 when ingesting via eSATA. You connect a drive, it reads the contents, you select CPL(s) to ingest, hit the right arrow button, and then it says "There was a problem with the Show Manager server - please try again later." Trying again later doesn't help, and neither does rebooting the thing. The only workarounds that I was able to come up with are a clean reinstall of 4.9.4 (5), in which case it's only a matter of time before the bug happens again, or downgrading to 4.9.1. Once again, reported to Dolby, once again, they confirmed that they were able to reproduce the fault, but so far, no bug fix. This time, I was actually told that because the DSS220 is now out of active support, this won't be at the top of their in-tray. So fair enough, I suppose. It does mean that 4.9.4 (5) is not reliably usable on the DSS220, though, unless ingestion is only done over the wire and/or by USB (no eSATA).
So actually, Steve is right - it seems that they are able to diagnose what is causing these bugs, but not, so far, to come up with fixes for them.
| IP: Logged
|
|
|
|
|
|
|
|
|
All times are Central (GMT -6:00)
|
|
Powered by Infopop Corporation
UBB.classicTM
6.3.1.2
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.
|