Skip to content

Windows updates to get vbcable working in latest windows runners#20

Open
sethvincent wants to merge 1 commit into
LABSN:mainfrom
sethvincent:windows-updates
Open

Windows updates to get vbcable working in latest windows runners#20
sethvincent wants to merge 1 commit into
LABSN:mainfrom
sethvincent:windows-updates

Conversation

@sethvincent

Copy link
Copy Markdown

Hello! I rewrote the windows/setup_sound.ps1 script to be able to get/list audio devices in SDL3 tests.

Changes include:

  • New setup_sound.ps1 script
  • Added windows-2025, removed windows-2019 (2019 support was removed very recently)
  • Switched to VBCABLE_Driver_Pack45 to get the needed win10 inf file
  • Changed the approach for testing device output to not rely on specific device number.

I'm using these changes in an SDL3 bindings project that you can check out for proof it works.

The ps1 script changes are pretty substantial so I'm happy to make changes if needed; I'm worried about having changed something needed for your use case.

- new setup_sound.ps1 script
- add windows-2025, remove windows-2019
- use VBCABLE_Driver_Pack45
- change approach for testing device output
set -xeo pipefail
python -m sounddevice | grep "[82] out"
name: Check that there is some output device
- run: sleep 10

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we keep the sleep in there? There must have been a reason we put it in there sleep at some point (I don't remember what it is offhand) so probably better to keep it and do the check twice.

Also the existing test made sure that there were actually output channels available, the test no longer does that. Looks like the output on Windows is:

<  4 Speakers (2- VB-Audio Virtual C, MME (0 in, 8 out)

so it should have still passed. So it's probably worth reverting these changes, or otherwise refactoring them to make sure they still check things as completely as they did before.

@larsoner

Copy link
Copy Markdown
Member

@sethvincent I updated the runner list in #26 and things appear to work in main using the existing tests. Are they broken?

In any case, happy to take another look at this if you fix the merge conflicts

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants