missing lines about whisper-standalone-win

[Purfview]

Upload the audio to a normal download site.

https://we.tl/t-hvSN7uy7JH

[Purfview]

Transcribes for me with whisper-faster.exe test.mka -m large-v2 -l en -v true -ct float32 -bs 1:

[02:14.040 --> 02:18.740]  But before we jump into the overclocking, let's first have a look at the hardware and the
[02:18.740 --> 02:23.640]  benchmarks that we'll be using in this guide. The system we're overclocking today consists of
Processing segment at 02:23.640
[02:23.640 --> 02:29.740]  the following hardware. The specific graphics card we're using to overclock the RTX 3050 GPU
[02:29.740 --> 02:39.460]  is the EVGA GeForce RTX 3050 XC Gaming. Of course, unfortunately, EVGA has recently exited the GPU
[02:39.460 --> 02:46.340]  business. The card has a dual fan thermal solution and an out of the box listed GPU boost frequency
Processing segment at 02:46.340
[02:46.340 --> 02:56.640]  of 1,845MHz, slightly up from NVIDIA's 1,777MHz specification. However, it appears as if EVGA
[02:56.640 --> 03:03.700]  overclocked the GPU even further as we get up to 2,055MHz when we power up the card. We'll get back
[03:03.700 --> 03:09.580]  to that later in this video. We use Windows 11 and the following benchmark applications to measure
[03:09.580 --> 03:14.660]  performance and ensure system stability. I'm introducing a couple of new applications in this
Processing segment at 03:14.660

Post what it shows for you in console at those times. [with bfloat16 and verbose enabled]

with .\whisper-faster.exe --sentence --model=large-v2 -v true --compute_type=bfloat16 --ff_rnndn_sh file.opus

[01:49.960 --> 02:13.360]  In this video we cover 3 overclocking strategies. First we manually increase the GPU and memory frequency using the EVGA Precision X1 software tool. Second, we slap on a full cover waterblock and try to overcome the power limitations by shunt modding. Third, we use the Elmo Labs EVC2 to work around other overclocking limitations.
Processing segment at 02:13.360
[02:13.940 --> 02:21.020]  But before we jump into the overclocking, let's first have a look at the hardware and the benchmarks that we'll be using in this guide.
Processing segment at 02:43.360
[03:04.380 --> 03:11.860]  We use Windows 11 and the following benchmark applications to measure performance and ensure system stability.
Processing segment at 03:11.860

problam was with bfloat16, float16 works gud

[Purfview]

It just doesn't transcribe those lines with bfloat16, no idea why. That's a question for faster-whisper devs.