Chi, all packages read the peak metres from the GUI because that's not available in the control surface SDK. The disappearing metre is due to the CWACCESS Window needing to be refreshed. Regards, Phil Muir Accessibility Training Telephone: US (615) 713-2021 UK +44-1747-821-794 Mobile: UK +44-7968-136-246 E-mail: info@xxxxxxxxxxxxxxxxxxxxxxxxxxx URL: http://www.accessibilitytraining.co.uk/ -----Original Message----- From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On Behalf Of Chi Sent: 23 November 2010 00:26 To: ddots-l@xxxxxxxxxxxxx Subject: [ddots-l] Unrelyable Meter Hi, I use latest sonar with latest ct update. I'm not sure why, but sometimes CT keeps says something like peak meter has not been registered yet. I can clearly hear the signal from the track, and arm and input echo is off. It should have the output meter. During playback, I have to press ctrl+f2 twice time to time in order to restore the meeter setting. I haven't pinned down the cause of this, but it happens very randomly. Does ct still read the peak meter from the GUI instead of from the control surface? Thanks, Chi PLEASE READ THIS FOOTER AT LEAST ONCE! To leave the list, click on the immediately following link: ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe If this link doesn't work then send a message to: ddots-l-request@xxxxxxxxxxxxx and in the Subject line type unsubscribe For other list commands such as vacation mode, click on the immediately following link: ddots-l-request@xxxxxxxxxxxxx?subject=faq or send a message, to ddots-l-request@xxxxxxxxxxxxx and in the Subject line type faq PLEASE READ THIS FOOTER AT LEAST ONCE! To leave the list, click on the immediately following link: ddots-l-request@xxxxxxxxxxxxx?subject=unsubscribe If this link doesn't work then send a message to: ddots-l-request@xxxxxxxxxxxxx and in the Subject line type unsubscribe For other list commands such as vacation mode, click on the immediately following link: ddots-l-request@xxxxxxxxxxxxx?subject=faq or send a message, to ddots-l-request@xxxxxxxxxxxxx and in the Subject line type faq