unable to configure "pulse" from the noOutputDlg
Bug #1514116 reported by
Daniel Schürmann
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Fix Released
|
Medium
|
Daniel Schürmann | ||
Bug Description
Even though pulse callback starts, it brakes short after.
Revision history for this message
| Daniel Schürmann (daschuer) wrote | #1 |
| Changed in mixxx: | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Daniel Schürmann (daschuer) |
| milestone: | none → 1.12.0 |
Revision history for this message
| Daniel Schürmann (daschuer) wrote | #2 |
| Changed in mixxx: | |
| status: | In Progress → Fix Committed |
| Changed in mixxx: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #3 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
This happens because
m_pSoundManager
is called twice.
The first starts pulse, the second brakes it again.
We can solve it by removing the second call, but it is only a band aid, since no call of setupDevices() should break anything.