Skip to main content ↑ ↓

Notice

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.
Recent Posts
11
3rd Party Plugins - (fb2k) / Re: foo_enhanced_spectrum_analyzer
Last post by TF3RDL -
Quote from: darkflame23 on
Another weird one, it seems to lag significantly behind the audio, what's the setting I need to adjust to get it in sync with the music?
While there is no such thing as "Reaction alignment" parameter as in foo_vis_spectrum_analyzer, you can lower the FFT size to 4096 or lower to get better sync through it loses the frequency resolution and also, the amount of delay ahead actual playback in proportion of FFT size parameter is exactly the same as this relevant CodePen project with something like "delay compensation" enabled

BTW, I would assume that if IIR filter bank mode is added, the filter bank-based musical spectrum doesn't have this problem of lagging behind the audio and have equal resolution for all frequencies in logarithmic frequency scale
14
3rd Party Plugins - (fb2k) / Re: Georgia-ReBORN - A Clean foobar2000 Theme
Last post by TT -
@regor,

sorry for the confusion and never mind. I just tried a too unrealistic/aggressive approach just to illustrate the issue
that it should be gracefully handled by foobar itself when exiting abruptly during HTTP requests...

Your approach works just fine and is the correct way to handle this situation, we don't even need the safeguard
at the beginning of bioSend, I have tested it and it works just fine. As you pointed out:
Quote
there is a small window of time between the shutdown request and the actual shutdown and you have to use that.
With my unrealistic/aggressive approach it failed  ;)

Anyways, all is good, thx for that regor =)
Btw, can you add your workaround here:
https://github.com/Wil-B/Biography/pull/7 or make a new PR for WilB?

@Majestyk, I have already made a commit here:
https://github.com/TT-ReBORN/Georgia-ReBORN/commit/7032ff781487054a368cbd6f42cea521a932b4a8

-TT
15
Other Lossy Codecs / Re: How to add new modes in WMA 9.2?
Last post by Apesbrain -
You could do it via commandline:
Code: [Select]
cscript.exe wmcmd.vbs –input inputfile.wav –output outputfile.wma -a_mode 0 –a_setting 56_44_2
-a_mode mode_number
Specifies the encoding mode for audio content. You can use one- or two-pass CBR encoding (-a_mode 0 or -a_mode 1, respectively), or a VBR encoding encoding mode: quality-based (-a_mode 2), bit rate-based (-a_mode 3), or peak bit rate-based (-a_mode 4). For more information, see Using CBR or VBR encoding.

-a_setting bitrate_samplerate_channel
Specifies the audio bit rate, sample rate, and channel setting for encoding. Or, if you are using the Windows Media Audio 9 Professional or Windows Media Audio 9 Lossless codecs, -a_setting also specifies 16- or 24-bit encoding, as bitrate_samplerate_channel_bitspersample. Use the -a_formats option to view the settings supported for each codec. If you are using the Windows Media Audio 9 Voice codec, the default value is 12_16_1. If you are using the Windows Media Audio 9 Professional codec, the default value is 128_44_2_24 (unless you are also implementing a quality-based VBR session, in which case the default is Q75_44_2_24.) If you are using the Windows Media Audio 9 Lossless codec, the default is Q100_44_2_16. If you are encoding uncompressed content, the default value is 705_22_2. For all other scenarios, the default value is 64_44_2.
18
MP3 - General / Re: Resurrecting/Preserving the Helix MP3 encoder
Last post by ha7pro -
Quote from: maikmerten on
Okay, I now threw out the 8-bit resampling code - now all sample formats are handled by the same 32-bit float resampling/conversion steps. https://github.com/maikmerten/hmp3/commit/a07d35c3dbe5acb22e1301c27df2dfe92dccb908

I also adjusted the Makefile and VisualStudio project files (by hand). Seems the automated builds on AppVeyor still work ( https://ci.appveyor.com/project/maikmerten/hmp3/builds/49846828/artifacts ), so I assume the VisualStudio project file surgery went okay.

thanks !!!