I am left behind with one big question: Is my meassurement useable, it is good or bad?Ĭompare this to the meassurement module in Audiolense: It will tell you three things: a) Average/Good/Excellent Dynamic Range, b) a value for dynamic range i dB, and c) a graph showing the loudest part to check for clipping.
Dirac live alternative software#
Unfortunately it was rather fustrating: The software tells me not to use excessive loudness and then shows some strange values without any explanation when meassurement is done. Maybe I would have gotten back to him again if the experience with the meassurement software had been a good one. Great, the author does not know his own software! Turns out I could not use the meassurement software after all and needed a special version of Acourate.
Dirac live alternative how to#
After spending hours tring to figure out how to do a multi-channel meassurement I gave up and wrote back to him. I was to load a special crossover file into the meassurement software and send the meassurement to him. I did not get one, but he agreed to prepare two tracks for me.
As I have a software crossover in combination with room correction, I wrote to Uli for a special XO trial.
Dirac live alternative trial#
And what is the chance of Uli choosing a target curve that is great for your system/room? Surely a proper trial involves the user fiddling with the target himself. But most people will need a little time to get used to the corrected sound before making any buying decision. We can probably easily tell that there is a difference between corrected and uncorrected sound. Even if the meassurement turns out well, two tracks are not enough. Expect the first meassurement to be far from optimal and have a negative effect on the result. You need the right microphone, a stand, something stable to place the stand on, the right spot to meassure, the right playback and recording levels, and you need to make sure objects in the room does not play along. You cannot expect anyone without prior experience to make a good meassurement. Now if we can just get the audio path to display what's going on so that convoluted test routines aren't required. This is a huge step forward for users of JRiver. (3) Setting Convolution to "on" on the DSP Studio Page and loading all the convolution files one by one and after each one playing a file with the corresponding sample rate of the filter just loaded note using "no change" also worked, but only after using one of the prior settings (2) Setting Output Format to 44.1 for all input sample rates on the DSP Studio Page, OR, setting each input sample rate to have an identical output sample rate (and checking the Output Format box). (1) Setting "Sample Rate Same As Source" on the Advanced page of the DLNA Servers Page Each had a unique shape so that I could use an RTA to see which filter was actually being used. I created convolution filters for 44k, 88k, 176k, and 192k. I have been able to confirm that in the latest build convolution works for alternative (varying) sample rates.
0 kommentar(er)
