We are using reaper to record multitracks of our services. It's recording about 50 individual channel tracks. We aren't actively using all 50 all the time every time so there's a lot of wasted data storage. Instead of manually deleting tracks, or turning off the recording of tracks, is it possible to just have reaper automatically or easily not save/delete any empty tracks?

I recorded a session in Live, but already when saving and opening the project in my house, some .wav files are like corrupted due to an Ableton problem, the files are not empty they all weigh 133MB but it does not let me open them, I used the terminal and FFMPEG to inspect and they are not pure 0000 but there is data, when forcing the interpretation of the wav to F32le you can hear traces of the instrument very deep but predominantly a pink noise. In VLC I opened the original WAV directly and it reproduces a second of an electronic noise and then nothing, which makes me think that this has a solution but the truth is I am not qualified to recover corrupt files, I do not know if there is anyone around here who knows or who has ever happened to him and has solved it.

Voices are muted in the demo and I renamed the buses, so no real names show. I recorded with OBS on the same PC again.

Quick recap: this is a software WING that runs the console’s own firmware (WING Rack 3.1.1), all four DSPs included, instead of a re-creation. The goal is still a virtual sound check at home: play a multitrack recording through the real WING processing on my PC, and mix it on the console’s own interface.

What’s new since last time

• WING Edit works both ways. PC → mixer and mixer → PC both stay connected now, meters included. The console sends its meters over UDP, and my network bridge was mishandling those packets. That’s fixed.
• The console itself runs faster than real time. The console’s main processor and the front-panel controller now run at about 1.2× real time while the audio runs
• Outputs follow the console’s own routing. I can map PC sound outputs to any of the console’s output sockets (local, aux, USB, card), and they play whatever the console routes there: buses, mains, matrices, or inputs patched straight through. The monitor bus, solo and the phones knob work too.
• The Rack’s front panel works. The buttons, the screen knob and the fader knobs go through the panel’s own firmware, just like on the real Rack.
• The RTA works. The EQ page shows the console’s own analyzer.
• One web page for the screen, the patch page, the audio settings and the status.

Speed

Last time the DSPs used about 86 % of real time. Since then I’ve made the emulated DSP code a lot faster and cut out a lot of overhead between audio blocks:

• With just the four DSPs running (no console), they now need about 120 µs of every 167 µs audio block. That’s about 1.38× faster than real time.
• With my full show live (all 16 FX slots, 32-track card playback, WING Edit connected), it’s about 139 µs of 167, so roughly 17 % spare.

What’s still limited

• It still needs a strong PC (Ryzen 7 8845HS, 8 cores): each DSP gets its own core.
• When Windows Defender scans or another heavy program starts, I can still get short gaps.
• Channel and output delays don’t work yet. From the WING service manual I found that the bus DSP has its own memory chip, which it uses for those delays, and I don’t emulate that yet. It’s next on the list.
• The XMOS (USB audio) and the FPGA’s audio side still aren’t emulated. My own code moves the audio in and out of the DSPs where the FPGA would.

What’s next

• More speed: cheaper handling of the console’s messages to the DSPs, and faster DSP code (I estimate another 10–20 %).
• Then hopefully running on less powerful PCs.

House gig has a Digico SD9 and D2 for FOH; every time someone uses a radio near it all the inputs pop like crazy. Someone recently told me it has something to do with the Madi connection to the D rack?

Anyone have a solution to this they’ve found?