Skip to main content
Recent Posts
General - (fb2k) / Re: New betas are coming but 1 sought-after feature is still missing...
Last post by Porcus -
what do you think about getting rid of the weeks part and just showing how many days of music you have? It fit more text in less space without dropping much of significant information I think.
As long as you don't remove the week in "DURING LAST 6 WEEKS" queries :-o

The presence of a "wk" highlights that a selection has more than seven days, and thus prevents me from misreading "11 days" as one day or "111 days" as eleven.  No big deal to me. (There must be people whose fb2k library need four digits for days though.)
Support - (fb2k) / Re: File operations are not sorted and it is impossible
Last post by Tropoje -
It works as advertised and it will be more accurate now, but why it is still not sorting alphabetically? The drop-down list is sorted (and was always), but context menu is not. What's the point? Conversion presets are sorted everywhere, for example. It is good that you can do anything manually in text file, but it is not good design to do something outside the app.
Now it is very good, you can set the display order in the context menu yourself. Just enter the order you are interested in to the file "FileOps-Presets.txt". In my opinion this is definitely a better solution than the alphabetical order.
General Audio / Re: Questions on "loudness wars" and/or bad CD engineering - doing a FLAClibrary
Last post by j7n -
Another source for general noisiness in loud albums is Clipping. It sounds like a few clicks during loudest monents, identifyable especially on bass or vocals, or a sustained crackle. Spectrally complex sections with multiple instruments sound like a fuzzy noise was mixed with them. Clipping is intentionally used because in many cases it is more transparent than a limiter, but this cannot be generalized to music with soft, pure sounds or human voice.

In waveform view, clipping looks like the top of the waveform was sliced off. It must be evaluated fully zoomed in on multiple loud sections. If the wave is scaled to fit in the range with a limiter, and has normal rounded peaks, then this is not clipping, and cannot be fixed.

In spectral view, clipping looks like a line at the top of the graph for each clipping event. Sustained clipping merges these lines into a band of high-frequency energy, which obstructs features in the original signal.

Unlike compression, clipping can be undone quite sucessfully by extrapolating the signal shape from surrounding data. But the tools for that are not free (free ones aren't very good). The best are Stereo Tool's declipper, and Izotope RX Elements.

For a spectral analyzer I like to use SoX. It is a free command line tool that can generate spectrograms and save them to disk for later viewing. The advantage is that I can scroll through the spectrogram quickly on a slower computer without waiting for it to be rebuilt, while looking a the waveform in another editor. Also, the zoom level can be fixed, which allows to compare spectra of multiple versions of a recording, quickly switching between them. Modern audio editors often have free zoom, and two windows are hard to align. SoX can be added to customizable front-ends, such as Frontah, to avoid using the command line.

Seeing fast amplitude changes on the spectrogram is not easy. To hear an exagerrated effect of a limiter, you could listen to the side/difference channel, subtracting left from right.
3rd Party Plugins - (fb2k) / Re: foo_midi
Last post by kode54 -
Dosbox resamples it from 49716Hz to whatever rate you have set, using a running average resampler. I resample using a sinc resampler.

It also depends on which Adlib emulator you're using. The "Nuclear Option" drivers use Nuked OPL3, while AdPlug uses the Dosbox "fast" emulator, mainly because it defaults to using 10 instances at once.
SimplePortal 1.0.0 RC1 © 2008-2018