fix: metering should come from the first assigned channel (until mult…

…i channel metering is available)
olzzon · Jun 1, 2020 · 2c01de9 · 2c01de9
1 parent 47b54d2
commit 2c01de9
Showing 1 changed file with 8 additions and 5 deletions.
diff --git a/server/utils/mixerConnections/productSpecific/midas.ts b/server/utils/mixerConnections/productSpecific/midas.ts
@@ -24,22 +24,25 @@ export const midasMeter = (message: any) => {
         level = dataview.getFloat32(4 * i + DATA_OFFSET, true)
         reductionLevel = dataview.getFloat32(4 * (i + 64) + DATA_OFFSET, true)
 
-        vuMeters[state.channels[0].channel[i].assignedFader] = level
         store.dispatch({
             type: SET_VU_LEVEL,
             channel: state.channels[0].channel[i].assignedFader,
             level: level,
         })
-
         reductionLevel = 1 - reductionLevel
-        vuReductionMeters[
-            state.channels[0].channel[i].assignedFader
-        ] = reductionLevel
         store.dispatch({
             type: SET_VU_REDUCTION_LEVEL,
             channel: state.channels[0].channel[i].assignedFader,
             level: reductionLevel,
         })
+        if (
+            vuMeters[state.channels[0].channel[i].assignedFader] === undefined
+        ) {
+            vuMeters[state.channels[0].channel[i].assignedFader] = level
+            vuReductionMeters[
+                state.channels[0].channel[i].assignedFader
+            ] = reductionLevel
+        }
     }
     socketServer.emit(SOCKET_SET_ALL_VU, {
         vuMeters: vuMeters,