@j7n: Oh... I see. You are probably right: 176000 /44100 = 3.99 (so, sample understood as individual sample, not as a sample frame)
Last post by Rollin -
It's a DSD512 DFF file (22 579 200 Hz / 1 bit). According to Rollin it was converted with WavPack 5, which is now able to losslessly compress DSD. And even if foobar2000 can't read DSD, the WavPack library automatically transforms DSD files to PCM at ultra-high resolution for compatibility reason.It WAS DSD512 DFF file. Then it was encoded with wavpack, then it was decoded to PCM with foobar2000's native wavpack decoder. So, finally, it is simple PCM wav with 16 bit 2822400 Hz.
Anyway i am satisfied with response from Peter.
Last post by lvqcl -
in the Opus encoder, in the advanced settings (Edit) - Display - Settings:, it always shows VBR for every settingI can also see 'CBR' or 'constrained VBR' in encoder settings.
Development - (fb2k) / Re: Not sure where to start in developing a plugin, documentation is fairly limitedLast post by ADAMPOKE111 -
Thanks for the help! There's lots of configurations in the foo_sample project that I found need to be copied over to any other plugin you're writing: the compiler option needed to be switched from /MD to /MT in my case - fixed issues when compiling. I also found out there's lots of plugins on GitHub whose code you can look through and get a grasp of what's going on, the foosion subdomain of foobar2000's website is also quite helpful even if it was originally written for the 0.9.x SDK.
Even with the improvements, FAAC is still probably not the best choice.It was true as of 184.108.40.206.
Development - (fb2k) / Re: Not sure where to start in developing a plugin, documentation is fairly limitedLast post by Peter -
The foobar2000 SDK, version 2015-08-03 is compatible with the latest version of Visual Studio 2017 at this time - I just tested it myself.
There was a period in which Visual Studio auto updater would give you broken platform SDK which made lots of my code fail to compile due to Windows.h vs WinSock #include order issues. This appears to have been fixed on their end.
You can load foo_sample workspace into VS2017, retarget to the new toolchain (original projects are VS2010), optionally enable -XP version of the toolchain in project settings, enable /d2notypeopt as per this thread and you're good to go.
foo_sample demonstrates most commonly used parts of foobar2000 SDK, it's a good starting point to learn how the SDK works. Also don't forget to check the readme doc first, it has lots of essential info on SDK architecture.
Last post by eahm -
Peter, another thing, in the Opus encoder, in the advanced settings (Edit) - Display - Settings:, it always shows VBR for every setting, can you please change that as well to make it more precise. In other words, I know which encoder settings I am saving and selecting from the list but I always want to double check I didn't make any errors selecting the correct one. I know I can and they are modified manually now but I rather see that in the default installation. Thanks.
Last post by 西门浪子哥 -
Thank you , always use your script!
Have been ripping same Daemon Tools Images with EAC v1.3. They remain in the list as "DiskSoftVirtual 1.0 Adapter 1 ID:x"
where x seems to increase each time, and they all stay in the drop down list. Is there any way to remove them?