The sidplaywx is a GUI player for Commodore 64 SID chip tunes aiming to provide a modern & comfortable SID tune playback experience on the PC.
The current alpha version is fully usable, supporting QoL features like seeking, drag & drop, unicode paths, DPI awareness and much more.
The sidplaywx uses libsidplayfp for ultimate quality in SID emulation, wxWidgets for native GUI on supported platforms, and PortAudio for audio output.
This project uses the GCC and the CMake, and at the moment Windows and Linux are supported.
The current version of the sidplaywx is 0.x.x (alpha), so in addition to bugfixes and common sense updates, I consider at least these features are needed before the sidplaywx can graduate to version 1.0:
- Playlist improvements such as
duration columns, reordering, remembering last state and playlist file save/loadetc. - Misc. necessary features
such as remembering window size & positionetc. - Exporting tunes to WAV
STILsupport for displaying tune commentsNative Linux supportTheming support / dark theme
- You can find a pre-built ready-to-use binary distribution(s) in the Releases sidebar.
- More package formats are planned for Linux (only AppImage at the moment).
Some alternatives to sidplaywx for playing the SID tunes I've tried and liked are:
- Windows: foobar2000 + foo_sid plugin
- Linux: DeaDBeeF player (note: it uses older/no longer maintained libsidplay2)
- Mac: I don't have a Mac so I haven't tried it, but this looks great: https://github.com/Alexco500/sidplay5
If you have an idea or a comment, feel free to post it in the Discussions. Issues can be reported here. There is also an email address provided in the application's Help > About box.
- Where can I get SID tunes?
- Check out the High Voltage SID Collection for a massive collection of SID tunes sorted by authors, and more!
- Why are some tunes crossed-out and cannot be played?
- Small number of tunes require a C64 system ROM to play. You can find the C64 system ROM files in e.g., open source C64 emulators (or elsewhere on the internet) and import them via the sidplaywx's Preferences.
- There are three main C64 system ROM types that the sidplaywx supports (and some tunes require):
- KERNAL ROM (tune indicated with a RED crossout text if missing)
- BASIC ROM (tune indicated with a BLUE crossout text if missing)
- CHARGEN ROM (you'll probably never need this one, so let's just ignore it for now)
- When drag & dropping the files, why the playlist sometimes gets cleared?
- By default, the sidplaywx will enqueue the files if dropped onto the playlist area, and clear (replace) the playlist if they are dropped onto the general player window area. This is configurable in the Preferences.
- Can sidplaywx open archive files?
- Yes, but only the Zip format in its simplest variant is supported due to wxZip limitation.
- How come the seeking is so slow?
- There is an "Instant seeking" option available which pre-renders the entire SID tune in the background. It is disabled by default, but if you enable it you will be able to seek instantly. See release notes of the old release (note: "Instant seeking" was formerly named "Fast seeking") for details on how it works and what are the caveats.
- SID tunes are actually small programs and not audio files like for example the MP3, so they have to be emulated linearly as fast as possible until the "seek" target is reached.
- Command-line options in sidplaywx?
- Focus so far is on the GUI experience. There exists a sidplayfp console-based player in the libsidplayfp repo (not to be confused with a sidplaywx which is unrelated and unaffiliated project).
- For now, you can pass the space-separated filenames. For example
sidplaywx Aces_High.sid Gunstar.sidto open those two tunes. This "feature" is actually a side-effect of single-instance support, so there will be a slight delay if the app is already running and the single-instance option is enabled.
Click to expand!
- GCC version with C++17 support is required (minimum I've tried is gcc-12).
- Don't forget the
sudo apt-get updateandsudo apt-get install build-essentialas well assudo apt-get install cmake
- NOTE: Building the libsidplayfp from its git master branch is more involved and not covered here. This guide assumes you're building one of the source releases of the libsidplayfp which is simpler.
- To enable C++20 set in the terminal
CXXFLAGS="$CXXFLAGS -std=c++20" - Commands to build statically:
./configure LDFLAGS="-static" && make - Copy the following includes (with their folder structures) to the appropriate
includefolder in the sidplaywx's/deps/:/builders/residfp.hsidbuilder.h,SidConfig.h,siddefs.h,SidInfo.h,sidplayfp.h,SidTune.h,SidTuneInfo.h,sidversion.h
- Copy the
/src/.libs/libsidplayfp.a(.libsis a hidden folder) to the appropriatelibfolder in the sidplaywx's/deps/
- Prerequisites: you must have installed the
libpulse-dev, ALSA (libasound2-dev),libsndio-dev,libjack-devBEFORE building the PortAudio, otherwise the resultant PortAudio may not find any devices.- See the main CMakeLists.txt for which ones are relevant.
cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Release -S . -B dist && cmake --build dist- Note: I had to use the git master version, had no luck with the stable version on the Xubuntu 24.04
- Copy files from
/dist/include/folder & thelibportaudio.afile to the appropriate sidplaywx's/deps/folders.
- Prerequisites: if needed, install the
libgtk-3-devandlibcurl-dev(the last one is needed for our "Check for updates" function). cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Release -S . -B dist && cmake --build dist- Exceptional cases (if you get an
#includeerror when building the sidplaywx):- You may need to call the
wx-config --cxxflagsto get necessary flags and update the equivalent variable in our sidplaywx CMakeLists.txt - May also be of interest:
- You may need to call the
- Exceptional cases (if you get an
- Copy files from
/dist/include/&/dist/lib/to the appropriate sidplaywx's/deps/folders.
- Copy contents of the
devfolder (except theicon_srcfolder and theSystemColorViewer.pyw) to thebuildfolder (create abuildfolder next to thedevfolder) - You can rename the
CMakeLists_linux.txttoCMakeLists.txt cmake -G "Unix Makefiles" -DCMAKE_BUILD_TYPE=Release -S . -B build && cmake --build build
- Tip: If the sidplaywx fails to launch after it was successfully built, try via terminal to see if something is missing.
- Tip: if trying to execute the sidplaywx in VSCode and getting exit code 177, you need to edit your config:
"terminal.integrated.env.linux": { "GTK_PATH": null }and restart VSCode (or for one-off thing run this in VS terminal:unset GTK_PATH)
At the moment, the easiest way to build the sidplaywx on Windows is probably by using the MSYS2 environment.
Note: you should install it into the default C:\msys64\ path in order for some hardcoded cmake paths to work out-of-the-box.
Once installed you need to first-time configure it like so:
- NOTE: MSYS2 supports modern UCRT64 and legacy MINGW environments. UCRT64 is recommended these days, and these instructions assume using it.
- Update package lists etc.:
pacman -Syuand after restart (if needed):pacman -Su - Install develpment prerequisites:
pacman -S base-devel - Install msvcrt-compatible gcc:
pacman -S mingw-w64-ucrt-x86_64-gcc - Install cmake & make tools (e.g., PortAudio needs those):
pacman -S mingw-w64-ucrt-x86_64-cmake && pacman -S mingw-w64-ucrt-x86_64-make - In your PATH environment variable add: "C:\msys64\ucrt64\bin"
- Extra if you need to install gdb separately for some reason:
pacman -S mingw-w64-ucrt-x86_64-gdb - IMPORTANT: run the terminal via ucrt64.exe, not default msys2 terminal (otherwise the proper gcc variant might not be used)!
- NOTE: Building the libsidplayfp from its git master branch is more involved and not covered here. This guide assumes you're building one of the source releases of the libsidplayfp which is simpler.
cd(with MSYS2 i.e., UCRT64.exe terminal) into the libsidplayfp's root.- To specify either:
- C++20 – set this in the terminal:
CXXFLAGS="$CXXFLAGS -std=c++20"(new) - C++14 – set this in the terminal:
CXXFLAGS="$CXXFLAGS -std=c++0x"(older versions of libsidplayfp)
- C++20 – set this in the terminal:
- Finally, run:
./configure LDFLAGS="-static" && make && make install- TIP: if doing this for the first time, break down these 3 commands (i.e., they are separated by
&&) and run them one by one so you can catch any problems more easily.
- TIP: if doing this for the first time, break down these 3 commands (i.e., they are separated by
- Note: the lib will be automatically found by our cmake later (if you've installed the msys into the
C:\msys64\) and it will get linked statically.
- Download the PortAudio stable source release or the master from the github.
- You can use the regular Windows cmd:
cdinto the PortAudio's root.cmake -G "MinGW Makefiles" -DCMAKE_BUILD_TYPE=Releasemingw32-make
- Copy files from
/dist/include/folder & thelibportaudio.afile to the appropriate sidplaywx's/deps/folders.
- Simply download the appropriate pre-built binaries for your compiler (e.g., GCC v14).
- Copy headers & libs to the appropriate sidplaywx's
/deps/folders. - IMPORTANT: additionally, in order to actually run the sidplaywx application after it's built, you need to copy the following wxWidgets'
.dllfiles into the sidplaywx's build folder:wxbaseVER_SUFFIX.dll,wxbaseVER_xml_SUFFIX.dll,wxmswVER_core_SUFFIX.dll,wxmswVER_propgrid_SUFFIX.dll(the exactVERversion and_SUFFIXsuffix differs depending on wxWidgets & gcc version etc.). - TIP: You can also build the wxWidgets yourself in the similar manner to building the PortAudio (in case you want to use a specific GCC version not offered among pre-built binaries).
- The main
CMakeLists.txtshould do the trick (I myself use the Visual Studio Code). - IMPORTANT: additionally, in order to actually run the sidplaywx application after it's built, you need to copy the following files into the sidplaywx's build folder:
libgcc_s_seh-1.dll,libstdc++-6.dll,libwinpthread-1.dllfound in your appropriate MSYS bin folders (e.g., ucrt64 or mingw64).- The entire
dev\themefolder (so you end up withbuild\theme). - The
dev\bundled-Songlengths.md5file (so you end up withbuild\bundled-Songlengths.md5). - The
dev\bundled-STIL.txtfile (so you end up withbuild\bundled-STIL.txt).
- Tip: you can see the release package for example of bundled dependency files if you get stuck.