Issue Playing Audio (Windows 3.1, Sb16 And WAV Files)

by ADMIN 54 views

Issue Playing Audio in Windows 3.1 with SB16 and WAV Files

As a user of the 86Box emulator, you may have encountered issues playing audio in Windows 3.1 with an SB16 sound card and WAV files. This article aims to provide a detailed analysis of the issue and potential solutions.

Symptoms

The issue is characterized by a distorted and sped-up audio playback, often referred to as an "AAAA" sound instead of the expected "Tadaaa" starting sound. This problem occurs when using the SB16 drivers for Windows 3.x, while MIDI playback and WAV files in DOS work correctly.

Configuration and Testing

To reproduce the issue, the following configuration was used:

  • Windows 3.1 installed on a virtual machine with an SB16 sound card
  • SB16 drivers installed and configured correctly
  • WAV files played in Windows 3.x resulted in a distorted and sped-up audio playback
  • MIDI playback and WAV files in DOS worked correctly
  • Testing was performed on both the latest AppImage and Gentoo port of 86Box

Configuration File

The configuration file used for testing is provided below:

[General]
video_fullscreen_first = 0
confirm_exit = 0
confirm_save = 0
confirm_reset = 0
sound_gain = 13
window_remember = 1
force_43 = 1
host_cpu = AMD Ryzen 7 5825U with Radeon Graphics
uuid = 08e473d5-b6d9-5a73-8be6-7992f00f9f0a
vid_renderer = qt_software
enable_discord = 1
language = en-GB
emu_build_num = 6209

[Machine]
machine = win486pci
cpu_family = i486dx2_slenh
cpu_speed = 66666666
cpu_multi = 2
cpu_use_dynarec = 1
fpu_softfloat = 0
time_sync = utc
fpu_type = internal
mem_size = 16384

[Video]
gfxcard = et4000ax
video_fullscreen_scale_maximized = 1

[Input devices]
mouse_type = logibus

[Sound]
fm_driver = nuked
sndcard = sbawe32

[Network]
net_01_link = 0
net_02_link = 0
net_03_link = 0
net_04_link = 0
net_01_card = ne2k
net_01_net_type = slirp

[Storage controllers]
hdc = none
cassette_mode = load

[Tseng Labs ET4000AX (ISA)]
memory = 1024

[Standard PS/2 Mouse]
buttons = 2

[Gravis UltraSound]
type = 0
base = 0220
gus_ram = 0
receive_input = 1

[Ports (COM & LPT)]
lpt1_device = postscript

[Hard disks]
hdd_01_parameters = 62, 4, 1930, 0, ide
hdd_01_fn = 486.vhd
hdd_01_speed = ramdisk
hdd_01_vhd_blocksize = 4096
hdd_01_ide_channel = 0:0

[Floppy and CD-ROM drives]
fdd_01_type = 35_2hd
fdd_02_type = 525_2hd
cdrom_01_parameters = 1, atapi
fdd_01_image_history_01 = /mnt/disk2/86Box/DOS+Win3.1/Microsoft Windows 3.1 (3.10.103) (3.5)/Disk02.img
fdd_01_image_history_02 = /mnt/disk2/86Box/Software/Borland CPP 3.1 and Application Frameworks (1992) (3.5-1.44mb)/Disk15.img
fdd_01_image_history_03 = /mnt/disk2/86Box/Software/Borland CPP 3.1 and Application Frameworks (1992) (3.5-1.44mb)/Disk12.img
cdrom_01_ide_channel = 0:1
fdd_02_image_history_01 = /mnt/disk2/86Box/Software/Floppy/Drivers/sb16w3x.img
cdrom_01_image_history_04 = /mnt/disk2/86Box/Software/ISO/Drivers/SB16.iso
cdrom_01_image_path = /mnt/disk2/86Box/Software/ISO/Drivers/SoundBlaster AWE32 Drivers (95 W31) (9-21-95) (CD)/sbawe32.cue
cdrom_01_image_history_01 = /mnt/disk2/86Box/Software/ISO/Games/CAESAR2IBM.iso
fdd_01_image_history_04 = /mnt/disk2/86Box/Software/Borland CPP 3.1 and Application Frameworks (1992) (3.5-1.44mb)/Disk14.img
cdrom_01_type = 86BOX_CD-ROM_1.00
cdrom_01_image_history_02 = /mnt/disk2/86Box/Games/CD/CAESAR2.ISO

[Novell NE2000 #1]
mac = 4f:62:41

[Logitech/Microsoft Bus Mouse]
base = 023C
irq = 5
hz = 45
buttons = 2

[Monitor #1]
window_coordinates = 1, 28, 640, 480

[Monitor #2]
window_coordinates = 0, 0, 0, 0

[NE2000 Compatible #1]
mac = d4:26:c3

Operating System and 86Box Version

The issue was tested on Gentoo Linux with 86Box version V4.2.2 [build 6209] and V4.2.1.

Build Architecture and Type

The build architecture used was Linux - x64 (64-bit), and the build type was a new recompiler.

Additional Context

No additional context was provided.

Conclusion

The issue of playing audio in Windows 3.1 with SB16 and WAV files is a complex problem that requires further investigation. The distorted and sped-up audio playback is likely related to the SB16 drivers and the 86Box emulator. To resolve this issue, it is recommended to:

  1. Verify that the SB16 drivers are installed and configured correctly.
  2. Test the issue with different versions of the SB16 drivers and 86Box emulator.
  3. Check for any updates or patches for the 86Box emulator that may resolve the issue.
  4. Consider using a different sound card or emulator to rule out any hardware or software issues.

By following these steps, you may be able to resolve the issue and enjoy smooth audio playback in Windows 3.1 with SB16 and WAV files.
Q&A: Issue Playing Audio in Windows 3.1 with SB16 and WAV Files

Q: What is the issue with playing audio in Windows 3.1 with SB16 and WAV files?

A: The issue is characterized by a distorted and sped-up audio playback, often referred to as an "AAAA" sound instead of the expected "Tadaaa" starting sound.

Q: What are the symptoms of this issue?

A: The symptoms include:

  • Distorted and sped-up audio playback
  • Audio playback is not smooth or clear
  • WAV files played in Windows 3.x result in a distorted and sped-up audio playback
  • MIDI playback and WAV files in DOS work correctly

Q: What are the possible causes of this issue?

A: The possible causes of this issue include:

  • Incorrectly installed or configured SB16 drivers
  • Incompatible or outdated SB16 drivers
  • Issues with the 86Box emulator
  • Hardware or software conflicts

Q: How can I troubleshoot this issue?

A: To troubleshoot this issue, you can try the following steps:

  1. Verify that the SB16 drivers are installed and configured correctly.
  2. Test the issue with different versions of the SB16 drivers and 86Box emulator.
  3. Check for any updates or patches for the 86Box emulator that may resolve the issue.
  4. Consider using a different sound card or emulator to rule out any hardware or software issues.

Q: Can I use a different sound card or emulator to resolve this issue?

A: Yes, you can try using a different sound card or emulator to rule out any hardware or software issues. Some popular alternatives include:

  • Sound Blaster AWE32
  • Gravis UltraSound
  • 86Box emulator
  • PCem emulator

Q: Are there any known workarounds for this issue?

A: Yes, there are some known workarounds for this issue. These include:

  • Using a different version of the SB16 drivers
  • Disabling the SB16 drivers and using a different sound card or emulator
  • Using a different emulator, such as PCem
  • Modifying the configuration file to change the sound settings

Q: Can I get help from the 86Box community or support team?

A: Yes, you can get help from the 86Box community or support team. You can try the following:

  • Posting on the 86Box forums or discussion groups
  • Contacting the 86Box support team via email or chat
  • Joining the 86Box community on social media platforms
  • Participating in online communities or forums related to 86Box or emulation

Q: How can I prevent this issue from occurring in the future?

A: To prevent this issue from occurring in the future, you can try the following:

  • Regularly update the SB16 drivers and 86Box emulator to the latest versions
  • Verify that the SB16 drivers are installed and configured correctly
  • Test the issue with different versions of the SB16 drivers and 86Box emulator
  • Consider using a different sound card or emulator to rule out any hardware or software issues.