Reaper Audio

Before you jump to any conclusions, you need to do a null test. Take your master mix from both DAW's, invert the phase of one and see how much signal is left when you mix them. Another thing to try is to take your PT stereo mix and bring it into Reaper in the same session as your multitrack Reaper session and solo/mute the two mixes that way. And take your Reper mix into the PT session and play that. Usually comparison problems are due to not knowing how to compensate for the pan laws of different DAW's.

Here we go again. :D Change the pan law in REAPER to -2.5. REAPER and Pro Tools null out 100%...even through ReWire with automation, including running through the same plug-ins ;): Shane

Just was about to ask: Didn't we have these discussions umpteen times before? We all know the answer. Maybe someone cares to assemble a list of links to threads dealing with this. -Data

I second a PAN LAW check and a PROJECT vs FILES' SAMPLERATE check. I saw so many people falling into the second one.... Being able to drop any file format into the arrangment without warnings is a great Reaper's feature, but the default settings for resampling on the fly are low quality.

All DAWs sound the same, with the same pan law, dithering etc. setting. Except SAWstudio. That one is more "analog". :P

Reaper stores the 1s and 0s in a Truetype font, so the sound is smoother.

Step 1) Render a mix from PT Step 2) Render the same mix from Reaper (match levels, panning, etc.) Step 3) Load the renders as tracks in the DAW of your choice, invert the polarity on one of them. Step 4) Look at your master level. If it reads -inf, then it's all in your head. If it reads a signal, either you did something wrong, or you might have actually stumbled on something. Until you do this, I don't believe you. Optional, but will really help your case: Step 5) Get Step 6) Get the for FB2k (unzip to Program Files\foobar2000\components) Step 7) Load the mixes into FB2k, select them both, right click, utilities->ABX Two Tracks Step 8) Keep going until the "Probability that you were guessing" goes under 5%, or you give up. EVERY trial counts, you do not get to scrap earlier trials and try again!

Asolutely :D just follow Analogy's steps 1-4 it will take you 10 minutes and you'll have your answer staring you in the face :) MC

I guess this is round 2. :D Here are two very extreme and over the top benchmarks and null tests: even through ReWire with automation: , even through ReWire: When a signal nulls, it is 100% identical. Shane

Honestly, i think this concern is genuine, but having taken part in the big daw null test a while back, im sure whatevers causing it can be tracked down to a setting or two somewhere (as recently occurred over here...). So, i suggest you upload your project files (just the .rpp, dont need the audio, but feel free to include it if you like) for both reaper and protools so we can take a close look and identify where things may be set different.