Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mixxx can't find my soundcard after installing Windows 10 #8209

Closed
mixxxbot opened this issue Aug 22, 2022 · 14 comments
Closed

Mixxx can't find my soundcard after installing Windows 10 #8209

mixxxbot opened this issue Aug 22, 2022 · 14 comments
Labels

Comments

@mixxxbot
Copy link
Collaborator

Reported by: artcoustic
Date: 2015-08-29T18:27:40Z
Status: Fix Committed
Importance: High
Launchpad Issue: lp1490181
Attachments: 0722161455_HDR.jpg


I have just installed Windows 10 and now Mixxx, both new and older version can't find my sound card Xone K2, it does not show in Audio devices API, nothing, it does show under controller though and I can custom map it, but can't load track and wont play.

I tried with Virtual DJ and it works fine and so does Serato, so it must be a MIxxx problem?

My computer is an Asus TP500L Intel Core i6-4218u, up to 2.7Ghz

@mixxxbot
Copy link
Collaborator Author

Commented by: benjamin-harling
Date: 2015-09-14T21:50:51Z


+1

No soundcards detected on Acer Aspire ( either on-board via ASIO4ALL or FastTrack Pro ASIO ). Just get the no audio devices detected dialog, but no available devices in the dropdowns.

@mixxxbot mixxxbot added the bug label Aug 22, 2022
@mixxxbot
Copy link
Collaborator Author

Commented by: ferranpujolcamins
Date: 2015-12-24T13:22:23Z


Same here, no sound api is shown. I can't even play through my laptop soundcard. Windows 10.

@mixxxbot
Copy link
Collaborator Author

Commented by: ferranpujolcamins
Date: 2015-12-24T13:56:20Z


It is a problem with portaudio (Mixxx log confirms this) like this one:
http://wiki.audacityteam.org/wiki/Windows_10_OS#No_audio_devices_found._Internal_PortAudio_error

I can confirm that disconnecting my Xone K2 causes Mixxx to function normally with the rest of my audio devices, even my external soundcard.

I can confirm that the Xone K2 still doesn't work after uninstalling my old driver and installing the latest one from A&H website.

@mixxxbot
Copy link
Collaborator Author

Commented by: Pegasus-RPG
Date: 2015-12-24T18:00:32Z


Ferran: can you try connecting your K2, then disabling its audio device in Device Manager and starting Mixxx? That may allow you to still use it as a control surface, but with an external sound card.

@mixxxbot
Copy link
Collaborator Author

Commented by: Pegasus-RPG
Date: 2015-12-24T18:14:26Z


For our reference, PA may have addressed this with the following commits:
https://www.assembla.com/spaces/portaudio/subversion/commits/1962
https://www.assembla.com/spaces/portaudio/subversion/commits/1963
(From audacity/audacity#79)

So we may need to pull in a newer snapshot of PortAudio, but we will not be able to do that for the 2.0 release.

@mixxxbot
Copy link
Collaborator Author

Commented by: ferranpujolcamins
Date: 2015-12-24T19:34:38Z


Yes I tried, problem persisted.

2015-12-24 19:14 GMT+01:00 Sean M. Pappalardo <email address hidden>:

For our reference, PA may have addressed this with the following commits:
https://www.assembla.com/spaces/portaudio/subversion/commits/1962
https://www.assembla.com/spaces/portaudio/subversion/commits/1963
(From audacity/audacity#79)

So we may need to pull in a newer snapshot of PortAudio, but we will not
be able to do that for the 2.0 release.

** Changed in: mixxx
Milestone: None => 2.1.0

** Changed in: mixxx
Importance: Undecided => Medium

** Changed in: mixxx
Importance: Medium => High

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1490181

Title:
Mixxx can't find my soundcard after installing Windows 10

Status in Mixxx:
Confirmed

Bug description:
I have just installed Windows 10 and now Mixxx, both new and older
version can't find my sound card Xone K2, it does not show in Audio
devices API, nothing, it does show under controller though and I can
custom map it, but can't load track and wont play.

I tried with Virtual DJ and it works fine and so does Serato, so it
must be a MIxxx problem?

My computer is an Asus TP500L Intel Core i6-4218u, up to 2.7Ghz

To manage notifications about this bug go to:
https://bugs.launchpad.net/mixxx/+bug/1490181/+subscriptions

@mixxxbot
Copy link
Collaborator Author

Commented by: rryan
Date: 2015-12-27T22:40:59Z


I borrowed a friend's W10 laptop and DirectSound and WDM-KS worked. So this means W10 support isn't broken for everyone.

@mixxxbot
Copy link
Collaborator Author

Commented by: benjamin-harling
Date: 2015-12-31T10:43:07Z


This actually got fixed for me after doing the first 'major' win10 update ( i dont know if its a service pack or what ). ASIO audio is great now both with internal soundcard and my fasttrack pro. Direct sound and WDM dont seem to work though.

@mixxxbot
Copy link
Collaborator Author

Commented by: neuromancer10
Date: 2016-01-26T20:37:24Z


I'm also seeing this problem.  I've got a Numark DJ|iO.  I can confirm that unplugging the device fixes the issue.... although it would stop me djing with the program.  Thankfully all I'm doing is using it to listen to one track and loop up parts to tab some drums out!

@mixxxbot
Copy link
Collaborator Author

Commented by: Pegasus-RPG
Date: 2016-06-14T01:55:22Z


I also see this problem on my Windows 10 installation (also upgraded from Windows 7.)

@mixxxbot
Copy link
Collaborator Author

Commented by: artrequestlive
Date: 2016-07-22T21:54:34Z


I just made sure that my sound device/ speakers were committed to being exclusively controlled by the application found in the property section of the playback devices toggle

@mixxxbot
Copy link
Collaborator Author

Commented by: artrequestlive
Date: 2016-07-22T21:56:17Z
Attachments: 0722161455_HDR.jpg

@mixxxbot
Copy link
Collaborator Author

Commented by: Be-ing
Date: 2017-11-12T16:30:58Z


Somehow we haven't received complaints about this in a while. I suppose Microsoft fixed stuff on their end since the initial Windows 10 release.

@mixxxbot
Copy link
Collaborator Author

Issue closed with status Fix Committed.

@mixxxbot mixxxbot transferred this issue from another repository Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant