|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
137.254.4.6
In Reply to: RE: Windows 10 and 41,000 Hz audio posted by Jaundiced Ear on July 01, 2015 at 20:00:27
I don't know. I've been very close to getting the Windows 10 preview, but I noticed that it could be out by August 1st anyway, so I might as well wait.
What exactly does all these Hz settings do for you? Just wondering as I just play with normal settings usually, which is?? Isn't 41KHz the normal sampling rate anyway??
I briefly tried Windows 10 at the Microsoft store: I found it as disorienting going BACK to the Start button as when I first found out that Windows 8 DIDN'T have a Start button!
Follow Ups:
" Isn't 41KHz the normal sampling rate anyway??"
It is if you are playing CDs or FLACs ripped from CDs. Other sources, such as DVDs or downloaded music files, may have other sampling rates. The idea is to match the PC's sampling rate to that of your source. If you've read these forums for a while you'll know that I'm a champion of CD resolution playback (Redbook), so this failing in Windows 10 is a pretty big deal for me.
JE
Most likely, this is hardware related and/or device driver related. It could also be "cockpit error" on your part as there could be new rules as to how programs share the audio stack and who gets control over sampling rate.
Frankly, I could care less about bugs related to the Windows audio stack. My two DACs both have ASIO drivers and I don't use the Windows audio stack for playing music files.
Tony Lauck
"Diversity is the law of nature; no two entities in this universe are uniform." - P.R. Sarkar
I'm guessing it's driver related. Builds before 10130 worked fine. 10130 killed off the 44,100Hz settings and they haven't worked since. This is not some fancy third party sound card either, but the bog stock Realtek chip. It shows in the device manager, says it is properly installed, it just doesn't play sound unless it's on one of the 48,000Hz settings.
I don't use this PC for high end audio, but I do use it watch things such as you tube or news snippets. Sound can be pretty important for them, too!
JE
Pretending that 44.1 kHz is SO important for watching youtube or whatever on your PC is rubbish, honestly.
As long as it plays, it's fine.
In this context worrying about sound quality would be wasted energy.
Now if Win10 somehow refused to let your music player software, like foobar, play your existing .wav files at 44.1kHz, now THAT would be a problem. But I wouldn't put it past the intellectual property lawyers to arrange something like that, since by now there must be billions of .wav hard drive copies of CDs burned by, say, EAC or dB power amp, and those are potentially copyright issues for any software manufacturer, including Microsoft. These are real issues. I certainly doubt there is any paid lobby which would pay to have 44.1khZ decoding included in the feature set of win10. But Microsoft would look pretty stupid if it refused to play its own .wav file format completely.
I'm not saying sound quality is an issue on that particular machine, far from it. I am saying that it is a test machine for the Windows 10 previews, and for the last month or so a pretty core part of Windows audio has been broken. If you set the audio output to 44100Hz, you get NO sound output.
JE
"I am saying that it is a test machine for the Windows 10 previews, and for the last month or so a pretty core part of Windows audio has been broken. If you set the audio output to 44100Hz, you get NO sound output."
Windows audio is of zero interest to anyone serious. It is a non-issue.
I have to disagree. While "serious" may mean a studio or producer of commercial projects with extensive facilities, multiple sessions and lots of editing, it can also mean someone - such as myself - who does recordings for schools and other organizations like churches and local performing groups, who will not pay $1,000+ to have their recording done on a purpose-built audio recording and editing system. I know a guy who has such a rig for location recording. He brings $25,000 worth of stuff to a site, and gets paid $500 for 6 hours of work. The numbers just don't add up. On the other hand, a Win-based PC with a good sound card, a FireWire or other interface, five good microphones and preamps can be had for under $10,000, and still get paid $300 - $500 for the job.:)
Edits: 07/03/15
As carcass93 already mentioned players will bypass the Win audio.
I misunderstood. I thought you were talking about dedicated hard drive recorders which don't use Windows PCs.
:)
I personally do not do any computer recording and I think most here do not either. The last recording I did was on half track tape several milleniums ago! :)
Instead, to built-in audio facilities (services etc.) in Windows OS, which get completely bypassed in properly used for audio playback Windows machine.
Windows Audio is kind of irrelevant in a context of quality audio playback.However, DirectSound still has to be able to function at correct sample rate - I wouldn't want to hear signal resampled to 48 KHz, even if it's only for sampling music on YouTube, through Realtek chip and Yamaha computer speakers.
Edits: 07/02/15
Normally when I listen to music I don't run any other applications. But sometimes I use the computer to play samples from music web sites or watch videos. If I do this, then Firefox glombs on to the Windows 7 audio stack and will lock in the sample rate. If I then try to run HQPlayer through the ASIO interface there can be a "war" as to the sample rate. Sometimes the result is comical, reminiscent of playing an LP on the wrong turntable speed. The cure is to exit both applications and start over. One other thing that I discovered is that the Mytek driver is perfectly happy to take audio from its ASIO interface and its Windows interface and mix them.
It is possible to avoid all of these conflicts by dispatching the Windows audio stack to a different audio device. This is the only certain cure, and it guarantees no "You have mail!" warnings coming out of the speakers. Another way for me to lock out Windows is to run HQPlayer and have it convert to DSD. This puts the device driver and DAC in DSD mode and the Windows audio stack doesn't support DSD, so it's locked out.
Tony Lauck
"Diversity is the law of nature; no two entities in this universe are uniform." - P.R. Sarkar
That would indeed be a big deal.
Joe
Yes, I meant 44,100Hz. And yes, to me it seems like a pretty big deal.
JE
Joe
Post a Followup:
FAQ |
Post a Message! |
Forgot Password? |
|
||||||||||||||
|
This post is made possible by the generous support of people like you and our sponsors: