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.
Topic: Disabling filters with command line (Read 15943 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Disabling filters with command line

Reply #25 –
But you don't listen to music with your eyes, so why do you want to see it? It won't tell you anything that you can't hear.

Cheers, Slipstreem. 

Disabling filters with command line

Reply #26 –
Quote from: Slipstreem on
But you don't listen to music with your eyes, so why do you want to see it? It won't tell you anything that you can't hear.

Cheers, Slipstreem. 


I know. I just wanted to see how certain other encoders cut certain frequencies off. For example, if someone rips something with iTunes at 256 kbps, I want to know if some frequencies were dropped. That kind of thing.

Disabling filters with command line

Reply #27 –
I would start by comparing Blade @ 192 CBR and Lame @ 192 CBR.  If you can't tell the difference in a blind test then drop the bitrate to 160.  Comparing your ABX results with a frequency response or spectral view of each sample should tell you all you need to know.

Disabling filters with command line

Reply #28 –
Quote from: greynol on
I would start by comparing Blade @ 192 CBR and Lame @ 192 CBR.  If you can't tell the difference in a blind test then drop the bitrate to 160.  Comparing your ABX results with a frequency response or spectral view of each sample should tell you all you need to know.

Well... with eig sample I can tell Blade@320 from Lame@320, but it isn't because of different lowpass value 

Disabling filters with command line

Reply #30 –
"According to the API description in lame.h, the lame_set_lowpassfreq and
lame_set_highpassfreq API functions should accept the value -1 to disable
filtering. "

Why on earth would I care about that ? Hardly anyone in these forums is interested in such things. Its interesting purely from a technical POV not for psychoacoustic encoding.
wavpack -b2.9cs.5
lame --preset cd -f

Disabling filters with command line

Reply #31 –
LAME history
 

Disabling filters with command line

Reply #32 –
Quote from: shadowking on
"According to the API description in lame.h, the lame_set_lowpassfreq and
lame_set_highpassfreq API functions should accept the value -1 to disable
filtering. "

Why on earth would I care about that ? Hardly anyone in these forums is interested in such things. Its interesting purely from a technical POV not for psychoacoustic encoding.


Well, it might be surprising, but some find it interesting!

Robert, when will this new version be released?