Skip to content

CD-Audio jerky and too quiet (non-Ultra) #438

Description

@jedcooper

On BlueSCSI v2 Desktop (not Ultra, not Ultra Wide) with the official DAC board connected via QWIIC through >09a port.

Audio playing is jerky, stuttery, inconsistent. I've tested two SanDisk Ultra A2 32 GB and 64 GB µSD-Cards.
The volume is about 1/3 of the general sound card sounds with mixer/slider all at same position.

[SCSI1] 
CDAVolume=255 

(which is default) doesn't help. My CDROM is SCSI ID 1.

Activity

  1. changed the title [-]CD-Audio jerky and too quiet[/-] [+]CD-Audio jerky and too quiet (non-Ultra)[/+] on Sep 19, 2026
  2. erichelgeson commented on Sep 19, 2026

    @erichelgeson
    Contributor

    Can you please provide a log and/or debug log? I can see the volume issue and will push a branch up for that but all the audio paths are in RAM so shouldn't have a stutter, but a log will help me dig in.

    Please give #439 a test (binaries will be linked in the PR once the build job is done)

  3. jedcooper commented on Sep 19, 2026

    @jedcooper
    Author

    log.txt - w/ Debug
    lastlog.txt - w/o Debug

    Debug log "workflow" was:

    Booted Win95, changed CD to Civ II, played a bit with CD-Audio (jerky), then suddenly crash, full reboot cold start. I guess cause of the log overload on SD? /shrug
    Then Scandisk (ofc)
    Again in Windows: Insert Screamer CD, open Windows CD-Player, played two tracks, jerky.

    IBM Aptiva 486DX/2-66, 32 MB RAM, Adaptec AHA-2842A Hostcontroller, Aztech 2316 Sound Galaxy Washington 16 something Sound card playing all other stuff 2-3x louder and flawlessly but CD

    Firmware is latest CD-Audio .uf2 BlueSCSI_V2_Audio_SPDIF_2026-08-17_4d0f96f.uf2
    I put it on via the USB-method

  4. jedcooper commented on Sep 19, 2026

    @jedcooper
    Author

    log.txt - w/ Debug
    Another debug log playing Warcraft 2 in DOS, CD-Audio also jerky.

  5. erichelgeson commented on Sep 20, 2026

    @erichelgeson
    Contributor

    Thanks! Nothing definitive from that log so I added some logging - please re-run the test with this and it should at least give me some areas to focus on #440

  6. jedcooper commented on Sep 20, 2026

    @jedcooper
    Author

    log.txt

    I've put the BlueSCSI binaries.zip from #440 (comment) on SD and started up, but it wasn't deleted, so I don't know if it's installed or not.

    SHA256: 43d0635fbbc2ad8f2ef7cfb42431938405516de509b520b12661fddcae6278f3

    Regardless it would be nice to have a zip for the SD card auto-update method, cause the USB method means inconvenient work for me every time dis- and re-assembling things.

  7. erichelgeson commented on Sep 20, 2026

    @erichelgeson
    Contributor

    No, that zip contains tall the artifacts that would go into the release including the zip you'd normally put on the SD card (I can see how it'd be easily confused. I'll add a note to the automated PR comment). The log you attached still has the prior build on it. Please re-run with the new build. Also I'll try to get my bench setup again so I can test too, just getting back from VCF Midwest and unpacking still!

  8. jedcooper commented on Sep 20, 2026

    @jedcooper
    Author

    Ah well, that makes sense. Now I gonna take the BlueSCSI_v2026.08.18_d3bc5c7.zip then and put it on SD. That worked, .zip is gone.

    Played some Warcraft 2 in DOS, at least 2-3 different CD-Audio tracks were playing.
    Volume is fine now, no clipping so far, too, if that's important ^^
    BUT still jerky audio, but that's expected, you're debugging it.

    Just out of interest or curiosity: what do you look for in the log?
    I don't need a lot of details—just an idea or a pointer.

    Log with debug enabled attached:
    log.txt

  9. erichelgeson commented on Sep 20, 2026

    @erichelgeson
    Contributor

    I've hopefully addressed the jerky debug issue because yes the debug writes are taking too long and drain the audio buffer. I'm looking for the stats log i added. I've pushed a new build to that same link (the "BlueSCSI Binaries.zip" will update momentarily) - Please run this build 2 ways -

    1. with debug on
    2. without debug off

    and provide both logs. I was now unable to reproduce any misses on my Pico2W with this audio build. (Finally got my bench tester set back up :) )

  10. jedcooper commented on Sep 20, 2026

    @jedcooper
    Author

    with debug on = Debug=1 in bluescsi.ini I assume
    without debug off??? I've removed Debug=1 in bluescsi.ini (I assume)

    1. debuglog.txt
    2. log.txt

    bluescsi.ini w/ Debug enabled:

    [SCSI]
    System=Generic
    Debug=1
    

    bluescsi.ini w/o Debug enabled:

    [SCSI]
    System=Generic
    

    Unfortunately still jerky audio. Gonna do some audio grabbing with Linux if I can manage that...

    This record is w/o Debug (track change at ~3:30):

    Warcraft 2 - Ingame - CD-Audio BlueSCSI.mp3

    Not much HDD activity in general in game once loaded. Nearly zero.
    Fluid gameplay on my 486DX/2-66, so I think this is not the issue.
    The CD-Audio volume is good/perfect. Did set the sliders both the same, digital audio and CD-Audio ingame and in sound card mixer.

  11. erichelgeson commented on Sep 20, 2026

    @erichelgeson
    Contributor

    Thanks for the details. One more question can you link to the exact bin/cue you're using? I just want to have the exact same bench setup as you.

  12. jedcooper commented on Sep 20, 2026

    @jedcooper
    Author

    I contacted you about this on Discord.

  13. 9 remaining items

  14. erichelgeson commented on Sep 29, 2026

    @erichelgeson
    Contributor

    Thanks for reporting and testing. I'll clean up and merge into the next release.

  15. jedcooper commented on Sep 29, 2026

    @jedcooper
    Author

    Great, and thank you! 👍

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions