No, I didn’t specify the audio drivers. I assumed that Dell would just build the computer properly, because that’s their area of expertise. However, after dealing with them, I can now easily imagine they could have built one or more components incorrectly.
If something is incorrect about the audio drivers, then why does that affect only Audacity, while all other sound applications function perfectly?
I will also mention that in the process of finding a company to build a Windows 7 computer for me, I learned that most companies now use Realtek as the manufacturer for the sound components; and Realtek apparently doesn’t manufacture an integrated sound recording device.
I chose to install Windows 7 because the many vst instruments and effects I use will all work with Windows 7, but many of them do not work with Windows 10. And many do not work with Macintosh.
Audacity is more important to me than this new computer. If you are able to definitely determine that Audacity cannot work properly with this computer because the drivers or something else are incorrect, then I can ensure that the correct drivers are installed (if you can provide me with the information necessary to accurately get that corrected), or I can return the computer (if I act within the next few days).
If I return the computer, then I could certainly use some advice from other Audacity/Windows7 users regarding how I might best acquire a different computer which will properly serve my music-creation needs.
I should also mention that I greatly appreciate the time and effort being put into this by Gale and Steve.
Go to the Dell site, enter your exact computer model number, select Windows 7 64-bit as the operating system then see if there are audio drivers available.
If so, install the latest available audio drivers then reboot.
I am not saying this will solve the playback issue you hear in Audacity, but it is one thing I would definitely check.
Please also try changing the project rate to 48000 Hz as I suggested.
I just posted an edited version of my previous post, adding additional information and thoughts; and I see you have already responded to that previous post.
I will do as you recommend, this evening after returning home from work. Then I will let you know the results.
Because Audacity can choose sample rate (project rate), the quality of resampling from one rate to another (if that is required), and different “audio hosts” (different interfaces for accessing the same sound device).
Realtek do make built-in sound devices for computer motherboards, which should be supplied complete with drivers specific to that motherboard directly to computer manufacturers.
Realtek only make available generic audio drivers from their site. These drivers should normally not be used because they will not be properly matched to the motherboard.
If Dell installed generic Realtek drivers, Windows 10 drivers or no drivers (thus letting Windows use its own even more generic drivers), it “might” explain the issues you are having.
I don’t have Skype on the new computer. The only music-related software apps that I have installed during these first few days are Audacity, LMMS, NI Kontakt, NI Reaktor, and a small number of my favorite vst instruments and effects…
When I get home, I’ll look at the Task Manager to see if there are any resident audio-related programs running in the background, as you suggested.
I have also brought one of the Dell technicians into the loop on this issue, so he can hopefully provide some helpful input, as well. Though he doesn’t make music, like we all do, so his insight into our issues and goals will probably be quite limited.
Also, I already extended thanks for the attention and assistance offered by Steve and Gale — I also wanted to take a moment and thank kozikowski, as well.
Please don’t go back and change old postings. We don’t always go back to the beginning for each response and changing a setting or comment at the beginning of a long posting can cause a lot of puzzled looks.
You know that cocker spaniel tilted head thing? “Wait. What did he say…?”
You can simply right-click the speaker icon by the system clock and choose Recording Devices to see if you have any recording devices enabled or not. Those NI apps might take exclusive control of the sound device.
I don’t know if such an app having exclusive control was running while Audacity was launched if it would cause the Audacity list of devices to be empty, or if Audacity would list the devices but error when playing or recording. I thought the latter would happen, but I could be wrong.
It may not be a driver problem that recording devices are hidden. Many drivers will normally hide all but the internal microphone. You can right-click in empty space in that Recording tab in Windows Sound, Show Disabled Devices then right-click again, Show Disconnected Devices, then right click the devices and Enable.
I just got home and saw your message about right-clicking in the Windows Sound dialog box, to see if there are any invisible disabled recording devices.
Yes, that caused “STEREO MIX Reaktek High definition Audio” to appear. So I enabled it.
I opened Audacity; and now that is displayed as an input option. And in Audacity’s Audio Host box, I now see Windows Direct Sound as an option, in addition to MME and WASAPI.
YAY!
I imported one of my bassline audio-files, and played it back. Still heard the extra high-pitched noise.
Followed your suggestion to change Project Rate to 48K Hz. Played back the audio file again — NO HIGH-PITCH NOISE!
Imported a different bassline audio file into Audacity, played it back. Again, no high-pitch noise!
I think that means my issue is resolved, I can use my beloved Audacity as I always have, and I don’t have to send my computer back to Dell.
YAY!!!
Please let me know if you recommend that I take any further actions with respect to this issue you have helped me address.
Other than that, I have just one last question: because I’ve always used 44K Hz in all my music creation (except when a music supervisor specifically requests that I do it in 48K Hz), is there anything special I should be aware of, if I’m going to use 48K Hz in Audacity, going forward?
Thanks so very much to Gale, Steve and kozikowski.
In fuzzy generalities, 48000 sample rate is for television and video editing. Most of my recording work was at 48000 because I knew the very next office after mine was Video Editorial.
44100 is the sample rate used in Audio CDs. It’s the generic sample rate used in the Audacity default and is generally accepted on Earth. All of it. That’s why, at the risk of being a Debbie Downer, having a system not work at all correctly at 44100 does get my attention. If something goes wrong in future, you will always have this nagging doubt not that something broke, but that your 44100 noise problem just got worse.
Again, fuzzy generalities: any system that accepts one will accept the other and you can convert in Audacity by changing the number in the lower left. That might be worth an experiment. Do a production at 48000 and convert it to 44100 just before you export it.
According to that Info there were no Recording Devices at all in Windows. Did you already have some input showing in the Recording tab of Windows Sound before you enabled stereo mix? If so I guess NI “might” have been using it.
I would guess if you go the Playback tab of Windows Sound, right-click the audio output you are using, Properties, then “Advanced” tab, you will see Default Format set to 48000 Hz. If so and you set that to 44100, you may be able to use MME host in Audacity and leave the Audacity project rate at 44100 Hz. It would save changing the project rate back to 44100 Hz when you export.
If that brings back the high-pitched noise, try enabling both Exclusive Mode boxes underneath Default Format, and choose Windows DirectSound host in Audacity. This should make Audacity ignore whatever the Default Format rate is in Windows Sound, so if you set 44100 Hz project rate in Audacity you should not get the high pitched noise.
That bass sound is not really hard to play. If your sound device makes such an issue of resampling you could certainly check at Dell’s site if you have the correct Windows 7 audio drivers. But it’s up to you. If you still need to change project rate to 48000 Hz even after the changes I suggest in Windows Sound, it does cast suspicion on the sound device drivers.
I heard back from the tech support guy at Dell. He seems to be totally clueless about the whole subject of audio drivers, and what drivers were installed, and what available drivers might represent an improvement over what was installed in this computer.
Anyway, an acceptable level of functionality has been achieved, thanks to Gale, Steve and kozikowski.
Am I the one who has the privilege of adding the word ‘RESOLVED’ to the original post? Or can only you guys do that?
Audio is the last vestige of technical black magic. People who can go for ten minutes about video oversampling and display frame rates go all “deer-in-headlights” when you want to add sound.
Sound without the picture is a radio show or podcast. Picture without the sound is a rehearsal…
When you are satisfied with the outcome of one of your topics, feel free to add “[SOLVED]” to the subject line in your final reply and in your original post.
Only moderators and admin can lock a topic, but we can do that after you have marked it “solved”.
