Create an account to follow your favorite communities and start taking part in conversations.
r/FL_Studio
Posted by4 years ago
Archived
What does this mean? How can i fix it? Please. Help me .
I go to asio panel and in the wdm device list whenever I choose my bluetooth speaker as the output it displays «Warning: The needed sample rate (44100Hz) couldn’t be set or is not suported by the ASIO driver. Please try another sample rate. » but it still applies the change and plays everything in shitty quality and wrong pitch and stuff.
This thread is archived
New comments cannot be posted and votes cannot be cast
level 1
I’ve been having a similar problem using the Scarlett 2i4, only solution I’ve found is to just use FL Studio ASIO instead of the interface’s driver. Kind of defeats the purpose of having an audio interface but oh well.
level 1
Have you tried other sample rates? Maybe 48k?
level 1
You may need to go to the sound settings in control panel (in windows) and make sure that your audio devices are set to use your desired sample rate there. Look under sound -> playback device -> properties -> advanced. My guess is that the WDM device is set to 48k under sound options, which conflicts with the 44k you’re tying to use in FL. There are probably similar troubleshooting steps for a mac.
level 2
Thank you SO much. Changing my sample rate just fixed my problem. I was about to give up until I found your comment.
level 1
Reinstall the ASIO driver? Or try using FL Studio ASIO or vice versa. Does it work when you don’t use ASIO(like using the primary driver or smthn)?
level 2
I go to asio panel and in the wdm device list whenever I choose my bluetooth speaker as the output it displays «Warning: The needed sample rate (44100Hz) couldn’t be set or is not suported by the ASIO driver. Please try another sample rate. » but it still applies the change and plays everything in shitty quality and wrong pitch and stuff.
level 1
guys i got the solution, just turn off the «slim level box …» option and turn on your sound target or whatever you are using (all i just said is you have to do it inside the asio4all panel in fl studio)
About Community
The best FL Studio resource on the internet!
Several Windows users have been reaching us with questions after seeing the “The sample rate for your microphone isn’t supported” error whenever they open the Xbox App and try to create a party. All affected users are reporting that the microphone or the headset works fine with any other application. As it turns out, the issue is not exclusive to a certain Windows version since it’s confirmed to occur on Windows 7, Windows 8.1 and Windows 10.
What is causing the “sample rate for your microphone isn’t supported” error?
We investigated this particular issue by looking at various user reports and by analyzing several fixes that are commonly recommended by those that managed to resolve the issue successfully. As it turns out, there are several different scenarios with the potential of triggering this issue. Here’s a shortlist with the most common culprits:
- Common recording device inconsistency – This error can occur due to a common Audio Recording inconsistency that can be caused by two conflicting apps or by a user mistake. In this case, you should deploy the Recording Audio troubleshooter (a built-in utility designed to identify and recommend an appropriate repair strategy).
- Bad windows update – We haven’t managed to pinpoint the exact update that caused the issue, but during two months, there was a surge of user reports complaining about this issue. Since then, Microsoft has released a hot-fix for the issue that is confirmed to fix the problem. With this in mind, you can resolve the problem by installing every pending update, bringing your Windows version to a newer version than 1803.
- Dedicated drivers are not compatible with the Windows version – As it turns out, several headsets haven’t yet been optimized for the latest Windows version. So if you use them with the dedicated drivers, chances are you’ll get this error message due to some incompatibility issues. If this scenario is applicable, you will be able to resolve the issue by uninstalling the current driver and reverting towards the generic one.
- Xbox Live Core service is down – Although this is an unlikely culprit, it’s confirmed that there’s a direct link between this error message and the status of the Xbox Live services. If the core services are down, the party requirements won’t be met and this error will show up. In this case, the only fix is to wait until the services return online.
- NAT Type is set to Close – Another potential culprit is a NAT Type that is set as closed. The Xbox Companion app might trigger this error because it can’t communicate with the Xbox servers. In this case, you can resolve the issue by repairing the NAT using the Fix it tool included in the Xbox Networking tab.
- Glitched Xbox App – Another reason that might trigger this error is a glitched Xbox app. Corruption inside the temp folder can fool the Xbox server that the connection is not proper. If this scenario is applicable, you should be able to resolve the issue by resetting the Xbox app altogether, deleting all temporary files.
Method 1: Running the Recording Audio troubleshooter
Before you try more complex repair strategies, you should start this troubleshooting quest by ensuring that your Windows version is not capable of resolving the issue automatically. As it turns out, an incorrect recording configuration can cause the “sample rate for your microphone isn’t supported”.
Under some circumstances, you might be able to fix it simply by running the Recording Audio troubleshooter and letting it recommend a suitable repair strategy. Some users have managed to fix the issue by deploying this troubleshooter and then restarting your computer.
Here’s a quick guide on running the Recording Audio troubleshooter to resolve the “sample rate for your microphone isn’t supported” error:
- Open a Run dialog box by pressing Windows key + R. Then, type ‘ms-settings:troubleshoot‘ and press Enter to open up Troubleshooting tab of the Settings app.
Accessing the Troubleshooting tab - Once you’re inside the Troubleshooting tab, move down to the right-hand menu and click on Recording Audio. Then, click on Run the troubleshooter to start the utility.
Running the Recording Audio troubleshooter - Wait until the analysis is complete, then click on Apply this fix if a viable repair strategy is recommended.
Apply this fix - After the fix is enforced, restart your computer and see if the issue is resolved at the next system startup.
If the same issue is still occurring or the Recording Audio troubleshooter didn’t manage to find an issue, move down to the next method below.
Method 2: Update Windows 10 build to the latest
If the first method didn’t allow you to resolve the issue, you should proceed by ensuring that every pending update is installed and you’re using the latest Windows 10 build available for your version. Several affected users that we’re struggling to resolve the same issue have managed to fix it by installing the Feature update version 1803.
This confirms the suspicion that Microsoft has quietly released an unannounced hotfix for the issue. Here’s a quick guide on installing every pending update:
- Press Windows key + R to open up a Run dialog box. Next, type “ms-settings:windowsupdate” inside the newly appeared text box and press Enter to open up the Windows Update tab of the Settings app.
Run dialog: ms-settings:windowsupdate - After you manage to get inside the Windows Update tab, click on Check for Update, then wait for the initial scan to complete.
Checking for updates on Windows 10 - Wait until the initial scan is complete. After the updating utility figures out which updates apply to your computer, follow the on-screen prompts to install them one-by-one.
Note: In case you’re prompted to restart before you get the chance to install every pending update do so but make sure to return to the same window and continue with the rest of the update installations until your Windows version is up to date. - Once every pending update is installed, restart your computer and see if the issue is resolved once the next startup is complete.
If you’re still seeing the “sample rate for your microphone isn’t supported” error when you open the Xbox app, move down to the next method below.
Method 3: Installing Generic drivers for your Microphone
As it turns out, another common cause that will produce this “sample rate for your microphone isn’t supported” error is an improper microphone driver. Several affected users have managed to resolve this issue by uninstalling the current driver to let Windows install its generic driver.
So far, there have been no reports of this issue occurring while the generic drivers are installed. We have only been able to confirm the effectiveness of this method on Windows 10, but the steps below can be followed on both Windows 7 and Windows 8.1.
Here’s a quick guide on uninstalling the current microphone drivers to allow Windows to install the generic drivers:
- Press Windows key + R to open up a Run dialog box. Next, type ” mmsys.cpl” and press Enter to open up the Sound window.
- Once you’re inside the Sound window, select the Recording tab and select the Microphone that you’re having issues with. With the recording device selected, click the Properties menu.
- After you’re inside the Microphone Properties menu, select the General tab and click on the Properties button under Controller information.
- Inside the next setup screen, select the Driver tab from the list horizontal menu and click on Uninstall Device. Then, click on Uninstall again to confirm the uninstallation.
- Once the process is complete, restart your computer to allow your operating system to install the generic drivers. You might be prompted to do so automatically
- After the next startup sequence is complete, repeat the action that was previously triggering the “sample rate for your microphone isn’t supported” error and see if the issue is now resolved.
If you’re still encountering the same issue, move down to the next method below.
Method 4: Checking your Xbox Live service status
As several users have reported, this particular issue can also occur in instances where one of more critical Xbox Live Core services are down or undergoing maintenance. Although the two doesn’t seem to be related, some users said that the “sample rate for your microphone isn’t supported” error stopped occurring once the Xbox Core services were back online.
You can check if this is the cause of your problem by visiting this page here. If all services have a green check-mark, it means that there is no problem with the core services and you can proceed with the next method below.
If the investigation reveals a problem with the Xbox Live services, wait a couple of hours before checking back if the issue is resolved automatically.
If there are no issues with the Xbox Live services, move down to the next method below.
Method 5: Fixing the NAT type
As it turns out, the inability to create parties can also be related to the fact that your NAT type is Closed. This can produce errors with various multiplayer games and can also interfere with the Xbox App‘s ability to create and maintain parties.
Several affected users that we’re also struggling to resolve this issue finally managed to do so by opening the NAT using the built-in Fix in utility. After doing so and restarting their machine, some said that the “sample rate for your microphone isn’t supported” error was no longer occurring.
Here’s a quick guide on Fixing the NAT type from the Xbox Networking tab:
- Press Windows key + R to open up a Run dialog box. Next, type “ms-settings:” and press Enter to open up the Settings app.
Accessing the Settings app - Once you’re inside the Settings app, scroll down to the bottom o list and click on Gaming.
- From the Gaming section, select the Xbox Networking from the vertical menu on the left.
- Wait until the NAT analysis is complete. If it reveals that the NAT type is closed, scroll down below and click on Fix it to start the troubleshooter capable of opening it.
Fixing a Closed NAT Type - Once the process is complete, restart your computer and see if the issue is resolved at the next startup sequence.
Method 6: Resetting the Xbox App
If none of the methods above have allowed you to resolve the issue, chances are you’re dealing with a glitched instance of Xbox Live App or Xbox Companion app. In this case, the fix with the most likelihood of succeeding is to reset the app, forcing it to load all components once again the next time it’s started.
Several affected users have confirmed that the issue was successful for them. If the error is caused by a glitch, there’s a high chance that the sample rate for your microphone isn’t supported” error will be fixed after you do this and restart your computer.
Here’s a quick guide on resetting the Xbox app that is causing the error message:
- Press Windows key + R to open up a Run dialog box. Once you’re inside the Run dialog box, type “ms-settings:appsfeatures” and press Enter to open up the Apps & Features screen of the Settings app.
Accessing the Apps & Features Menu - After you’re inside the Apps & features menu, scroll down through the list of installed UWP applications and locate the Xbox app that is triggering the error message.
- Once you see it, click on it once to select it then click on the associated Advanced Options hyperlink.
Accessing the Advanced Options menu of the Xbox app - Inside the Advanced Options menu, scroll down to the Reset tab and click on Reset to initiate the process.
Resetting the Xbox app - Click the Reset button at the confirmation prompt to start the process, then wait for it to complete.
- Restart your computer and see if the issue is now resolved.
Kevin Arrows
Kevin is a dynamic and self-motivated information technology professional, with a Thorough knowledge of all facets pertaining to network infrastructure design, implementation and administration. Superior record of delivering simultaneous large-scale mission critical projects on time and under budget.
Hello guys, I have installed SoundWire 2.1 64 Bit version on my Arch Linux x86_64 but I have a little problem, when I open the SoundWire Server the program says this: «Audio capture running at 48 kHz», when I open pavucontrol the SoundWire Server is not listed on tab Recording and the program just doesn’t work, don’t play any audio on my phone, but if I’m using the 32 Bit version of Arch Linux when I open the SoundWire Server the program says this: «Audio capture running at 44.1 kHz» and are listed on tab Recording of pavucontrol, and the audio works perfectly. I install both versions of Arch Linux as the same, the only diference is that one is 32 Bit and the other is 64 Bit. So, the problem is with x86_64 version, anyone can help me? Thank you in advance! 
Here is the output when I open SoundWire Server on terminal with Arch Linux x86_64:
[eduardo@chappie ~]$ SoundWireServer
/usr/bin//win_bitmap.bmp
This server's probable IPv4 address: 192.168.0.102
SoundWire Server v2.1
Initializing server network communication
Portaudio reported default input device sample rate is 48000 (may be incorrect)
Audio stream info: sample rate = 48000, input latency = 0.0213333 sec
Audio input device opened successfully
SoundWireServer: Audio capture runningLast edited by eduardojunio (2015-03-28 03:31:51)
Сказали же уже выше:
на самом деле звуковуха используется как системная и кто-то успел захватить ее раньше (в монопольном режиме)
В этом трабла, при чём тут хр.
Если звуковуха стоит по-умолчанию как системная, она воспроизводит всё что звучит — кино, мп3, вавки, флэш и пр. А они могут быть любой частоты. Ну вот человек включает куб после просмотра очередного выпука прожекторперисхилтон, а он имеет звук 48 килохерц, и звуковая на них так и стоит после просмотра этого весёлого сериала, а куб имеет частоту 44. Куб обязан соединиться со звуковухой при включении — он соединяется и ба!.. Что я вижу мамадарагая — говорит он, — частота-то звуковухи с моим 44-херцовым проектом не совпадает, пиля! Дай-ка я скажу об этом хозяину. Что собсна и делает, после чего пытается переключить звуковуху на 44, но.. поздно, батенька.. :spiteful: Более того, куб заточен под ASIO интерфейс (изобретённый кстати фирмой Steinberg, собсна создавшей кубэйс), и при включении он обязан ещё и в режим ASIO звуковуху перевести с директ-х’овского режима винды, в результате шок получают все — и куб и звуковая и их незадачливый хозяин.. Поэтому, чтобы не портить себе нервы этой хренью, burken, тебе надо купить вторую звуковуху, или назначить на звук системы (для винды и всех её плееров) встроенную (на мамке которая), а кубэйсу, как точно и красиво сказал Alf_Zetas, — монопольно отдать M-audio. Причём навеки! И чтоб никакая кака даже близко не приближалась к его личной монопольной звуковой карте! :mamba:
Но лучше купить серьёзную карту для куба — и я однозначно могу в этом смысле посоветовать только RME AIO. Она, конечно, дороговатенькая, но лучше ничего нет, причём это конкретно я говорю. А на винду поставить м-аудиву, ибо во-первых и кино с хорошим звуком иногда хочется посмотреть, и в игру поиграть так чтоб волосы дыбом вставали от звука крыльевых пулемётов и! — что важно! — иметь возможность, работая в кубэйсе, включить спец-про-прогу типа мелодины стэндэлон, или ресайкли, или самплы, или контакта либо какого-нить другого сэмплера и т.д., имеющих ASIO интерфейс для работы со звуком, и спокойно работать в них обоих параллельно — и в кубе и в этой проге с ASIO (M-audio имеет ASIO а встроенная звуковуха не имеет). Но в любом случае, как бы то ни было, кубэйсу нужно отдать одну из звуковух в единоличное пользование и смириться с этим. Не случайно ведь золотые годы Про Тулса прошли под девизом — «работаю только со своим железом!» Ща вот он решил прогнуться под чужие железки ну и где протулс.. :SHABLON_padonak_02: Вот представь, что кубэйс это тот же ПТ и купил ты его в комплекте со звуковой картой. Просто забыл её в магазине почему-то. Вперёд! :dance:
|
I recorded songs on another computer which had the sample rate to my StudioLive at 48kHz. I am now trying to edit them on a different computer using Windows sound drivers. I have set every playback and recording interface that I could find to 48kHz, but I still get this warning. Songs play fine, so does this warning matter? Is there something else I need to do? Thanks for your help! |
|
StudioOne will automatically adjust to set your system sample rate, but you really don’t want it to in this case. Personally I would close the project and go to the start page, and check to make sure your interface is set to the sample rate you think it is. Also keep in mind that if at some stage, you have inadvertently saved your project at the different sample rate, say 44.1kHz, that is the sample rate it will try to use. You may simply need to resave your project set to your desired sample rate (48kHz) and problem solved. I would be using the ‘save as’ feature to make progressive files of your project just in case you have unexpected errors. You also may have accrued quite a large number of files in the cache folder if you have tried to work at a different sample rate. Although innocuous, you may want to ‘save your project to new folder’ so you can delete all these cache files and free up hard disk. The cache could be several Gbytes by now.
i7 3770,ASUS P8Z68-V-LE RME Multiface x2,RME ADI2,Lucid 2496. Casio PX-3,Yamaha V50,Korg 05,Roland SH-01,Korg Nanopad2,Behringer BCF,BCR2000(studio). https://soundcloud.com/andrew-emery |
|
Thank you for the feedback. I see the error on the song page. Here is what I see: I have set all recording and playback rates at 48kHz, but I still get this warning. If I don’t plan to record with this setup, does this warning matter? |
|
Most ASIO sound devices will be able to use 44.1 or 48kHz. Is your audio device able to switch to 48kHz? Maybe that’s your problem. If you aren’t recording, you won’t create new files at the wrong sample rate, but your project will use the cache to convert all the files to the new rate. Someone else may be able to help you with any complications this may create, because for me, whenever it happens I just fix it. You may have some application running that is clamping the sample rate to 44.1, making impossible for StudioOne to select a new sample rate. StudioOne is able to take care of this mismatch for you, but I cannot say whether it will impact the sound quality, or require more CPU at times. To preempt what may be causing this, have you gone through and done all the basic tweaks on your PC? I know one of those things is to turn off ‘windows sounds’, you know those annoying little sounds that play whenever windows wants to tell you how good it is?
i7 3770,ASUS P8Z68-V-LE RME Multiface x2,RME ADI2,Lucid 2496. Casio PX-3,Yamaha V50,Korg 05,Roland SH-01,Korg Nanopad2,Behringer BCF,BCR2000(studio). https://soundcloud.com/andrew-emery |
|
On my start up I’m getting a Then it says Can anyone help me with that |
|
I suggest a support ticket. I am not familiar with the first message. There may be more going on than we know. Matt Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon S1Pro V5 |
|
I was getting the same message. My sound card was at 48 and S1 was at 44.1. Here’s what I did on Windows 10 to correct. This seems to have gotten rid of the message. I hope this helps. |
|
I don’t know, but there seems to be something buggy with all this. I often will get a messaged saying the sample rates don’t match, when starting a new song / project, and then often when reopening a song that had this error message first time. But the weirdest thing is I get something like: «Sample rates don’t match. Sample rate set = 0.0KHz…» Which is bizarre, as I have everything everywhere set to 44.1KHz. I don’t use any other sample rate for anything, ever. This is just to me a bug that is an annoyance more than anything. I get the pop-up error message from time to time, but it doesn’t interfere with the sample rates in my projects / songs at all. I think I even raised this as a bug with Studio One support but got no help on it, so I just have to ignore it and carry on. |
|
Just an FYI. If you are on a PC, and you use your interface as the soundcard, turn off Windows event sounds. Those sounds are at 48.0 sample rate, and will change the sample rate of the soundcard when they are played. Matt Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon S1Pro V5 |
|
This is good advice, and is good advice also because we don’t want a windows event triggering a sound right in the middle of recording, or during mixing in our DAW, for example. I do turn off Windows sounds always, when setting up my PC for DAW use. But I wonder in Windows 10, as you said, the default sound sample rate is 48KHz.. maybe this could be causing problems? |
|
It could be Justin. One of the many little annoying things that can happen. Also watching a movie on the pc would change the sample rate. FWIW, I don’t think its just a Win 10 thing. I have had this happen on 7 also, and it probably goes back further than that. Matt Lenovo ThinkServer TS140 Win 10 64bit, 8GB RAM, Intel Xeon S1Pro V5 |
|
I get this message too; even on a fresh install of Windows 10. I have my sound interface and the windows sound driver set to 48, but Studio One insists the Windows Sound is at 44. |
by scottyo7 on
Fri Jul 05, 2019 11:15 am
|
See above — have you tried what Ranger Sam said? There are a few steps there to methodically go through but after that you should be able to open S1 and be good. Please add your Signature/Info to your Profile here. |
Who is online
Users browsing this forum: No registered users and 11 guests
SoundWire helps us stream any audio and music from PC to Android phones and tablets. It works with Windows, Linux, Raspberry Pi and Android. In order to mirror or cast sound from computer to Android, you need to install SoundWire Server on PC and install SoundWire client on Android phone. Then connect to SoundWire Server using the SoundWire for Android. SoundWire for Windows gives the IP address which you can connect it. In SoundWire for Windows 10 however we found this IP address does not work. We can’t connect to SoundWire in Win 10 from the mobile device. After some research I found that it is possible to connect to your PC local IP other than the IP provided by SoundWire Server on your PC. So if anyone also run into the SoundWire on Windows 10 can’t be connected issue, you can follow these steps see if any luck.
Connect both your Windows 10 PC and Android phone to the same wi-fi network or wireless router. Then on the Windows 10 computer, right click on the Start icon, choose Command Prompt from the pop-up menu, the Command Prompt should open right away. Type in ‘ipconfig‘ and press Enter on the keyboard to execute the command. Find the IPv4 address in the Command Prompt, you can then find out your local IP address of the Windows computer in your LAN.
Now on your Android device, run the Soundwire app. Enter the Windows 10 local IP address we found above, and then tap on the soundwire button above the IP address, you would be successfully connected to your SoundWire server on Windows 10.
The playback options available are: Master, Headphone, Headphone Mic Boost, Speakers, PCM, Mic Mute-LED Mode, S/PDIF, S/PDIF1, S/PDIF1, S/PDIF2, S/PDIF3, S/PDIF4, S/PDIF1, Auto-Mute Mode.
Perhaps its a stupid question, but I did not find how to select a desired playback output while in Alsa…
Here’s the output you asked
Code: Select all
$ amixer
Simple mixer control 'Master',0
Capabilities: pvolume pswitch pswitch-joined
Playback channels: Front Left - Front Right
Limits: Playback 0 - 65536
Mono:
Front Left: Playback 65536 [100%] [on]
Front Right: Playback 65536 [100%] [on]
Simple mixer control 'Capture',0
Capabilities: cvolume cswitch cswitch-joined
Capture channels: Front Left - Front Right
Limits: Capture 0 - 65536
Front Left: Capture 65540 [100%] [on]
Front Right: Capture 65540 [100%] [on]
Code: Select all
$ lspci | grep -i audio
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)Code: Select all
$ lsmod | grep '^snd' | column -t
snd_hda_codec_hdmi 73728 1
snd_hda_codec_realtek 159744 1
snd_hda_codec_generic 98304 1 snd_hda_codec_realtek
snd_soc_skl 180224 0
snd_soc_hdac_hda 24576 1 snd_soc_skl
snd_hda_ext_core 36864 2 snd_soc_hdac_hda,snd_soc_skl
snd_soc_sst_ipc 20480 1 snd_soc_skl
snd_soc_sst_dsp 36864 1 snd_soc_skl
snd_soc_acpi_intel_match 45056 1 snd_soc_skl
snd_soc_acpi 16384 2 snd_soc_acpi_intel_match,snd_soc_skl
snd_hda_intel 57344 6
snd_intel_dspcfg 28672 2 snd_hda_intel,snd_soc_skl
snd_soc_core 315392 3 soundwire_intel,snd_soc_hdac_hda,snd_soc_skl
snd_compress 32768 1 snd_soc_core
snd_hda_codec 172032 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda
snd_hda_core 110592 8 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_hdac_hda,snd_soc_skl
snd_hwdep 16384 1 snd_hda_codec
snd_pcm 135168 10 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_compress,snd_soc_core,snd_soc_skl,snd_hda_core
snd_timer 49152 1 snd_pcm
snd 110592 20 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcmCode: Select all
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC3246 Analog [ALC3246 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
stevengarland
- Level 5
- Posts: 708
- Joined: Tue Mar 05, 2019 4:04 pm
- Location: Michigan
Re: No sound Dell XPS 9700
Will one of you fine folks please post a final corrected version of the commands so that a simple guy like me can give it a try.
Thanks
Keep It Simple Sweetheart
-
hglee
- Level 6
- Posts: 1423
- Joined: Fri Jun 22, 2018 4:31 pm
Re: No sound Dell XPS 9700
Post
by hglee »
That fix doesn’t appear quite in order.
Once we do cd soundwire-dkms/ as the second step, we can’t do sudo mv soundwire-dkms /usr/src/soundwire-1.4.0 as a later step, because there isn’t another soundwire-dkms subdirectory inside of soundwire-dkms/. I’d guess we need ‘..’ in there.
How about this? …
Code: Select all
git clone https://github.com/maaarghk/soundwire-dkms
cd soundwire-dkms/
git checkout latest-sofproject
sudo dkms add soundwire/1.4.0
sudo dkms build soundwire/1.4.0
sudo dkms install soundwire/1.4.0
cd ..
sudo mv soundwire-dkms/ /usr/src/soundwire-1.4.0
Ian?
Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU — 14″ WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
-
MrEen
- Level 23
- Posts: 18345
- Joined: Mon Jun 12, 2017 8:39 pm
Re: No sound Dell XPS 9700
Post
by MrEen »
Well, as you’ve already attempted most of these steps, let’s see this output:
If that actually returns stuff other than an error, I think this will probably work:
Code: Select all
cd
cd soundwire-dkms/
git checkout latest-sofproject
sudo dkms add soundwire/1.4.0
sudo dkms build soundwire/1.4.0
sudo dkms install soundwire/1.4.0-
stevengarland
- Level 5
- Posts: 708
- Joined: Tue Mar 05, 2019 4:04 pm
- Location: Michigan
Re: No sound Dell XPS 9700
Post
by stevengarland »
It returns an error:
stevengarland@stevengarland-XPS-17-9700:~$ ls -l /usr/src/soundwire-1.4.0
ls: cannot access ‘/usr/src/soundwire-1.4.0’: No such file or directory
stevengarland@stevengarland-XPS-17-9700:~$
Keep It Simple Sweetheart
-
hglee
- Level 6
- Posts: 1423
- Joined: Fri Jun 22, 2018 4:31 pm
Re: No sound Dell XPS 9700
Post
by hglee »
Oops, my earlier code won’t work either.
This is correct:
Remove the downloaded source folder from any previous attempt…
This will do as originally intended, with Ian’s addition, plus a necessary cd in the right place…
Code: Select all
git clone https://github.com/maaarghk/soundwire-dkms
cd soundwire-dkms/
git checkout latest-sofproject
cd ..
sudo mv soundwire-dkms /usr/src/soundwire-1.4.0
sudo dkms add soundwire/1.4.0
sudo dkms build soundwire/1.4.0
sudo dkms install soundwire/1.4.0
Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU — 14″ WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
-
stevengarland
- Level 5
- Posts: 708
- Joined: Tue Mar 05, 2019 4:04 pm
- Location: Michigan
Re: No sound Dell XPS 9700
Post
by stevengarland »
I am not sure just what to do here. «select all» gives this output:
stevengarland@stevengarland-XPS-17-9700:~$ rm -rf ./soundwire-dkms
stevengarland@stevengarland-XPS-17-9700:~$ git clone https://github.com/maaarghk/soundwire-dkms
bash: git: command not found
stevengarland@stevengarland-XPS-17-9700:~$ cd soundwire-dkms/
bash: cd: soundwire-dkms/: No such file or directory
stevengarland@stevengarland-XPS-17-9700:~$ git checkout latest-sofproject
bash: git: command not found
stevengarland@stevengarland-XPS-17-9700:~$ cd ..
stevengarland@stevengarland-XPS-17-9700:/home$ sudo mv soundwire-dkms /usr/src/soundwire-1.4.0
[sudo] password for stevengarland: *********************************************
Sorry, try again.
[sudo] password for stevengarland:
mv: cannot stat ‘soundwire-dkms’: No such file or directory
stevengarland@stevengarland-XPS-17-9700:/home$
If I am supposed to do one at a time and not «select all» please clarify.
Thanks
Keep It Simple Sweetheart
-
hglee
- Level 6
- Posts: 1423
- Joined: Fri Jun 22, 2018 4:31 pm
Re: No sound Dell XPS 9700
Post
by hglee »
I thought you’d already have the necessary code-building tools, from your previous troubleshooting exercises.
Copy-and-paste the following Terminal command line, to install the required software…
Code: Select all
sudo apt install git dkms build-essential linux-headers-$(uname -r)
Now let’s start over. Copy-and-paste this Terminal command line, to remove previous git code download…
Code: Select all
rm -rf ./soundwire-dkms # clean up
As a general rule, never «Select All» code here for more than one command-line that you’re copying into your desktop Terminal.
Each of the following eight Terminal command lines need copy-and-paste — one by one — pressing Enter after each…
Code: Select all
git clone https://github.com/maaarghk/soundwire-dkms
cd soundwire-dkms/
git checkout latest-sofproject
cd ..
sudo mv soundwire-dkms /usr/src/soundwire-1.4.0
sudo dkms add soundwire/1.4.0
sudo dkms build soundwire/1.4.0
sudo dkms install soundwire/1.4.0
Reboot.
Sound still not working? «Ahoy, MrEen?»
Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU — 14″ WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
-
MrEen
- Level 23
- Posts: 18345
- Joined: Mon Jun 12, 2017 8:39 pm
Re: No sound Dell XPS 9700
Post
by MrEen »
hglee wrote: ⤴Fri Jan 22, 2021 3:52 pm
Sound still not working? «Ahoy, MrEen?»
Thanks for adding some much needed assistance here hglee. I struggle with code blocks like the one you’ve helped with here.
I’m hoping like heck this is going to work. And if the sound isn’t working right off the bat, it could be a simple setting that pacmd list-cards and pacmd list-sinks should reveal.
The OP and I have been through the wringer trying to get this to work. Based on some outputs almost exactly matching Ian’s, this became a new «last chance» solution.
-
stevengarland
- Level 5
- Posts: 708
- Joined: Tue Mar 05, 2019 4:04 pm
- Location: Michigan
Re: No sound Dell XPS 9700
Post
by stevengarland »
Mr een
I did the eight steps. Step 7 looked funny and hung up. waited 5 min and went on. NOW I have no sound at all. No headphones no speakers.
I will post what you asked.. HELP!
Keep It Simple Sweetheart
-
stevengarland
- Level 5
- Posts: 708
- Joined: Tue Mar 05, 2019 4:04 pm
- Location: Michigan
Re: No sound Dell XPS 9700
Post
by stevengarland »
stevengarland@stevengarland-XPS-17-9700:~$ pacmd list-cards
0 card(s) available.
stevengarland@stevengarland-XPS-17-9700:~$ pacmd list-sinks
1 sink(s) available.
* index: 0
name: <auto_null>
driver: <module-null-sink.c>
flags: DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE
priority: 1000
volume: front-left: 55692 / 85% / -4.24 dB, front-right: 55692 / 85% / -4.24 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 0.00 ms
max request: 344 KiB
max rewind: 344 KiB
monitor source: 0
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
Stereo
used by: 0
linked by: 0
configured latency: 0.00 ms; range is 0.50 .. 2000.00 ms
module: 13
properties:
device.description = «Dummy Output»
device.class = «abstract»
device.icon_name = «audio-card»
stevengarland@stevengarland-XPS-17-9700:~$
Keep It Simple Sweetheart
-
MrEen
- Level 23
- Posts: 18345
- Joined: Mon Jun 12, 2017 8:39 pm
Re: No sound Dell XPS 9700
Post
by MrEen »
Let’s get the big picture:
Code: Select all
curl https://gitlab.freedesktop.org/pulseaudio/pulseaudio/raw/master/src/utils/pa-info?inline=false | bash | nc termbin.com 9999-
stevengarland
- Level 5
- Posts: 708
- Joined: Tue Mar 05, 2019 4:04 pm
- Location: Michigan
Re: No sound Dell XPS 9700
Post
by stevengarland »
Heres the output:
stevengarland@stevengarland-XPS-17-9700:~$ curl https://gitlab.freedesktop.org/pulseaud … line=false | bash | nc termbin.com 9999
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2093 100 2093 0 0 7023 0 —:—:— —:—:— —:—:— 7000
ls: cannot access ‘/proc/asound/card[0-9]’: No such file or directory
cat: /proc/asound/version: No such file or directory
cat: /proc/asound/cards: No such file or directory
cat: /proc/asound/modules: No such file or directory
alsactl: save_state
No soundcards found…
cat: /tmp/alsa-info.MUXsesbjUG/alsactl.tmp: No such file or directory
https://termbin.com/x2sn
stevengarland@stevengarland-XPS-17-9700:~$
Also: When I bring up Sound in applications there is a whole list of items
Echomixer
HDAJackRetask
Envy24control
Rmedigicontrol
and again another Envy24control
The jack retask looks like something needs doing
Keep It Simple Sweetheart
-
MrEen
- Level 23
- Posts: 18345
- Joined: Mon Jun 12, 2017 8:39 pm
Re: No sound Dell XPS 9700
Post
by MrEen »
You did not successfully attach anything. Don’t worry about the Sound menu items. They are things that came with alsa-tools and/or alsa-tools-gui.
That output had practically nothing for errors listed, so this could take a bit of guesswork. For starters, let’s undo a change we made earlier with this:
Code: Select all
sudo rm /etc/modprobe.d/sof-fix.confReboot after running that, and if you’re still in the same situation see if this gets back something:
-
hglee
- Level 6
- Posts: 1423
- Joined: Fri Jun 22, 2018 4:31 pm
Re: No sound Dell XPS 9700
Post
by hglee »
From this article referenced here, you’ve done the soundwire installation, but not the blacklist noted in this paragraph: «If you have an error about symbol version disagreements, probably your kernel has an old sof driver which should be disabled by creating /etc/modprobe.d/no-builtin-soundwire.conf with the contents blacklist snd_soc_skl.»
Is that blacklist not needed in this case?
Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU — 14″ WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
-
MrEen
- Level 23
- Posts: 18345
- Joined: Mon Jun 12, 2017 8:39 pm
Re: No sound Dell XPS 9700
Post
by MrEen »
hglee wrote: ⤴Sat Jan 23, 2021 2:06 pm
Is that blacklist not needed in this case?
It may not be needed, but we can’t tell yet as the output was devoid of error messages.
And as a reminder to myself, we still haven’t got to the alsaucm stuff yet.
EDIT: Not entirely correct, as there was this:
Code: Select all
[ 436.377471] rmedigicontrol[2933]: segfault at 30 ip 00007f4069f8a80f sp 00007ffd76ff4150 error 4 in libasound.so.2.0.0[7f4069f78000+8f000]Have to wait and see if removing the other «fix» fixes this.
-
stevengarland
- Level 5
- Posts: 708
- Joined: Tue Mar 05, 2019 4:04 pm
- Location: Michigan
Re: No sound Dell XPS 9700
Post
by stevengarland »
Did last suggestions fro Mr EEn
Nothing changed
stevengarland@stevengarland-XPS-17-9700:~$ sudo modprobe snd-hda-intel
[sudo] password for stevengarland:
modprobe: ERROR: could not insert ‘snd’: Operation not permitted
modprobe: ERROR: ../libkmod/libkmod-module.c:990 command_do() Error running install command ‘/sbin/modprobe —ignore-install snd && { /sbin/modprobe —quiet —use-blacklist snd-ioctl32 ; /sbin/modprobe —quiet —use-blacklist snd-seq ; }’ for module snd: retcode 1
modprobe: ERROR: could not insert ‘snd_hda_intel’: Invalid argument
stevengarland@stevengarland-XPS-17-9700:~$
I was unable to post my earlier copy because it was too large even as a tar. I guess hath does not matter.
Keep It Simple Sweetheart
-
hglee
- Level 6
- Posts: 1423
- Joined: Fri Jun 22, 2018 4:31 pm
Re: No sound Dell XPS 9700
Post
by hglee »
stevengarland wrote: ⤴Sun Jan 24, 2021 9:52 am
I was unable to post my earlier copy because it was too large even as a tar. I guess hath does not matter.
You could use xclip to copy the contents of your clipboard directly to a file or webpage.
sudo apt install -y xclip
To copy your clipboard to file fubar.txt: xclip -o > fubar.txt
To then upload that fubar.txt file to a webpage do cat fubar.txt | nc termbin.com 9999 and wait for the URL to be displayed.
Or upload the content of your clipboard directly to a webpage — xclip -o | nc termbin.com 9999 — and then post just the URL that is displayed after the upload completes. I don’t know what limits termbin.com might have.
Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU — 14″ WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
-
stevengarland
- Level 5
- Posts: 708
- Joined: Tue Mar 05, 2019 4:04 pm
- Location: Michigan
Re: No sound Dell XPS 9700
Post
by stevengarland »
Before I try that last post by hglee I want to mention that one item that comes up under App Sound is «Jack re tasking for HDA Intel sound cards» Says things like «no codecs» and offers many options including installing or removing «boot overide». May mean nothing but seems serious.
Keep It Simple Sweetheart