Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
For example, the top of the Y axis (-6db) cannot be displayed any further.
Is it something like this?
First, I had thought CVBR mode generated consistent results and it was only TVBR that didn't, but further testing has revealed that's not necessarily the case. In fact, I found a file for which all modes generate inconsistent, multiple-variant output.
That discovery prompted me to install iTunes (which as far as I recalled has only CVBR and ABR modes) in a VM and test it directly instead of using QAAC. Both modes showed the same inconsistent behavior with this particular file.
So, ultimately, the seemingly odd behavior I encountered just appears to be how Apple's encoder works. I still can't shake the feeling that it's a bit weird, especially considering how other encoders are totally consistent. but it is what it is.
X axis is OK. There is still a problem with the Y axis.Erhm... the Y-axis is right there in your screenshot. What do you mean by: "how do I use it?"
Hmm, how do I use it?
- fb2k v2 is now required.
- Best run in a new portable installation.
- Configuration is not v1.0 backward compatible.
- Dark mode.
- 'Hide header' is no longer available in context menus.
- Issues related to enabling/disabling columns and column auto-resize.
I will review the latest posts after a short break...
Download: Queue Editor v2.0 beta
I hope you like it... thanks for your feedback!
Using different Windows DPI setting than 100% clips the contents of the window and things are only partially visible. At least here easily reproducible.It's not here. I just switched one of my screens to 125%, created a new tab and added a new instance of the element. Perfect sizing from the start.
As mentioned here, this is the standard specification.
I was able to display it.
X axis is OK. There is still a problem with the Y axis.
Hmm, how do I use it?
I am glad you liked it...
thanks a lot for your feedback!
Regarding your second paragraph, I can't quite visualize your methods for preventing IS distortion problems. But I'm hoping that IF I'm ultimately unable or choose not to pursue software based room correction that Porcus's Foobar/Replay Gain solution will solve my IS distortion issues where extant in my music sources. But tutorials for dummies would be essential.ReplayGain data is collected by scanning the source materials without taking room correction into account.
Because you are doing room correction and room correction is basically a customized EQ applied to the source. After room correction the waveform will change and ReplayGain peak values based on the source cannot precisely reflect the peak values after room correction.
If you still want to do it in the RG way you will need to store the room corrected audio data into a separate set of audio files using a lossless floating point PCM format, then perform RG scan on these floating point files to find the actual, room corrected peaks.
Hopefully you already understand the differences between sample over and intersample over. Headroom in the DAC can only mitigate intersample over, not sample over, and room correction can introduce sample over. Regarding the Gearspace thread you pointed to, the OP of the thread (Ian) in fact confused about different types of over and made a clarification:
If you are doing room correction on the fly, then you are sending the room corrected audio data to the audio driver, and even my cheapo Sound Blaster has a realtime meter to monitor the room corrected input level to the device driver. Basically, you just lower the software playback level to the device driver so that the meter peaks at several dBs below full scale and the job of preventing intersample over is done.
With your first paragraph, I've never read about much less encountered anything with ADAT connectivity and don't know how it would be applicable for equalizing my system to my room. https://emastered.com/blog/what-is-adat Among other things, what I don't get is how Kal Rubinson seemed able to steer clear of all or most of the connectivity issues raised, plus without any temporary or permanent use of multiple ADC channels (beyond the one for making microphone test recordings) and yet have complete success implementing DIRAC Live 3 RC . Indeed, save for whatever mic/preamp/ADC/USB hardware he needed to run DIRAC mic test signal measurement recordings for his main speakers and subs (Revel and SVS all passively crossed I think), this Exasound e38MK2 eight-channel DAC was the only converter I read about which remained in his system, at least for MCH playback. https://www.stereophile.com/content/music-round-85-nimitra-exasound-baetis-roonSynchronization is required only if you want to operate two independent devices simultaneously with one clock source. It is not required if you only use the ADC to capture a room correction profile and use the profile during playback. I just wanted to point out USB has no role on syncing two independent devices.
The only thing Kal did find was that use of DIRAC imposed nearly a 20db gain loss when he reviewed and used this DAC for room correction. https://www.stereophile.com/content/okto-research-dac8-pro-da-processor To make up for that loss he resorted to the rather clunky solution of installing three of these stereo preamps. https://www.stereophile.com/content/topping-pre90-line-preamplifier
But I still wish I could understand how Kal apparently achieved system/room eq if he did not have to contend the connectivity protocols you describe or what he did to circumvent those issues. https://www.audiosciencereview.com/forum/index.php?threads/audiopraise-vanitypro-review-hdmi-audio-extractor.30440/page-14