<?xml version="1.0"?>
<ArrayOfFBEvent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-08-24T00:14:52Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-18T22:24:35Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Tested  Other filter ratios/ filter rates with each version of datapro ...


Tested a slice Pro sim  that AAF is set to max in realtime with Turn off realtime aaf enabled , in the config file and  when this is not enabled , realtime AAF is set to ...

	Testing with non default  AAF settings/ Ratios  by setting in system settings ..

 													
See attached Spreadsheet for complete test coverage performed...


		
														
														
														
														
														
														
														
														
														
														


</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-06-18T21:28:18Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-18T20:12:17Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-18T20:12:06Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-18T16:18:17Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-06-18T16:17:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Chris  I did adjust some of the Sample Rate/ AAF rates in the datapro  system settings, and confirmed they changed  on the das so the ratio was no longer 1/5  , And checked the filter cutoff  -3db point in netview to verify ..
but I can do more testing if needed .
</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-18T16:15:44Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-06-17T23:57:24Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment />
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-06-17T23:57:11Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Chris Balogh</User>
    <Comment>SQA should prove that the AAF rates in a streaming test match the table in system settings rather than verifying the ratio. Probably can do this by adjusting one aaf to sample rate combination and testing since Justin did nearly the whole default table already.

I would propose defaulting the TurnOffAAFRealitme to false because of Loc Pham's suggestion that the SLICE PRO bug has been fixed for quite some time now. SQA needs to prove that performance of real-time is no longer degraded when applying the adjustable AAF during RT on SLICE PRO before and after his fix in FW.

I would recommend leaving the 1:1 ratio as is for RT and confirm we're indeed using that ratio vs the sample rate to AAF table in system settings.
</Comment>
    <StatusString>Reopened</StatusString>
    <TimeStamp>2024-06-17T23:56:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Tested this case with Datapro versions 4.0.1164.50884 ,4.2.440.50920,4.3.206.50891

Tested By creating a test setup  with streaming  checkbox checked...
1. In diagnostics the AAF filter is set to 1/5 the sample rate and when arming  also
2. The Realtime Rate  = the sample rate  set in test setup , confirmed this by the datapro log file and arm attribute 17 .
3. The AAF filter rate in diagnostics and arm step is 1/5 of the  realtime rate  ( this can be changed in system setting Slice AAF rates however) . Confirmed this by checking datapro logs and checking Arm Attr 17 and 18 using FWTU.
4. Armed S6A in streaming mode at various sample rates ( see attached chart) and verified  the AAF filter was set as expected for each sample rate by injecting a  signal and checking in netview for the  filter cutoff, also checked the  Arm Attr  17 and 18 and the datapro Log For the RealtimeAAFilter and RealtimeRate


5. For Tsr Air , the  realtime sample rate attributes arm attr# 17 and 18 are fixed at 1000 and  40  , and dont change with the set sample rate  in streaming mode.. , the diagnostic rates  arm attr 23 and 24 do change when setting the sample rate and  the aaf rate attr 24 is 1/5 of diagnostic rate.

Not sure that is the expected result in that case for Tsr Air or not, but Eric mentioned TSR Air has a fixed realtime rate in attr 17 , and I dont  see datapor setting that attribute in the logs.





</Comment>
    <StatusString>Closed</StatusString>
    <TimeStamp>2024-06-17T23:31:12Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Closed</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-17T23:06:30Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>it appears that the design is to run realtime at 1:1 AAF when not running abiding by the "turn off aaf for realtime",
 
however this shouldn't affect streaming as it is using the arm aaf, which is not at 1:1
 
notified chris of this to get feedback.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-06-17T23:05:05Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-17T23:02:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>it looks like the default ratio for realtime aaf is 1:1
 
 
been that way for a _log_ time</Comment>
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-17T23:00:49Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment>Tested this case with Datapro versions 4.0.1164.50884 ,4.2.440.50920,4.3.206.50891  Noticed that when in realtime step in Datapro , the sample rate is set to 1000 and the AAF filter rate is also 1000 , shouldnt the  filter be set to 1/5 of sample rate at this step also?





Tested By creating a test setup  with streaming  checkbox checked...
1. In diagnostics the AAF filter is set to 1/5 the sample rate and when arming  also/
2. The Realtime Rate  = the sample rate   set in test setup , confirmed this by the datapro log file and arm attribute 17 .
3. The AAF filter rate in diagnostics and arm step is 1/5 of the  realtime rate  ( this can be changed in system setting Slice AAF rates however) . Confirmed this by checking datapro logs and checking Arm Attr 17 and 18 using FWTU.
4. Armed S6A in streaming mode at various sample rates ( see attached chart) and verified  the AAF filter was set as expected for ach sample rate by injecting a  signal and checking in netview for the  filter cutoff, also checked the  Arm Attr  17 and 18  


5. For Tsr Air , the  realtime sample rate attributes arm attr# 17 and 18 are fixed at 1000 and  40  , and dont change with the set sample rate   in streaming mode.. , the diagnostic rates   arm attr 23 and 24 do change when setting the sample rate and  the aaf rate attr 24 is 1/5 of diagnostic rate.

Not sure that is the expected result in that case for Tsr Air or not, but Eric mentioned TSR Air has a fixed realtime rate in attr 17 , and I dont  see datapor setting that attribute in the logs.



TO Reproduce issue with  S6A sample rate  in datapro realtime mode:

1.Create Test setup set to streaming  add some channels.
2.Run test through diagnostics and then run realtime step.
3. Search datapro log for the last entry RealtimeAAFilter and RealtimeSampleRate 
4. Notice  the in the last entry in the log  they are both set to 1000 , I would expect the AAF to be 1/5 of the sample rate   here...



 2024-06-17 15:34:18.729 -&gt;  Attribute - SetArmAttribute [00000269], S6A0772, local: 192.168.1.20:52306, Remote: 192.168.4.50:8301 Key: RealtimeSampleRate, DataType: UInt32, Length: 4, Overwrite: True, Value: 1000
 
2024-06-17 15:34:18.732 &lt;-  Attribute - SetArmAttribute [00000269]\[00000269] - (3.0027ms), S6A0772
 
2024-06-17 15:34:18.732 -&gt;  Attribute - SetArmAttribute [00000270], S6A0772, local: 192.168.1.20:52306, Remote: 192.168.4.50:8301 Key: RealtimeAAFilterFrequencyHz, DataType: Float32, Length: 4, Overwrite: True, Value: 1000











</Comment>
    <StatusString>Reactivated</StatusString>
    <TimeStamp>2024-06-17T22:40:32Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Reactivated</Status>
  </FBEvent>
  <FBEvent>
    <User>Justin Richardson</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-06-14T16:20:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-06-11T22:50:51Z</TimeStamp>
    <ReleaseNote>Corrects an issue where the wrong AAF could be used for streaming</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>ReleaseNoted</StatusString>
    <TimeStamp>2024-06-11T22:50:20Z</TimeStamp>
    <ReleaseNote>the "TurnOffAAFRealtime" feature is only used for S6 now</ReleaseNote>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-05T21:48:23Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-05T21:36:14Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-05T20:46:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>4.0/4.2/4.3@50861
 
This setting is on by default, the patch doesn't change this, nor should it change the behavior for SLICE1 and SLICE2 DAS.
 
if you run realtime with these das it should set the realtime sample rate to the MAXAAF, for SLICE2 that is 100,000hz normally.
 
this should be true before or after the patch, however SLICE6 and SLICE6AIR and TSR AIR should now have 1/5 of realtime sample rate as their requested AAF in realtime, you can check this by looking in the log for the attribute: RealtimeAAFilterFrequencyHz
 
these AAF changes should also be applied to S6A that are set for streaming only recording modes.
 
if there are relevant realtime performance tests for DAS, I would consider running those too.</Comment>
    <StatusString>Resolved</StatusString>
    <TimeStamp>2024-06-05T20:45:34Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Resolved</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-06-05T15:33:37Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-06-04T20:26:38Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-05-21T21:58:51Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-05-21T20:31:08Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Edited</StatusString>
    <TimeStamp>2024-05-21T20:12:36Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment />
    <StatusString>Assigned</StatusString>
    <TimeStamp>2024-05-21T17:21:44Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>UNKNOWN</Status>
  </FBEvent>
  <FBEvent>
    <User>Dan McFadden</User>
    <Comment>If you configure a S6A to do streaming at 100 sps you can see unexpected output.  This was tracked down to the setting RealtimeAAFilterFrequencyHz
 
 
this attribute is set in two places, one is in realtime with devices that support inidividual channel realtime streaming, and in SetStreamingRealtimeSampleRate.
 
In SetStreamingRealtimeSampleRate it's only being set for recording mode S6A streaming mode only:
 
                //we don't need to set the realtime sample rate for record and stream recording modes, they won't use it
                 if (DFConstantsAndEnums.RecordingMode.S6A_DeviceStreamingOnly ==
                     ConfigData.Modules[0].RecordingMode &amp;&amp;
                     IsCommandSupported(DFConstantsAndEnums.ProtocolLimitedCommands.SetRealtimeSampleRate))
 
and not all streaming modes:
 
        private static readonly HashSet&lt;RecordingModes&gt; _streamModes = new HashSet&lt;RecordingModes&gt;()
         {
             RecordingModes.CircularBufferAndStreamSubSample,
             RecordingModes.RecorderAndStreamSubSample,
             RecordingModes.S6A_DeviceStreamingOnly,
             RecordingModes.Streaming,
             RecordingModes.HybridAndStream,
             RecordingModes.MultipleEventCircularBufferAndStream,
             RecordingModes.MultipleEventRecorderAndStream,
             RecordingModes.MultipleEventHybridAndStream
         };
 
further the freqeuency chosen for the AAF is relevant, if turn off aaf realtime is selected then it will set the value to the max available;
 
                    var aafRate = info.TurnOffAAFRealtime
                         ? MaxAAFilterRateHz
                         : ConfigData.Modules[0].AAFilterRateHz;
 
this appears to be what happens with the S6A
 
the max available was done to turn off AAF for responsiveness, case 16520 goes into that a bit.
 
related case 16520
 
this function SetStreamingRealtimeSampleRate should apply the sample rate for all streaming modes (the stream and record sample modes won't use it, but it's fine to set), and for S6 and beyond we don't need to use the info.TurnOffAAFRealtime logic either.
 
SetStreamingRealtimeSampleRate is virtual so it's easy to override it but there's work to be done here to make sure 
 
1) S6 and all devices remain just as responsive in realtime before and after
 
2) we don't turn the realtimesample rate to max for S6 and beyond</Comment>
    <StatusString>Opened</StatusString>
    <TimeStamp>2024-05-21T17:21:44Z</TimeStamp>
    <ZendeskNumber>0</ZendeskNumber>
    <Status>Opened</Status>
  </FBEvent>
</ArrayOfFBEvent>