The TidalCycles extension for VS Code has a fresh update. A couple of improvements have been made around configuration setting errors and custom boot file path errors.
Config Setting Errors
The new update now removes errors telling you that the TidalCycles config settings were “unknown”. Now it’s just a clean config:
Boot File Path Errors
A few minor versions ago, we introduced the ability to configure a path to a custom Tidal boot file. With that, you can now configure Tidal to load up all of your custom stuff in a seamless bootup sequence. However, if VS Code could not locate your custom bootup file it wouldn’t tell you.
Now, the Tidal console output and a VS Code message will notify you that you boot file was not found:
What’s more is that you can fix your boot file config settings and try to reboot Tidal without restarting VS Code. Fancy!
Oh Hey One More Thing!
VS Code recently released a new feature where you can dock the terminal to the right-hand side of the IDE:
So now you can put the Tidal output to the side instead of below your Tidal code, if you so desire: