Dangerous D-BOX Monitor Controller & Summing Box 2006-2019

8 channels at high level. (trim 4 o'clock) 8 channels at medium. (trim 11 o'clock) (I mix with the unit at 12 o'clock, -6 dB.) Probably won't matter capturing at 2 different levels, but you don't know til ya try... This is for a clean active circuit. Very transparent. For detail and a natural, open sound. Nothing drastic. Avoids the dull, claustrophobic ITB sound. Gives a wide, open soundstage. No added distortion or saturation. You can insert at the end of a mix to open things up without coloring the mix or having to dial everything in all over again. I've been mixing through it across my Group Sub-mixes from the beginning. Try this, first thing; when you receive a multitrack to mix, insert your summing across all the tracks and bounce/print it right then. Get it over with and don't think about it. Then begin mixing. TECHNICAL DETAILS 400 Epochs Ferrofish A32 A/D: CS5368 D/A: CS4365 The analog output stage uses RC4580 and OPA1664 op-amps. Original Silver D-Box Active summing, transformerless, no frills. Analog-only connections. Balanced line receivers (THAT 1240/1246) on all inputs. Summing op-amps (TI OPA2134) at the mix bus. Line drivers (THAT 1646). Low noise floor (< −89 dBu) The mix-bus circuitry is physically partitioned from the monitoring circuitry to keep crosstalk below −97 dB. TESTS I tested captures on a couple multitracks. It seems that the more channel models you insert across the tracks, the better - that includes utilizing both "MED" and "HIGH" captures across the tracks. (It works but there's probably no difference between MED and HIGH.) Consider omitting it on a couple of legato keyboard instruments that you want to sit further back in the mix. Apply summing where you want more detail. I compared two setups; AnalogX Genesis and Tone3000: I used the GPU mode with Genesis across 42 tracks. There were timing issues (not crackling or glitches) but difficulty maintaining synchronization. The instruments were drifting rhythmically. Genesis performed somewhat better when NOT using the GPU mode. This was totally alleviated by freezing the tracks. I didn't have the issue at all with Tone3000 across the same 42 tracks. Probably not the CPU but rather the plugin delay compensation reporting that was struggling. I am inclined to avoid Genesis on things you can't freeze like sends, groups, and the 2-bus - at least until I get a faster computer. Future Tests I want to try it on a second stage, both the groups and the tracks. Also might insert the same two channels across the whole song, to compare it against 8+ channels.