Beside old *.WAV files?

Thank you for reading and hopefully answering soon. :)
--
"Praise the LORD, O my soul. I will praise the LORD all my life; I will sing praise to my God as long as I live." --Psalm 146:1-2. Yay 4 Lakers 4 smacking da bears hard!
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:

> Is there a way to have W10's sounds' program events use *.MP3 files?
> Beside old *.WAV files?
>
> Thank you for reading and hopefully answering soon. :)

Buy Microsoft. Then you can order Microsoft to do what you want,
as Elmo Mussed is doing with Twitcher.

A cheaper alternative is to run those *.MP3 files through an MP3
to WAV converter.
<https://duckduckgo.com/?q=MP3+to+WAV+converter>

Ant <ant@zimage.comANT> wrote:

> Beside old *.WAV files?

The Sound Event player only recognizes WAV files. I suspect WAV has
been the standard and only choice ever since Windows had sound events.
WAV is a pretty old standard (circa 1991), but still very usable, and
developed by IBM and Microsoft, so it's Microsoft preferred choice (they
defined it, so they want to use it).

https://en.wikipedia.org/wiki/WAV

MP3 files are more compressed, so they are smaller, but it's lossy
compression. WAV files are not compressed and not lossy, so they have
more data so better quality.

https://www.google.com/search?q=convert+mp3+to+wav
(J already gave a search using DuckDuckGo)

Lots of choices on converters. Although I haven't used it in a long
time and no longer have it installed, Audacity will do the conversion.

https://www.audacityteam.org/
https://en.wikipedia.org/wiki/Audacity_(audio_editor)

A lot of people like Audacity because it is FOSS (Free and Open Source
Software). A lot of people like it, because it is a very capable audio
editor. I remember using Audacity to change the volume of a sound file.
Sometimes whoever is recording has crappy speakers, and have to turn
them way up, and do so also when recording their music. I'd rather
attenuate the music in the sound file instead of having to play with the
OS sound settings which affects all sounds to whichever player the OS
settings apply.

As I recall, you can also use Audacity to trim the output by dragging
sliders on the loaded audio file if you only want part of the song in
the output instead of the whole song. Lots of online help on doing the
conversion, like the following one on how to use Audacity:

https://www.wikihow.com/Convert-MP3-to-WAV

Hmm, I just convinced myself to re-install Audacity. Handy tool. It
can run on Windows, Linux, and Mac.

https://www.audacityteam.org/download/

Audacity is one of those programs you put in your toolbox: might not use
it a lot, but very handy when you need it. I do the same with the
SysInternals and Nirsoft software.

On Sun, 23 Apr 2023 05:52:31 +0000, in alt.comp.os.windows-10, Ant wrote:
>Beside old *.WAV files?
>
>Thank you for reading and hopefully answering soon. :)

The hell? It never occurred to me that they still haven't fixed that.
WTAF? That sh!t goes back to Windows 3.1 (or even Multimedia Extensions
for Windows 3.0).

Convert 'em I guess. Audacity can do it.

https://solutioncenter.stenograph.com/en_US/audio/mp3towav

https://www.audacityteam.org/

--
Zag

No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten

On Sun, 23 Apr 2023 15:24:41 -0400, in alt.comp.os.windows-10, Paul
wrote:

>On 4/23/2023 1:52 AM, Ant wrote:
>> Beside old *.WAV files?
>>
>> Thank you for reading and hopefully answering soon. :)
>>
>
>Anything with even the "potential" for patent overhang, cannot be used.
>
>Since WAV is a native format and effectively "belongs" to Microsoft,
>it is a natural solution.
>
Jeez. Google can do notification sounds that are mp3. Is Microsoft really
that strapped for cash?

I think they are just too lazy to update the Win95 era code. Probably
something about sample rate or some other bs.

--
Zag

No one ever said on their deathbed, 'Gee, I wish I had
spent more time alone with my computer.' ~Dan(i) Bunten

On 4/23/23 01:52, this is what Ant wrote:
> Beside old *.WAV files?
>
> Thank you for reading and hopefully answering soon. :)
Found this on line.

Convert one file: ffmpeg -i xxx.mp3 xxx.wav.

https://www.cisdem.com/resource/mp3-to-wav.html next to last option.
--
Al

On 4/23/2023 11:15 PM, Zaghadka wrote:
> On Sun, 23 Apr 2023 15:24:41 -0400, in alt.comp.os.windows-10, Paul
> wrote:
>
>> On 4/23/2023 1:52 AM, Ant wrote:
>>> Beside old *.WAV files?
>>>
>>> Thank you for reading and hopefully answering soon. :)
>>>
>>
>> Anything with even the "potential" for patent overhang, cannot be used.
>>
>> Since WAV is a native format and effectively "belongs" to Microsoft,
>> it is a natural solution.
>>
> Jeez. Google can do notification sounds that are mp3. Is Microsoft really
> that strapped for cash?
>
> I think they are just too lazy to update the Win95 era code. Probably
> something about sample rate or some other bs.
>

MP3 might be clear now, enough for them to use,
but with lawyers, you can never be too sure there
isn't an "angle" somewhere.

Licensing fees would be a contributing factor to the
disappearance of Media Center. The Guide Data bill likely
did not help. From an implementation perspective, you
can run a tuner without Guide Data (that's why the
Canadian version of Media Center is almost impossible to use).

At one time, I think when you installed Audacity, you
"got the LAME file for it" from "somewhere". As there were
legal issues with the MP3, and no Linux distro could afford
legal issues, so the LAME was separately installed. And
the same procedures were needed for the Windows version.

It is possible today, that the MP3 handling is built into
Audacity. Although I haven't installed any modern Audacity
here in quite a while. Audacity changed hands.

Paul

VanguardLH <V@nguard.LH> posted this
via news:1oaoako5wn3oc.dlg@v.nguard.lh:

> Ant <ant@zimage.comANT> wrote:
>
>> Beside old *.WAV files?
>
> The Sound Event player only recognizes WAV files.
>
> [History of WAV files snipped...]
>

My Windows 10 Pro 64-bit HP system plays MP3s all the time.

No big deal.

--

I AM Bucky Breeder, (*(^;

And *NO*, that is *NOT* a Jedi Light Saber I have in my pocket!

But that doesn't necessarily mean I'm happy to see you either.

On 4/23/2023 1:52 AM, Ant wrote:
> Beside old *.WAV files?
>
> Thank you for reading and hopefully answering soon. :)
>

Anything with even the "potential" for patent overhang, cannot be used.

Since WAV is a native format and effectively "belongs" to Microsoft,
it is a natural solution.

*******

MIDI files would have been a good way to encode audio, and
Microsoft may license some soundbank (Microsoft GS Wavetable?)
for that in the past. While the technique might be clear enough for them to use,
the available sound banks associated with MIDI vary in quality
and some of the free ones sound dreadful.

From a reddit:

"Is there a way to install the default Windows Roland GS MIDI driver and soundfont in Wine?"

So the part that makes the noise, has an external dependency.

Paul

The following probably only applies if you've changed Windows DPI
setting from 100% (96 dpi) to something larger, like 150% (144 dpi).

I just re-installed Audacity, and I noticed its display is a bit fuzzy.
I would've thought Audacity would've been DPI aware decades ago after
published their DPI awareness docs back around 2002. It is usable
as-is, but to get it a bit better focused, you do the following:

- Right-click on the audacity.exe file wherever you installed it.
- Select Properties from the context menu.
- Select the Compatibility tab.
- Click on "Change settings for all users" (unless you want the DPI
change to be effective only under your Windows account).
- Click "Change high DPI settings".
- Under "High DPI scaling override", select "Application". This lets
the application paint at its native resolution within the window
rather than have the OS scale the output into the window.
- Click OK.
- Click Apply (or OK your way out of the dialogs).

Run audacity.exe to see if you like the fuzzy display from before, or
the sharper display after changing DPI settings on just the program.
Because Audacity is not written as a DPI-aware program, text fields
inside of objects (e.g., labels on buttons) may get truncated, because
the program author did not account for more space when the app choses
the resolution instead of the OS. Text labels not fitting inside an
element (i.e., button) belies the program is not DPI-aware.

You might not run into the fuzzy output if using the standard DPI (96
dpi, or 100%) in Windows. My old eyes need text to be a bit larger, so
I upped DPI (to 150%, or 144 dpi). When buying monitors with higher
resolution, that does not change how many pixels are used to paint
character. The result is a higher resolution monitor shows characters
as smaller: same number of pixels, but in less space. So, I up the DPI
to use more pixels per character to make them larger (well, the size
they were before on a smaller resolution monitor). I'm not downing the
DPI just for this program. Instead I let the app use the resolution it
knows which would probably paint okay at 100% DPI, but gets fuzzy when
those same characters are painted at 150% DPI. By letting the app
instead of the OS choose the resolution within a window, the characters
in the app look more crisp, but there can be problems with a non-DPI
aware program with its text labels in buttons, or other places where the
text gets truncated. Since Audacity shows popups when hovering the
mouse cursor over a button, and the popup bubble has the complete text,
having truncated labels on buttons is not a problem

Odd Audacity has not bothered to become DPI-aware after decades of
Windows having the DPI setting. I did not find any DPI settings inside
of Audacity's preferences; however, a DPI-aware program doesn't need
user-facing DPI settings. Others have noticed this problem, too. Been
too long since I last used Audacity that maybe it was back before I got
a higher resolution monitor which made me up the DPI (from 100% to 150%,
or 96 to 144 dpi).

https://github.com/audacity/audacity/issues/503
Opened April 2020. Status = closed, won't fix - but the issue was not
fixed!

The problem is much older than just a few years ago. I found forum
posters noting the problem going back to 2016, perhaps farther back if I
searched more.

Well, I said it was powerful and free, not that it is perfect. A very
powerful audio editor, but lame on DPI support.

On 4/23/2023 1:52 AM, Ant wrote:
> Beside old *.WAV files?
>
> Thank you for reading and hopefully answering soon. :)

Have you even tried to make it play your own MP3?

Most likely Windows is designed to play system sound in WAV format only.

But you can still try to see if Microsoft has changed that. Stick your
MP3 file into   "C:\Windows\Media\" and then change your system sound
setting to that file.

If Windows doesn't want to use that MP3 sound file, then you can covert
your MP3 to WAV file using:

LameXP Portable
https://portableapps.com/apps/music_video/lamexp-portable

Bucky Breeder <Breeder_Bucky-Breeder@that's.my.name_don't.wear.it.out> wrote:
> VanguardLH <V@nguard.LH> posted this
> via news:1oaoako5wn3oc.dlg@v.nguard.lh:

> > Ant <ant@zimage.comANT> wrote:
> >
> >> Beside old *.WAV files?
> >
> > The Sound Event player only recognizes WAV files.
> >
> > [History of WAV files snipped...]
> >

> My Windows 10 Pro 64-bit HP system plays MP3s all the time.

> No big deal.

Huh? How? It only lets me use *.WAV files. When I force it, W10's
sound's program events says "Error! Only files with extension .WAV can
be used for notifications". :(
--
"But godliness with contentment is great gain." ???1 Timothy 6:6. Somewhat quiet weekend & maybe Mon., but next week won't be. Every1 is BUSY. :( Crazy IG's AI 2! It's winter again, but summer returns l8r this wk.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Zaghadka <zaghadka@hotmail.com> wrote:
> On Sun, 23 Apr 2023 05:52:31 +0000, in alt.comp.os.windows-10, Ant wrote:
> >Beside old *.WAV files?
> >
> >Thank you for reading and hopefully answering soon. :)

> The hell? It never occurred to me that they still haven't fixed that.
> WTAF? That sh!t goes back to Windows 3.1 (or even Multimedia Extensions
> for Windows 3.0).

> Convert 'em I guess. Audacity can do it.

> https://solutioncenter.stenograph.com/en_US/audio/mp3towav

> https://www.audacityteam.org/

Does Audacity have a batch conversion feature to convert many audio
files (24)? If so, then I couldn't find it.
--
"But godliness with contentment is great gain." ???1 Timothy 6:6. Somewhat quiet weekend & maybe Mon., but next week won't be. Every1 is BUSY. :( Crazy IG's AI 2! It's winter again, but summer returns l8r this wk.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant <ant@zimage.comant> wrote:
> Bucky Breeder <Breeder_Bucky-Breeder@that's.my.name_don't.wear.it.out> wrote:
> > VanguardLH <V@nguard.LH> posted this
> > via news:1oaoako5wn3oc.dlg@v.nguard.lh:

> > > Ant <ant@zimage.comANT> wrote:
> > >
> > >> Beside old *.WAV files?
> > >
> > > The Sound Event player only recognizes WAV files.
> > >
> > > [History of WAV files snipped...]
> > >

> > My Windows 10 Pro 64-bit HP system plays MP3s all the time.

> > No big deal.

> Huh? How? It only lets me use *.WAV files. When I force it, W10's
> sound's program events says "Error! Only files with extension .WAV can
> be used for notifications". :(

OK, https://www.cisdem.com/resource/mp3-to-wav.html#audacity answers it,
but "To convert multiple MP3 files to WAV" doesn't work in my old
updated, 64-bit W10 Pro PC. My 64-bit portable Audacity opens 24 short
*.MP3 windows and then crashes (not responding). :(
--
"But godliness with contentment is great gain." ???1 Timothy 6:6. Somewhat quiet weekend & maybe Mon., but next week won't be. Every1 is BUSY. :( Crazy IG's AI 2! It's winter again, but summer returns l8r this wk.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Big Al <Bears@invalid.com> wrote:
> On 4/23/23 01:52, this is what Ant wrote:
> > Beside old *.WAV files?
> >
> > Thank you for reading and hopefully answering soon. :)
> Found this on line.

> Convert one file: ffmpeg -i xxx.mp3 xxx.wav.

> https://www.cisdem.com/resource/mp3-to-wav.html next to last option.

Perfect with Convert multiple file: for i in *.mp3; do ffmpeg -i "$i"
"${i%.*}.wav"; done."

Not newbie friendly either. :(
--
"But godliness with contentment is great gain." ???1 Timothy 6:6. Somewhat quiet weekend & maybe Mon., but next week won't be. Every1 is BUSY. :( Crazy IG's AI 2! It's winter again, but summer returns l8r this wk.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant <ant@zimage.comant> wrote:
> Zaghadka <zaghadka@hotmail.com> wrote:
> > On Sun, 23 Apr 2023 05:52:31 +0000, in alt.comp.os.windows-10, Ant wrote:
> > >Beside old *.WAV files?
> > >
> > >Thank you for reading and hopefully answering soon. :)

> > The hell? It never occurred to me that they still haven't fixed that.
> > WTAF? That sh!t goes back to Windows 3.1 (or even Multimedia Extensions
> > for Windows 3.0).

> > Convert 'em I guess. Audacity can do it.

> > https://solutioncenter.stenograph.com/en_US/audio/mp3towav

> > https://www.audacityteam.org/

> Does Audacity have a batch conversion feature to convert many audio
> files (24)? If so, then I couldn't find it.

OK, https://www.cisdem.com/resource/mp3-to-wav.html#audacity answers it,
but "To convert multiple MP3 files to WAV" doesn't work in my old
updated, 64-bit W10 Pro PC. My 64-bit portable Audacity opens 24 short
*.MP3 windows and then crashes (not responding). :(
--
"But godliness with contentment is great gain." ???1 Timothy 6:6. Somewhat quiet weekend & maybe Mon., but next week won't be. Every1 is BUSY. :( Crazy IG's AI 2! It's winter again, but summer returns l8r this wk.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

On 4/24/23 15:59, this is what Ant wrote:
> Big Al <Bears@invalid.com> wrote:
>> On 4/23/23 01:52, this is what Ant wrote:
>>> Beside old *.WAV files?
>>>
>>> Thank you for reading and hopefully answering soon. :)
>> Found this on line.
>
>> Convert one file: ffmpeg -i xxx.mp3 xxx.wav.
>
>> https://www.cisdem.com/resource/mp3-to-wav.html next to last option.
>
> Perfect with Convert multiple file: for i in *.mp3; do ffmpeg -i "$i"
> "${i%.*}.wav"; done."
>
> Not newbie friendly either. :(
Of course that's a linux command is it not. This win 10
--
Al

On 23/04/2023 19:55, VanguardLH wrote:
> Ant <ant@zimage.comANT> wrote:
>
>> Beside old *.WAV files?
>
> The Sound Event player only recognizes WAV files. I suspect WAV has
> been the standard and only choice ever since Windows had sound events.
> WAV is a pretty old standard (circa 1991), but still very usable, and
> developed by IBM and Microsoft, so it's Microsoft preferred choice (they
> defined it, so they want to use it).
>
> https://en.wikipedia.org/wiki/WAV
>
> MP3 files are more compressed, so they are smaller, but it's lossy
> compression. WAV files are not compressed and not lossy, so they have
> more data so better quality.

Strictly WAV is a container and could contain audio compressed with
various codecs including ADPCM and MP3.

However by far the most common type of WAV file seems to be uncompressed
PCM.

--
Brian Gregory (in England).

On 24/04/2023 12:54, Big Al wrote:
> On 4/23/23 01:52, this is what Ant wrote:
>> Beside old *.WAV files?
>>
>> Thank you for reading and hopefully answering soon. :)
> Found this on line.
>
> Convert one file: ffmpeg -i xxx.mp3 xxx.wav.
>
> https://www.cisdem.com/resource/mp3-to-wav.html  next to last option.

Windows might accept an MP3 inside a WAV container:

ffmpeg -i xxx.mp3 -c:a copy xxx.wav

--
Brian Gregory (in England).

On 24/04/2023 23:32, Big Al wrote:
> On 4/24/23 15:59, this is what Ant wrote:
>> Big Al <Bears@invalid.com> wrote:
>>> On 4/23/23 01:52, this is what Ant wrote:
>>>> Beside old *.WAV files?
>>>>
>>>> Thank you for reading and hopefully answering soon. :)
>>> Found this on line.
>>
>>> Convert one file: ffmpeg -i xxx.mp3 xxx.wav.
>>
>>> https://www.cisdem.com/resource/mp3-to-wav.html  next to last option.
>>
>> Perfect with Convert multiple file: for i in *.mp3; do ffmpeg -i "$i"
>> "${i%.*}.wav"; done."
>>
>> Not newbie friendly either. :(
> Of course that's a linux command is it not.   This win 10

It's fairly easy to find and download ffmpeg.exe for Windows.

e.g. https://www.gyan.dev/ffmpeg/builds/ then under "Release Builds"
download ffmpeg-release-full.7z

--
Brian Gregory (in England).

On 4/24/2023 3:59 PM, Ant wrote:
> Big Al <Bears@invalid.com> wrote:
>> On 4/23/23 01:52, this is what Ant wrote:
>>> Beside old *.WAV files?
>>>
>>> Thank you for reading and hopefully answering soon. :)
>> Found this on line.
>
>> Convert one file: ffmpeg -i xxx.mp3 xxx.wav.
>
>> https://www.cisdem.com/resource/mp3-to-wav.html next to last option.
>
> Perfect with Convert multiple file: for i in *.mp3; do ffmpeg -i "$i"
> "${i%.*}.wav"; done."
>
> Not newbie friendly either. :(
>

First, we work backwards, and see what a typical WAV for this looks like.

D:

ffprobe -i "Windows Hardware Remove.wav"

Input #0, wav, from 'Windows Hardware Remove.wav':
Duration: 00:00:00.84, bitrate: 1536 kb/s
Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, 2 channels, s16, 1536 kb/s

So they're using stereo with 48KHz sampling rate.

*******

Next, I check my source MP3 file. And it is twice CD rate and monophonic.

ffprobe -i Aria.mp3

Input #0, mp3, from 'Aria.mp3':
Metadata:
genre : Other
Duration: 00:00:14.78, start: 0.000000, bitrate: 64 kb/s
Stream #0:0: Audio: mp3, 44100 Hz, mono, fltp, 64 kb/s

*******

FFMPEG of course, can fit a square peg into a round hole.

Over the time I've used FFMPEG, I have been pistol-whipped into
specifying audio parameters. This is why I was immediately suspicious
of Big Als idea. If I try to do conversions without specifying
what I want, I've always gotten kicked in the teeth for it.
This usually happens when I'm processing a two hour movie, and
the bloody sound track is screwed on it :-) And then I remember
"oh, yeah, I didn't put the effort into the audio part of the command".

And when I did a Google then, I was holding out for this sort of format,
to refresh my memory.

ffmpeg -i Aria.mp3 -acodec pcm_s16le -ac 2 -ar 48000 out.wav

Whether this is important or not, who can say. Maybe Windows
will always adjust the parameters when it uses a random WAV file.
Or, maybe not. So I check my converted file, to see if it matches
the Windows sample.

ffprobe -i out.wav

Input #0, wav, from 'out.wav':
Metadata:
genre : Other
encoder : Lavf59.17.103
Duration: 00:00:14.76, bitrate: 1536 kb/s
Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, 2 channels, s16, 1536 kb/s

*******

A little AWK to make a batch script.

********************************** Begin batch.awk ****************************************

# Input file made via: dir *.mp3 > input.txt <=== Command Prompt, works
# (Powershell method): get-childitem -name *mp3 > input.txt <=== unicode, dont do this!
# # gawk -f batch.awk input.txt > checkmeclosely.bat
# # Output:
# # ffmpeg -i "Aria.mp3" -acodec pcm_s16le -ac 2 -ar 48000 "Aria.wav"
# ffmpeg -i "fluffy cat.mp3" -acodec pcm_s16le -ac 2 -ar 48000 "fluffy cat.wav"
# # Note: This script has no sanitizing on input! Because it scares people.

BEGIN {
FS="."
firstbit="ffmpeg -i \""
secondbit="\" -acodec pcm_s16le -ac 2 -ar 48000 \""
thirdbit="\""
}

{ print firstbit $1 ".mp3" secondbit $1 ".wav" thirdbit }

********************************** End batch.awk ****************************************

You can add -y to override the "output already exists" check.

For example, if you run this command over and over again, it finishes OK.
The output redirection removes the scum from the screen.

ffmpeg -y -i "Aria.mp3" -acodec pcm_s16le -ac 2 -ar 48000 "Aria.wav" 2>NUL

Paul

On 4/24/2023 8:17 PM, Brian Gregory wrote:
> On 23/04/2023 19:55, VanguardLH wrote:
>> Ant <ant@zimage.comANT> wrote:
>>
>>> Beside old *.WAV files?
>>
>> The Sound Event player only recognizes WAV files.  I suspect WAV has
>> been the standard and only choice ever since Windows had sound events.
>> WAV is a pretty old standard (circa 1991), but still very usable, and
>> developed by IBM and Microsoft, so it's Microsoft preferred choice (they
>> defined it, so they want to use it).
>>
>> https://en.wikipedia.org/wiki/WAV
>>
>> MP3 files are more compressed, so they are smaller, but it's lossy
>> compression.  WAV files are not compressed and not lossy, so they have
>> more data so better quality.
>
>
> Strictly WAV is a container and could contain audio compressed with various codecs including ADPCM and MP3.
>
> However by far the most common type of WAV file seems to be uncompressed PCM.
>
The description here indicates it's a "troubled" format.

https://en.wikipedia.org/wiki/WAV

"The RIFF specification attempts to be a formal specification, but its
formalism lacks the precision seen in other tagged formats."

Paul

Ant vient de nous annoncer :
> Ant <ant@zimage.comant> wrote:
>> Zaghadka <zaghadka@hotmail.com> wrote:
>>> On Sun, 23 Apr 2023 05:52:31 +0000, in alt.comp.os.windows-10, Ant wrote:
>>>> Beside old *.WAV files?
>>>>
>>>> Thank you for reading and hopefully answering soon. :)

>>> The hell? It never occurred to me that they still haven't fixed that.
>>> WTAF? That sh!t goes back to Windows 3.1 (or even Multimedia Extensions
>>> for Windows 3.0).

>>> Convert 'em I guess. Audacity can do it.

>>> https://solutioncenter.stenograph.com/en_US/audio/mp3towav

>>> https://www.audacityteam.org/

>> Does Audacity have a batch conversion feature to convert many audio
>> files (24)? If so, then I couldn't find it.

> OK, https://www.cisdem.com/resource/mp3-to-wav.html#audacity answers it,
> but "To convert multiple MP3 files to WAV" doesn't work in my old
> updated, 64-bit W10 Pro PC. My 64-bit portable Audacity opens 24 short
> *.MP3 windows and then crashes (not responding). :(

foobar2000 should do it.

On 25/04/2023 08:17, Paul wrote:
> On 4/24/2023 3:59 PM, Ant wrote:
>> Big Al <Bears@invalid.com> wrote:
>>> On 4/23/23 01:52, this is what Ant wrote:
>>>> Beside old *.WAV files?
>>>>
>>>> Thank you for reading and hopefully answering soon. :)
>>> Found this on line.
>>
>>> Convert one file: ffmpeg -i xxx.mp3 xxx.wav.
>>
>>> https://www.cisdem.com/resource/mp3-to-wav.html  next to last option.
>>
>> Perfect with Convert multiple file: for i in *.mp3; do ffmpeg -i "$i"
>> "${i%.*}.wav"; done."
>>
>> Not newbie friendly either. :(
>>
>
> First, we work backwards, and see what a typical WAV for this looks like.
>
>    D:
>
>    ffprobe -i "Windows Hardware Remove.wav"
>
> Input #0, wav, from 'Windows Hardware Remove.wav':
>   Duration: 00:00:00.84, bitrate: 1536 kb/s
>   Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, 2
> channels, s16, 1536 kb/s
>
> So they're using stereo with 48KHz sampling rate.
>
> *******
>
> Next, I check my source MP3 file. And it is twice CD rate and monophonic.
>
>    ffprobe -i Aria.mp3
>
> Input #0, mp3, from 'Aria.mp3':
>   Metadata:
>     genre           : Other
>   Duration: 00:00:14.78, start: 0.000000, bitrate: 64 kb/s
>   Stream #0:0: Audio: mp3, 44100 Hz, mono, fltp, 64 kb/s
>
> *******
>
> FFMPEG of course, can fit a square peg into a round hole.
>
> Over the time I've used FFMPEG, I have been pistol-whipped into
> specifying audio parameters. This is why I was immediately suspicious
> of Big Als idea. If I try to do conversions without specifying
> what I want, I've always gotten kicked in the teeth for it.
> This usually happens when I'm processing a two hour movie, and
> the bloody sound track is screwed on it :-) And then I remember
> "oh, yeah, I didn't put the effort into the audio part of the command".
>
> And when I did a Google then, I was holding out for this sort of format,
> to refresh my memory.
>
>    ffmpeg -i Aria.mp3 -acodec pcm_s16le -ac 2 -ar 48000 out.wav
>
> Whether this is important or not, who can say. Maybe Windows
> will always adjust the parameters when it uses a random WAV file.
> Or, maybe not. So I check my converted file, to see if it matches
> the Windows sample.
>
>    ffprobe -i out.wav
>
> Input #0, wav, from 'out.wav':
>   Metadata:
>     genre           : Other
>     encoder         : Lavf59.17.103
>   Duration: 00:00:14.76, bitrate: 1536 kb/s
>   Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 48000 Hz, 2
> channels, s16, 1536 kb/s
>
> *******
>
> A little AWK to make a batch script.
>
> ********************************** Begin batch.awk
> ****************************************
>
> # Input file made via:   dir *.mp3 > input.txt                  <===
> Command Prompt, works
> # (Powershell method):   get-childitem -name *mp3 > input.txt   <===
> unicode, dont do this!
> #
> # gawk -f batch.awk input.txt > checkmeclosely.bat
> #
> # Output:
> #
> # ffmpeg -i "Aria.mp3" -acodec pcm_s16le -ac 2 -ar 48000 "Aria.wav"
> # ffmpeg -i "fluffy cat.mp3" -acodec pcm_s16le -ac 2 -ar 48000 "fluffy
> cat.wav"
> #
> # Note: This script has no sanitizing on input!   Because it scares people.
>
> BEGIN {
>   FS="."
>   firstbit="ffmpeg -i \""
>   secondbit="\" -acodec pcm_s16le -ac 2 -ar 48000 \""
>   thirdbit="\""
> }
>
> { print firstbit $1 ".mp3" secondbit $1 ".wav" thirdbit }
>
> ********************************** End batch.awk
> ****************************************
>
> You can add -y to override the "output already exists" check.
>
> For example, if you run this command over and over again, it finishes OK.
> The output redirection removes the scum from the screen.
>
> ffmpeg -y -i "Aria.mp3" -acodec pcm_s16le -ac 2 -ar 48000 "Aria.wav" 2>NUL
>
>    Paul
>
>

I'd be very surprised if W10 insisted on the exact bit rate etc.
I just tried this WAV file that's part of my website as a Windows 7
system sound and it played fine.

https://www.Brian-Gregory.me.uk/Sounds/Purr.wav

Input #0, wav, from 'Purr.wav':
Duration: 00:00:11.87, bitrate: 45 kb/s
Stream #0:0: Audio: adpcm_ms ([2][0][0][0] / 0x0002), 11025 Hz, 1
channels, s16, 44 kb/s

--
Brian Gregory (in England).

On 25/04/2023 09:05, Paul wrote:
> The description here indicates it's a "troubled" format.
>
> https://en.wikipedia.org/wiki/WAV
>
>    "The RIFF specification attempts to be a formal specification, but its
>     formalism lacks the precision seen in other tagged formats."

ADPCM inside WAV files certainly used to work.

I used to make and play ADPCM compressed WAV files of music on Windows 3.1.

--
Brian Gregory (in England).