This is topic Datasat AP20 errors in log at format change... in forum Digital Cinema Forum at Film-Tech Forum ARCHIVE.


To visit this topic, use this URL:
https://ft-forum.com/ft/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic;f=16;t=002864

Posted by Christian Hove (Member # 6743) on 11-14-2016, 07:57 AM:
 
Hi,
We have just got Datasat AP20 audio processors installed in three auditoriums.
Looking through the AP20 logfile I see errors every time a format change is made:

Nov 14 13:32:43 192.168.206.132 user info apMgr changed: changing format, <Musik>-><DCP 5.1>
Nov 14 13:32:43 192.168.206.132 user err apMgr save to /rwm/global.cfg, opts 1
Nov 14 13:32:43 192.168.206.132 user info apMgr cp::loadFormat(DCP 5.1)
Nov 14 13:32:43 192.168.206.132 user err apMgr cp::load: load from /rwm/format/DCP 5.1.fmt, opts = 4
Nov 14 13:32:43 192.168.206.132 user info apMgr file read in 8 ms
Nov 14 13:32:44 192.168.206.132 user info apMgr setCardRoutingFromTable route ->DSP1->
Nov 14 13:32:44 192.168.206.132 user info apMgr updateSrcMuteForDCOpt 0->ff00
Nov 14 13:32:44 192.168.206.132 user info apMgr found dsp1func.ldr in /dde/lib/dsp
Nov 14 13:32:44 192.168.206.132 user info apMgr updateSrcMuteForDCOpt ff00->ff00
Nov 14 13:32:44 192.168.206.132 user info apMgr config load done with /rwm/format/DCP 5.1.fmt
Nov 14 13:32:44 192.168.206.132 user info apMgr load in 852 ms
Nov 14 13:32:44 192.168.206.132 user info apMgr cp::loadFormat(DCP 5.1) done status 0
Nov 14 13:32:44 192.168.206.132 user info apMgr updateSrcMuteForDCOpt ff00->ff00

Is this expected behavior or is something configured wrong?

All our DA20 is running 1.05.00.
 
Posted by Carsten Kurz (Member # 5396) on 11-14-2016, 08:13 AM:
 
We have the same messages in our logs, even with earlier firmware. Doesn't seem to cause any harm.

BTW - current is 1.05.01.

Please fix the topic and text to 'AP20', not 'DA20', as DA20 is a common Dolby Digital decoder, might confuse people.
Note Datasat also used to sell a DCI server 'DC20'.

- Carsten
 
Posted by Christian Hove (Member # 6743) on 11-14-2016, 09:18 AM:
 
Thanks Carsten,

It is comforting to know that I am not the only one seeing these errors.
(I've fixed the topic, but for some reason I'm not allowed to edit the post itself)
 




Powered by Infopop Corporation
UBB.classicTM 6.3.1.2