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.

Sign up for GitHub

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

Jump to bottom

No Transport with Windows WDM-KS #10186

Closed

mixxxbot opened this issue Aug 23, 2022 · 25 comments

Labels

bug party stopper windows

Collaborator

mixxxbot commented Aug 23, 2022

Reported by: rockinrod
Date: 2020-10-31T08:22:09Z
Status: Fix Released
Importance: Critical
Launchpad Issue: lp1902344
Tags: windows
Attachments: [Log File As Requested](https://bugs.launchpad.net/bugs/1902344/+attachment/5432067/+files/Log File As Requested)

I have just installed version 2.3.0 Beta. I ran into trouble as soon as I tried to load a track.
When I load the first track after opening Mixxx it displays the last half of the waveform in the deck before it displays the entire waveform. When I push play, the play button turns red but the track does not play. I can pause the track and then eject it, any tracks I try to load to any deck after that just shows the message in the selected deck, "Loading Track" but it never loads. I am using Windows WDM-KS Sound API.
Have been using Mixxx 2.2.0 on this machine since it first came out without any problems.
Running Windows 10 Professional 64 Bit, Intel Core I7 3.40Ghz, 16Gb RAM ASUS Deluxe MB, Onboard Realtek High Def Audio with driver version 10.0.19041.1.
Graphics is onboard Intel HD Graphics 3000 Driver 9.17.10.4459 with generic PnP monitor 1920 x 1080 Res.

mixxxbot added bug party stopper windows labels

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: ronso0
Date: 2020-10-31T12:20:34Z

That sounds like your sound outputs are not configured.
You need to set up at least one sound output device.

In the 'Gettin started' section of the 2.3 manual, check this chapter:
https://www.mixxx.org/manual/2.3/en/chapters/getting_started.html#configuring-sound-input-and-output

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: daschuer
Date: 2020-11-03T08:37:54Z

Did you manage to fix the issue?

Normally transport should fall back to internal network clock if no sound-card is configured.
This seams to be not the case.

Does Mixxx start with a message box complaining about missing sound devices?

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: rockinrod
Date: 2020-11-04T01:01:40Z

There are no message boxes at startup. The master output device is definately configured.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: daschuer
Date: 2020-11-04T05:44:50Z

Do you have a workaround, like restart Mixxx or using a different API?

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: rockinrod
Date: 2020-11-04T09:04:55Z

I have just tried various APIs and found that sometimes it will start working when I select a different one. Most of the time I just get "unanticipated host errors". Once it starts working, it continues to work even if I change APIs on the fly, including the WDM-KS API. As soon as I close and re open Mixxx the API that was working when I closed Mixxx no longer works again. I have not been able to find a reliable pattern that always makes it work.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: daschuer
Date: 2020-11-04T09:42:25Z

Is your Realtek driver up to date?

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: rockinrod
Date: 2020-11-04T10:31:19Z

Yes, I cant find a later one. Its from Microsoft 12/6/2019 Version 10.0.19041.1.
I have checked with Asus, Realtek and Microsoft. It never showed any problem with version 2.2.0. Has something changed in Mixxx that affects how it interacts with the sound drivers.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: daschuer
Date: 2020-11-04T12:58:01Z

Maybe the portaudio dll has been updated ...

This can also be an issue:
PortAudio/portaudio#310

Is the issue gone after downgrade to Mixxx 2.2?

As far as I can see the portaudio dll should be the same:
pa_stable_v190600_20161030.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: rockinrod
Date: 2020-11-05T09:56:07Z

I have just reinstalled 2.2.0 and it works perfectly.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: Holzhaus
Date: 2020-11-05T10:52:28Z

Most of the time I just get "unanticipated host errors".

Where did you get that from? Can you post the mixxx.log file?

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: rockinrod
Date: 2020-11-07T04:09:26Z
Attachments: [Log File As Requested](https://bugs.launchpad.net/mixxx/+bug/1902344/+attachment/5432067/+files/Log File As Requested)

I have just re installed 2.3.0 and it behaves exactly as before.
Please see attached log file as requested.
The unanticipated host errors show up in a message box that often pops up when I select different APIs in the sound options page

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: rockinrod
Date: 2020-11-07T04:25:11Z

I noticed a warning in the log file "Output sound device clock reference not set! Using "Network stream""
The clock source in the sound options is currently set to "soundcard clock"(default) Not sure if this has something to do with the problem or not.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: Be-ing
Date: 2020-11-17T21:10:20Z

As far as I can see the portaudio dll should be the same:
pa_stable_v190600_20161030.

Yes, I just double checked. The Windows build environments for 2.2 and 2.3 are using the same version of PortAudio.

I am puzzled what is causing this.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: JoergAtGithub
Date: 2020-11-17T21:15:29Z

I expierenced this issue with WDM-KS also, some weeks ago. But now I can't reproduce it.
It helped, to open the preferences and click once on "Query Devices", and leave the dialog without further changes.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: rockinrod
Date: 2020-11-18T08:17:55Z

The title may be a bit misleading as it does not matter which API is selected.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: rockinrod
Date: 2020-11-18T08:32:41Z

I have just tried to run 2.3.0 again and its working ok. I have been trying different things nearly everyday with no success, but today it is working. I can't recreate the fault. The only thing that has changed on this PC is a Windows 10 update was installed yesterday. I cant think of anything else that has changed.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: Be-ing
Date: 2020-11-18T13:15:04Z

Interesting. This would not be the first time a Windows update has broken audio I/O for Mixxx. I'm not sure there's anything we could or should do other than tell people to update to the latest Windows update.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: notyouraverageal
Date: 2020-11-23T09:57:32Z

Can confirm I can reproduce this bug too on Windows 10
OS Windows 10 Pro 10.0.18363
Processor Core i7-6600U CPU @ 2.60GHz
RAM 16.0 GB

Happens when I select Sound API: Windows WDM-KS and output as the laptop speakers. Can confirm I get the issue "Loading Track" but it never loads.

Sometimes when selecting the api I will get - Error opening "Speakers (Conexant HD Audio output)" Invalid device.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: iamjackg
Date: 2020-12-30T21:19:22Z

I'm also experiencing this, but interestingly enough it used to work perfectly fine for a few sessions before I eventually ran into this issue. I did indeed install a Windows update between the last good session and the current broken state.

See this thread on the Discourse forum for more details, including logs: https://mixxx.discourse.group/t/mixxx-stopped-being-able-to-open-wdm-ks-devices/20791/3

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: rockinrod
Date: 2021-01-17T05:31:47Z

This problem has returned. Sometimes it works fine and other times I cant make it work no matter what I seem to do.

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: Be-ing
Date: 2021-01-17T05:45:00Z

I wonder if this issue has already been fixed upstream in PortAudio but not released?

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: Be-ing
Date: 2021-03-08T20:44:20Z

Is this an issue with current 2.3 beta builds?

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: rockinrod
Date: 2021-08-02T02:37:28Z

This does not seem to be a problem since I installed the latest stable release of 2.3.0

Collaborator Author

mixxxbot commented Aug 23, 2022

Commented by: Be-ing
Date: 2021-08-02T02:50:09Z

I guess this was fixed somehow by switching to vcpkg for Windows dependencies? We are building a more up-to-date version of PortAudio.

Collaborator Author

mixxxbot commented Aug 23, 2022

Issue closed with status Fix Released.

mixxxbot closed this as completed

mixxxbot transferred this issue from another repository

iamjackg mentioned this issue

WDM-KS not working with Numark Mixtrack Pro FX #11393

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment