KXStudio Website https://kx.studio/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

News.php 339KB

1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
1 year ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
2 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
3 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
5 years ago
7 years ago
7 years ago
7 years ago
7 years ago
7 years ago
7 years ago
7 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
8 years ago
  1. <?php
  2. $PAGE_TITLE = "KXStudio News";
  3. $PAGE_TYPE = "NEWS";
  4. $PAGE_SOURCE_1 = ARRAY("/News");
  5. $PAGE_SOURCE_2 = ARRAY("News");
  6. include_once("includes/header.php");
  7. ?>
  9. <p>
  10. <span style="font-size: 20px">&gt; Cardinal 22.05 has been released</span><br/>
  11. On <i>2022-05-15</i> by<i> falkTX</i>
  12. </p>
  13. <p>
  14. Hello everyone, yet another release of <a href="https://github.com/DISTRHO/Cardinal" target="_blank">Cardinal</a> is here.<br/>
  15. <a href="https://github.com/DISTRHO/Cardinal" target="_blank">Cardinal</a>
  16. is a free and open-source virtual modular synthesizer plugin.<br/>
  17. It is based on the popular <a href="https://github.com/VCVRack/Rack/" target="_blank">VCV Rack</a>
  18. but with a focus on being a fully self-contained plugin version.
  19. </p>
  20. <p>
  21. This is a big update with not just bug-fixes but also new modules and a few behaviour changes too.<br/>
  22. Particularly interesting for existing Rack users is the inclusion of the popular Fundamental modules,
  23. though in customized fashion.<br/>
  24. A new
  25. <a href="https://github.com/DISTRHO/Cardinal/blob/main/docs/CARDINAL-MODULES.md#audio-to-cv-pitch" target="_blank">Audio to CV Pitch</a>
  26. module also makes a debut, based on
  27. <a href="https://github.com/DISTRHO/PitchTrackingSeries" target="_blank">DISTRHO PitchTrackingSeries</a>
  28. which was a shared effort for
  29. <a href="https://moddevices.com/guitar-synth/" target="_blank">pushing the feature into hardware units</a>.
  30. </p>
  31. <p>
  32. <img src="/screenshots/news/cardinal-fundamental.png" alt="cardinal-fundamental"/>
  33. </p>
  34. <h3>Changelog</h3>
  35. <ul>
  36. <li>Add macos-intel build (smaller in size and better fit for intel-based macs)</li>
  37. <li>Add main <a href="https://forum.moddevices.com/t/cardinal/7287/81" target="_blank">Cardinal variant for MOD builds</a></li>
  38. <li>Add <a href="https://github.com/DISTRHO/Cardinal/blob/main/docs/CARDINAL-MODULES.md#audio-to-cv-pitch" target="_blank">Audio to CV Pitch</a> Core module</li>
  39. <li>Fix buffer size not always correct in the Audio Unit plugin</li>
  40. <li>Force UI keyboard focus (delayed focus grab after UI is open)</li>
  41. <li>Mute audio output if bypassed</li>
  42. <li>Remap Ctrl key + mouse clicks to right-click on macOS to better deal with its silly "one button" UX</li>
  43. <li>Store a few more properties as plugin state, including favorites</li>
  44. </ul>
  45. <h3>Added plugins</h3>
  46. <ul>
  47. <li><a href="https://github.com/CardinalModules/Fundamental" target="_blank">Fundamental</a> (fork with custom panels)</li>
  48. <li><a href="https://github.com/knchaffin/Meander" target="_blank">Meander</a></li>
  49. <li><a href="https://github.com/VegaDeftwing/PinkTromboneVCV" target="_blank">PinkTrombone</a></li>
  50. <li><a href="https://gitlab.com/unlessgames/unless_modules" target="_blank">unless_modules</a></li>
  51. <li><a href="https://github.com/korfuri/WhatTheRack" target="_blank">WhatTheRack</a></li>
  52. </ul>
  53. <h3>Updated modules</h3>
  54. <ul>
  55. <li><a href="https://github.com/jhoar/AmalgamatedHarmonics" target="_blank">Amalgamated Harmonics</a></li>
  56. <li><a href="https://github.com/CardinalModules/AudibleInstruments" target="_blank">Audible Instruments</a></li>
  57. <li><a href="https://github.com/VCVRack/Befaco" target="_blank">Befaco</a> (adds Channel Strip)</li>
  58. <li><a href="https://github.com/sebastien-bouffier/Bidoo" target="_blank">Bidoo</a></li>
  59. <li><a href="https://github.com/bogaudio/BogaudioModules" target="_blank">BogaudioModules</a></li>
  60. <li><a href="https://github.com/jatinchowdhury18/ChowDSP-VCV/" target="_blank">ChowDSP</a></li>
  61. <li><a href="https://github.com/dbgrande/GrandeModular" target="_blank">GrandeModular</a> (adds VCA4)</li>
  62. <li><a href="https://github.com/MarcBoule/ImpromptuModular" target="_blank">ImpromptuModular</a> (adds Sygen and Variations)</li>
  63. <li><a href="https://github.com/MarcBoule/MindMeldModular" target="_blank">MindMeldModular</a></li>
  64. <li><a href="https://github.com/patheros/PathSetModules" target="_blank">Path Set</a> (adds GlassPane, Nudge and ShiftyExpander)</li>
  65. <li><a href="https://github.com/SteveRussell33/Prism" target="_blank">Prism</a></li>
  66. <li><a href="https://github.com/SteveRussell33/repelzen" target="_blank">repelzen</a></li>
  67. <li><a href="https://github.com/clone45/voxglitch" target="_blank">Voxglitch</a> (adds GrooveBox)</li>
  68. <li><a href="https://github.com/ValleyAudio/ValleyRackFree" target="_blank">ValleyAudio</a></li>
  69. </ul>
  70. <h3>Module fixes</h3>
  71. <ul>
  72. <li>Fix Core Audio2 meters stuck state when both L &amp; R are disconnected</li>
  73. <li>Fix Core Blank panel tags</li>
  74. <li>Fix Core Host-MIDI-Map flooding console logs in case of error (only print the same error once)</li>
  75. <li>Fix Core Host-Time reset trigger for hosts with non-static buffer sizes</li>
  76. <li>Fix DrumKit Sequencer memory corruption</li>
  77. <li>Fix mscHack PingPong filter cutoff value when loaded without GUI</li>
  78. </ul>
  79. <h3>Extra Notes</h3>
  80. <p>
  81. For packagers: fftw3f is now an optional dependency, required for "Audio to CV Pitch" module.<br/>
  82. The module will built if fftw3f is available during build, otherwise disabled.
  83. </p>
  84. <p>
  85. The "lv2export" stuff has been reworked and works now, includes 3 test plugins.<br/>
  86. This allows to export individual modules as single lv2 plugins, with very minimal binaries and no UI.<br/>
  87. For now it is still quite experimental, just to mess around with.<br/>
  88. Future releases might enable them by default, still undecided.
  89. </p>
  90. <h3>Downloads</h3>
  91. <p>
  92. The source code plus Linux, macOS and Windows binaries can be downloaded at
  93. <a href="https://github.com/DISTRHO/Cardinal/releases/tag/22.05" target="_blank">
  94. https://github.com/DISTRHO/Cardinal/releases/tag/22.05</a>.<br/>
  95. Cardinal is released as LV2, VST2 and VST3 plugin, plus AudioUnit and JACK standalone for certain systems.<br/>
  96. The VST3 version is still considered experimental, prefer to use LV2 or VST2 if possible at this time.
  97. </p>
  98. <hr/>
  99. <p>
  100. <span style="font-size: 20px">&gt; Correction: Changes in KXStudio repositories</span><br/>
  101. On <i>2022-04-25</i> by<i> falkTX</i>
  102. </p>
  103. <p>
  104. This is a quick correction to <a href="https://kx.studio/News/?action=view&url=changes-in-kxstudio-repositories-2">yesterday's post regarding changes in the KXStudio repositories</a>.<br/>
  105. I mentioned that the minimum required version was Debian 12 / Bookworm.<br/>
  106. This is incorrect, the minimum is actually Debian 11 / Bullseye.
  107. </p>
  108. <p>
  109. Apologies for the lapse, have a good day! :)
  110. </p>
  111. <hr/>
  112. <p>
  113. <span style="font-size: 20px">&gt; Changes in KXStudio repositories</span><br/>
  114. On <i>2022-04-24</i> by<i> falkTX</i>
  115. </p>
  116. <p>
  117. For the impatient ones, the too-long-didn't-read short summary is:
  118. </p>
  119. <ul>
  120. <li>Minimum required version to use the KXStudio repositories is now 20.04 / Focal or Debian 11 / Bullseye</li>
  121. <li>i386 / 32bit systems are no longer supported</li>
  122. <li>"Extras" repository has been marked as deprecated and should no longer be used</li>
  123. </ul>
  124. <h3>Updating base version to 20.04 / focal</h3>
  125. <p>
  126. As Ubuntu 22.04 was just announced, I began to do work on the KXStudio repositories once again.<br/>
  127. They were using Ubuntu 18.04 as base for all builds, which is getting old now and only has 1 more year of support.<br/>
  128. That last part is important - when 18.04 goes end-of-line, no new
  129. <a href="https://help.launchpad.net/Packaging/PPA" class="external free" rel="nofollow" target="_blank">Launchpad PPA</a>
  130. builds are possible.<br/>
  131. And since the KXStudio project relies on those for its packages, I need to update the base version from time to time in order to be able to keep building things.
  132. </p>
  133. <p>
  134. If you need to ask why using PPAs and not something else, there just isn't another service that can do all that is required (that I know of).<br/>
  135. <a href="https://build.opensuse.org/" class="external free" rel="nofollow" target="_blank">OpenSUSE's Open Build System</a>
  136. is similar, but it cannot handle the inter-dependency of the different sub-repositories.<br/>
  137. For example, a "toolchain" repo is used on all builds but not exported to the user, so it is safe to update things like cmake and meson only for the repository builds without breaking the user's system/packages.
  138. </p>
  139. <p>
  140. The extreme alternative would be to move to ArchLinux and their new
  141. <a href="https://github.com/osam-cologne/archlinux-proaudio/blob/master/ANNOUNCEMENT.md" class="external free" rel="nofollow" target="_blank">Unofficial Pro-Audio Package Repository</a>,
  142. and while tempting, I think a lot of users would be disappointed and sad with that call.<br/>
  143. And hosting the entire build setup myself is not going to happen, I do not have the capacity or funds for such a thing.
  144. </p>
  145. <p>
  146. But back to the topic at hand, moving up on the base version for KXStudio package builds means the user-facing minimum version also goes up.
  147. </p>
  148. <p>
  149. So as of today <b>the minimum required version to use the KXStudio repositories is 20.04 / Focal or Debian 11 / Bullseye</b>.<br/>
  150. Newly installed systems can no longer use the old variant of the KXStudio repositories.<br/>
  151. The old 18.04-base packages are not going to be updated anymore.
  152. </p>
  153. <h3>Issues with i386 builds</h3>
  154. <p>
  155. On 20.04 onwards, Ubuntu has disabled i386 PPA builds for all packages except those that are part of 20.04 release.<br/>
  156. The move to 20.04 as repository base is already taking place and I did quite a few tests to try and workaround the build limitation, but from what I can tell it is just not possible.<br/>
  157. This means <b>the KXStudio repositories will no longer provide i386 packages</b>.
  158. </p>
  159. <p>
  160. Everything else will keep working, including armhf and arm64 packages.<br/>
  161. Hopefully there are ways to still build a few 32bit things like wineasio and carla wine bridges, but those will be 64bit packages just with 32bit libraries.<br/>
  162. I did not actually test for this yet, more news on it soon.
  163. </p>
  164. <h3>Deprecated repositories</h3>
  165. <p>
  166. The lack of i386 package builds makes it impossible to build system libraries as was the case for the
  167. <a href="https://kx.studio/Repositories:Extras">"Extras" repository</a>.<br/>
  168. Without such packages it becomes pointless, so the <b>"Extras" repository has been marked as deprecated and should no longer be used</b>.
  169. </p>
  170. <p>
  171. Somewhat related, the KXStudio "Music" sub-repository served no real use in the end.<br/>
  172. And since now seems to be the time for cleanup and breakage, this one was marked as deprecated too.
  173. </p>
  174. <p>
  175. Such deprecations make <b>apt</b> very unhappy, and it will begin complaining something like this:<br/>
  176. </p>
  177. <pre>
  178. E: Repository 'http://ppa.launchpad.net/kxstudio-debian/music/ubuntu bionic InRelease' changed its 'Label' value from 'Music' to 'Deprecated'
  179. N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
  180. </pre>
  181. <p>
  182. Just cleanup the apt list cache and the errors go away, like this:<br/>
  183. </p>
  184. <p>
  185. <code>
  186. &nbsp;sudo rm -f /var/lib/apt/lists/*
  187. </code>
  188. </p>
  189. <p>
  190. If you were using the "Extras" repository and now have issues because JACK can not be installed or updated,
  191. you will need to revert it to the version from your official distribution repositories.<br/>
  192. Run this to fix it, replacing "focal" by the linux distribution version label that applies to your case:<br/>
  193. </p>
  194. <p>
  195. <code>
  196. &nbsp;sudo apt-get update<br/>
  197. &nbsp;sudo apt-get install libjack-jackd2-0/focal libjack-jackd2-0:i386/focal jackd2/focal
  198. </code>
  199. </p>
  200. <h3>Final notes</h3>
  201. <p>
  202. I realize this will make a few people sad, if the i386 builds were something you were relying on.<br/>
  203. It pains me too, as this kinda encourages throwing away old usable hardware that cannot do 64bit.<br/>
  204. Moving away from Debian base is not something I want to do at this point, but keeping 18.04 as base is not sustainable, as builds for it will soon stop working.<br/>
  205. And doing full custom repositories is a massive endeavour, something I don't have the time and resources (or patience) for.<br/>
  206. In the end, I am grateful to still be able to push new builds.
  207. </p>
  208. <p>
  209. Speaking of new builds, those will still take a bit to appear, as I have decided to do things a bit better this time.<br/>
  210. Using Ubuntu 20.04 as base allows to update the "debian format" to 13 which simplifies the builds, all packages are being converted one by one.<br/>
  211. Also, I am uploading all
  212. <a href="https://github.com/KXStudio/Repository/tree/master/sources" class="external free" rel="nofollow" target="_blank">debian source details on a public git repo</a>,
  213. as a backup/precaution measure and also to more easily allow others to see how packages in the KXStudio repositories are done.<br/>
  214. I do not really expect contributions that way, but more transparency is always nice.<br/>
  215. </p>
  216. <p>
  217. Based on previous work done for
  218. <a href="https://github.com/DISTRHO/DPF-Plugins/blob/289bd3e0af17aea5849ebafa28ed1c609db68369/.github/workflows/build.yml#L358" class="external free" rel="nofollow" target="_blank">continous-testing in Carla and DPF</a>,
  219. I want to setup similar runtime tests for all plugins before they get pushed into the repositories.<br/>
  220. Compared to just a few years ago, testing plugins is now much easier,
  221. with Carla having a dedicated command-line test mode,
  222. <a href="https://lv2plug.in/pages/validating-lv2-data.html" class="external free" rel="nofollow" target="_blank">LV2 validation tools</a>
  223. becoming better and even
  224. <a href="https://open-music-kontrollers.ch/lv2/lv2lint/#" class="external free" rel="nofollow" target="_blank">lv2lint</a>
  225. that performs runtime tests.
  226. </p>
  227. <p>
  228. I still want to finalize a few things in
  229. <a href="https://github.com/DISTRHO/Cardinal" class="external free" rel="nofollow" target="_blank">Cardinal</a>
  230. before going full-force on the repositories, but that side is almost done now, so very soon my attention can go back to packaging.<br/>
  231. Good times ahead!
  232. </p>
  233. <hr/>
  234. <p>
  235. <span style="font-size: 20px">&gt; Carla 2.4.3 has been released</span><br/>
  236. On <i>2022-02-19</i> by<i> falkTX</i>
  237. </p>
  238. <p>
  239. This is a small bugfix release for the Carla v2.4 series.
  240. </p>
  241. <p>
  242. <img src="/screenshots/carla.png" alt="carla"/>
  243. </p>
  244. <p>
  245. <a href="https://kx.studio/carla" class="external free" rel="nofollow" target="_blank">Carla</a>
  246. is an audio plugin host, with support for many audio drivers and plugin formats.<br/>
  247. It has some nice features like automation of parameters via MIDI CC (and send output back as MIDI too) and full OSC control.<br/>
  248. </p>
  249. <h3>Fixes</h3>
  250. <ul>
  251. <li>Fix build for Alpine Linux and BSD</li>
  252. <li>Fix integration with internal Qt toolbar visibility state</li>
  253. <li>Fix plugin search (regression from 2.4.2)</li>
  254. <li>Fix several Windows UTF-16 issues</li>
  255. </ul>
  256. <h3>Build related changes</h3>
  257. <ul>
  258. <li>Add -fno-gnu-unique to default build flags</li>
  259. <li>Implement VERBOSE make flag</li>
  260. <li>Make build compatible with LTO, now enabled on official macOS/Windows binaries</li>
  261. <li>Replace CARLA_EXPORT macro with separate API / PLUGIN export options</li>
  262. <li>Set new X-NSM-Exec desktop file property</li>
  263. </ul>
  264. <h3>Downloads</h3>
  265. <p>
  266. To download Carla binaries or source code, jump on over to the <a href="https://kx.studio/Downloads" class="external free" rel="nofollow" target="_blank">KXStudio downloads section</a>.<br/>
  267. If you're using the KXStudio repositories, you can simply install "carla".<br/>
  268. Bug reports and feature requests are welcome! Jump on over to the <a href="https://github.com/falkTX/Carla" class="external free" rel="nofollow" target="_blank">Carla's Github project</a> page for those.
  269. </p>
  270. <h3>Notes for users</h3>
  271. <p>
  272. This was already the case for v2.2 and v2.3 but it is worth reiterating:<br/>
  273. When using JACK2, the canvas - plugin integrations requires at least JACK2 v1.9.13.<br/>
  274. This is because Carla relies on JACK meta-data in order to store information about each plugin/client,
  275. and meta-data was only added to JACK2 in version 1.9.13.<br/>
  276. Alternatively, you can use JACK1 instead of JACK2, which has meta-data support since a long time.
  277. </p>
  278. <p>
  279. Also there are still no official Linux binary builds for v2.4.3.<br/>
  280. Carla v2.4.3 is provided in the KXStudio repositories and in many official Linux distribution repositories anyway.
  281. </p>
  282. <hr/>
  283. <p>
  284. <span style="font-size: 20px">&gt; Cardinal 22.04 released</span><br/>
  285. On <i>2022-04-04</i> by<i> falkTX</i>
  286. </p>
  287. <p>
  288. Hello everyone, yet another release of <a href="https://github.com/DISTRHO/Cardinal" target="_blank">Cardinal</a> is here,
  289. this time focused on bugfixes.<br/>
  290. <a href="https://github.com/DISTRHO/Cardinal" target="_blank">Cardinal</a>
  291. is a free and open-source virtual modular synthesizer plugin.<br/>
  292. It is based on the popular <a href="https://github.com/VCVRack/Rack/" target="_blank">VCV Rack</a>
  293. but with a focus on being a fully self-contained plugin version.
  294. </p>
  295. <p>
  296. <img src="/repo/screenshots/cardinal.png" alt="cardinal"/>
  297. </p>
  298. <p>
  299. Changelog:
  300. </p>
  301. <ul>
  302. <li>Add Interverb demo patch (in source code)</li>
  303. <li>Add retrigger to Host-MIDI</li>
  304. <li>Do not show resize handle on JACK Standalone</li>
  305. <li>Fix and enable ChowDSP Credit module</li>
  306. <li>Fix potential noise burts on load with ihtsyn MVerb-based modules</li>
  307. <li>Fix messed up graphics on Windows with High-DPI screens</li>
  308. <li>Fix resources not found on some Windows systems (by not relying on environment variables)</li>
  309. <li>Fix several Windows UTF-16 issues</li>
  310. <li>Fix X11 file dialogs not appearing on some systems (auto-activate needed DBus portal)</li>
  311. <li>Fix VST3 state under some hosts</li>
  312. <li>Make JACK Standalone more useful on Windows (log to console when possible, show error dialog if JACK not running)</li>
  313. <li>Optimizations to core modules and headless build</li>
  314. <li>Refresh default template, add FX and Synth specific template variants</li>
  315. <li>Tweak Host-MIDI default parameters</li>
  316. </ul>
  317. <h3>Downloads</h3>
  318. <p>
  319. The source code plus Linux, macOS and Windows binaries can be downloaded at
  320. <a href="https://github.com/DISTRHO/Cardinal/releases/tag/22.04" target="_blank">
  321. https://github.com/DISTRHO/Cardinal/releases/tag/22.04</a>.<br/>
  322. Cardinal is released as LV2, VST2 and VST3 plugin, plus AudioUnit and JACK standalone for certain systems.<br/>
  323. The VST3 version is still considered experimental, prefer to use LV2 or VST2 if possible at this time.
  324. </p>
  325. <hr/>
  326. <p>
  327. <span style="font-size: 20px">&gt; Cardinal 22.03 released</span><br/>
  328. On <i>2022-03-21</i> by<i> falkTX</i>
  329. </p>
  330. <p>
  331. Hello everyone, a new release of Cardinal is here.<br/>
  332. This brings quite a few new extra modules, updates the existing ones and adds a few nice features as requested by users.<br/>
  333. This is what changed compared to the (initial) 22.02 release:
  334. </p>
  335. <ul>
  336. <li>Add Windows installer, shipping with optional Carla Plugin Host integration and JACK Standalone</li>
  337. <li>Add AudioUnit plugin format for macOS</li>
  338. <li>Fix build for HaikuOS (only headless possible for now)</li>
  339. <li>Fix crash in headless build when loading certain modules</li>
  340. <li>Fix GUI resize in high-dpi systems</li>
  341. <li>Fix Host MIDI-CC channel pressure and pitchbend interfering with CCs</li>
  342. <li>Fix repaints in macOS, allow to set update rate limit (only works in some hosts)</li>
  343. <li>Fix VST2 keyboard input always in uppercase in some hosts</li>
  344. <li>Force 32bit alignment for vectorized operations, fixes 32bit build</li>
  345. <li>Initial bypass implementation, MIDI only for now</li>
  346. <li>Make host audio meters independent from each other</li>
  347. <li>Merge CardinalFX and CardinalSynth VST2 folders as single Cardinal.vst</li>
  348. <li>Update VCV Rack base to v2.1</li>
  349. </ul>
  350. <h3>New modules</h3>
  351. <p>
  352. There's quite a few modules in this release, below follows a link to each project.<br/>
  353. Same as in the previous release, all modules were checked for compatibility with GPLv3+ license.
  354. More details <a href="https://github.com/DISTRHO/Cardinal/blob/main/docs/LICENSES.md" target="_blank">here</a>.
  355. </p>
  356. <ul>
  357. <a href="https://github.com/8Mode/8Mode-VCV_Modules" target="_blank"><li>8Mode</a></li>
  358. <a href="https://github.com/aaronstatic/AaronStatic_modules" target="_blank"><li>Aaron Static</a></li>
  359. <a href="https://github.com/algoritmarte/AlgoritmarteVCVPlugin" target="_blank"><li>AlgoritmArte</a></li>
  360. <a href="https://github.com/AnimatedCircuits/RackModules" target="_blank"><li>Animated Circuits</a></li>
  361. <a href="https://github.com/CardinalModules/ArableInstruments" target="_blank"><li>Arable Instruments</a></li>
  362. <a href="https://github.com/kauewerner/Axioma" target="_blank"><li>Axioma</a></li>
  363. <a href="https://github.com/VCVRack/Befaco" target="_blank"><li>Befaco</a></li>
  364. <a href="https://github.com/catronomix/catro-modulo" target="_blank"><li>Catro/Modulo</a></li>
  365. <a href="https://github.com/jensschulze/GoodSheperd" target="_blank"><li>GoodSheperd</a></li>
  366. <a href="https://gitlab.com/hampton-harmonics/hampton-harmonics-modules" target="_blank"><li>Hampton Harmonics</a></li>
  367. <a href="https://github.com/janne808/kocmoc-rack-modules" target="_blank"><li>kocmoc</a></li>
  368. <a href="https://github.com/grough/lilac-loop-vcv" target="_blank"><li>Lilac Loop</a></li>
  369. <a href="https://github.com/martin-lueders/ML_modules" target="_blank"><li>ML Modules</a></li>
  370. <a href="https://github.com/MockbaTheBorg/MockbaModular" target="_blank"><li>Mockba Modular</a></li>
  371. <a href="https://github.com/netboy3/MSM-vcvrack-plugin" target="_blank"><li>MSM</a></li>
  372. <a href="https://github.com/mhetrick/nonlinearcircuits" target="_blank"><li>Nonlinear Circuits</a></li>
  373. <a href="https://github.com/RareBreeds/Orbits" target="_blank"><li>Orbits</a></li>
  374. <a href="https://github.com/CardinalModules/ArableInstruments" target="_blank"><li>Parable Instruments</a></li>
  375. <a href="https://github.com/patheros/PathSetModules" target="_blank"><li>Path Set</a></li>
  376. <a href="https://github.com/aptrn/stocaudio-modules" target="_blank"><li>stocaudio</a></li>
  377. <a href="https://github.com/clone45/voxglitch" target="_blank"><li>Voxglitch</a></li>
  378. </ul>
  379. <h3>Downloads</h3>
  380. <p>
  381. The source code plus Linux, macOS and Windows binaries can be downloaded at
  382. <a href="https://github.com/DISTRHO/Cardinal/releases/tag/22.03" target="_blank">
  383. https://github.com/DISTRHO/Cardinal/releases/tag/22.03</a>.<br/>
  384. Cardinal is released as LV2, VST2 and VST3 plugin, plus AudioUnit and JACK standalone for certain systems.<br/>
  385. The VST3 version is still considered experimental, prefer to use LV2 or VST2 if possible at this time.
  386. </p>
  387. <hr/>
  388. <p>
  389. <span style="font-size: 20px">&gt; Ildaeil v1.0 released</span><br/>
  390. On <i>2022-02-21</i> by<i> falkTX</i>
  391. </p>
  392. <p>
  393. Hello everyone, another release is here, this time it is
  394. <a href="https://github.com/DISTRHO/Ildaeil" target="_blank">Ildaeil</a>.<br/>
  395. Something that was initially done as a test for
  396. <a href="https://github.com/falkTX/Carla" target="_blank">Carla</a>
  397. and
  398. <a href="https://github.com/ocornut/imgui" target="_blank">ImGui</a>
  399. usage within
  400. <a href="https://github.com/DISTRHO/DPF" target="_blank">DPF</a>,
  401. but turns out to be actually quite useful!<br/>
  402. To those that are not up to date on KXStudio developments, let's recap this little new project...<br/>
  403. </p>
  404. <p>
  405. <img src="/repo/screenshots/ildaeil.png" alt="ildaeil"/>
  406. </p>
  407. <p>
  408. <a href="https://github.com/DISTRHO/Ildaeil" target="_blank"><b>Ildaeil</b></a>
  409. is mini-plugin host working as a plugin allowing one-to-one plugin format reusage.<br/>
  410. The idea is to load it as a plugin inside your DAW and then the other "real" plugin inside Ildaeil.<br/>
  411. This allows, for example, a VST3 host to load LV2 plugins.
  412. </p>
  413. <p>
  414. For the more technically-minded people, this is basically a combination of
  415. <a href="https://github.com/falkTX/Carla" target="_blank">Carla</a>,
  416. <a href="https://github.com/DISTRHO/DPF" target="_blank">DPF</a>
  417. and
  418. <a href="https://github.com/DISTRHO/DPF-Widgets" target="_blank">DPF-Widgets</a>.<br/>
  419. There is some small code of its own for handling the drawing of the plugin list, generic GUI and offset the embed GUIs,
  420. but everything else is done by these other projects.<br/>
  421. Nothing that Ildaeil does is special, that Carla can't do, but using Carla means always having to deal with an extra window.<br/>
  422. When wanting to load a single LV2 plugin on a non-LV2 supported host for example, this becomes quite cumbersome.<br/>
  423. With a little bit of glue code to tie up Carla, DPF and a little GUI, this project becomes possible.
  424. </p>
  425. <h3>Example</h3>
  426. <p>
  427. Here is an example, loading the LV2-specific plugin
  428. <a href="https://github.com/Dougal-s/Aether" target="_blank">Aether</a>
  429. inside
  430. <a href="https://www.renoise.com/" target="_blank">Renoise</a>, which does not support LV2 plugins.
  431. </p>
  432. <p>
  433. <img src="/screenshots/news/ildaeil-renoise-aether.png" alt="ildaeil-renoise-aether"/>
  434. </p>
  435. <p>
  436. You can see more of these screenshots
  437. <a href="https://github.com/DISTRHO/Ildaeil/tree/v1.0#screenshots" target="_blank">here</a>.
  438. </p>
  439. <h3>Details</h3>
  440. <p>
  441. The Ildaeil name comes from the korean 일대일, which means "one to one".<br/>
  442. It is one plugin exposed to the host (Ildaeil itself) and one plugin loaded inside Ildaeil.
  443. </p>
  444. <p>
  445. When open, Ildaeil will show a list of plugins to pick from or the plugin editor if one is already selected.<br/>
  446. If the plugin provides an embedable UI, Ildaeil show will that by default, otherwise it shows a generic parameter list.<br/>
  447. Toggling between generic vs custom/embed view is possible.<br/>
  448. In the case of a plugin providing a custom UI that is not embedable, Ildaeil will show the generic view by default.<br/>
  449. You can press "Show Custom GUI" to open the plugin UI in an external window.<br/>
  450. </p>
  451. <p>
  452. For version 1.0, this is what we have:
  453. </p>
  454. <ul>
  455. <li>Available as JACK/Standalone, LV2, VST2 and VST3 (with VST3 being experimental)</li>
  456. <li>Can load internal (from Carla) and LV2 plugins</li>
  457. <li>Comes in Synth, FX and MIDI variants</li>
  458. <li>LV2 plugins can run in-process or bridged</li>
  459. <li>Works on macOS, Windows and Linux/X11 systems</li>
  460. </ul>
  461. <p>
  462. And these are the current limitations:
  463. </p>
  464. <ul>
  465. <li>Plugin parameters are not exposed to the host</li>
  466. <li>UI is not resizable by the host</li>
  467. </ul>
  468. <p>
  469. Later on, in theory, it should be able to load the other plugin formats supported by Carla
  470. (that being LADSPA, DSSI, VST2, VST3 and AU).<br/>
  471. There are some technical limitations that prevent this from happening right now,
  472. Carla will need some backend changes before this can happen.
  473. </p>
  474. <p>
  475. Note that exposing the parameters to the host is not in the immediate plans.
  476. </p>
  477. <h3>Downloads</h3>
  478. <p>
  479. There are pre-compiled binaries for Linux, macOS and Windows which can downloaded at
  480. <a href="https://github.com/DISTRHO/Ildaeil/releases/tag/v1.0" target="_blank">
  481. https://github.com/DISTRHO/Ildaeil/releases/tag/v1.0</a>.<br/>
  482. You can also find it in the KXStudio repositories as <b>ildaeil</b> package.<br/>
  483. </p>
  484. <p>
  485. Have fun!
  486. </p>
  487. <hr/>
  488. <p>
  489. <span style="font-size: 20px">&gt; Carla 2.4.2 has been released</span><br/>
  490. On <i>2022-02-19</i> by<i> falkTX</i>
  491. </p>
  492. <p>
  493. This is a bugfix release for Carla version v2.4 series, with some extra user-experience related changes.
  494. </p>
  495. <p>
  496. <img src="/screenshots/carla.png" alt="carla"/>
  497. </p>
  498. <p>
  499. <a href="https://kx.studio/carla" class="external free" rel="nofollow" target="_blank">Carla</a>
  500. is an audio plugin host, with support for many audio drivers and plugin formats.<br/>
  501. It has some nice features like automation of parameters via MIDI CC (and send output back as MIDI too) and full OSC control.<br/>
  502. </p>
  503. <h3>Fixes</h3>
  504. <ul>
  505. <li>Fix a few crashes with JACK applications inside Carla</li>
  506. <li>Fix build on non-supported systems by JUCE</li>
  507. <li>Fix crash when LV2 X11 UI has non-mapped child window</li>
  508. <li>Fix compatibility with Python 3.10</li>
  509. <li>Fix default SF2/3 path</li>
  510. <li>Fix LV2 UI resizing on macOS</li>
  511. <li>Fix missing VST3 plugins not being searched recursively</li>
  512. <li>Disable GraphicsScene indexing method to prevent crashes</li>
  513. <li>Ensure custom data state save and restore always match</li>
  514. </ul>
  515. <h3>Changes</h3>
  516. <ul>
  517. <li>Add "[carla]" prefix to printed messages</li>
  518. <li>Add appdata metadata information</li>
  519. <li>Add notice when Carla needs to be restarted after an LV2 rescan</li>
  520. <li>Add VST3 Windows common files to the default path (required by the latest VST3 spec)</li>
  521. <li>Default to JACK backend if pipewire-jack replacement is installed</li>
  522. <li>Implement dry/wet, volume and balance on JUCE hosted plugins</li>
  523. <li>Reload audio file if sample rate changes</li>
  524. <li>Use temporary files for big custom data values in bridges</li>
  525. </ul>
  526. <h3>Changes for using Carla as library</h3>
  527. <ul>
  528. <li>Add 8 CV, 32 IO and 64 IO CarlaPatchbay variants</li>
  529. <li>Add audio port hints to backend, starting with lv2 sidechain</li>
  530. <li>Add static plugin build target</li>
  531. <li>Add WITH_LTO build option, disabled by default</li>
  532. <li>Allow setting a custom C++ namespace</li>
  533. <li>More work on experimental embed plugin UIs, now also possible on plugin bridges</li>
  534. </ul>
  535. <h3>Downloads</h3>
  536. <p>
  537. To download Carla binaries or source code, jump on over to the <a href="https://kx.studio/Downloads" class="external free" rel="nofollow" target="_blank">KXStudio downloads section</a>.<br/>
  538. If you're using the KXStudio repositories, you can simply install "carla".<br/>
  539. Bug reports and feature requests are welcome! Jump on over to the <a href="https://github.com/falkTX/Carla" class="external free" rel="nofollow" target="_blank">Carla's Github project</a> page for those.
  540. </p>
  541. <h3>Notes for users</h3>
  542. <p>
  543. This was already the case for v2.2 and v2.3 but it is worth reiterating:<br/>
  544. When using JACK2, the canvas - plugin integrations requires at least JACK2 v1.9.13.<br/>
  545. This is because Carla relies on JACK meta-data in order to store information about each plugin/client,
  546. and meta-data was only added to JACK2 in version 1.9.13.<br/>
  547. Alternatively, you can use JACK1 instead of JACK2, which has meta-data support since a long time.
  548. </p>
  549. <p>
  550. Also there are still no official Linux binary builds for v2.4.2.<br/>
  551. Carla v2.4.2 is provided in the KXStudio repositories and in many official Linux distribution repositories anyway.
  552. </p>
  553. <hr/>
  554. <p>
  555. <span style="font-size: 20px">&gt; WineASIO v1.1.0 released</span><br/>
  556. On <i>2022-02-18</i> by<i> falkTX</i>
  557. </p>
  558. <p>
  559. Hello everyone, a new release of WineASIO is here.<br/>
  560. This is mostly for Wine >= 6.5 compatibility, and a few small fixes here and there.<br/>
  561. Check the <a href="https://github.com/wineasio/wineasio/commits/master" target="_blank">git log</a> for the precise changes.
  562. </p>
  563. <p>
  564. Details are explained in the <a href="https://github.com/wineasio/wineasio/tree/master#wine--65" target="_blank">README file</a>,
  565. but in short we now need to build an extra fake dll and use full paths when calling <b><code>regsvr32</code></b>.<br/>
  566. Where we previously needed:<br/>
  567. <b><code>wine64 regsvr32 wineasio.dll</code></b>
  568. <br/>
  569. Now we require the full path, on Ubuntu for example it is:<br/>
  570. <b><code>wine64 regsvr32 /usr/lib/x86_64-linux-gnu/wine/x86_64-windows/wineasio.dll</code></b>
  571. </p>
  572. <p>
  573. As was the case with v1.0.0, there are no pre-compiled binaries for WineASIO, though it is available as a package in the KXStudio repositories.<br/>
  574. You can find this v1.1.0 release at <a href="https://github.com/wineasio/wineasio/releases/tag/v1.1.0" target="_blank">github.com/wineasio/wineasio</a>.
  575. </p>
  576. <p>
  577. Small warning: WineASIO is not compatible with PipeWire.<br/>
  578. This is
  579. <a href="https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1495" target="_blank">under investigation</a>,
  580. it is not known at this point why it does not work for PipeWire's JACK implementation.
  581. </p>
  582. <hr/>
  583. <p>
  584. <span style="font-size: 20px">&gt; Cardinal 22.02 is now released</span><br/>
  585. On <i>2022-02-14</i> by<i> falkTX</i>
  586. </p>
  587. <p>
  588. It is finally here, the first release of <a href="https://github.com/DISTRHO/Cardinal" target="_blank">Cardinal</a>.<br/>
  589. Has been slowly brewing behind the scenes, and now ready for the masses.<br/>
  590. First, some introductions...
  591. </p>
  592. <p>
  593. <img src="/repo/screenshots/cardinal.png" alt="cardinal"/>
  594. </p>
  595. <p>
  596. <a href="https://github.com/DISTRHO/Cardinal" target="_blank">Cardinal</a>
  597. is a free and open-source virtual modular synthesizer plugin.<br/>
  598. It is based on the popular <a href="https://github.com/VCVRack/Rack/" target="_blank">VCV Rack</a>
  599. but with a focus on being a fully self-contained plugin version.
  600. </p>
  601. <p>
  602. Cardinal was created first and foremost as a way to have Rack as a proper open-source audio plugin.<br/>
  603. A proper audio plugin should be self-contained as much as possible, as to not interfere with the DAW/Host. Loading external modules clearly goes against this idea.<br/>
  604. Not to mention being <b>open-source</b>, otherwise we are at the mercy of the wishes of a company for what we can and cannot do, which is not that great...<br/>
  605. (in case you were not aware, VCV's Rack plugin version, called "Rack Pro", is a commercial closed-source product)
  606. </p>
  607. <p>
  608. It needs to be said that Cardinal project and its authors do not wish anything bad to the original/official Rack project.<br/>
  609. In fact, Cardinal wouldn't exist if not for Rack v2 release. (which has many needed things to make a plugin version work)<br/>
  610. Cardinal and Rack should be able to co-exist friendly and peacefully, as they clearly have different targets.<br/>
  611. It is likely most people will prefer to use Rack Pro for its official support and its big module collection (including commercial ones).<br/>
  612. A feature comparison between Cardinal and Rack Pro can be seen
  613. <a href="https://github.com/DISTRHO/Cardinal/blob/main/docs/DIFFERENCES.md" target="_blank">here</a>.
  614. </p>
  615. <p>
  616. With that out of the way, let's go through a quick overview.
  617. </p>
  618. <h3>Plugin variants</h3>
  619. <p>
  620. Cardinal provides 3 plugin variants - <b>Main</b>, <b>Synth</b> and <b>FX</b>.<br/>
  621. They are all equivalent in performance and behaviour, with only the IO and metadata that changes.<br/>
  622. This is because some hosts are very strict on which plugins are allowed as instruments vs FX, so separate variants of the same plugin are needed.<br/>
  623. </p>
  624. <p>
  625. <b>FX</b> and <b>Synth</b> variants both have 2 audio outputs, while <b>Main</b> has 8.<br/>
  626. All variants have MIDI input and output support.
  627. </p>
  628. <p>
  629. <b>Main</b> provides 8 audio inputs and outputs and 10 CV inputs and outputs.<br/>
  630. Note that due to VST2 format not supporting CV ports, this variant is not available for VST2.
  631. </p>
  632. <p>
  633. <b>Synth</b> provides 2 audio outputs but no audio inputs or CV ports.<br/>
  634. Plugin type is set as "instrument".
  635. </p>
  636. <p>
  637. And finally <b>FX</b> provides 2 audio inputs and outputs, but no CV ports.<br/>
  638. Plugin type is set as regular "effect".
  639. </p>
  640. <h3>Included modules</h3>
  641. <p>
  642. At the moment the following 3rd-party modules are provided:
  643. </p>
  644. <ul>
  645. <a href="https://github.com/netboy3/21kHz-rack-plugins" target="_blank"><li>21kHz</a></li>
  646. <a href="https://github.com/jhoar/AmalgamatedHarmonics" target="_blank"><li>Amalgamated Harmonics</a></li>
  647. <a href="https://github.com/AriaSalvatrice/AriaModules" target="_blank"><li>Aria Salvatrice</a></li>
  648. <a href="https://github.com/VCVRack/AudibleInstruments" target="_blank"><li>Audible Instruments</a></li>
  649. <a href="https://github.com/NikolaiVChr/Autinn" target="_blank"><li>Autinn</a></li>
  650. <a href="https://github.com/baconpaul/BaconPlugs" target="_blank"><li>Bacon Music</a></li>
  651. <a href="https://github.com/sebastien-bouffier/Bidoo" target="_blank"><li>Bidoo</a></li>
  652. <a href="https://github.com/bogaudio/BogaudioModules" target="_blank"><li>Bogaudio</a></li>
  653. <a href="https://github.com/cfoulc/cf" target="_blank"><li>cf</a></li>
  654. <a href="https://github.com/jatinchowdhury18/ChowDSP-VCV/" target="_blank"><li>ChowDSP</a></li>
  655. <a href="https://github.com/SVModular/DrumKit/" target="_blank"><li>DrumKit</a></li>
  656. <a href="https://github.com/VCVRack/ESeries" target="_blank"><li>E-Series</a></li>
  657. <a href="https://github.com/expertsleepersltd/vcvrack-encoders" target="_blank"><li>ExpertSleepers Encoders</a></li>
  658. <a href="https://github.com/EaterOfSheep/Extratone" target="_blank"><li>Extratone</a></li>
  659. <a href="https://github.com/RCameron93/FehlerFabrik" target="_blank"><li>Fehler Fabrik</a></li>
  660. <a href="https://github.com/gluethegiant/gtg-rack" target="_blank"><li>Glue the Giant</a></li>
  661. <a href="https://github.com/dbgrande/GrandeModular" target="_blank"><li>Grande</a></li>
  662. <a href="https://github.com/mhetrick/hetrickcv" target="_blank"><li>HetrickCV</a></li>
  663. <a href="https://github.com/nysthi/ihtsyn" target="_blank"><li>ihtsyn</a></li>
  664. <a href="https://github.com/MarcBoule/ImpromptuModular" target="_blank"><li>Impromptu</a></li>
  665. <a href="https://github.com/jeremywen/JW-Modules/" target="_blank"><li>JW-Modules</a></li>
  666. <a href="https://github.com/SteveRussell33/LifeFormModular" target="_blank"><li>LifeFormModular</a></li>
  667. <a href="https://github.com/mgunyho/Little-Utils" target="_blank"><li>Little Utils</a></li>
  668. <a href="https://github.com/LomasModules/LomasModules" target="_blank"><li>Lomas Modules</a></li>
  669. <a href="https://github.com/VegaDeftwing/LyraeModules" target="_blank"><li>Lyrae Modules</a></li>
  670. <a href="https://github.com/MarcBoule/MindMeldModular" target="_blank"><li>MindMeld</a></li>
  671. <a href="https://github.com/JustMog/Mog-VCV" target="_blank"><li>Mog</a></li>
  672. <a href="https://github.com/mschack/VCV-Rack-Plugins" target="_blank"><li>mscHack</a></li>
  673. <a href="https://github.com/SteveRussell33/Prism" target="_blank"><li>Prism</a></li>
  674. <a href="https://github.com/n0jo/rackwindows" target="_blank"><li>rackwindows</a></li>
  675. <a href="https://github.com/SteveRussell33/repelzen" target="_blank"><li>repelzen</a></li>
  676. <a href="https://gitlab.com/sonusdept/sonusmodular" target="_blank"><li>Sonus Modular</a></li>
  677. <a href="https://github.com/ValleyAudio/ValleyRackFree" target="_blank"><li>Valley</a></li>
  678. <a href="https://github.com/mhampton/ZetaCarinaeModules" target="_blank"><li>ZetaCarinae</a></li>
  679. <a href="https://github.com/zezic/ZZC" target="_blank"><li>ZZC</a></li>
  680. </ul>
  681. <p>
  682. Additionally Cardinal
  683. <a href="https://github.com/DISTRHO/Cardinal/blob/main/docs/CARDINAL-MODULES.md" target="_blank">provides its own modules</a>
  684. for DAW/Host automation, time position and internal plugin hosting.
  685. </p>
  686. <h3>Current status and future plans</h3>
  687. <p>
  688. With the exception of a few bugs, Cardinal can be considered stable.<br/>
  689. Though currently the following should be noted:
  690. </p>
  691. <ul>
  692. <li>Keyboard input does not always work in some hosts <a href="https://github.com/DISTRHO/Cardinal/issues/24" target="_blank">#24</a></li>
  693. <li>VST3 support incomplete/experimental <a href="https://github.com/DISTRHO/Cardinal/issues/41" target="_blank">#41</a></li>
  694. <li>Windows 32bit builds do not work well <a href="https://github.com/DISTRHO/Cardinal/issues/80" target="_blank">#80</a></li>
  695. </ul>
  696. <p>
  697. A parameter expander module was not ready on time for this release, but will come soon in a future release.<br/>
  698. <a href="https://github.com/VCVRack/Fundamental" target="_blank">Fundamental</a>
  699. is on a similar situation, there are some artwork license issues that prevent us from using Fundamental exactly as we want.<br/>
  700. We plan to redo Fundamental's panel graphics in a more liberal license, so it then can be included in Cardinal.
  701. </p>
  702. <p>
  703. There are a few modules we want to add, but they are being evaluated carefully as going forward anything we add in Cardinal needs to remain there forever, for backwards compatibility.<br/>
  704. They must also have a GPLv3+ compatible license, which not all of them do.<br/>
  705. Not to mention a clear artwork/graphics license... it is amazing how many of these projects do not care or understand about software licenses :(<br/>
  706. Overall it makes packaging quite difficult, so it is natural that new modules are not added as fast as we wished for.
  707. </p>
  708. <p>
  709. Something I hope to try soon is an alternative way to handle MIDI to CV conversion, as I don't like the way Rack does it at the moment.<br/>
  710. The current Cardinal "core" modules follow the same exact approach as the official Rack, to make the transition easier,
  711. but some kind of "MIDI v2" modules will be done eventually.
  712. </p>
  713. <h3>Contributing</h3>
  714. <p>
  715. If you like the project and want to help out, there are basic building instructions
  716. <a href="https://github.com/DISTRHO/Cardinal/blob/main/docs/BUILDING.md" target="_blank">here</a>,<br/>
  717. And an overview of the source code is available
  718. <a href="https://github.com/DISTRHO/Cardinal/blob/main/docs/OVERVIEW.md" target="_blank">here</a>.<br/>
  719. </p>
  720. <p>
  721. Currently we are all on <b>#cardinal</b> IRC room in irc.libera.chat server.<br/>
  722. Come join us in your favorite IRC client or through a Matrix bridge.
  723. </p>
  724. <p>
  725. Installing new modules on an existing Cardinal binary is not possible at run-time, but we can add new modules to the build.<br/>
  726. Details on this are available
  727. <a href="https://github.com/DISTRHO/Cardinal/discussions/28" target="_blank">here</a>.<br/>
  728. Also check
  729. <a href="https://github.com/DISTRHO/Cardinal/wiki/Possible-modules-to-include" target="_blank">this wiki page</a>
  730. where we discuss possible modules to include.
  731. </p>
  732. <h3>Installing and using</h3>
  733. <p>
  734. Install instructions are available on
  735. <a href="https://github.com/DISTRHO/Cardinal/wiki/Install" target="_blank">this wiki page</a>.<br/>
  736. If you are using the KXStudio repositories you can simply install <b>cardinal-lv2</b>, <b>cardinal-vst2</b> or <b>cardinal-vst3</b> packages as usual.<br/>
  737. Consult the wiki page linked above for details on other distributions, or otherwise use the prebuilt binaries on the
  738. <a href="https://github.com/DISTRHO/Cardinal/releases" target="_blank">Cardinal releases</a> page.
  739. </p>
  740. <p>
  741. There is no Cardinal official media content as of yet,
  742. but if you are looking for tutorials just look for "VCV Rack" stuff which pretty much applies to Cardinal unchanged.<br/>
  743. Some modules will appear slightly different, or not be available, but the overall idea on how to use it is the same.
  744. </p>
  745. <p>
  746. A few CC-0 / public domain Cardinal patches are present
  747. <a href="https://github.com/DISTRHO/Cardinal/tree/main/patches" target="_blank">directly in the source code</a>.<br/>
  748. You can use those as your starting point, they are fully free to do what you want with.
  749. </p>
  750. <p>
  751. And that is it, go download, install and have fun!<br/>
  752. If you find an issue or want to request a potentially useful feature, please use the
  753. <a href="https://github.com/DISTRHO/Cardinal/issues" target="_blank">Cardinal issue tracker</a>.<br/>
  754. And happy Valentine's day too. \o/
  755. </p>
  756. <hr/>
  757. <p>
  758. <span style="font-size: 20px">&gt; DPF-Plugins v1.5 released</span><br/>
  759. On <i>2022-01-16</i> by<i> falkTX</i>
  760. </p>
  761. <p>
  762. Hello everyone, a new release of DPF-Plugins is here.<br/>
  763. DPF-Plugins is a collection of DPF-based plugins, including Kars, MVerb and Nekobi.<br/>
  764. This is mostly a bugfix release, keeping up with the cool kids for regular releases.<br/>
  765. </p>
  766. <p>
  767. Changelog:
  768. </p>
  769. <ul>
  770. <li>Initial experimental VST3 support</li>
  771. <li>Add bottom-right resize handle in glBars and ProM, needed in plugin formats that can't do host-side resizing<br/>
  772. (ProM resize handle is invisible but still works, known issue)</li>
  773. <li>Some plugin GUIs can use Cairo instead of OpenGL, if OpenGL is not available at build time</li>
  774. <li>Standalones no longer require JACK, instead detecting at runtime if it is available</li>
  775. <li>Standalones will now use RtAudio for native audio device access in case JACK is not available</li>
  776. <li>ProM now ships with (optional) vendored libprojectM in case it is not available as system library</li>
  777. <li>ProM now sets up and uses OpenGL3 context instead of OpenGL2 forward compatibility mode, fixing usage on macOS and Windows</li>
  778. <li>Fix modal about dialogs</li>
  779. <li>Fix more High-DPI related issues</li>
  780. <li>Fix OpenGL context swap on GUI deletion, needed on hosts using OpenGL</li>
  781. </ul>
  782. <h3>Downloads</h3>
  783. <p>
  784. The source code plus Linux, macOS and Windows binaries can be downloaded at
  785. <a href="https://github.com/DISTRHO/DPF-Plugins/releases/tag/v1.5" target="_blank">
  786. https://github.com/DISTRHO/DPF-Plugins/releases/tag/v1.5</a>.<br/>
  787. The plugins are released as LADSPA, DSSI, LV2, VST2, VST3 and JACK standalone.<br/>
  788. </p>
  789. <hr/>
  790. <p>
  791. <span style="font-size: 20px">&gt; KXStudio Monthly Report (November + December 2021)</span><br/>
  792. On <i>2021-12-31</i> by<i> falkTX</i>
  793. </p>
  794. <p>
  795. Hello all, this is yet another one of those monthly reports about the KXStudio project.<br/>
  796. But this time I also want to give a little overview of 2021 as a year.<br/>
  797. There was no November monthly report, due to me being busy with moving to a new place and a few other personal things.<br/>
  798. This month though there are a few things to report on.
  799. </p>
  800. <h3>DPF and VST3 work resumes</h3>
  801. <p>
  802. After a little break on the VST3 implementation in DPF, I went back and
  803. <a href="https://github.com/DISTRHO/DPF/commit/2d916332ff773db629ef9211ac3b3a8a5a428ea0" target="_blank">reworked a few things</a>
  804. that were clearly done wrong.<br/>
  805. It is still considered experimental, but already works much better than before.<br/>
  806. For example, UI to DSP parameter changes works properly now, which was not the case before in some hosts (including reaper).
  807. </p>
  808. <p>
  809. Once complete, DPF based plugins will be one of the few that implement the whole component vs edit-controller separation.<br/>
  810. This might prove quite valuable in the future, specially after hosts also implement the same.<br/>
  811. We need to come back to this after I natively implement VST3 support in Carla.
  812. </p>
  813. <p>
  814. Just as before, I am keeping a TODO list of items
  815. <a href="https://github.com/DISTRHO/DPF/blob/develop/distrho/src/DistrhoPluginVST3.cpp#L39" target="_blank">near the top of the relevant source code</a>
  816. file for VST3. The same also
  817. <a href="https://github.com/DISTRHO/DPF/blob/develop/distrho/src/DistrhoUIVST3.cpp#L24" target="_blank">applies to the UI side</a>.<br/>
  818. The super short summary is that most common things already work, with only optional buses, MIDI CC handling and minor details missing.<br/>
  819. We don't get VST3 support finalized in DPF during 2021, but it shouldn't take that much longer now.
  820. </p>
  821. <h3>Continuing: Separating JACK tools from JACK1 and JACK2</h3>
  822. <p>
  823. Mentioned last time was the effort of
  824. <a href="https://kx.studio/News/?action=view&url=kxstudio-monthly-report-october-2021" target="_blank">splitting the example-clients and tools</a>
  825. from the JACK repositories into a new repository/project.<br/>
  826. I have been working with David Runge on this (or better said,
  827. <a href="https://github.com/jackaudio/jack-example-tools/issues/9" target="_blank">he has been doing most of the work</a>)
  828. with me reviewing each set of changes to each file one by one.<br/>
  829. We are nearly finished, with only 1 file remaining.
  830. </p>
  831. <p>
  832. Afterwards there is still some work to be done on the build setup and testing the whole thing,
  833. but it is good to see things progressing on this area that was being sadly neglected for many years.<br/>
  834. If everything goes well, no one will notice a thing!<br/>
  835. Maintenance is a lot of work that goes unnoticed, fun stuff..
  836. </p>
  837. <h3>Python 3.10 and updated PyQt woes</h3>
  838. <p>
  839. I do not know exactly the change that triggered it, but with newer versions of python and PyQt, pretty much all my tools that use PyQt are broken.<br/>
  840. The community was quite helpful on
  841. <a href="https://github.com/falkTX/Carla/pull/1550" target="_blank">fixing some Carla</a>
  842. <a href="https://github.com/falkTX/Carla/pull/1551" target="_blank">issues themselves</a>
  843. without my direct intervention (as I do not run a rolling-release Linux distribution, I am not directly affected).<br/>
  844. With this a new release of Carla is needed, the same for Cadence but that remains unfixed for the time being.
  845. </p>
  846. <h3>Cardinal, the Rack!</h3>
  847. <p>
  848. A new project has been
  849. <a href="https://github.com/DISTRHO/Cardinal/issues/1" target="_blank">brewing behind the scenes</a>
  850. for more or less 3 months now.<br/>
  851. It was not in my plans when 2021 started, specially since quite a few other things needed more attention..<br/>
  852. But this was one of these things that is just impossible to put down as an idea.<br/>
  853. In fact, lack of attention in Carla and JACK lately are due to this project, it is simply too exciting.
  854. </p>
  855. <p>
  856. The quick history of the project is that, after
  857. <a href="https://vcvrack.com/" target="_blank">VCV Rack</a>
  858. <a href="https://github.com/VCVRack/Rack/tree/v2" target="_blank"> v2 source code was made public</a>,
  859. I began wondering if that codebase could be used for building an open-source plugin
  860. (unlike the official product, which is closed-source and commercial).<br/>
  861. After finding out that VCV's official plugin would only support VST2 and still only the same 3 base architectures (Linux, macOS and Windows 64bit),
  862. also how the whole thing would supposedly work - loading modules from the library just like in the standalone -
  863. I was quite disappointed with the whole thing.<br/>
  864. Rack is something that always interested me, but I was put off from the (to put it mildly) abrasive attitude towards open-source ideas and Linux packaging.<br/>
  865. Running as standalone was also not that fun for me, I personally want to create synths and have those integrated in a DAW/sequencer workflow.
  866. </p>
  867. <p>
  868. There was a project called
  869. <a href="https://github.com/bsp2/VeeSeeVSTRack" target="_blank">VeeSeeVSTRack</a>
  870. that also attempted an open-source plugin version of Rack, but it had some serious drawbacks:
  871. </p>
  872. <ul>
  873. <li>Needs heavy changes to Rack source, which would have to be regularly maintained in order to keep up with upstream</li>
  874. <li>All included modules need to be patched a fair bit just to work with it</li>
  875. <li>Custom written plugin format support (so it only supported VST2)</li>
  876. <li>Custom written OS-level Window handling (only supporting Windows and Linux/X11)</li>
  877. </ul>
  878. <p>
  879. While the idea in general great, there was a not insignificant amount of work needed to maintain it.<br/>
  880. If attempting something like this, would be best to not make the same "mistakes", and think about the whole deal on the long term.<br/>
  881. With that in mind, the Cardinal project:
  882. </p>
  883. <ul>
  884. <li>Does not fork Rack's source code, instead it uses it as submodule, replacing only a few critical functions and files</li>
  885. <li>Besides internal modules, 3rd-party ones can be linked as-is with only changes to not use <i>osdialog</i> due to its event-blocking nature</li>
  886. <li>Relies on DPF for plugin format support, so we get JACK, LV2 and VST2 from the start, VST3 in progress</li>
  887. <li>Also relies on DPF for OS-level Window handling, so it works on macOS too (and eventually Haiku)</li>
  888. </ul>
  889. <p>
  890. Similar to VeeSeeVSTRack, Cardinal builds the entire module collection as part of one binary and uses the host audio thread to drive the engine.<br/>
  891. This means no online library access or external module loading, which is quite intentional.<br/>
  892. More information on the
  893. <a href="https://github.com/DISTRHO/Cardinal#why" target="_blank">"why" section of Cardinal's README</a>.
  894. </p>
  895. <p>
  896. The obvious question that might be in the air is what to make of the official Rack Pro plugin.<br/>
  897. To which I say - <b>if you enjoy Cardinal, go buy Rack Pro!</b><br/>
  898. Cardinal would not exist without VCV Rack, so it is for our best interest that Rack lives on for a long while.<br/>
  899. Also they serve different purposes:<br/>
  900. <b>Cardinal</b> is open-source modules only, all integrated into 1 binary.<br/>
  901. <b>Rack Pro</b> is just like the standalone with online library access, commercial modules etc. And obviously the official product too.<br/>
  902. The Cardinal project includes a
  903. <a href="https://github.com/DISTRHO/Cardinal/blob/main/doc/DIFFERENCES.md" target="_blank">table of differences between itself and Rack Pro</a>,
  904. in case you want to go deeper into technical details.
  905. </p>
  906. <p>
  907. Cardinal should be considered beta-state at the moment.<br/>
  908. While it already works quite well (except for a few known bugs as typical), there are a few missing pieces and license situation to sort out in detail.<br/>
  909. A lot of Rack module developers started coding because of it,
  910. so without fully understanding artwork and source code license implications quite a few of them just copied what others were doing.<br/>
  911. And this is the problem, Rack itself contains non-commercial and even non-derivatives clauses for its artwork.<br/>
  912. A lot of developers copied the non-commercial clause without thinking too much about it, which makes them quite tricky if not impossible to package in a Linux distribution.<br/>
  913. Before tagging v1.0, I want to sort out these details first, to ensure everything is done not only legally but also respectfully.<br/>
  914. Already started this on
  915. <a href="https://github.com/DISTRHO/Cardinal/blob/main/doc/LICENSES.md" target="_blank">this document</a>,
  916. which greatly helps in giving an overview of the used source code and artwork licenses.
  917. </p>
  918. <p>
  919. Before moving on, here's a screenshot, because everyone likes those. :)
  920. </p>
  921. <p>
  922. <img src="/screenshots/news/cardinal-2021-12.png" alt="cardinal"/>
  923. </p>
  924. <h3>Many other DPF additions</h3>
  925. <p>
  926. While working on Cardinal, DPF got a real stress-test for some of its features.<br/>
  927. Some were missing and needed to be added in order to make Cardinal work proper, some were found to be broken.<br/>
  928. In no particular order, these changes were made in DPF to accommodate for Cardinal:
  929. </p>
  930. <ul>
  931. <li>Add clipboard (copy &amp; paste) support</li>
  932. <li>Add cursor support</li>
  933. <li>Add file dialog save support (used to be only loading allowed)</li>
  934. <li>Add "desktop portal" DBus service support for providing native file browser dialogs on Linux</li>
  935. <li>Add APIs around finding the bundle path of the plugin</li>
  936. <li>Allow LTO (Link-Time-Optimization) build</li>
  937. <li>Auto-creating macOS VST2 bundle from build step, instead of needing to run a script</li>
  938. <li>Many fixes around file browser dialog support</li>
  939. <li>Many fixes around VST2 keyboard input (WIP)</li>
  940. </ul>
  941. <p>
  942. The only missing feature at the moment is drag&amp;drop support, but that needs an implementation on pugl's side first.<br/>
  943. Once that side is done, I already have a plugin in which to test it the functionality, so it should be pretty quick.
  944. </p>
  945. <p>&nbsp;</p>
  946. <p>
  947. And that is all for now.<br/>
  948. If you appreciate the kind of work I do, please
  949. <a href="https://kx.studio/Donations">consider a donation</a>.<br/>
  950. Thank you in advance for your support, happy holidays and a happy new year!<br/>
  951. </p>
  952. <hr/>
  953. <p>
  954. <span style="font-size: 20px">&gt; KXStudio Monthly Report (October 2021)</span><br/>
  955. On <i>2021-10-31</i> by<i> falkTX</i>
  956. </p>
  957. <p>
  958. Hello all, another one of those monthly reports about the KXStudio project is here.<br/>
  959. As you might have seen a few days ago we had
  960. <a href="https://kx.studio/News/?action=view&url=carla-241-has-been-released" target="_blank">v2.4.1 Carla release</a>.<br/>
  961. I was hoping to do a JACK2 release as well, but was busy with other things and did not have it ready on it. Next time then.
  962. </p>
  963. <h3>DPF + VST3 on pause</h3>
  964. <p>
  965. While VST3 support in DPF has advanced enough to load already in quite a few hosts,
  966. I got personally annoyed with it after finding out the way I did the UI/DSP separation is just completely wrong. :(<br/>
  967. Working with the internals of VST3 has been quite frustrating, so just taking a little break from it.<br/>
  968. Currently still going with the target of finalizing VST3 support in DPF (at least in beta-like status) by the end of the year.
  969. </p>
  970. <p>
  971. I want to say, dealing with VST3 internals has made me appreciate LV2 even more.<br/>
  972. VST3 has some good design choices and ideas, but parts of it are also just awful and nonsensical.<br/>
  973. Hopefully after the initial implementation is done we do not have to change it much.
  974. </p>
  975. <h3>ImGui rendering issues fixed</h3>
  976. <p>
  977. Last month I reported about
  978. <a href="https://github.com/ocornut/imgui" target="_blank">Dear ImGui</a>
  979. being integrated as a DPF widget, with only some high-dpi rendering issues remaining.<br/>
  980. Happy to report that this is finalized and tested to work on a couple of different configurations.<br/>
  981. I might do a quick plugin set from porting existing audio software to DPF, as a way to 100% verify ImGui in DPF.<br/>
  982. But for now Ildaeil (more on that below) has served as a nice test-case.
  983. </p>
  984. <h3>JSFX as plugin type in Carla</h3>
  985. <p>
  986. Jean Pierre Cimalando has started work on adding
  987. <a href="https://www.reaper.fm/sdk/js/js.php" target="_blank">JSFX "plugin"</a> support
  988. for Carla.<br/>
  989. JSFX has nothing to do with JavaScript, but rather it originally comes from REAPER's extended audio processing capabilities.<br/>
  990. They have defined a format for writing audio plugins that can be written and compiled on the fly.<br/>
  991. This work from Jean is not yet complete, but great progress has already been made.<br/>
  992. It is likely to end up on the next Carla release.
  993. </p>
  994. <h3>A little new test-project: Ildaeil</h3>
  995. <p>
  996. One crucial point for me accepting JSFX support in Carla was that it couldn't be limited to just Carla.<br/>
  997. But this support being added directly in Carla doesn't help with that.. or does it?
  998. </p>
  999. <p>
  1000. Announcing <b>Ildaeil</b>! (sorta.. read on)<br/>
  1001. In case you do not know,
  1002. <a href="https://www.zrythm.org/en/" target="_blank">Zrythm</a>
  1003. is using Carla as backend to deal with non-LV2 plugins.<br/>
  1004. Some of the things it uses were never properly tested in Carla or any other software, making it hard to fix bugs.<br/>
  1005. This combined with wanting JSFX on more hosts than just Carla and ImGui now fully working in DPF
  1006. has given me enough motivation to try out a new project that would just combine everything into one.<br/>
  1007. This project is called "Ildaeil".
  1008. </p>
  1009. <p>
  1010. <a href="https://github.com/DISTRHO/Ildaeil" target="_blank">Ildaeil</a>
  1011. is basically Carla as a minified plugin, where instead of running the full GUI you have a super minimal GUI and set of features.<br/>
  1012. It uses DPF for the plugin-side (that is, to be an LV2, VST2 and VST3 plugin) and then Carla for the plugin hosting side.
  1013. A bridge between the 2 worlds, basically.<br/>
  1014. For now I made it so that it lists the available LV2 plugins on the system and allows to load 1 from the list, embedding its custom GUI if possible.
  1015. </p>
  1016. <p>
  1017. <img src="/screenshots/news/ildaeil-2021-10.png" alt="ildaeil"/>
  1018. </p>
  1019. <p>
  1020. This is not really an announcement because I have not yet decided the full scope of the project.<br/>
  1021. There are a LOT of things it could do, but then it becomes quite the work to maintain.<br/>
  1022. If you want to give it a try, feel free. But reports are welcome, feature requests are not (at this point).
  1023. </p>
  1024. <h3>Separating JACK tools from JACK1 and JACK2</h3>
  1025. <p>
  1026. For a very long time I have been meaning to merge back the changes done in JACK examples and tools from JACK2 back to JACK1.<br/>
  1027. Back in
  1028. <a href="https://jackaudio.org/news/2020/10/15/jack2-v1915-release-and-current-status.html" target="_blank">JACK2 v1.9.15 release</a>
  1029. I stated that help on this would be appreciated, but not much has happened since then.<br/>
  1030. Now that PipeWire is slowly becoming a thing, this is becoming crucial.
  1031. </p>
  1032. <p>
  1033. For distributions like Arch that do not typically split packages (hypothetically) installing pipewire-jack would remove jack2 and replace it with PipeWire's version.<br/>
  1034. But the tools like <b>jack_connect</b>, <b>jack_wait</b>, etc are part of the jack2 package, not pipewire-jack.<br/>
  1035. Installing pipewire-jack would (hypothetically) remove these tools.<br/>
  1036. There are quite a few set ups out there that rely on them, so a solution is needed here.
  1037. </p>
  1038. <p>
  1039. David Runge has started the effort of
  1040. <a href="https://github.com/jackaudio/jack-example-tools" target="_blank">splitting these tools from the JACK repositories into a new one</a>.<br/>
  1041. The idea is that JACK will no longer ship with them, and they become an extra set of tools to install separately.<br/>
  1042. This allows to switch between JACK versions (JACK1, JACK2 or PipeWire) and keep the same exact set of tools.
  1043. </p>
  1044. <p>
  1045. We will need to have new JACK1 and JACK2 versions that remove these tools before the new project can be officially tagged and released.<br/>
  1046. More news on this soon.
  1047. </p>
  1048. <p>&nbsp;</p>
  1049. <p>
  1050. That is all for now.<br/>
  1051. There were a couple of other things done in DPF and a few other projects, but something I will cover in upcoming months.<br/>
  1052. If you appreciate the kind of work I do, please
  1053. <a href="https://kx.studio/Donations">consider a donation</a>.<br/>
  1054. Thank you in advance for your support, and stay safe out there!<br/>
  1055. </p>
  1056. <hr/>
  1057. <p>
  1058. <span style="font-size: 20px">&gt; Carla 2.4.1 has been released</span><br/>
  1059. On <i>2021-10-15</i> by<i> falkTX</i>
  1060. </p>
  1061. <p>
  1062. This is a bugfix for Carla version v2.4 series, bringing some improvements and fixing a few bugs.
  1063. </p>
  1064. <p>
  1065. <a href="https://kx.studio/carla" class="external free" rel="nofollow" target="_blank">Carla</a>
  1066. is an audio plugin host, with support for many audio drivers and plugin formats.<br/>
  1067. It has some nice features like automation of parameters via MIDI CC (and send output back as MIDI too) and full OSC control.<br/>
  1068. </p>
  1069. <h3>Changelog</h3>
  1070. <ul>
  1071. <li>Better handling of VST3 parameters (hide as needed, number of steps, etc)</li>
  1072. <li>Fix compatibility with Python 3.10</li>
  1073. <li>Fix getting the proper X11 UIs size for more plugins</li>
  1074. <li>Fix plugin bridges not automatically closing if main Carla dies on macOS (similar to how it is done on Linux)</li>
  1075. <li>Fix unused parameters preventing real ones from showing up in the edit plugin dialog</li>
  1076. <li>Fix CarlaNativePlugin.h and CarlaPluginPtr.hpp header files not installed system-wide</li>
  1077. <li>Fix XY-Controller GUI missing on "make install" target</li>
  1078. <li>Fix VST2 plugins under macOS and High-DPI (by not reporting scale factor)</li>
  1079. <li>Replace -lpthread usage with -pthread, fixing RISC-V builds</li>
  1080. <li>Send keyboard and focus events as needed/possible to VST2 and VST3 UIs</li>
  1081. <li>Small tweaks to XY-Controller (make lines 1px thick, close UI with Esc key)</li>
  1082. <li>Special tweaks for static plugin target build (embeding carla statically in other applications/plugins)</li>
  1083. <li>Other minor fixes and tweaks</li>
  1084. </ul>
  1085. <h3>Downloads</h3>
  1086. <p>
  1087. To download Carla binaries or source code, jump on over to the <a href="https://kx.studio/Downloads" class="external free" rel="nofollow" target="_blank">KXStudio downloads section</a>.<br/>
  1088. If you're using the KXStudio repositories, you can simply install "carla".<br/>
  1089. Bug reports and feature requests are welcome! Jump on over to the <a href="https://github.com/falkTX/Carla" class="external free" rel="nofollow" target="_blank">Carla's Github project</a> page for those.
  1090. </p>
  1091. <h3>Notes for users</h3>
  1092. <p>
  1093. This was already the case for v2.2 and v2.3 but it is worth reiterating:<br/>
  1094. When using JACK2, the canvas - plugin integrations requires at least JACK2 v1.9.13.<br/>
  1095. This is because Carla relies on JACK meta-data in order to store information about each plugin/client,
  1096. and meta-data was only added to JACK2 in version 1.9.13.<br/>
  1097. Alternatively, you can use JACK1 instead of JACK2, which has meta-data support since a long time.<br/>
  1098. Note that the <a href="/Repositories:Extras">"extras" KXStudio repository</a> (which provides an updated JACK2) supports both Ubuntu 18.04 and 20.04.<br/>
  1099. The UbuntuStudio backports PPA also provides updated JACK2 packages.
  1100. </p>
  1101. <p>
  1102. There are no official Linux binary builds for v2.4.1 at this point.<br/>
  1103. Carla v2.4.1 is provided in the KXStudio repositories and in many official Linux distribution repositories too anyway.
  1104. </p>
  1105. <hr/>
  1106. <p>
  1107. <span style="font-size: 20px">&gt; KXStudio Monthly Report (September 2021)</span><br/>
  1108. On <i>2021-09-30</i> by<i> falkTX</i>
  1109. </p>
  1110. <p>
  1111. Hello all, it is time for yet another one of those monthly reports about the KXStudio project.<br/>
  1112. In case you missed it last month, there are now dedicated
  1113. <a href="https://kx.studio/Board" target="_blank">KXStudio Board</a>
  1114. and
  1115. <a href="https://kx.studio/Development" target="_blank">KXStudio Development</a>
  1116. pages.<br/>
  1117. These serve to give a quick overview of the work being planned and the one actively being done.<br/>
  1118. Note that I typically remove stuff from the "done" column of the board a few days into the start of each month.
  1119. </p>
  1120. <h3>VST3 for DPF</h3>
  1121. <p>
  1122. The first new thing worth mentioning is the substantial work for VST3 in
  1123. <a target="_blank" href="https://github.com/DISTRHO/DPF">DPF</a>
  1124. made this month.<br/>
  1125. Though it is still in a state I consider alpha at the moment, everything that is crucial is implemented:
  1126. from audio, midi, time position, parameters, programs, state, latency and gui.<br/>
  1127. Not recommended to release anything based on this yet, as there are memory leaks and the GUI only works on Linux at the moment (and known to break REAPER due to not plugging into the host runloop yet).
  1128. </p>
  1129. <p>
  1130. This VST3 implementation uses
  1131. <a target="_blank" href="https://github.com/DISTRHO/DPF/tree/develop/distrho/src/travesty">custom C-compatible API headers</a>
  1132. instead of the official SDK, so that we can have commercial plugins while not being tied to Steinberg and its restrictive licensing.<br/>
  1133. There is a lot of boilerplate code to implement for stuff that the SDK typically does for you, and it is still pretty unclean, but works for now for testing.
  1134. </p>
  1135. <p>
  1136. Worth noting that there is a clear DSP / UI separation for this VST3-compatible DPF implementation.<br/>
  1137. Instead of the UI having direct access to the DSP side and just calling functions, everything is passed through a VST3 "connection point" as messages.<br/>
  1138. There is something in place to support hosts that do not provide the "connection point" interfaces, so everything still works there too.
  1139. </p>
  1140. <p>
  1141. I expect to finalize the VST3 support already in October as there does not seem to be any technical limitation or blocker,
  1142. it is just time needed to implement all the things.<br/>
  1143. Sadly VST3 only officially specifies support for Linux, macOS and Windows.<br/>
  1144. DPF can build for more systems than just these 3, so I
  1145. <a target="_blank" href="https://github.com/steinbergmedia/vst3sdk/issues/86">made a question/request upstream</a>
  1146. for how to tackle the issue.
  1147. </p>
  1148. <h3>Other DPF updates</h3>
  1149. <p>
  1150. In other DPF news, I began experimenting with supporting
  1151. <a target="_blank" href="https://github.com/ocornut/imgui">Dear ImGui</a>
  1152. as a widget implementation.<br/>
  1153. Everything already works except drawing on the correct position with high-dpi, there are some weird quirks to figure out in regards to the OpenGL viewport.<br/>
  1154. The target is to allow to use ImGui for the full plugin gui or just as a subwidget.
  1155. </p>
  1156. <p>
  1157. <img src="/screenshots/news/imgui-widgets-2021-09.png" alt="imgui-widgets"/>
  1158. </p>
  1159. <p>
  1160. Other worthy mentions on DPF world are the
  1161. <a target="_blank" href="https://github.com/DISTRHO/DPF/blob/develop/FEATURES.md">FEATURES</a>
  1162. and
  1163. <a target="_blank" href="https://github.com/DISTRHO/DPF/blob/develop/LICENSING.md">LICENSING</a>
  1164. table, which should help people decide if DPF is worthy for them or not.<br/>
  1165. As you might know, DPF is liberally licensed (under ISC) so that it can be used for commercial plugins without restrictions.<br/>
  1166. Hopefully clearing the license situation helps on that side of things.
  1167. </p>
  1168. <p>&nbsp;</p>
  1169. <p>
  1170. That is all for now.<br/>
  1171. There are some bug-fix releases planned, but that will be something for October.<br/>
  1172. If you appreciate the kind of work I do, please
  1173. <a href="https://kx.studio/Donations">consider a donation</a>.<br/>
  1174. Thank you in advance for your support, and stay safe out there!<br/>
  1175. </p>
  1176. <hr/>
  1177. <p>
  1178. <span style="font-size: 20px">&gt; KXStudio Monthly Report (August 2021)</span><br/>
  1179. On <i>2021-08-31</i> by<i> falkTX</i>
  1180. </p>
  1181. <p>
  1182. Hello all, another one of those monthly reports about the KXStudio project is here.<br/>
  1183. This month as you might have seen we had
  1184. <a href="https://kx.studio/News/?action=view&url=carla-232-has-been-released" target="_blank">not one</a>
  1185. but
  1186. <a href="https://kx.studio/News/?action=view&url=carla-plugin-host-v240-is-here" target="_blank">two Carla releases</a>.<br/>
  1187. Mostly bugfixes as expected, the new stuff was all very minor compared to past releases.<br/>
  1188. A few additonal things were added/fixed in Carla already since then, but all still very minor.<br/>
  1189. Whatever is ready by next release day (October 15) will be what gets in next, just to get a nice pace of releases going.
  1190. </p>
  1191. <h3>More (final?) DPF updates</h3>
  1192. <p>
  1193. DPF got a lot of attention once again.<br/>
  1194. It is now on a state where I can focus on bugfixes rather than new things,
  1195. even though I still want to try official SVG support.<br/>
  1196. Everything that was in the previous DPF (that is, the git
  1197. <a href="https://github.com/DISTRHO/DPF/tree/master/" target="_blank">master branch</a>)
  1198. should now be in the develop branch.<br/>
  1199. I am confident enough in this that made a new
  1200. <a href="https://github.com/DISTRHO/DPF/tree/main" target="_blank">"main" branch</a>
  1201. to be the default clone target (I will keep the old master branch untouched, as there are a few minor things that can't be made backwards compatible).
  1202. </p>
  1203. <h4>Fixing high-dpi support</h4>
  1204. <p>
  1205. Something that got a fair bit of attention was high-dpi support.<br/>
  1206. Previously DPF read the scale factor from the host (if provided, most do not) but now it can also figure it out on its own as fallback.<br/>
  1207. There was a lot of
  1208. <a href="https://github.com/DISTRHO/DPF/pull/301" target="_blank">back and forth</a>
  1209. until
  1210. <a href="https://github.com/DISTRHO/DPF/issues/308" target="_blank">it was verified</a>
  1211. to
  1212. <a href="https://github.com/DISTRHO/DPF/issues/311" target="_blank">work on all major OSes and formats</a>.<br/>
  1213. I also updated the DPF-Plugins project so that all plugins contained within it support this.<br/>
  1214. Even though some being bitmap-based causes their UI to look blurry, at least they will appear in the correct size.<br/>
  1215. You can see them in the screenshot below.
  1216. </p>
  1217. <p>
  1218. <img src="/screenshots/news/dpf-plugins-big-2021-08.png" alt="dpf-plugins-big"/>
  1219. </p>
  1220. <h4>sofd improvements</h4>
  1221. <p>
  1222. Some care was given to the
  1223. <a href="https://github.com/x42/sofd/" target="_blank">sofd module</a>
  1224. used by DPF as fallback X11 file browser dialog.<br/>
  1225. It serves us well enough because it generally works fine, but never looked that great in my opinion..<br/>
  1226. I spent some time to change its colors a bit to follow a more traditional/usual approach, plus a dark theme because yes.<br/>
  1227. And then on top make it work nicely for high-dpi setups too.<br/>
  1228. Not everyone uses dark themes, so there needs to be a light theme option too, not sure yet if it can be chosen automatically.<br/>
  1229. Personally I think it looks much better, but tastes are subjective. Anyway, the differences can be seen below:<br/>
  1230. (will submit the changes upstream after all the DPF file dialog stuff is finalized and stable)
  1231. </p>
  1232. <p>
  1233. <img src="/screenshots/news/sofd-compare-2021-08.png" alt="sofd-compare"/>
  1234. </p>
  1235. <h4>External UI</h4>
  1236. <p>
  1237. As a final thing to mention for DPF, the last item that needed attention before the rework being in feature-parity with old branch, is external UI support.<br/>
  1238. The idea being that we can reuse DPF APIs and plugin export support but do the UI stuff completely separately - be it separate process or a custom implementation.<br/>
  1239. As long as it is in a way the plugin host expects things (ie, X11 window on Linux) things should just work..
  1240. </p>
  1241. <p>
  1242. The old DPF master branch didn't support this fully, but there was some experimental stuff in place.<br/>
  1243. Now it is back again, with a little
  1244. <a href="https://github.com/DISTRHO/DPF/blob/main/distrho/extra/ExternalWindow.hpp#L37" target="_blank">more documentation</a>
  1245. and better support - it should eventually be an official DPF feature.<br/>
  1246. You can follow its discussion and progress
  1247. <a href="https://github.com/DISTRHO/DPF/issues/313" target="_blank">here</a>
  1248. and because everyone likes screenshots, here is one as a quick test of mpv running as the external UI:
  1249. </p>
  1250. <p>
  1251. <img src="/screenshots/news/external-ui-mpv-2021-08.png" alt="external-ui-mpv"/>
  1252. </p>
  1253. <h3>ProM revived</h3>
  1254. <p>
  1255. One little plugin I made quite some years ago but left it aside due to difficulties in packaging was
  1256. <a href="https://github.com/DISTRHO/ProM/" target="_blank">ProM</a>.<br/>
  1257. ProM is basically
  1258. <a href="https://github.com/projectM-visualizer/projectm/" target="_blank">projectM</a>
  1259. in plugin form, on top of DPF.<br/>
  1260. It allows you to have old-school milkdrop-like visualizations on your DAW/host, it is an audio plugin after all.<br/>
  1261. After a little fighting over building projectM correctly (directly in ProM source, aka "vendored"),
  1262. I can now say it builds and runs on at least GNU/Linux, macOS and Windows.<br/>
  1263. Taking from
  1264. <a href="https://kx.studio/News/?action=view&url=kxstudio-monthly-report-july-2021" target="_blank">last month's automatic build setup</a>,
  1265. binaries are
  1266. <a href="https://github.com/DISTRHO/ProM/actions" target="_blank">automatically generated for these 3 OSes directly from GitHub</a>.<br/>
  1267. To make Linux distribution packagers happy, the option to build against system-provided libprojectM is still present,
  1268. and should work even better now as it finds the shared data prefix to use via pkg-config.
  1269. </p>
  1270. <p>
  1271. <img src="/screenshots/news/prom-revival-2021-08.png" alt="prom-revival"/>
  1272. </p>
  1273. <h3>Website updates</h3>
  1274. <p>
  1275. Worth of a little note, I updated the kx.studio website to better work in smaller screens, or vertical ones, or both like in mobile phones.<br/>
  1276. The content itself is mostly unchanged, still need to tackle that (specially documentation, there is a lot of old stuff there).<br/>
  1277. They typically call this "responsive design" I guess.<br/>
  1278. The news part I didn't update, as otherwise it would break RSS readers, and the top menu needs to become of one those "hamburguer"-style things when width is low. A task for later.
  1279. </p>
  1280. <p>
  1281. A final website update worth mentioning is the addition of the
  1282. <a href="https://kx.studio/Board" target="_blank">board</a>
  1283. and
  1284. <a href="https://kx.studio/Development" target="_blank">development</a>
  1285. pages.<br/>
  1286. As people sometimes wonder what I have been doing lately (specially important for those that give out donations, thanks for that by the way!)
  1287. the board view is now integrated into the site. I added color descriptions there too.<br/>
  1288. Hopefully that makes everything more clear, and more visible too of course.
  1289. </p>
  1290. <p>&nbsp;</p>
  1291. <p>
  1292. That is all for now.<br/>
  1293. If you appreciate the kind of work I do, please
  1294. <a href="https://kx.studio/Donations">consider a donation</a>.<br/>
  1295. Thank you in advance for your support, and stay safe out there!<br/>
  1296. </p>
  1297. <hr/>
  1298. <p>
  1299. <span style="font-size: 20px">&gt; Carla Plugin Host v2.4.0 is here</span><br/>
  1300. On <i>2021-08-20</i> by<i> falkTX</i>
  1301. </p>
  1302. <p>
  1303. Hello everyone, this is the announcement of the 2.4.0 version of the Carla Plugin Host.<br/>
  1304. If you do not know, Carla is a fully-featured cross-platform audio plugin host, which can also run as a plugin.
  1305. </p>
  1306. <p>
  1307. This release was initially meant to be 2.3.3 but there are some small new features so treating it as bugfix would be misleading.<br/>
  1308. Semantically-speaking, new stuff means new version, so 2.4 it is.<br/>
  1309. I was going to wait a bit more until a release, but it is Ubuntu feature freeze time, so got to go with what is available now in order to make it.<br/>
  1310. Anyway, let's go through the (small) release highlights.
  1311. </p>
  1312. <table><tr><td width="40%">
  1313. <a href="/screenshots/news/carla-2.4_classic-skin.png">
  1314. <img src="/screenshots/news/carla-2.4_classic-skin.png" style="max-width:100%;height:auto;" alt="audiofile"/>
  1315. </a>
  1316. </td><td width="60%">
  1317. <h3>Option to use classic skin by default</h3>
  1318. <p>
  1319. Who doesn't like a little bit of nostalgia?<br/>
  1320. Reminiscent of its v1.x days, the "classic" rack skin can now be made into the default.<br/>
  1321. So now you can be on latest Carla with all the new stuff, but still feel retro. :D
  1322. </p>
  1323. <p>
  1324. The dry/wet and volume controls are only accessible through the built-in plugin edit dialog,<br/>
  1325. but in return the whole rack takes less screen space.
  1326. </p>
  1327. </td></tr></table>
  1328. <br/>
  1329. <table><tr><td width="40%">
  1330. <a href="/screenshots/news/carla-2.4_lv2-gtk-windows.png">
  1331. <img src="/screenshots/news/carla-2.4_lv2-gtk-windows.png" style="max-width:100%;height:auto;" alt="lv2-gtk-windows"/>
  1332. </a>
  1333. </td><td width="60%">
  1334. <h3>LV2 Gtk UIs on any system</h3>
  1335. <p>
  1336. After some changes on how Carla handles its Gtk UI bridges, it is now possible to build and use them on any system.<br/>
  1337. Behind the scenes instead of directly linking against Gtk libraries,
  1338. the Carla Gtk UI bridge will open the Gtk library/DLL to find the needed symbols in order to get a working Gtk setup.<br/>
  1339. This doesn't change the behaviour on Linux, but allows to use Gtk-based UIs on systems like Windows and macOS.<br/>
  1340. Its usefulness is a bit questionable, my main reason to change this was to be able to adapt to new Gtk versions more easily, but it has nice side effects.
  1341. </p>
  1342. <p>
  1343. Currently there are no LV2 plugins released on macOS or Windows that make use of such a UI, but could change soon via
  1344. <a href="https://github.com/DISTRHO/PawPaw" target="_blank">PawPaw</a>.<br/>
  1345. I have been doing some tests and at least amsynth and Invada are possible to get working with their full UIs.<br/>
  1346. Later on I will see if and how it could be possible to package such plugins with their UIs.
  1347. </p>
  1348. </td></tr></table>
  1349. <br/>
  1350. <h3>Full changelog</h3>
  1351. <ul>
  1352. <li>Add option to use classic skin by default</li>
  1353. <li>Add support for lv2 ui gtk bridges on any system</li>
  1354. <li>Set display scale factor for carla-bridge-*/carla-single standalone usage (on macOS and X11 systems)</li>
  1355. <li>Fix Linux VST3 plugin GUIs crash on close</li>
  1356. <li>Fix build under msys2 (will not force static binaries)</li>
  1357. <li>Fix keyboard focus for bridges on macOS (2nd attempt)</li>
  1358. <li>Fix canvas icon in settings to be high-dpi compatible</li>
  1359. <li>Fix wrong scale factor of plugin GUIs under macOS</li>
  1360. </ul>
  1361. <h3>Downloads</h3>
  1362. <p>
  1363. To download Carla binaries or source code, jump on over to the <a href="https://kx.studio/Downloads" class="external free" rel="nofollow" target="_blank">KXStudio downloads section</a>.<br/>
  1364. If you're using the KXStudio repositories, you can simply install "carla".<br/>
  1365. Bug reports and feature requests are welcome! Jump on over to the <a href="https://github.com/falkTX/Carla" class="external free" rel="nofollow" target="_blank">Carla's Github project</a> page for those.
  1366. </p>
  1367. <h3>Notes for users</h3>
  1368. <p>
  1369. This was already the case for v2.2 and v2.3 but it is worth reiterating:<br/>
  1370. When using JACK2, the canvas - plugin integrations requires at least JACK2 v1.9.13.<br/>
  1371. This is because Carla relies on JACK meta-data in order to store information about each plugin/client,
  1372. and meta-data was only added to JACK2 in version 1.9.13.<br/>
  1373. Alternatively, you can use JACK1 instead of JACK2, which has meta-data support since a long time.<br/>
  1374. Note that the <a href="/Repositories:Extras">"extras" KXStudio repository</a> (which provides an updated JACK2) supports both Ubuntu 18.04 and 20.04.<br/>
  1375. The UbuntuStudio backports PPA also provides updated JACK2 packages.
  1376. </p>
  1377. <p>
  1378. There are no official Linux binary builds for v2.4 at this point.<br/>
  1379. Carla v2.4 is provided in the KXStudio repositories and in many official Linux distribution repositories too anyway.
  1380. </p>
  1381. &nbsp;
  1382. <p>
  1383. As always, if you appreciate the kind of work I do, please
  1384. <a href="https://kx.studio/Donations">consider a donation</a>.<br/>
  1385. Thank you in advance for your support, and stay safe out there!<br/>
  1386. </p>
  1387. <hr/>
  1388. <p>
  1389. <span style="font-size: 20px">&gt; Carla 2.3.2 has been released</span><br/>
  1390. On <i>2021-08-08</i> by<i> falkTX</i>
  1391. </p>
  1392. <p>
  1393. This is a bugfix for Carla version v2.3 series, mostly fixing a few regressions with the previous release.
  1394. </p>
  1395. <h3>Changelog</h3>
  1396. <ul>
  1397. <li>Add 32x32 icon</li>
  1398. <li>Do not show --gdb in usage/help when not installed system-wide</li>
  1399. <li>Fix default SF2 search path</li>
  1400. <li>Fix keyboard focus for bridges on macOS</li>
  1401. <li>Fix X11-UIs related regressions in v2.3.1</li>
  1402. </ul>
  1403. <h3>Downloads</h3>
  1404. <p>
  1405. To download Carla binaries or source code, jump on over to the <a href="https://kx.studio/Downloads" class="external free" rel="nofollow" target="_blank">KXStudio downloads section</a>.<br/>
  1406. If you're using the KXStudio repositories, you can simply install "carla".<br/>
  1407. Bug reports and feature requests are welcome! Jump on over to the <a href="https://github.com/falkTX/Carla" class="external free" rel="nofollow" target="_blank">Carla's Github project</a> page for those.
  1408. </p>
  1409. &nbsp;
  1410. <p>
  1411. As always, if you appreciate the kind of work I do, please
  1412. <a href="https://kx.studio/Donations">consider a donation</a>.<br/>
  1413. Thank you in advance for your support, and stay safe out there!<br/>
  1414. </p>
  1415. <hr/>
  1416. <p>
  1417. <span style="font-size: 20px">&gt; KXStudio Monthly Report (July 2021)</span><br/>
  1418. On <i>2021-07-31</i> by<i> falkTX</i>
  1419. </p>
  1420. <p>
  1421. Hello all, another monthly report about the KXStudio project is here.<br/>
  1422. First, in case you missed it,
  1423. <a href="https://kx.studio/News/?action=view&url=carla-231-has-been-released" target="_blank">Carla v2.3.1</a>
  1424. and
  1425. <a href="https://jackaudio.org/news/2021/07/16/jack2-v1919-release.html" target="_blank">JACK2 v1.9.19</a>
  1426. have been released.<br/>
  1427. A few issues were reported against this latest Carla release (regressions) so expect a v2.3.2 very soon.<br/>
  1428. Due to travis-ci.org shutting down (and the replacement travis-ci.com being absolutely terrible) the binaries for these releases were not automated.<br/>
  1429. Which brings me to this month's first topic.
  1430. </p>
  1431. <h3>Automated builds &amp; artifacts</h3>
  1432. <p>
  1433. Since travis became unusable, and manually doing builds everytime is a bit of a pain, I began looking for alternatives.<br/>
  1434. GitHub Actions seems to be what most developers have run to, but I am not really happy putting yet more stuff into GitHub.<br/>
  1435. While there are some alternatives, even self-hosting, in the end being pragmatic I threw the towel and just let GitHub handle it.<br/>
  1436. For projects that already have a presence on GitHub, the integration just makes sense.
  1437. </p>
  1438. <p>
  1439. One of the issues with travis was the lack of daily/latest build binaries.<br/>
  1440. While it was possible to setup, it usually required creating a tag or release to upload the binaries into.<br/>
  1441. GitHub Actions can have "artifacts" associated with any build, with no special setup required from contributors.<br/>
  1442. This was the main thing that pushed me to just stick with GitHub for this.<br/>
  1443. If someone external to a project submits a pull-request, there will be automated builds with the proposed changes ready for testing.<br/>
  1444. The fact that builds start immediately (instead of sometimes having to wait several hours like in other services) is super nice to see.
  1445. </p>
  1446. <p>
  1447. But are there any benefits to users, you may ask.<br/>
  1448. Well, take for the example JACK, for which I already added automated builds.<br/>
  1449. If you open the
  1450. <a href="https://github.com/jackaudio/jack2/actions" target="_blank">JACK2 GitHub Actions</a>
  1451. page, there will be macOS and Windows installers for each build going forwards.<br/>
  1452. When there comes a time where a change requires testing, there is no longer a need to build things manually.
  1453. </p>
  1454. <p>
  1455. Automated builds via GitHub Actions (and the resulting artifacts) also fit nicely for DPF.<br/>
  1456. I was able to create a "workflow" file (that is, a file that describes what to build and how) for DPF-based plugins,
  1457. where it builds and publishes linux-armhf, linux-arm64, linux-x64, macOS (universal), win32 and win64 binaries,
  1458. all in a single file.<br/>
  1459. So you can basically take
  1460. <a href="https://github.com/DISTRHO/DPF-Plugins/blob/master/.github/workflows/build.yml" target="_blank">
  1461. this file</a>,
  1462. place it in your own repository, and directly have all those linux, macOS and windows builds right away.<br/>
  1463. I already have this setup for pretty all of DPF-based plugins under the
  1464. <a href="https://github.com/DISTRHO/" target="_blank">DISTRHO GitHub organization</a>.<br/>
  1465. As an experiment, I
  1466. <a href="https://github.com/michaelwillis/dragonfly-reverb/pull/106" target="_blank">added the same support to dragonfly-reverb project</a>.<br/>
  1467. So now if you go to its
  1468. <a href="https://github.com/michaelwillis/dragonfly-reverb/actions" target="_blank">GitHub Actions</a>
  1469. page and click on the latest commit, you will be able to download and install/use the build artifacts.
  1470. </p>
  1471. <p>
  1472. This is extremely valuable, as not everyone has a macOS or Windows machine in order to do builds for those.<br/>
  1473. Or maybe the other way around, someone on macOS or Windows without a Linux machine, etc etc.<br/>
  1474. I also think of the situation of people wanting to try out a change in the code but don't have the developer tools needed to build the project themselves.<br/>
  1475. While maybe not a big issue for DPF/Plugin projects (as they tend to be small in size),
  1476. for things like Carla where build dependencies are a lot more involved, almost no one will have everything needed to make binaries alike the official ones.<br/>
  1477. With these automated builds, you can basically create a pull request and just enjoy the build - which will follow the same exact conventions as official builds.
  1478. </p>
  1479. <p>
  1480. Now, this is not in place for Carla just yet, but it is in progress.<br/>
  1481. Currently DPF (plus the plugins made with them under DISTRHO) and JACK2 have automated builds via GitHub Actions.<br/>
  1482. More will follow soon.
  1483. </p>
  1484. <h3>Packaging</h3>
  1485. <p>
  1486. There are no updates regarding packages in the KXStudio repositories at this time.<br/>
  1487. Even though some packaged plugins are out-of-date, yes..<br/>
  1488. </p>
  1489. <p>
  1490. Thinking of packages, I might just do a whole month focused on them soon.<br/>
  1491. There has been quite some nice releases of open-source audio plugins lately that would be great to have packaged,
  1492. but lack of proper time for them is a problem.<br/>
  1493. As the last details on DPF new release are being resolved, packaging might be the next thing to focus on.
  1494. </p>
  1495. <p>
  1496. Special attention is needed on JUCE things though, because the LV2 wrapper is still somewhat of a pain for external developers to integrate properly.<br/>
  1497. (If only JUCE devs made the LV2 wrapper official! errr...)
  1498. </p>
  1499. <p>
  1500. Anyway, this packaging thing is not so much of news but more of wishes.<br/>
  1501. Before new JUCE-based plugins get packaged, I want to sort out the LV2 wrapper mess, make it as easy as possible for developers to have official LV2 variants.<br/>
  1502. Only me building LV2 versions (for the KXStudio repositories) is not something I want to push for anymore,
  1503. rather it would be best for everyone to have said LV2 versions.
  1504. </p>
  1505. <p>&nbsp;</p>
  1506. <p>
  1507. That is all for now.<br/>
  1508. If you appreciate the kind of work I do, please
  1509. <a href="https://kx.studio/Donations">consider a donation</a>.<br/>
  1510. Thank you in advance for your support, and stay safe out there!<br/>
  1511. </p>
  1512. <hr/>
  1513. <p>
  1514. <span style="font-size: 20px">&gt; Carla 2.3.1 has been released</span><br/>
  1515. On <i>2021-07-16</i> by<i> falkTX</i>
  1516. </p>
  1517. <p>
  1518. This is a bugfix for Carla version v2.3 series, fixing many bug reports and stuff I found along the way.
  1519. </p>
  1520. <p>
  1521. Carla is an audio plugin host, with support for many audio drivers and plugin formats.<br/>
  1522. It has some nice features like automation of parameters via MIDI CC (and send output back as MIDI too) and full OSC control.<br/>
  1523. </p>
  1524. <h3>Changelog</h3>
  1525. <ul>
  1526. <li>Add NSLocalNetworkUsageDescription and NSMicrophoneUsageDescription in macOS builds</li>
  1527. <li>Allow canvas eyecandy for Qt >= 5.12</li>
  1528. <li>Alternative approach to deal with JACK postponed events (improves PipeWire usage)</li>
  1529. <li>Implement parameter groups for VST2 plugins</li>
  1530. <li>Ignore hosts calling Carla-VST effOpen twice (don't print errors)</li>
  1531. <li>Listen to Windows and X11 plugin UI resize events (without extensions)</li>
  1532. <li>Make some macOS dialogs modal</li>
  1533. <li>Remove favorite plugins from list when they fail to load</li>
  1534. <li>Update JUCE plugin code to new APIs, hook into VST2 for feature parity with native implementation</li>
  1535. <li>Use new tick_double for JACK transport</li>
  1536. <li>Use posix_spawn to launch macOS bridges</li>
  1537. <li>Fix available decimal points on a few dialogs being incorrect</li>
  1538. <li>Fix bridged plugin UIs appearing behind main carla window on macOS</li>
  1539. <li>Fix canvas auto-refreshing on exit, potentially leading to crash</li>
  1540. <li>Fix canvas split/join action</li>
  1541. <li>Fix carla-vst-wine symbol visibility</li>
  1542. <li>Fix default rack "skin" for a few plugins</li>
  1543. <li>Fix initial size for LV2 UIs with no UI resize extension (all OSes)</li>
  1544. <li>Fix loading state of Windows/macOS VST2 plugins without chunk</li>
  1545. <li>Fix macOS binaries not being debug/symbol stripped</li>
  1546. <li>Fix midi-pattern plugin having double notes on transport reposition</li>
  1547. <li>Fix race condition (and potential crash) around postponed RT events</li>
  1548. <li>Fix Qt >= 5.10 version checks</li>
  1549. <li>Fix unused JACK latency callbacks (removed)</li>
  1550. <li>Fix X11 UIs not having keyboard focus</li>
  1551. </ul>
  1552. <h3>Downloads</h3>
  1553. <p>
  1554. To download Carla binaries or source code, jump on over to the <a href="https://kx.studio/Downloads" class="external free" rel="nofollow" target="_blank">KXStudio downloads section</a>.<br/>
  1555. If you're using the KXStudio repositories, you can simply install "carla".<br/>
  1556. Bug reports and feature requests are welcome! Jump on over to the <a href="https://github.com/falkTX/Carla" class="external free" rel="nofollow" target="_blank">Carla's Github project</a> page for those.
  1557. </p>
  1558. <h3>Notes for users</h3>
  1559. <p>
  1560. This was already the case for v2.2 and v2.3 but it is worth reiterating:<br/>
  1561. When using JACK2, the canvas - plugin integrations requires at least JACK2 v1.9.13.<br/>
  1562. This is because Carla relies on JACK meta-data in order to store information about each plugin/client,
  1563. and meta-data was only added to JACK2 in version 1.9.13.<br/>
  1564. Alternatively, you can use JACK1 instead of JACK2, which has meta-data support since a long time.<br/>
  1565. Note that the <a href="/Repositories:Extras">"extras" KXStudio repository</a> (which provides an updated JACK2) supports both Ubuntu 18.04 and 20.04.<br/>
  1566. The UbuntuStudio backports PPA also provides updated JACK2 packages.
  1567. </p>
  1568. <p>
  1569. There are no official Linux binary builds for v2.3.1 at this point.<br/>
  1570. Carla v2.3.1 is provided in the KXStudio repositories and in many official Linux distribution repositories too anyway.
  1571. </p>
  1572. <hr/>
  1573. <p>
  1574. <span style="font-size: 20px">&gt; Changes in the extra KXStudio repositories regarding JACK2</span><br/>
  1575. On <i>2021-07-05</i> by<i> falkTX</i>
  1576. </p>
  1577. <p>
  1578. This is a small notice to everyone using JACK2 with the extra KXStudio repositories.
  1579. (those for Ubuntu 18.04 and 20.04)
  1580. </p>
  1581. <p>
  1582. A change in the JACK2 code has made it so a restart of the server is required after the update.<br/>
  1583. The technical reason for this is an internal ABI change due to forced-alignment in a few struct/classes.<br/>
  1584. This change is required for some ARM platforms where non-aligned access results in a bus error.
  1585. </p>
  1586. <p>
  1587. If you use jackdbus (likely with KXStudio stuff), you will need to actually kill it. (or use the usual <b>cadence-session-start -s</b> command.<br/>
  1588. If that does not work, good old restart is your friend. :)
  1589. </p>
  1590. <p>
  1591. This small update brings JACK2 v1.9.19 early, as a way to get a little more testing before official release.<br/>
  1592. That said release is planned for April 15.
  1593. </p>
  1594. <hr/>
  1595. <p>
  1596. <span style="font-size: 20px">&gt; KXStudio Monthly Report (June 2021) and a Little Personal Note</span><br/>
  1597. On <i>2021-06-31</i> by<i> falkTX</i>
  1598. </p>
  1599. <p>
  1600. Hello all, another monthly report about the KXStudio project is here.<br/>
  1601. A bit late this time, but let's ignore that. :)<br/>
  1602. </p>
  1603. cadence-session-start -s
  1604. <p>
  1605. <span style="font-size: 20px">&gt; KXStudio Monthly Report (June 2021) and a Little Personal Note</span><br/>
  1606. On <i>2021-06-31</i> by<i> falkTX</i>
  1607. </p>
  1608. <p>
  1609. Hello all, another monthly report about the KXStudio project is here.<br/>
  1610. A bit late this time, but let's ignore that. :)<br/>
  1611. </p>
  1612. <h3>DPF updates</h3>
  1613. <p>
  1614. <a href="https://github.com/DISTRHO/DPF" target="_blank">
  1615. DPF
  1616. </a>
  1617. got most of the attention again.<br/>
  1618. Things are progressing, not as fast as I hoped, but there is progress.
  1619. (I really underestimated the amount of time DPF would take)<br/>
  1620. The main reason for the DPF attention and rework
  1621. - updating its
  1622. <a href="https://github.com/lv2/pugl" target="_blank">pugl graphics backend</a>
  1623. to latest upstream with no patches - is complete.<br/>
  1624. Only 1 small change is still custom, related to using
  1625. <a href="https://github.com/x42/sofd/" target="_blank">sofd</a>
  1626. as a fallback file browser dialog on Linux.<br/>
  1627. After
  1628. <a href="https://github.com/lv2/pugl/pull/49" target="_blank">some discussion with the author</a>,
  1629. I realized such a change/patch doesn't belong in pugl.
  1630. I will change this part of DPF at a later time.<br/>
  1631. There are some small additions made on DPF-side of the code for pugl, but nothing that requires changing pugl itself.
  1632. </p>
  1633. <p>
  1634. New stuff was added in DPF of course, first we have a complete
  1635. <a href="https://github.com/DISTRHO/DPF/commit/495dcc4f03d6a2ed0d30c56c885e4eb7476f4488" target="_blank">port groups</a>
  1636. implementation, based on an
  1637. <a href="https://github.com/DISTRHO/DPF/pull/193" target="_blank">initial PR from Jean Pierre Cimalando</a>.<br/>
  1638. It is supported on LV2, VST2 and JACK targets, wherever is possible on those anyway.<br/>
  1639. For LV2, port groups are set in the meta-data for both audio/CV ports and parameters.<br/>
  1640. For VST2, parameter groups are supported (named categories in VST world)<br/>
  1641. For JACK, lv2-like meta-data is set on the audio and CV ports.<br/>
  1642. </p>
  1643. <p>
  1644. Next, the JACK target can now always be built, by including
  1645. <a href="https://github.com/DISTRHO/DPF/tree/develop/distrho/src/jackbridge" target="_blank">jackbridge</a>
  1646. code from Carla (adapted to make fit DPF better, also liberally licensed).<br/>
  1647. This makes it so that:
  1648. </p>
  1649. <ol>
  1650. <li>JACK headers and libraries are not needed at build-time</li>
  1651. <li>Compiled binaries to not link to libjack</li>
  1652. <li>libjack is loaded dynamically at runtime, printing an error if not found</li>
  1653. </ol>
  1654. <p>
  1655. As a 2nd step on top of this,
  1656. <a href="https://github.com/thestk/rtaudio" target="_blank">RtAudio</a>
  1657. is used as fallback in case JACK is not available or connecting to the JACK server fails
  1658. (usually because it is simply not running)<br/>
  1659. This has been requested a few times, and it is finally here.<br/>
  1660. DPF will setup RtAudio so it opens the default audio input and output as needed. MIDI is not supported yet.<br/>
  1661. In any case, such fallback makes testing of DPF plugins much easier, specially on systems that do not have JACK.
  1662. </p>
  1663. <p>
  1664. Moving on, I started some
  1665. <a href="https://github.com/DISTRHO/DPF/blob/develop/dgl/EventHandlers.hpp" target="_blank">
  1666. classes that simply do event handling</a>,
  1667. split off from the ImageButton and ImageKnob into something generic.<br/>
  1668. The idea here is to make it easier for developers to get a working widget from scratch.<br/>
  1669. Maybe this will help DPF based plugins to be more consistent on their behaviour too.<br/>
  1670. Note that this work is not yet finalized, so these classes are not yet documented.<br/>
  1671. I am using them on a new set of plugins, coding on a as-needed basis, so this will keep evolving over time.
  1672. </p>
  1673. <p>
  1674. More stuff was added too, though not as substantial, including (in no particular order):
  1675. </p>
  1676. <ul>
  1677. <li>Allow UI_TYPE = generic, so UI can be opengl or cairo, whichever is available</li>
  1678. <li>Initial work for VST3 compatible plugins, lots to do.. (nothing to see just yet)</li>
  1679. <li>Implemented Window::openFileBrowser() fallback for state files, so you always get a file browser</li>
  1680. </ul>
  1681. <p>
  1682. DPF is now at a point where I want to focus on stability and testing.<br/>
  1683. Out of all feature requests, only SVG support is deemed important and "breakage-worthy" (if that makes sense).<br/>
  1684. Once SVG support is in, there will be a feature freeze and then getting everything to work at least as good as before.
  1685. </p>
  1686. <h3>One-Knob Series</h3>
  1687. <p>
  1688. As a way to stress-test the new DPF and also start having some usable
  1689. <a href="https://github.com/DISTRHO/DPF-Widgets" target="_blank">DPF-Widgets</a>
  1690. I began a
  1691. <a href="https://github.com/DISTRHO/OneKnob-Series" target="_blank">new project called One-Knob Series</a>
  1692. that is going to be slowly brewing for the upcoming months.<br/>
  1693. I am not taking a rush on this one, its initial purpose is to test DPF but it so happens that it is also a nice, fun and useful project.<br/>
  1694. The idea here is to make a collection of stupidly simple but well-polished and visually pleasing audio plugins,
  1695. with as little controls as possible, often just one knob and a few options.<br/>
  1696. Eventually they will be not just as a test for DPF, but also as a show-case of what it can do, plus give an example of good practices within DPF.
  1697. </p>
  1698. <p>
  1699. <img src="/screenshots/news/ok-series-2021-07.png" alt="ok-series"/>
  1700. </p>
  1701. <p>
  1702. The guidelines for the collection are:
  1703. </p>
  1704. <ul>
  1705. <li>Must have one main control/knob (linear or logarithmic), with one auxiliary slider/knob allowed but discouraged</li>
  1706. <li>Can have maximum 3 auxiliary options (list of values or toggles)</li>
  1707. <li>Parameter changes must be click-free</li>
  1708. <li>GUI must be cleanly scalable (no bitmaps allowed or blurred resources when scaled)</li>
  1709. <li>GUI must follow the same style</li>
  1710. </ul>
  1711. <p>
  1712. I have a few ideas for useful one-knob style of plugins, to slowly be put into action throughout the year.<br/>
  1713. Before you ask, you can already build and use them yes.<br/>
  1714. I don't recommend doing so right now though.
  1715. </p>
  1716. <h3>Other</h3>
  1717. <p>
  1718. A new Carla release is coming very soon, for the quarterly release pact once again.<br/>
  1719. It is going to be a bugfix release, I will write more details about it in 13 days for the 15th of July.<br/>
  1720. JACK2 will very likely see a new version too, pretty minimal but keeping with the spirit of doing regular releases.
  1721. </p>
  1722. <p>
  1723. Now, into some personal notes...<br/>
  1724. I am a little frustrated, perhaps disappointed, that pushing for donations doesn't work.<br/>
  1725. The number of subcriptions has been going down, not up.<br/>
  1726. While I want to keep doing these kinda of things, being realistic, it is really not sustainable.<br/>
  1727. All the free time is basically spent on this, but it does not pay off.<br/>
  1728. Perhaps that should have been expected..<br/>
  1729. It seems that (in my opinion), in order to make it really pay off, a whole lot more effort would be needed.<br/>
  1730. Not just with coding, but more regular interaction with community, basically a whole lot of reporting and being present.<br/>
  1731. The projects that really succeed in such funding pretty much always have someone very "present" and visible within their community.<br/>
  1732. It is tough, and maybe was just not feasible at all. We know audio development, specially on Linux or open-source, is very very niche.
  1733. </p>
  1734. <p>
  1735. So it is clear that keeping this up as-is is not possible, a lot of my life stuff was ignored or put on hold (it was lockdown anyway, so not much of a problem).<br/>
  1736. For the sake of sanity and balance, going forward for the next 6 months (so the rest of the year), plan is now:
  1737. </p>
  1738. <ul>
  1739. <li>no more new-feature developments, bugfixes only (the svg and vst3 support in dpf being the exception, I feel like they are essential)</li>
  1740. <li>will restrict time spent working on floss stuff to whatever is left from main job, no more weekends, max 40h/week</li>
  1741. <li>when bugfixes get boring, will do packaging, website updates or writting user manuals</li>
  1742. </ul>
  1743. <p>
  1744. And that's all for now.<br/>
  1745. Obviously I will still keep working on these things, don't worry.<br/>
  1746. Specially Carla and DPF have my main attention, but will be on a more reasonable pace from now on.<br/>
  1747. As always, if you appreciate the kind of work I do, please
  1748. <a href="https://kx.studio/Donations">consider a donation</a>.<br/>
  1749. Thank you in advance for your support, and stay safe out there! See you soon!<br/>
  1750. </p>
  1751. <hr/>
  1752. <p>
  1753. <span style="font-size: 20px">&gt; KXStudio Monthly Report (May 2021)</span><br/>
  1754. On <i>2021-05-31</i> by<i> falkTX</i>
  1755. </p>
  1756. <p>
  1757. Hello all, another monthly report about the KXStudio project is here.<br/>
  1758. I skipped last month as there was not much to report.<br/>
  1759. Mainly there were new releases, but those had their own announcement (specifically,
  1760. <a href="https://kx.studio/News/?action=view&url=carla-plugin-host-v23-is-here" target="_blank">
  1761. Carla v2.3</a>
  1762. and
  1763. <a href="https://jackaudio.org/news/2021/04/15/jack2-v1918-release.html" target="_blank">
  1764. JACK2 v1.9.18</a>).<br/>
  1765. Afterwards there was a small personal situation (that is still unfolding) that took all my free time, so that was it.<br/>
  1766. There are a few updates related to the month of May though!
  1767. </p>
  1768. <h3>DPF updates</h3>
  1769. <p>
  1770. The main thing to report today is all the work that I've been putting in
  1771. <a href="https://github.com/DISTRHO/DPF" target="_blank">DPF</a>
  1772. recently.<br/>
  1773. This has been a long-time coming, but better late than never.<br/>
  1774. For those unaware, DPF is a very small C++ framework to create audio plugins with.<br/>
  1775. It has UI support, but it is intentionally not a fully-fledged UI toolkit, same for its DSP side.<br/>
  1776. It can export as LV2, VST2 and other plugin formats, but it does not try to do much more than that.<br/>
  1777. Native OS events is handled behind the scenes via
  1778. <a href="https://gitlab.com/lv2/pugl" target="_blank">pugl</a>.
  1779. </p>
  1780. <p>
  1781. One major task to do was updating to
  1782. <a href="https://drobilla.net/files/pugl_docs/overview.html" target="_blank">latest pugl</a>,
  1783. because it supports many more things compared to old versions.<br/>
  1784. pugl had its event system completely reworked though, so we can't just update and use it as-is.<br/>
  1785. In the end, this update work is something that
  1786. <a href="https://github.com/DISTRHO/DPF/pull/272" target="_blank">took several weeks</a>.<br/>
  1787. I took the chance to rework some core components of DPF UI handling together with this,
  1788. as there were a few parts of the code that
  1789. <a href="https://github.com/DISTRHO/DPF/issues/68" target="_blank">proved confusing</a>
  1790. to
  1791. <a href="https://github.com/DISTRHO/DPF/issues/136" target="_blank">other developers</a>.<br/>
  1792. Also added in
  1793. <a href="https://github.com/DISTRHO/DPF/tree/develop/tests" target="_blank">testing units and demo applications</a>
  1794. to help test several parts of DPF, though this is still very much work-in-progress.<br/>
  1795. This was specially useful to ensure core parts were working before proceeding with the rework.<br/>
  1796. Related to pugl update and rework, the Cairo backend of DPF is now pretty much on-par with its OpenGL one.<br/>
  1797. The Demo tool (where we test images, events, resizing, etc) has consistent behaviour between the two.<br/>
  1798. <br/>
  1799. <img src="/screenshots/news/dpf-demo-2021-05.png" alt="dpf-demo"/>
  1800. </p>
  1801. <p>
  1802. Continuing with the rework,
  1803. <a href="https://github.com/DISTRHO/DPF/pull/281" target="_blank">special attention was given to resizing</a>.<br/>
  1804. Resizing in LV2 UIs has always been something very painful, which still does not work correctly in many hosts.<br/>
  1805. One culprit of this was the bad initial decision to use an LV2 extension to deal with UI resizing.<br/>
  1806. Turns out,
  1807. <a href="https://github.com/lv2/pugl/issues/42" target="_blank">we do not need this at all</a>!<br/>
  1808. So the next version of DPF will
  1809. <a href="https://github.com/DISTRHO/DPF/commit/0d6f63e9b284207efe27e798ccdfbb307ee56302" target="_blank">no longer make use</a>
  1810. of
  1811. <a href="https://github.com/DISTRHO/DPF/commit/d2b96431b2a5790e9d281f97e09e42ab2f90a927" target="_blank">LV2 UI resize extensions</a>.<br/>
  1812. We will need to accommodate hosts to this, which is a breaking change.<br/>
  1813. But it is not like LV2 plugin-side resizing was working well in the first place anyway.<br/>
  1814. I already
  1815. <a href="https://github.com/falkTX/Carla/commit/75ea9f5b2d184151c696f1dc648dfb700959c876" target="_blank">did this for Carla</a>.
  1816. Likely will do similar things to
  1817. <a href="http://drobilla.net/software/suil" target="_blank">suil</a>
  1818. if no one else does.
  1819. </p>
  1820. <p>
  1821. On even more DPF news, I created a new
  1822. <a href="https://github.com/DISTRHO/DPF-Widgets" target="_blank">open-source code repository meant for reusable DPF UI widgets</a>.<br/>
  1823. It has come to my attention that developers struggle with DPF having very little common widgets they are used to.<br/>
  1824. I have made a few ones based on images for the
  1825. <a href="https://github.com/DISTRHO/DPF-Plugins/" target="_blank">DPF-Plugins collection</a>,
  1826. but some developers struggle to create individual widgets from scratch.<br/>
  1827. This code repository will evolve over time, obviously as a new project which is only a few days old there is not much to see.<br/>
  1828. One common request has been a resize handle, so that for plugin formats like VST2 which do not allow user-side resizing we still have a way for the user to resize the UI.<br/>
  1829. There is one
  1830. <a href="https://github.com/DISTRHO/DPF-Widgets/blob/main/generic/ResizeHandle.hpp" target="_blank">generic resize handle in the repository now</a>,
  1831. usable for both Cairo and OpenGL backends.<br/>
  1832. The first real widgets I am contributing to the repository are a port of
  1833. <a href="https://github.com/IceDragon200/oui-blendish" target="_blank">oui-blendish</a>
  1834. which provides blender-style looking widgets.<br/>
  1835. I am still setting up the whole thing, but initial impressions are very good. It even works with High-DPI / custom scale factors!<br/>
  1836. (ignore the bitmap icons on the screenshot below, those are only used in testing, I will later either replace them or remove them)<br/>
  1837. <br/>
  1838. <img src="/screenshots/news/dpf-widgets-blendish-2021-05.png" alt="dpf-widgets-blendish"/>
  1839. </p>
  1840. <p>
  1841. Finally on DPF side, as contributions by Jean Pierre Cimalando,
  1842. <a href="https://github.com/DISTRHO/DPF/pull/269" target="_blank">CMake is now supported</a>
  1843. for building DPF and using it in plugins targeting DPF.<br/>
  1844. As a second step on top of CMake, it is now possible to
  1845. <a href="https://github.com/DISTRHO/DPF/pull/278" target="_blank">build DPF with MSVC on Windows</a>.<br/>
  1846. I tried this myself and was able to build a DPF VST2 plugin with MSVC and run the output binary inside Carla.<br/>
  1847. This is not my development workflow by any means (it was the first time I used MSVC!) but it opens up the process for many more people, which always great.<br/>
  1848. <br/>
  1849. <img src="/screenshots/news/dpf-msvc-2021-05.png" alt="dpf-msvc"/>
  1850. </p>
  1851. <p>
  1852. One last bit of news regarding DPF is that I started testing the waters for VST3 support.<br/>
  1853. There is almost nothing to see just yet, as there is enough to do in DPF regarding polishing, fixing bugs and handling requests so that VST3 work is not a priority.<br/>
  1854. It is something that I have took an interest on lately though, as a potential way to attract commercial developers/vendors to DPF.<br/>
  1855. (and perhaps some well needed funding? who knows..)
  1856. </p>
  1857. <p>
  1858. Work on DPF will continue, you can grab all these changes from its
  1859. <a href="https://github.com/DISTRHO/DPF/tree/develop" target="_blank">develop branch</a>.<br/>
  1860. Expect more news about it next month.
  1861. </p>
  1862. <h3>Other updates</h3>
  1863. <p>
  1864. While most of my time and attention was given to DPF, a few other things happened.<br/>
  1865. There is the whole "Audacity was bought up by Muse Group and added CLA, plus telemetry coming soon" thing...<br/>
  1866. I did some tests with building Audacity with mingw, and succeeded in setting up scripts to
  1867. <a href="https://github.com/DISTRHO/PawPaw/blob/master/bootstrap-audacity.sh" target="_blank">build required dependencies</a>
  1868. and then
  1869. <a href="https://github.com/DISTRHO/PawPaw/blob/master/build-audacity.sh" target="_blank">build audacity itself</a>.<br/>
  1870. From what I tested on Windows everything seems to work.<br/>
  1871. (screenshot below is from Wine, but I also tested on real Windows via Virtual Machine)<br/>
  1872. <br/>
  1873. <img src="/screenshots/news/audacity-win32-build-2021-05.png" alt="audacity-win32-build"/>
  1874. <br/>
  1875. Most mingw needed fixes were
  1876. <a href="https://github.com/audacity/audacity/pull/881" target="_blank">submitted upstream</a>,
  1877. but them now requiring a CLA means the PR will likely stay open indefinitely.<br/>
  1878. Also did some tests with
  1879. <a href="https://github.com/audacity/audacity/discussions/877" target="_blank">building Audacity with wxQt</a>
  1880. and while it kinda works, still has some obvious issues - the wxWidgets Qt backend is not feature complete so it is normal for those to happen.<br/>
  1881. It is very likely I will end up maintaining some custom builds for Audacity once more network features creep in
  1882. (analytics is coming to Audacity for sure, it is just a matter of when and how).<br/>
  1883. I am not interested on a fork, only in a way for casual users to get similar builds to the official ones without user-data tracking.
  1884. </p>
  1885. <p>
  1886. There are some other random things too, for example adding a new "-w" argument to the new jack2 zalsa tools so that it
  1887. <a href="https://github.com/jackaudio/jack2/commit/23b9fb71b943595db90eb6e8dd48294600cfb0bb" target="_blank">waits until the requested soundcard is available</a>
  1888. instead of failing to start.<br/>
  1889. This is very handy when adding it as part of some boot process.
  1890. </p>
  1891. <p>
  1892. Carla has also seen some
  1893. <a href="https://github.com/falkTX/Carla/commit/c777cd02d92ba8a61adb29d61fd39f84e3d1bc55" target="_blank">pipewire-related</a>
  1894. <a href="https://github.com/falkTX/Carla/commit/62a6410171c4b88b0b5a76cd0681d16152f9c9d1" target="_blank">fixes</a>.<br/>
  1895. It is still not working 100%, but already know of a solution for them, just need to put that into code.<br/>
  1896. Expect a v2.3.1 release soon with these fixes, and also the LV2 UI resize handling mentioned above.
  1897. </p>
  1898. <p>
  1899. Finally I added support for
  1900. <a href="https://github.com/falkTX/FFmpeg/commits/n4.4-jackoutdev" target="_blank">FFmpeg JACK output</a>.
  1901. Seems to work well from what I tested, but I no longer have a need for it.<br/>
  1902. Once I am done with DPF and other things, I will try to submit this upstream.
  1903. </p>
  1904. <p>
  1905. Regarding packages in the KXStudio repositories, there are some small updates. Those are:
  1906. </p>
  1907. <ul>
  1908. <li>Added bjumblr</i>
  1909. <li>Added bslizr-uwu (custom skin to bslizr)</i>
  1910. <li>bslizr updated to 1.2.14</i>
  1911. <li>lsp-plugins updated to 1.1.30</i>
  1912. </ul>
  1913. <p>&nbsp;</p>
  1914. <p>
  1915. That is all for now.<br/>
  1916. If you appreciate the kind of work I do, please
  1917. <a href="https://kx.studio/Donations">consider a donation</a>.<br/>
  1918. Thank you in advance for your support, and stay safe out there!<br/>
  1919. </p>
  1920. <hr/>
  1921. <p>
  1922. <span style="font-size: 20px">&gt; Carla Plugin Host v2.3 is here</span><br/>
  1923. On <i>2021-04-15</i> by<i> falkTX</i>
  1924. </p>
  1925. <p>
  1926. Hello everyone, this is the announcement of the 2.3 version of the Carla Plugin Host.<br/>
  1927. If you do not know, Carla is a fully-featured cross-platform audio plugin host, which can also run as a plugin.
  1928. </p>
  1929. <p>
  1930. This specific release, compared to v2.3-RC2, brings some much needed fixes to the MIDI Pattern plugin - it finally works as expected.<br/>
  1931. There were some fixes done on the patchcanvas side, and for other stuff as reported by users.<br/>
  1932. The full list of changes for v2.3 (coming from v2.3-RC2) are:
  1933. </p>
  1934. <ul>
  1935. <li>Fix a float vs int usage, which will break in python soon</li>
  1936. <li>Fix cancelling plugin discovery</li>
  1937. <li>Fix main client name for multiple carlas inside NSM</li>
  1938. <li>Fix missing vst3 poly aftertouch</li>
  1939. <li>Fix patchcanvas use of keyboard modifiers</li>
  1940. <li>Fix project filename/folder only set after saving once</li>
  1941. <li>Fix recursive VST2 audioMasterAutomate parameter changes</li>
  1942. <li>Fix sorting plugins by favorite</li>
  1943. <li>Do not run 2nd instance of lv2 plugin if it has event output(s)</li>
  1944. <li>Read lv2 midi:binding on control ports and parameters</li>
  1945. <li>Use Ctrl+P to open/close side panel</li>
  1946. <li>Use fixed buffers on standalone bridge mode</li>
  1947. <li>midipattern: overall fix up</li>
  1948. <li>midipattern: use Esc key to close UI</li>
  1949. </ul>
  1950. <p>
  1951. The v2.3-RC1 announcement already listed the new features that v2.3 brings (compared to v2.2),
  1952. but let's go through the release highlights again.
  1953. </p>
  1954. <table><tr><td width="40%">
  1955. <a href="/screenshots/news/carla-2.3_macos-universal.png">
  1956. <img src="/screenshots/news/carla-2.3_macos-universal.png" style="max-width:100%;height:auto;" alt="macos-universal"/>
  1957. </a>
  1958. </td><td width="60%">
  1959. <h3>macOS arm64/universal build support</h3>
  1960. <p>
  1961. Starting with v2.3, Carla natively supports the new macOS arm64 architecture, used in the new M1 hardware models.<br/>
  1962. The Carla macOS universal build supports x86_64 and arm64 architectures at the same time, and should run on anything 10.12 or newer.
  1963. </p>
  1964. <p>
  1965. As Carla has support for plugin bridges (even across architectures), I took care to make sure that the arm64 version can load x86_64 plugins.<br/>
  1966. When a plugin fails to load in a specific way, Carla will try to load it again but now in x86_64 mode.<br/>
  1967. This is currently working for VST2 and VST3 plugins.
  1968. </p>
  1969. <p>
  1970. Additionally, for something that kept bothering me a lot, Carla will automatically remove plugins from macOS quarentine before loading them.<br/>
  1971. This is not possible to do for AudioUnits as we do not have the full path to the plugin binary, but valid for all other formats.<br/>
  1972. No more security theatre shenanigans here! :)
  1973. </p>
  1974. </td></tr></table>
  1975. <br/>
  1976. <table><tr><td width="40%">
  1977. <a href="/screenshots/news/carla-2.3_audiofile.png">
  1978. <img src="/screenshots/news/carla-2.3_audiofile.png" style="max-width:100%;height:auto;" alt="audiofile"/>
  1979. </a>
  1980. </td><td width="60%">
  1981. <h3>General improvements to AudioFile plugin</h3>
  1982. <p>
  1983. The AudioFile internal plugin received some deserved attention this time around.<br/>
  1984. Besides basically reworking how its disk-streaming functionality (more robust and much less CPU usage),<br/>
  1985. it finally can do resampling so it will sound correctly no matter the sample rate.<br/>
  1986. Additionally mp3 support was added via
  1987. <a href="https://github.com/mackron/dr_libs/blob/master/dr_mp3.h" target="_blank">dr_mp3</a>,
  1988. as
  1989. <a href="http://www.mega-nerd.com/libsndfile/" target="_blank">libsndfile</a>
  1990. used by it does not yet officially support it.
  1991. </p>
  1992. <p>
  1993. Both Audio and MIDI file plugins are now exposed as LV2 plugins, allowing to load and use these plugins outside of Carla.<br/>
  1994. It supports file parameter plus patch Get/Set with State mapPath as expected for these kinds of plugins.<br/>
  1995. The experimental "inline-display" of the AudioFile is also exposed as an LV2 feature.
  1996. </p>
  1997. </td></tr></table>
  1998. <br/>
  1999. <table><tr><td width="40%">
  2000. <a href="/screenshots/news/carla-2.3_audiofile.png">
  2001. <img src="/screenshots/news/carla-2.3_midipattern.png" style="max-width:100%;height:auto;" alt="midipattern"/>
  2002. </a>
  2003. </td><td width="60%">
  2004. <h3>General improvements to MIDI Pattern plugin</h3>
  2005. <p>
  2006. Not just the AudioFile plugin, but the MIDI Pattern one also received some much needed attention.<br/>
  2007. The piano-roll UI code was reworked to ensure it worked well, as previously moving notes around just didn't work at all.<br/>
  2008. Many precautions were added against edge-cases.
  2009. </p>
  2010. <p>
  2011. Hovering notes will change the mouse cursor to better indicate the potential action in case of mouse press.<br/>
  2012. And as with pretty much all other plugins in Carla, using Escape key will now close the plugin UI too.
  2013. </p>
  2014. </td></tr></table>
  2015. <br/>
  2016. <table><tr><td width="40%">
  2017. <a href="/screenshots/news/carla-2.3_windows.png">
  2018. <img src="/screenshots/news/carla-2.3_windows.png" style="max-width:100%;height:auto;" alt="windows"/>
  2019. </a>
  2020. </td><td width="60%">
  2021. <h3>Reworked Windows builds</h3>
  2022. <p>
  2023. The infrastructure used to build Windows binaries is now through
  2024. <a href="https://github.com/DISTRHO/PawPaw" target="_blank">PawPaw</a>,
  2025. as done with
  2026. <a href="https://github.com/jackaudio/jack2-releases" target="_blank">JACK2</a>
  2027. already.<br/>
  2028. With this, I have control over the whole toolchain and libraries that are used in Carla Windows binaries (previously msys2 packages were used).
  2029. </p>
  2030. <p>
  2031. For users, this means these binaries are more robust and with less dependencies.<br/>
  2032. (I am building with static libraries as much as possible, so no more ligcc/libstdc++6 mess).<br/>
  2033. The Windows zip file download no longer ships with a single Carla.exe, instead please run Carla.exe inside the Carla folder, should be easy to spot.
  2034. </p>
  2035. <p>
  2036. For developers, a nice side-effect is that we can finally tweak the behaviour of the startup executable, now allowing debug messages to be seen.
  2037. (though you need to run it in Console/PowerShell for that)<br/>
  2038. The libraries that allow to use and talk to Carla Host API are now provided on these builds.
  2039. </p>
  2040. <p>
  2041. Finally, it should be possible to build Carla under msys2 on Windows now.<br/>
  2042. I can make a quick tutorial if that is something that interests you, let me know if that is the case.
  2043. </p>
  2044. </td></tr></table>
  2045. <br/>
  2046. <table><tr><td width="40%">
  2047. <a href="/screenshots/news/carla-2.3_icons.png">
  2048. <img src="/screenshots/news/carla-2.3_icons.png" style="max-width:100%;height:auto;" alt="icons"/>
  2049. </a>
  2050. </td><td width="60%">
  2051. <h3>Use system/desktop theme icons (non-macOS/Windows only)</h3>
  2052. <p>
  2053. Due to popular demand, there is now an option in the experimental settings to use system/desktop theme icons.<br/>
  2054. This will remain as experimental feature for 1 release, so we can catch potential issues in the mean time, and fix them.<br/>
  2055. </p>
  2056. <p>
  2057. Since I do not mind the default Carla icons (quite like them actually), this is not meant for me.<br/>
  2058. Feel free to use it and report back if you spot something weird or incorrect.
  2059. </p>
  2060. </td></tr></table>
  2061. <br/>
  2062. <h3>Other notable changes</h3>
  2063. <ul>
  2064. <li>Allow to run CV plugins in rack mode, with CV connected to a dummy port</li>
  2065. <li>Carla-Control no longer has return remote url option, not needed after some fixes</li>
  2066. <li>Clear up situation with nogui and carla-osc-gui script (explanation article to come later)</li>
  2067. <li>Disable OSC by default on macOS (needs to ask permission to use network, which may look suspicious)</li>
  2068. <li>Do not build external plugins by default</li>
  2069. <li>General improvement to LV2 parameter API support</li>
  2070. <li>Many, many, many bug-fixes</li>
  2071. </ul>
  2072. <h3>Downloads</h3>
  2073. <p>
  2074. To download Carla binaries or source code, jump on over to the <a href="https://kx.studio/Downlo