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
21
Lossless / Other Codecs / Re: libttaR (TTA rewrite part 2)
Last post by mycroft -
Using (old version) ffmpeg of cli tool for performance comparison is flawed and extremely biased.
Also current ffmpeg cli tool have bad performance with smaller packets due to clumsy MT work of ex-developer.
Also just to run generic build of ffmpeg for the first time takes extra time... That is just few points I wanted to emphasize how such comparison is unfair and biased.
23
3rd Party Plugins - (fb2k) / Re: foo_truepeak True Peak Scanner
Last post by wojak -
@Case sorry to bother you again but could you please consider implementing PLR in your scanner. Recently you have incorporated LUFS so now PLR is the last thing we have to calculate with enormously long formula and it does not go to tags.
Thank you for this (and many other) great component.
24
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by darkflame23 -
Hey, it's all good! We now have DR built into Foobar natively, with this component (and the True Peak Scanner), so can use what we need. It's brilliant for mastering as I can get an instant readout of many different variables, track to track. Well done Cae. Does the True Peak Scanner now make this DR component redundant?
25
Lossless / Other Codecs / Re: libttaR (TTA rewrite part 2)
Last post by rdtsh -
1.1 is now nearly finished. There is just some minor stuff for me to get at. I plan to officially release it on the first of next month.

here is a benchmark against ffmpeg:

system:
   Linux 5.10.0-23-amd64 SMP Debian 5.10.179-1 (2023-05-12) x86_64 GNU/Linux
CPU:
   AMD Ryzen 7 1700 64-bit 8-Core MT MCP 1550/3750 MHz
ffmpeg:
   ffmpeg version 4.3.6-0+deb11u1
   built with gcc 10 (Debian 10.2.1-6)
   libavutil      56. 51.100 / 56. 51.100
   libavcodec     58. 91.100 / 58. 91.100
   libavformat    58. 45.100 / 58. 45.100
   libavdevice    58. 10.100 / 58. 10.100
   libavfilter     7. 85.100 /  7. 85.100
   libavresample   4.  0.  0 /  4.  0.  0
   libswscale      5.  7.100 /  5.  7.100
   libswresample   3.  7.100 /  3.  7.100
   libpostproc    55.  7.100 / 55.  7.100
ttaR:
   Debian clang version 11.0.1-2
   -march=native -mtune=native
file:
   Nirvana - MTV Unplugged in New York
   571084460   mtv.wav
   337981896   mtv.tta

##############################################################################

 Performance counter stats for 'ffmpeg -loglevel quiet -threads 1 -i mtv.wav -f tta /dev/null -y' (20 runs):

          8,925.80 msec task-clock                #    1.000 CPUs utilized            ( +-  0.06% )
                60      context-switches          #    0.007 K/sec                    ( +-  5.24% )
                16      cpu-migrations            #    0.002 K/sec                    ( +-  2.69% )
            86,798      page-faults               #    0.010 M/sec                    ( +-  0.00% )
    33,302,059,704      cycles                    #    3.731 GHz                      ( +-  0.05% )  (83.33%)
       566,286,522      stalled-cycles-frontend   #    1.70% frontend cycles idle     ( +-  0.54% )  (83.33%)
     3,988,341,464      stalled-cycles-backend    #   11.98% backend cycles idle      ( +-  0.18% )  (83.33%)
    65,718,741,261      instructions              #    1.97  insn per cycle
                                                  #    0.06  stalled cycles per insn  ( +-  0.00% )  (83.33%)
     8,702,525,883      branches                  #  974.986 M/sec                    ( +-  0.01% )  (83.34%)
       384,955,890      branch-misses             #    4.42% of all branches          ( +-  0.03% )  (83.33%)

           8.92647 +- 0.00557 seconds time elapsed  ( +-  0.06% )


 Performance counter stats for 'ffmpeg -loglevel quiet -threads 1 -i mtv.tta -f s16le /dev/null -y' (20 runs):

          6,504.99 msec task-clock                #    1.000 CPUs utilized            ( +-  0.13% )
                55      context-switches          #    0.008 K/sec                    ( +-  2.46% )
                16      cpu-migrations            #    0.002 K/sec                    ( +-  2.49% )
             3,692      page-faults               #    0.567 K/sec                    ( +-  0.04% )
    24,289,757,929      cycles                    #    3.734 GHz                      ( +-  0.13% )  (83.31%)
       327,298,120      stalled-cycles-frontend   #    1.35% frontend cycles idle     ( +-  0.15% )  (83.31%)
     3,454,321,337      stalled-cycles-backend    #   14.22% backend cycles idle      ( +-  0.20% )  (83.33%)
    67,039,367,957      instructions              #    2.76  insn per cycle
                                                  #    0.05  stalled cycles per insn  ( +-  0.00% )  (83.35%)
     8,499,223,928      branches                  # 1306.569 M/sec                    ( +-  0.00% )  (83.36%)
       313,478,808      branch-misses             #    3.69% of all branches          ( +-  0.01% )  (83.34%)

           6.50534 +- 0.00866 seconds time elapsed  ( +-  0.13% )


 Performance counter stats for 'ffmpeg -loglevel quiet -threads 16 -i mtv.tta -f s16le /dev/null -y' (320 runs):

          9,947.58 msec task-clock                #   12.309 CPUs utilized            ( +-  0.09% )
             4,450      context-switches          #    0.447 K/sec                    ( +-  0.37% )
             1,041      cpu-migrations            #    0.105 K/sec                    ( +-  1.04% )
             8,380      page-faults               #    0.842 K/sec                    ( +-  0.00% )
    36,296,805,088      cycles                    #    3.649 GHz                      ( +-  0.02% )  (83.37%)
       562,776,161      stalled-cycles-frontend   #    1.55% frontend cycles idle     ( +-  0.15% )  (83.13%)
     5,056,980,289      stalled-cycles-backend    #   13.93% backend cycles idle      ( +-  0.02% )  (83.21%)
    67,127,958,734      instructions              #    1.85  insn per cycle
                                                  #    0.08  stalled cycles per insn  ( +-  0.00% )  (83.30%)
     8,518,827,278      branches                  #  856.372 M/sec                    ( +-  0.00% )  (83.43%)
       317,537,726      branch-misses             #    3.73% of all branches          ( +-  0.00% )  (83.57%)

           0.80817 +- 0.00137 seconds time elapsed  ( +-  0.17% )

##############################################################################

 Performance counter stats for 'ttaR encode -q -S mtv.wav -o /dev/null' (20 runs):

          5,697.67 msec task-clock                #    1.000 CPUs utilized            ( +-  0.10% )
                13      context-switches          #    0.002 K/sec                    ( +- 14.11% )
                 0      cpu-migrations            #    0.000 K/sec                    ( +- 31.26% )
               252      page-faults               #    0.044 K/sec                    ( +-  0.10% )
    21,277,212,273      cycles                    #    3.734 GHz                      ( +-  0.08% )  (83.32%)
       424,132,363      stalled-cycles-frontend   #    1.99% frontend cycles idle     ( +-  1.19% )  (83.32%)
     8,164,992,255      stalled-cycles-backend    #   38.37% backend cycles idle      ( +-  0.17% )  (83.33%)
    50,036,808,248      instructions              #    2.35  insn per cycle        
                                                  #    0.16  stalled cycles per insn  ( +-  0.00% )  (83.34%)
     3,929,444,278      branches                  #  689.658 M/sec                    ( +-  0.01% )  (83.36%)
       371,064,057      branch-misses             #    9.44% of all branches          ( +-  0.01% )  (83.34%)

           5.69822 +- 0.00548 seconds time elapsed  ( +-  0.10% )


 Performance counter stats for 'ttaR encode -q -t16 mtv.wav -o /dev/null' (320 runs):

          8,177.73 msec task-clock                #   15.379 CPUs utilized            ( +-  0.02% )
             1,300      context-switches          #    0.159 K/sec                    ( +-  2.07% )
               203      cpu-migrations            #    0.025 K/sec                    ( +-  2.01% )
             5,834      page-faults               #    0.713 K/sec                    ( +-  0.04% )
    30,484,625,770      cycles                    #    3.728 GHz                      ( +-  0.02% )  (83.09%)
       439,889,964      stalled-cycles-frontend   #    1.44% frontend cycles idle     ( +-  0.38% )  (83.18%)
     4,980,516,390      stalled-cycles-backend    #   16.34% backend cycles idle      ( +-  0.04% )  (83.31%)
    50,068,984,657      instructions              #    1.64  insn per cycle        
                                                  #    0.10  stalled cycles per insn  ( +-  0.00% )  (83.46%)
     3,937,619,679      branches                  #  481.505 M/sec                    ( +-  0.00% )  (83.60%)
       380,192,849      branch-misses             #    9.66% of all branches          ( +-  0.00% )  (83.36%)

          0.531753 +- 0.000344 seconds time elapsed  ( +-  0.06% )


 Performance counter stats for 'ttaR decode -q -S mtv.tta -f raw -o /dev/null' (20 runs):

          5,807.10 msec task-clock                #    1.000 CPUs utilized            ( +-  0.12% )
                15      context-switches          #    0.003 K/sec                    ( +-  9.58% )
                 1      cpu-migrations            #    0.000 K/sec                    ( +- 25.36% )
               207      page-faults               #    0.036 K/sec                    ( +-  0.10% )
    21,697,968,813      cycles                    #    3.736 GHz                      ( +-  0.12% )  (83.29%)
       409,444,598      stalled-cycles-frontend   #    1.89% frontend cycles idle     ( +-  0.06% )  (83.33%)
     8,348,408,571      stalled-cycles-backend    #   38.48% backend cycles idle      ( +-  0.30% )  (83.35%)
    53,311,974,255      instructions              #    2.46  insn per cycle        
                                                  #    0.16  stalled cycles per insn  ( +-  0.00% )  (83.35%)
     3,884,628,982      branches                  #  668.945 M/sec                    ( +-  0.00% )  (83.36%)
       370,081,414      branch-misses             #    9.53% of all branches          ( +-  0.01% )  (83.32%)

           5.80763 +- 0.00684 seconds time elapsed  ( +-  0.12% )


 Performance counter stats for 'ttaR decode -q -t16 mtv.tta -f raw -o /dev/null' (320 runs):

          8,396.63 msec task-clock                #   15.660 CPUs utilized            ( +-  0.02% )
             2,705      context-switches          #    0.322 K/sec                    ( +-  0.61% )
                70      cpu-migrations            #    0.008 K/sec                    ( +-  1.97% )
             4,820      page-faults               #    0.574 K/sec                    ( +-  0.00% )
    31,341,341,315      cycles                    #    3.733 GHz                      ( +-  0.02% )  (83.16%)
       404,497,658      stalled-cycles-frontend   #    1.29% frontend cycles idle     ( +-  1.11% )  (83.19%)
     4,983,844,918      stalled-cycles-backend    #   15.90% backend cycles idle      ( +-  0.03% )  (83.27%)
    53,368,851,871      instructions              #    1.70  insn per cycle        
                                                  #    0.09  stalled cycles per insn  ( +-  0.00% )  (83.37%)
     3,896,895,024      branches                  #  464.102 M/sec                    ( +-  0.00% )  (83.55%)
       378,556,224      branch-misses             #    9.71% of all branches          ( +-  0.00% )  (83.45%)

          0.536170 +- 0.000363 seconds time elapsed  ( +-  0.07% )
26
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by omasciarotte -
Quote from: Treelady on
MAAT Digital obtained the rights to the DR intellectual property from Pleasaurize and immediately issued the plug-in meter as well as the off line stats generator.  LUFS may be standard, but it fails to accurately represent some genres of music, which is why DR is useful.

Yup! We are the guys who created the PMF back in the day. I was a board member along with Karl Maria Brandenburg, and my MAAT co–founder Friedemann Tischmeyer was the PMF’s creator. Friedemann is a member of the ploud group that formulated 1770. We designed and launched the DRi standard to provide an easy to understand and repeatable measurement method to represent the perceived loudness of pop music.
27
3rd Party Plugins - (fb2k) / Re: Dynamic Range plugin
Last post by omasciarotte -
Quote from: darkflame23 on
IMHO completely unnecessary now we have True Peak, LUFS-I and PLR available natively in Foobar.

Hi Mr. “darkflame,”

The BS.1770 metrics to which you refer, True Peak and LRA (as expressed in LUFS-I; LUFS is a unit of measure) were never designed to represent subjective or perceived loudness. In a digital broadcast environment, LRA is a standardized dynamic range measurement, but it is tailored specifically for a particular purpose; the algorithmic control of playback gain to provide uniform subjective loudness across all broadcast program content. That standardized measurement is LRA or Loudness Range, and is part of the ITU-R BS.1770 family of recommendations ( as recommended by the ploud expert group) used by content providers, distributors, and hardware manufacturers to automatically reproduce all broadcast audio content at a similarly perceived loudness.

LRA was designed to reflect the deviation of loudness events primarily for broadcast applications. Unfortunately, LRA isn’t ideal for evaluating the subjective loudness of pop and other styles of music since most of recorded music happens in a range of amplitude which is explicitly ignored by the mandated LRA algorithm. LRA is a “weighted” or purposefully skewed measurement, designed to force “interstitials” or short duration content, usually advertisements, into a similar perceived loudness as that to the “program” or long–form content that surrounds them. For good or ill, BS.1770 has come to be thought of as The Path to subjective loudness control of all audio, even of music, even though it was designed to crush television commercials that were too loud.

As to Crest Factor and PLR, there is no standard measurement method. So, different manufacturer’s meters and algorithms display varying results, with each showing its own interpretation of the same audio source. As an example, many use RMS instead of Short–term LU or Loudness Units. The difference between PLR and DRi (integrated DR Dynamic Range) is simple: PLR is the difference between peak and average, and is not standardized, while DRi is always, repeatably DR. The i in DRi stands for integrated in the same way that the I in LUFS–I also stands for integrated. That is, integrated or “windowed” over time; a rolling integration. Also, DRi ignores low amplitude information, so called “background loudness,” for the sake of a more predictable measurement result. That is the opposite of LRA, which ignores the highest amplitude information. Plus, the DR algorithm incorporates additional processing for meaningful measurement of the dynamic integrity and dynamic density of popular music.

Lastly, for easy understanding and comparison, official DRi is always an integer value. Note that the Foobar plug–in does not perform either an LRA nor a DRi measurement. BTW, neither does Roon!

P.S. — True Peak or “TP” has absolute nothing to do with perceived loudness in the human perception sense, or Loudness in the 1770 sense. The human ear cannot detect True Peaks! TP was designed to prevent, by way of accurate measurement, DAC overloads and subsequent distortion due to inter–sample peaks. As with 1770 as a whole, TP is about machine behavior, not human hearing.
28
Lossless / Other Codecs / Re: Lossless music stores (files!) not offering FLAC, but other lossless compressed?
Last post by Porcus -
Quote from: mycroft on
Last time i checked all >2ch music mostly was classic only.
Maybe what is released as audio-only. DVD and BluRay?

Since you mention TAK ... which needs a time capsule, but anyway: http://audiograaf.nl/losslesstest/revision%206/Average%20of%205.1%20surround%20sources.pdf
(The only that decorrelates more than channel pairs?)
30
Lossless / Other Codecs / Re: Lossless music stores (files!) not offering FLAC, but other lossless compressed?
Last post by Porcus -
Quote from: guruboolez on
Tried with Qobuz on 192 Khz album:
Qobuz claim to support those four you mention, but for CDDA also WMAL: https://help.qobuz.com/en/articles/10167-what-are-the-different-audio-formats-available-for-download

Quote from: guruboolez on
I know that the 2L label (classical) also has different exotic options for file delivery:
- MQA
- flac
- mp4 (?)
- mkv
- wav

(the DXD discrete channels WAV 7.1.4 immersive only costs 80€…)
https://shop.2l.no/collections/latest-releases/products/lyden-av-arktis?variant=41448957968567
Dolby Atmos TrueHD is something I don't know. If it is high-channel Atmos (5.1.4/7.1.4/9.1.4) encoded with TrueHD (= MLP), then in the very least they are losslessly compressing more channels than FLAC can handle.
https://shop.2l.no/en-us/collections/dolby-atmos-mp4-files/dolby-atmos-truehd-in-mkv

They deliver that in MKV, as dual stream. The MP4 version of that album seems to be more conventional Dolby Atmos.

If you want to pay $52 extra to get DXD-WAVE in place of that MKV, then maybe Mr. Lindberg will drink something better than Carlsberg for dinner.