- #Foobar2000 graphic equalizer presets xgeq how to
- #Foobar2000 graphic equalizer presets xgeq manual
- #Foobar2000 graphic equalizer presets xgeq code
- #Foobar2000 graphic equalizer presets xgeq license
- #Foobar2000 graphic equalizer presets xgeq Offline
In this thread, I proposed to use the SoX resampler both for real-time monitoring the mix and for offline rendering.
#Foobar2000 graphic equalizer presets xgeq how to
I am trying to figure out how to handle overshoots in the feature request I plan to submit in the REAPER Issue Tracker.
#Foobar2000 graphic equalizer presets xgeq code
Any forum member knowledgeable enough about building and testing C code willing to find out about libsox and libsoxr?įor resampling, the difference between libsox and libsoxr is that libsoxr is for real-time only (and therefore smaller and simpler), while libsox also supports offline processing, which includes a guard against clipping of overshoots (automatic gain adjustment). I don't know if stand-alone SoX is using 32-bit fixed-point I/O for speed, or if libsox and libsoxr behave as above - even with 64-bit floating-point I/O. Looking at the code, I see that libsox and libsoxr support 64-bit floating-point I/O. I recall reading somewhere that stand-alone SoX uses 32-bit fixed-point for I/O internally, and this behavior agrees with that. Again, I found that SoX clipped the overshoots at 0dBFS. I also used SoX to sample-rate convert a full-scale (0dBFS) 100-Hz square wave. I found that SoX clipped the output at 0dBFS. I created with REAPER a 100-Hz sine wave with peaks at +6dBFS. I tested the stand-alone/command-line SoX application with 64-bit floating-point input files and 32-bit floating-point output files (stand-alone SoX v14.4.1 has a bug preventing output to 64-bit). It may work well in something like Foobar that only has one file to playback at a time, but would be a much more complicated thing to do in something like Reaper that could have hundreds of files playing at once.)
#Foobar2000 graphic equalizer presets xgeq license
It's curious though how the SOX licensing has went for the Foobar plugin.Foobar is also a closed source application, so the SOX library doesn't seem like a "clean" fit there.Perhaps the plugin developer has simply decided not to care about the licensing implications? Or it's actually the SOX developer himself who has done the plugin? Or a friend of his? (The GPL license could also be circumvented by doing interprocess communication but that would hardly be a good choice for something like Reaper.
ZPlane on the other hand is a commercial company that doesn't to my knowledge even license source code at all, only binaries. There probably isn't a more commercial applications hostile license in existence than the GPL. Good work, also re GPL I thought that the z-plane elastique was GPL so using SoX would be no different. Do I understand correctly that Cockos would need to do this (as opposed to the REAPER community)? Since SoX has a GPL license, a GPL (free) REAPER plugin to add SoX resampler functionality may be the way to go. After all, this applies to rendering too. The point I am making is that SoX audio performance is at least as good as REAPER's Extreme mode, yet SoX is 100 times more efficient in CPU! Other than the effort it takes to add the SoX resampler option to REAPER, I can't see why REAPER wouldn't be better off with a resampler that is 100 times more efficient. I don't want to debate the audibility of aliasing in this thread. When I compare the audio performance of SoX 14.4 VHQ modes to REAPER's resampler at, SoX has significantly less aliasing. I changed "Playback resample mode" to Best, and my CPU showed 50% during playback. In the Project Settings menu, I set "Playback resample mode" to Extreme, and my CPU showed 100% during playback of the same 44k WAV file. In the Options|Preferences|Audio|Device menu, I set "Request sample rate" to 192k and unchecked "Allow projects to override device sample rate". Here is my test with REAPER to do the same thing. Every 10 seconds or so, the CPU jumps to 2%. With quality=best and output rate=192k on the SoX plugin, using either the ASIO or WASAPI exclusive-mode output, my Intel Core-i5 CPU sees only a 1% load while I listen to a 44k 24-bit stereo WAV file in foobar2000.
#Foobar2000 graphic equalizer presets xgeq manual
Since using the internal clock source requires manual selection of the sample rate, I would like to leave it at 192k and have REAPER handle the resampling.įoobar2000 with the open-source SoX resampler plugin ( ) shows that my wish is practical. I plan to buy a Lynx Hilo, and its internal clock source has significantly less jitter than the USB clock. One reason is the my soundcard internally runs at 192k, it doesn't support 88k or 176k, it internally resamples the other rates to 192k, and especially its 44k resampling degrades the naturalness on my recordings of the autoharp compared to the SoX resampler. I would like REAPER to always drive my output device at a sample rate 192k and resample 44k, 48k, 88k, 96k and 176k rates.