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
1
Speech Codecs / No ACELP.KELVIN encoder!
Last post by MihaiPopa12346 -
Hello, I heard about this format: ACELP.KELVIN
It's like ACELP.net but it also supports stereo encoding.
Searched "ACELP.KELVIN encoder", but no luck. :-X
This is the stereo file:
Quote from: Google Cloud (https://cloud.google.com/blog/products/ai-machine-learning/using-ffmpeg-with-google-cloud-speech-to-text)
Stream #0:0: Audio: acelp.kelvin (5[1][0][0] / 0x0135), 8000 Hz, 2 channels, s16p, 17 kb/s
This is the mono file on MediaInfo:
Quote from: MediaInfo
General
Complete name               : E:\Sample files\format-0x135-Roligt_samtal.wav
Format                      : Wave
Format settings             : WaveFormatEx
File size                   : 175 KiB
Duration                    : 2 min 44 s
Overall bit rate            : 8 723 b/s

Audio
Format                      : KELVIN
Codec ID                    : 135
Codec ID/Hint               : Sipro
Duration                    : 2 min 44 s
Bit rate                    : 8 720 b/s
Channel(s)                  : 1 channel
Sampling rate               : 8 000 Hz
Stream size                 : 175 KiB (100%)
And on FFmpeg:
Quote from: FFmpeg
Stream #0:0: Audio: acelp.kelvin (5[1][0][0] / 0x0135), 8000 Hz, 1 channels, s16p, 8 kb/s
Full portion:
Quote from: FFmpeg
[wav @ 0000000000142d00] Estimating duration from bitrate, this may be inaccurate
[aist#0:0/acelp.kelvin @ 0000000000162b00] Guessed Channel Layout: mono
Input #0, wav, from 'E:\Sample files\format-0x135-Roligt_samtal.wav':
  Duration: 00:02:44.82, bitrate: 8 kb/s
  Stream #0:0: Audio: acelp.kelvin (5[1][0][0] / 0x0135), 8000 Hz, 1 channels, s16p, 8 kb/s
Stream mapping:
  Stream #0:0 -> #0:0 (acelp.kelvin (native) -> pcm_s16le (native))
Press [q] to stop, [?] for help
Output #0, wav, to 'E:\Sample files\format-0x135-Roligt_samtal_.wav':
  Metadata:
    ISFT            : Lavf60.10.100
  Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 8000 Hz, mono, s16, 128 kb/s
    Metadata:
      encoder         : Lavc60.22.100 pcm_s16le
[out#0/wav @ 00000000007875c0] video:0kB audio:2552kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.002985%
size=    2552kB time=00:02:43.31 bitrate= 128.0kbits/s speed= 261x

This:
Quote from: FFmpeg
Stream #0:0: Audio: acelp.kelvin (5[1][0][0] / 0x0135), 8000 Hz, 1 channels, s16p, 8 kb/s
which it's in mono

looks like this:
Quote from: Google Cloud (https://cloud.google.com/blog/products/ai-machine-learning/using-ffmpeg-with-google-cloud-speech-to-text)
Stream #0:0: Audio: acelp.kelvin (5[1][0][0] / 0x0135), 8000 Hz, 2 channels, s16p, 17 kb/s
which it's in stereo
Same program used!! FFmpeg!!!!

I want to encode speech and music to ACELP.KELVIN!!!

Many wises and wishes to find or create a ACELP.KELVIN encoder that works in Windows 7 (64-bit, also supports 32-bit programs)!!
4
MP3 - General / Re: ffmpeg: A buggy MP3 (MPEG-2 mode) decoder?
Last post by MihaiPopa12346 -
Quote from: maikmerten on
Turns out that the encoding most likely is fine, but that ffmpeg (which I use for a quick command-line listen) apparently has a MP3 decoder that introduces the chirp artifacts...
...
(The chirp artifact is pretty obvious, e.g., around the 8.4 seconds mark)
I still hear the chirp artifacts with headphones. LAME is a better decoder than FFmpeg for that type of files.
6
Lossless / Other Codecs / Re: HALAC (High Availability Lossless Audio Compression)
Last post by Hakan Abbas -
Quote from: Porcus on
https://wiki.hydrogenaud.io/index.php?title=LossyWAV ;  IDK if HALAC could (easily) be adapted to 512 bytes per block.

My idea was more, if one wants to throw a bone to those who want a lossy version of HALAC - then making for it to work with LossyWAV would enable those users to work out settings at their preferred bit rates and see how it compares to other compressors.
Since the compression part is lossless (the lossiness is in the LossyWAV pre-processor), there would be no considerations about audio quality between compressors - speed and size would still be comparable in an apples to apples way.
X
I got an output with LossyWAV with the default settings. The new data obtained seems to be quite suitable for compression. So it has made the 16-bit data almost 8-bit. However, when I listened to the lossy music, I didn't see much difference.
Of course, in this case, the lossless HALAC is not suitable for these data. However, a good harmony can be achieved with a small change.
8
General - (fb2k) / attach pictures on-line in foobar2000
Last post by damians -
Hi everyone, I'm new to foobar, I just started using it.  I wanted to know if there is the possibility of attaching the album cover to a music file by taking the image online.  When I right-click on the audio file, tagging and then attach pictures there is no option to choose the image from an online database but only to choose an image saved locally on the PC.
10
Lossless / Other Codecs / Re: Tested: Lossless decoding speed, multithreaded - and fast verification
Last post by bryant -
Quote from: Porcus on
@bryant on WavPack:
Whether wvunpack --threads=<N> vs ffmpeg -threads=<N> is apples to apples ... I don't know. It might be "better" than comparing wvunpack --threads vs ffmpeg (spawning all), and all I could do was to get it down to thread count matters enough to tilt the numbers.
I believe, based on my experiments, that FFmpeg -threads <n> specifies the total number of threads to use, which is identical to WavPack’s interpretation.

When specifying nothing (option alone) WavPack simply defaults to 5 threads (a good compromise on all machines, if not necessarily the fastest). FFmpeg either determines the number of physical threads and uses that (my guess), or uses unlimited threads (like “make”). The option is there to limit the use of threading only.

Another difference is specifying zero; FFmpeg ignores this (I guess it's the default) whereas WavPack disallows it.