Unable to mix and master at 96kHz

Rat · May 22, 2019, 1:54am

bobybayo:

Rat:

I make the observation that there are a couple reasons to work at 96kHz that aren’t specifically linked to ‘hearing a difference’.

Firstly, for some labels and clients, the deliverable for MFiT/streaming is 96kHz 24 bit and you must not submit a file that is simply up-sampled. It follows that it is, from a practical perspective, necessary to work and process natively at 96kHz

Secondly, there are some hi end plugs (the DMG Equilibrium is one) that are audibly improved at 96kHz (compared to 48kHz) … probably a function of the way that it does not x2 on the incoming sample. The difference is not that subtle and if, like me, you work a lot in the box, this is typical of the small margins we are looking for.

I add that I work at 96 kHz on essentially every project, mostly ITB, and this has yet to present any WL ‘problems’ linked to the file being 96kHz. However, unlike some other posters, I am on a Windows 10 OS.

Rat, I agree with you.

Is there a perfomance monitor in Wavelab like the one on Reaper where you can see the real block size and adjust Buffer to meet the demand?

To be honest I’d have to check.

I have my system set up so that the meters are on a separate screen (for distraction reasons) and these include a bit meter. The RME AIO card has the buffer set so that the system doesn’t encounter ‘problems’. Like I said, I’ve not experienced a WL issue linked to a file being 96kHz.