No Transport with Windows WDM-KS

Bug #1902344 reported by Rod Smart
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Critical
Unassigned

Bug Description

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.

Tags: windows
Rod Smart (rockinrod)
description: updated
description: updated
Rod Smart (rockinrod)
description: updated
Revision history for this message
ronso0 (ronso0) wrote :

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

tags: added: windows
summary: - Trouble Loading Tracks in 2.3.0 Beta
+ No Transport with Windows WDM-KS
Revision history for this message
Daniel Schürmann (daschuer) wrote :

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?

Changed in mixxx:
status: New → Incomplete
Revision history for this message
Rod Smart (rockinrod) wrote :

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

Revision history for this message
Daniel Schürmann (daschuer) wrote :

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

Changed in mixxx:
status: Incomplete → New
Revision history for this message
Rod Smart (rockinrod) wrote :

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.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Is your Realtek driver up to date?

Revision history for this message
Rod Smart (rockinrod) wrote :

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.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

Maybe the portaudio dll has been updated ...

This can also be an issue:
https://github.com/PortAudio/portaudio/issues/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.

Revision history for this message
Rod Smart (rockinrod) wrote :

I have just reinstalled 2.2.0 and it works perfectly.

Changed in mixxx:
importance: Undecided → Critical
Changed in mixxx:
milestone: none → 2.3.0
Revision history for this message
Jan Holthuis (holthuis-jan) wrote :

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

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

Revision history for this message
Rod Smart (rockinrod) wrote :

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

Revision history for this message
Rod Smart (rockinrod) wrote :

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.

Revision history for this message
Be (be.ing) wrote :

> 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.

Revision history for this message
Jörg Wartenberg (joerg-ubuntu) wrote :

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.

Revision history for this message
Rod Smart (rockinrod) wrote :

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

Revision history for this message
Rod Smart (rockinrod) wrote :

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.

Revision history for this message
Be (be.ing) wrote :

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.

Revision history for this message
Al (notyouraverageal) wrote :

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.

Revision history for this message
Jack (iamjackg) wrote :

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

Revision history for this message
Rod Smart (rockinrod) wrote :

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

Revision history for this message
Be (be.ing) wrote :

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

Changed in mixxx:
status: New → Confirmed
Revision history for this message
Be (be.ing) wrote :

Is this an issue with current 2.3 beta builds?

Changed in mixxx:
milestone: 2.3.0 → none
Revision history for this message
Rod Smart (rockinrod) wrote :

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

Revision history for this message
Be (be.ing) wrote :

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

Changed in mixxx:
status: Confirmed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/10186

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.