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
2
General Audio / Re: Change sample rate of an audio with best quality?
Last post by fooball -
You've got to admit that commenting out of the blue in a thread that's been dead four years looks a bit weird.  I'm sure there are more recent threads about tempo/pitch shifting.  IMO it would be appropriate for the moderators to split Reply 17 onwards into a new thread, although some patching up may be required throughout the new to make it read properly.

Quote from: Metal-HTPC on
Of course the main toppic was about sample rate conversions but pitch shifting somehow belongs to that too and was brought up here as well.
No, pitch shifting has very little (if anything) to do with sample rate conversion, the subject only came up as a side issue.  Sample rate conversion does not change the pitch/tempo at all, the question of "best quality" is about the interpolation algorithm required to re-sample the audio waveform in between the existing samples, and the problem of (potentially) exceeding the digital full scale in extreme cases.

For info: I'm mainly interested in tempo shifting, but that's the opposite side of the same coin (tempo shift = speed shift + pitch correction).
3
3rd Party Plugins - (fb2k) / Re: JS3 Text Display + Album Art + Seekbar + Buttons - Defender
Last post by Defender -
New version.

Buttons can now support mousewheel as well.

1.29   2025-01-25

Volume can only be muted/unmuted by rightclick.

Added mousewheel functionality to buttons (hover stays active):
PBO            Cycles
RG            Cycles
NowPlaying      Cycles
No point activating mousewheel for DSP and Output buttons.

Button Previous still has its original LeftClick (Previous Track) and RightClick (Seek back 10 seconds) behavior.
Button Next still has its original LeftClick (Next Track) and RightClick (Seek ahead 10 seconds) behavior.

To both the Next and Previous buttons the following (same) fixed mousewheel functionality has been added:

ACTION                       SEEK
--------------------------------------
CTRL-Mousewheel            +/-  1 sec
Mousewheel               +/-  5 sec
SHIFT-Mousewheel         +/- 10 sec
ALT-Mousewheel            +/- 30 sec
SPACE-CTRL-Mousewheel      +/-  1 min
SPACE-Mousewheel         +/-  2 min
SPACE-SHIFT-Mousewheel      +/-  5 min

This is different from scrollwheel on seekbar which uses a dynamic mousewheel step based on tracklength.

The active area for seekbar is increased, which makes clicking, swiping and mousewheeling on the seekbar a bit easier.

Solved a tiny mouseswipe bug that only occurred when both volume buttons/bars were displayed.

Enhanced the Artist TF - for instance icons for AC/DC (AC-DC) will be found now. Also fixes the most obvious stream issues.
Added an extra folder to search for logos.
5
FLAC / Re: FLAC v1.4.x Performance Tests
Last post by hat3k -
Here is "exact" encoder results.

ParamsAVG SizeAVG RatioAVG Speed
-8 -per7 -A "subdivide_tukey(4);flattop" -j2826 159 74269,282%25,594
-8 -er7 --lax -l15 -A "subdivide_tukey(4);flattop" -j2826 146 32269,246%145,857x
-8 -pr7 --lax -l15 -A "subdivide_tukey(4);flattop" -j2826 133 79469,213%150,357x
-8 -pr7 -A "subdivide_tukey(5);flattop" -j2826 162 84969,290%172,837x

Files with same sizes:
Spoiler (click to show/hide)

Here is "inexact" encoder results (from my previous post):

ParamsAVG sizeAVG ratioAVG speed
-8 -per7 -A "subdivide_tukey(4);flattop" -j2826 168 05569,304%88,983x
-8 -er7 --lax -l15 -A "subdivide_tukey(4);flattop" -j2826 153 38669,265%306,023x
-8 -pr7 --lax -l15 -A "subdivide_tukey(4);flattop" -j2826 140 68869,231%212,109x
-8 -pr7 -A "subdivide_tukey(5);flattop" -j2826 170 40269,310%453,227x

Files with same sizes:

Spoiler (click to show/hide)

Quote from: Wombat on
The versions with disable-asm-optimizations only did better with 16bit material but loose big time with hires stuff. Good for cdda related apps.
Yes I've read it but thanks anyway and for the hint about version info in file. I will test your builds for sure.

Quote from: Porcus on
Yeah. If you want to kill absolutely all metadata - including the vendor naming string, but everything else too - then
metaflac --remove-all --dont-use-padding
Nice idea. I will try to implement it in benchmark-H to to achieve more accurate comparisons of the output file sizes.
6
General Audio / Re: Change sample rate of an audio with best quality?
Last post by Metal-HTPC -
Thanks for the replies so far.
My post wasn't intended to make any product placements. I thought it was ok to continue the discussion in this old thread, sorry if I made a mistake here. Of course the main toppic was about sample rate conversions but pitch shifting somehow belongs to that too and was brought up here as well.  I have to educate myself what double blind listening tests (ABX or ABC/HR) are to be able to post comparisons so please bear with me there. But I am willing to post those once a solution for the audacity pitch correction replacement is found, so no worries.
My intentions for the conversions are more movie audio track than music related.
23,976fps speed with correct pitch, conversion to 25fps with higher pitch due to PAL speedup, 25fps with the same pitch as 23,976 which would sound too low when slowed down to 23,976 again and as to be pitch corrected and vice versa and so on and so forth for cases in 24fps as well.
I usually used EAC3to to for speeding or slowing down the audio which somewhat is a natural conversion that the pitch is a bit lower when slowed down or a bit higher when sped up meaning that a 23,976fps sped up to 25 would sound correct when slowed down to 23,976 again without any audible loss of quality. For cases where somebody screwed with the pitch aside from the regular conversion I used audacity to do the pitch correction and applied that on the sped up/slowed down audio. So it is all a 2step scenario not an all on one conversion.

For the regular speed up/slow down only process I replaced EAC3to with ffmpeg and went for the following:
23,976fps sped up to 25fps
Code: [Select]
-drc_scale 0 -i %INPUTFILE% -af aresample=resampler=soxr:precision=20:osf=s16:dither_method=triangular,asetrate=50050 -ar 48000 -acodec pcm_s16le -f WAV %1%-25.wav
25fps slowed down to 23,976fps
Code: [Select]
-drc_scale 0 -i %INPUTFILE% -af aresample=resampler=soxr:precision=20:osf=s16:dither_method=triangular,asetrate=46033.966 -ar 48000 -acodec pcm_s16le -f WAV %1%-23976.wav
so the next step would be to find out how to apply a "stretch-free" pitch only correction to those while keeping the exact same length of the file such as audacity is able to do. That ascale solution with the ffmpeg fork sounds interesting.  The pitch shifts I'm looking for are +/- 0,10, 0,71, 0,72, 0,68, 0,69 cents.

PS.: of course I am willing to post this in a new thread is you want it that way, let me know
7
General Audio / Re: Where did these (obsolete!) sampling rates come from?
Last post by Porcus -
Quote from: Porcus on
5.6, 7.4, 11.1 and 22.2 kHz?
[...]
Those sampling rates were used in Apple SoundCap ("HCOM" fourcc) files - anyone even seen one?
Both FFmpeg and SoX got some support. The SoX documentation refers to them as:
Code: [Select]
Format: hcom
Description: Mac FSSD files with Huffman compression
Channels restricted to: mono
Sample-rate restricted to: 22050 11025 7350 5512.5
Reads: yes
Writes:
   8-bit HCOM (8-bit precision)
Those sample rates do make sense, but who am I to tell whether a mid-eighties Macintosh would use 22050 or something so close that 22050 is a practical approximation. Anyway 1/2, 1/3 and 1/4 is also sensible - remember this was before .wav, so its restriction to integer was not a concern.

Also interesting is that this could be the first lossless audio format, although it might be a stretch to call it an audio compressor if it merely let a general-purpose compressor (PackIt?) loose on files that happen to contain audio.
8
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by regor -
Quote
For my part, I'll make a quickie tool to clean up/uninstall my components (and others, given a list of GUIDs) from the configuration database.
That would be wonderful.

Anyway I don't think the discussion per se is bad, to me it's clear some people have problems with the current design and there are some legit use cases where V2 has been a downgrade instead of an improvement.

I think it's useful to develop that discussion -obviously not in this thread, sorry- to hopefully reach to some solutions for the problems mentioned. Or at least give them an answer if it's a design decision which will not change.
9
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by Defender -
Quote from: oops on
Quote from: Defender on
Play from ELP - VU 2024 fullscreen - Exit - Crash
Video of the gaudiest setup I could squeeze in to torture test.
Video is sped up 50% to squeeze it under the imgur limits (since it's MP4 cannot embed either).

Cannot reproduce the crash. I mistakenly hit the X button for the VU meter instance in the Jsplitter panel; it didn't crash. And you can see the 0 exit code at the end. Don't know what how your set up is knocking the VU meter off kilter.
In your video I do not see an active ELP. The issue is ELP and ELP only. And only when at least once a play command was issued from ELP AND VU has been put in fullscreen.

Also ELP is running fine and keeps running fine going fullscreen with VU and back again a 100x.

The ONLY (but big) issue is fooBar crashes on exit, when the above situation is met.

BTW. I am going to respond to your earlier message to me.
10
3rd Party Plugins - (fb2k) / Re: foo_vis_vumeter
Last post by oops -
To all. Mea culpa. I didn't mean to spark a discussion on the design decisions of the player. I missed some detail that led to a crash. We found the problem and fixed it. Let's move past it.

Just tried to get someone going again until I roll out a fixed release. It's what I wish someone did for me if I ever was stuck with a showstopper.

For my part, I'll make a quickie tool to clean up/uninstall my components (and others, given a list of GUIDs) from the configuration database.