Skip to main content

Recent Posts

Support - (fb2k) / Re: ReplayGain on Opus files
Last post by kode54 -
Oh god, I just realized what's causing it: VGMStream. I'll disable the .opus extension there and push another release shortly. E: Released, hit your update button or menu item.
Since Atmasphere can't seem to get his FLAC posted here, I'll just repost it. 13MB of wasted disk space on uploading a second copy, one he can't meddle with now that he's shared it.
File size - For uncompressed files, file size is simply the product of sample rate (kHz), bit depth (converted to bytes), number of channels, and the playing time.   As long as you know there at 8-bits in a byte, it's a straightforward calculation.     For example, CD audio is 44.1kHz, 16-bits, 2-channel stereo.   That's 44,100 samples per second x 2 bytes x 2 channels = 176,400 bytes per second, which works-out to about 10MB per minute.   A mono file will be half the size of a stereo file.  A 24-bit file is 50% bigger than a 16-bit file.  (An 8-Bit file would be half the size but probably unacceptable quality.)

A FLAC will be about 60% the size of the uncompressed original.    (You won't get as much compression with mono, but the mono starts-out smaller.)

I increase the volume to 999% (software limit)
I don't know what that means.   Most audio editors/tools (Audacity/GoldWave/Sox, etc.) have a normalize (maximize) function that adjusts the volume as high as possible without clipping  (distortion).     That's often not loud enough because one "loud peak" limits the volume of the entire program.  To get-around that, you can use limiting or dynamic compression to "push down" the peaks and then boost the overall volume.
 and continue with the conversion, doing math to calculate the highest bitrate possible that will still get me under or at 291 MB.

doing math to calculate the highest bitrate possible that will still get me under or at 291 MB
I'm not sure what you mean by that...  With FLAC you have very-little control over the bitrate, except that you can start with a lower-bitrate original (a lower sample, rate or lower bit-depth, etc.).

Support - (fb2k) / Re: ReplayGain on Opus files
Last post by Seymour -
Occurrence is not 1 by 1. Sometimes it starts normally, another time gives me a "low-level Opus mode".
Support - (fb2k) / Re: ReplayGain on Opus files
Last post by Seymour -
Tried disabling media library - removed all strings from music folder paths. Now Waveform Minibar (Mod) plugin doesn't remember waveforms, but a couple of restarts and the same situation - low Opus level, +5 dB RG scan result. And it's remarkable that every second restart shows the problem, and every other one - does not (everything seems ok then, level is normal, etc.).
Below down here is my components report.
Spoiler (click to show/hide)
Support - (fb2k) / Re: ReplayGain on Opus files
Last post by Seymour -
Okay, it happened again.
Opus files (it seems all but from yesterday event, unclear) have low level. RG scan gives strange +5 dB result, peak level shows value around 0.25.
ReplayGain scanner reports that the file already has RG info, but file properties (details tab) does not show any replaygain-related information. But somewhere, despite low-level output and +5 dB RG scan result, fb2k shows RG info in the details tab.
"Edit RG info" command always (as much as I checked) shows Track/Album-mode values.
Any suggestions?
Is there anybody, who can help me?
Thanks, Peter! I'll give this a look soon hopefully.
General Audio / Re: How to code with WASAPI ?
Last post by [JAZ] -
Then my last question, how can i know whether it needs a bottom-padding or top-padding ?
Is it up to the CPU (x86) or to the audio chip (Realtek)?

If I have to tell the truth, right now I don't remember.  Checking at my code, it seems that you need bottom padding. Also, remember that you're on little endian, so bottom padding means the first byte.
19:46:49 : 02/03  50.0%    << dog barked in my ear wanting to go out