Now what happens if I rotate the speaker position slightly towards the right side and by doing so saving my left ear a little bit extra? First thing that happens is that I had to readjust the distance between left and right a bit. I've done about an hour of listening per 10° and so far I think that a setting around 20° is what I prefer. It seems to work well to start with.ĭay1: I've quickly realized that a front speaker position of 60° is not going to work for me with any hard panned stereo recording. To avoid clipping I've set the Output Gain on -3. They keep their position in relation to each other, but the sound projection against where you sit is changed. There's another setting called Rotate in which the speaker pair can be moved around 360°. My left ear is borderline hyperacusis so I'm trying to find a speaker position setting where hard panned stereo sounds "natural" and not flat/dead as I sometimes get from mono yet bearable for my ear(s). I'll work myself towards 60° and stop wherever I can find it bearable. I'm coming from a preference of MONO in which the setting for speaker position is 0° so that's where I started. Speaker position defaults at 60° and Waves recommends that you keep it at that to start with. You can create "distance" between your head and the recording. Room Ambience setting defaults on 17 and I've left it like that for now. You can click on the ? in the top right of the Head Modeling setting to see how you're supposed to measure your head and why.Īfter that you're basically positioning the artist(s) in relation to each other and in relation to where you sit. The different versions (Stereo, 5.1, 7.1) will land on top of each other, so you need to move them around and/or remove them to get the view as seen below. Once you chose "Load plugin", you navigate to the Waves dll file and it loads within the wrapper. This is the demo version, I haven't bought the full version yet. It's needed for Waves NX to work with a dedicated playback software.Īs you can see I've loaded NX into the wrapper and then I'm just sending audio L and audio R through Waves. Here's the Metaplugin wrapper loaded into the jRiver DSP.
I'm quite sure I won't stay with the factory defaults, well maybe with Room Ambience, that's one insane setting to play with. I'll keep filling in findings here throughout next week but the initial experience is.holy shit! How the hell can I go back from this?! Opportunity: that this solution is the final solution towards living with my jazz collection without having to mix to mono and sometimes suffer from dull/flat/dead music. Risk: that I like it so much that I feel forced to file a divorce with Roon only a few days after the launch of 1.3 which allows for album art/booklets to be viewed within the software - one of the greatest updates in playback software history.
Being forced to always listen to a pure mono mixdown which sometimes causes otherwise very dynamic and lively recordings to fall flat and die. Single side ear death, fatigue, anger, rage, gear abuse and tears.Ģ. My purpose of this test is to first and foremost try to investigate whether a close to mono crossover will allow my ears to enjoy hard panned stereo recordings without:ġ. Second round with same SW setup + ModiMB -> Spdif converter -> Vali2 -> Beyerdynamic T5P. This is still the case in W9 Pro however as there are a whole bunch of lovely meters, I would like to use them! The issue being (as described here: ) the monitoring point can’t be changed to allow the monitoring meters to reflect the signal pre-Room Correction EQ VSTs.Click to expand.Test notes using Metaplugin + WavesNX + JRiver Media Center with Lynx AES16 - Yggdrasil -> Mjolnir2 -> HD800 (stock balanced cable, no mods). I was using this in Wavelab 6 and worked extremely well for my needs. I use (as many people do nowadays it seems) Waves NX -> Sonarworks for Headphone room simulation and eq correction. I have just upgraded to W9 Pro from 6… And very pleased indeed with improved performance and workflow.
0 kommentar(er)
