Home Creators Posts Import Register Favorites Logout

Content

I genuinely thought I was finished with 0.13 last week. Then I discovered that the new session notepad did not work on Windows. I fixed it there, tested everything again, and found that it no longer worked properly on Mac.

The Mac version had Retina sizing problems, and the 0.13.0 disk image had a separate packaging issue that prevented Dusk Studio from launching outside the machine that built it.

So, here we are. Dusk Studio 0.13.1 is a portability, packaging, and notepad rescue release. I still need to add a zoom in/out for the page itself, but its getting there.

Lots of JUCE code has been removed, so definitely let me know if you guys run into bugs.

What changed:

UI Scaling in the settings.

The Windows installer now includes a pinned software OpenGL renderer, allowing the notepad to work in virtual machines, Remote Desktop sessions, and systems limited to basic-display graphics.

The macOS disk image is self-contained and includes the libraries it needs to launch.

Windows now uses Dusk Studio's native CLAP and VST3 hosts, matching Linux and macOS.

macOS and Windows packages no longer contain unnecessary Linux desktop-integration files.

Release packaging and validation received several additional safeguards.

Grab it here ($1+ paid members): https://builds.duskaudio.com/latest

Source Code: https://github.com/dusk-audio/dusk-studio

Report Bugs Here: https://github.com/dusk-audio/dusk-studio/issues/new

If you are compiling from source, use the main branch. To reproduce the exact source used for the 0.13.1 binaries, check out the v0.13.1 tag.

Thanks again for all the support! I will have another update in a few days.

Marc

Files

Comments

Matthew Sims

I'm in a plug-in scanning death spiral. I toggled on the background seeking option. Is there a way for me to toggle this off or a way to uninstall completely to start over? I'm fine with testing batches of plugins to see if any are causing the problem. Thanks!

Dusk Audio

Oh No! I am working on a hotfix for this now. I have a handful of bug reports that have rolled in since the release. The joys of removing JUCE :) You don't need to uninstall, the scan setting lives in a text file you can edit while the app is closed. Force quit Dusk Studio. Open: Linux: ~/.config/Dusk Studio/app-config.properties macOS: ~/Library/Dusk Studio/app-config.properties Windows: %APPDATA%\Dusk Studio\app-config.properties and change this line: scan_plugins_on_startup=1 to scan_plugins_on_startup=0 If you'd rather not edit it, just delete that file. It only holds per-machine preferences (UI scale, autosave interval, stop behavior) and they all go back to defaults, with scan-on-startup off. Launch. It comes up on the cached plugin list with no scan. From then on scanning is manual, via the Scan plugins button in the plugin picker. To start plugin discovery completely fresh, delete these two files in that same folder: plugin-cache.xml (the known-plugin list, including anything quarantined) plugin-scan-deadmanspedal.txt (record of the file being probed when a scan died) For batch testing, move your plugin folders aside and put them back a few at a time, running Scan plugins after each batch. The search paths are ~/.vst3, /usr/lib/vst3, /usr/local/lib/vst3, ~/.clap, /usr/lib/clap, ~/.lv2, /usr/lib/lv2, /usr/local/lib/lv2. Start the app from a terminal and you'll see the scan log on stderr, so the last plugin named before a hang is your suspect.

Dusk Audio

Please try the 0.13.2 release and let me know how it works for you

Matthew Sims

Great! I only had a few minutes to peek. It looks like Arturia plugins are causing it to crash. I will, however, systematically go through and audit all of my plugins. It's about time I organized and labeled them anyway.