Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
ezfit:clarujust:issues [2009/02/04 12:54]
smayr created
ezfit:clarujust:issues [2012/05/15 13:45] (current)
smayr
Line 1: Line 1:
 == Clarujust Issues == == Clarujust Issues ==
  
 +== Test Sequences Run Without Any User Input ==
 +
 + * Edit ''user.config'' file in:
 +   * ''C:\Documents and Settings\sarmstrong\Local Settings\Application Data\Audina_Hearing_Instrument\DefaultDomain_Path_dsl4vgsxzhirslr3yunxaqywmfwoa2qx\4.18.0.0'' 
 + * Disable the response recording feature:
 +<code xml>
 +<setting name="RecordResponses" serializeAs="String">
 +    <value>False</value>
 +</setting>
 +</code>
 +
 +See the entire ''user.config'' file:
 +<code xml>
 +<?xml version="1.0" encoding="utf-8"?>
 +<configuration>
 +    <configSections>
 +        <sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
 +            <section name="Audigence.Library.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
 +            <section name="AudigenceUI.Wpf.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
 +        </sectionGroup>
 +    </configSections>
 +    <userSettings>
 +        <Audigence.Library.Properties.Settings>
 +            <setting name="SignalPan" serializeAs="String">
 +                <value>Center</value>
 +            </setting>
 +            <setting name="NoisePan" serializeAs="String">
 +                <value>Center</value>
 +            </setting>
 +            <setting name="CallUpgrade" serializeAs="String">
 +                <value>False</value>
 +            </setting>
 +            <setting name="ReadyPan" serializeAs="String">
 +                <value>Center</value>
 +            </setting>
 +            <setting name="RecordResponses" serializeAs="String">
 +                <value>False</value>
 +            </setting>
 +        </Audigence.Library.Properties.Settings>
 +        <AudigenceUI.Wpf.Properties.Settings>
 +            <setting name="PrimarySoundDevice" serializeAs="String">
 +                <value>SoundMAX Digital Audio</value>
 +            </setting>
 +            <setting name="SecondarySoundDevice" serializeAs="String">
 +                <value>SoundMAX Digital Audio</value>
 +            </setting>
 +            <setting name="ShowLicenseAgreement" serializeAs="String">
 +                <value>False</value>
 +            </setting>
 +            <setting name="CallUpgrade" serializeAs="String">
 +                <value>False</value>
 +            </setting>
 +            <setting name="ShowTestPhonemeKeyboard" serializeAs="String">
 +                <value>True</value>
 +            </setting>
 +            <setting name="ShowSnrPhonemeKeyboard" serializeAs="String">
 +                <value>True</value>
 +            </setting>
 +        </AudigenceUI.Wpf.Properties.Settings>
 +    </userSettings>
 +</configuration>
 +</code>
  
 == Getting the Open Ear Response Correct == == Getting the Open Ear Response Correct ==
 +**Steve Armstrong says:**
 +
 Even with the correct receiver models neither Intricon's ''ethos.dll'' (or SoundDesigns ARK for that matter) will correctly predict the total sound pressure in the ear canal. Even with the correct receiver models neither Intricon's ''ethos.dll'' (or SoundDesigns ARK for that matter) will correctly predict the total sound pressure in the ear canal.
    
Line 11: Line 75:
 Ideally we would develop a model for that acoustic pathway as well, but as a start lets assume it is simply unity gain at all frequencies. Ideally we would develop a model for that acoustic pathway as well, but as a start lets assume it is simply unity gain at all frequencies.
    
-For the purposes of the on screen display we shold really sum these 2 effects together. The trick is that the summation can't be done with dBs, we have to convert back to linear pressure first, and needs to mean the RMS sum+For the purposes of the on screen display we should really sum these 2 effects together. The trick is that the summation can't be done with dBs. We have to convert back to linear pressure first, and needs to mean the RMS sum:
  
 <code vb>  <code vb>