It all starts with the envelope, so that even a few milliseconds of sound can generate "thousands of sonic trajectories." Built entirely in the free, open-source Pure Data, Envion is a deep compositional playground. You can think of it like an algorithmic drum machine. Emiliano Pennisi shares his creation with us.
The post Envion: a free, open, algorithmic drum composition environment in Pd appeared first on CDM Create Digital Music.
With deeper support for Linux and high-DPI rendering, NAP, the expressive, low-latency, efficient framework for control and visuals, can now awe audiences anywhere. Visualization, sound, running electronics, whatever it is you want to throw at NAP, now you can do it better on Windows and Linux, including embedded platforms. And did we mention it's free and open source?
The post NAP, free visual and media framework, now dazzles anywhere appeared first on CDM Create Digital Music.
The super talented [Switch Angel] is an electronic music artist, with a few cool YouTube videos to show off their absolute nailing of how to live code with Strudel. For us mere mortals, Strudel is a JavaScript port of TidalCycles, which is an algorithmic music generator which supports live coding, i.e. the music that is passed down to the synthesizer changes on-the-fly as you manipulate the code. It’s magical to watch (and listen!) to how you can adapt and distort the music to your whims just by tweaking a few lines of code: no compilation steps, hardly any debugging and instant results.
The traditional view of music generators like this is to create lists of note/instrument pairs with appropriate modifiers. Each sound is specified in sequence — adding a sound extends the sequence a little. Strudel / Tidalcycles works a little differently and is based on the idea of repeating patterns over a fixed time. Adding an extra sound or breaking down one sound slot into multiple sounds squeezes all the remaining slots down, causing the whole pattern to repeat in the same period, with the sounds individually taking up less space. This simple change makes it really easy to add layer upon layer of interest within a sequence with a few extra characters, without recalculating everything else to fit. On top of this base, multiple effects can be layered—more than we can mention here—and all can be adjusted with pop-in sliders directly in the code.
You see, the code is also the visualizer. As the sequence runs, the notes and time periods are highlighted, with piano rolls and oscilloscope views adding to the visuals to help guide you. Tweaking the various components of the sound composition in real time with embedded sliders is a quick and easy way to smoothly hear the impact of settings. It just makes sense. Additionally, since Strudel is written in JavaScript, you can pull in external libraries of customized functions to make your code more straightforward to read, like this short library from [Switch Angel].
On the back end, the built-in web-based synthesizer is basic but functional for roughing out. Still, for absolute control, you’re going to want to send the notes over to something like SuperCollider or Sonic Pi. This is easy because Strudel supports OSC, making it a simple, configurable item.
If you were thinking that you’ve seen a JavaScript-based generative music thing before, you’d be right. Whilst we’re thinking about generative music and generative art in general, what about having a look at this neat sound-and-light sculpture?
Thanks to [JohnU] for sending this in!
The GStreamer team is pleased to announce another bug fix release in the new stable 1.26 release series of your favourite cross-platform multimedia framework!
This release only contains bugfixes, and it should be safe to update from 1.26.x.
Highlighted bugfixes:
See the GStreamer 1.26.7 release notes for more details.
Binaries for Android, iOS, Mac OS X and Windows will be available shortly.
The GStreamer Conference team is pleased to announce that the full conference schedule including talk abstracts and speaker biographies is now available for this year's lineup of talks and speakers, covering again an exciting range of topics!
The GStreamer Conference 2025 will take place on 23-24 October 2025 in London, UK, followed by a hackfest.
Details about the conference, hackfest and how to register can be found on the conference website.
This year's topics and speakers:
Lightning Talks:
Showing the invisible: Analysing buffer flow with tracers
François Laignel, Centricular
Video Frame Scheduler Plugin for Improving WebRTC Playback Quality
Haejung Hwang, LG Electronics
Many thanks to our amazing sponsors ‒ Platinum sponsors Centricular, Collabora, Igalia, and Pexip, Gold sponsors Axis Communications and Fluendo, and Silver sponsors MediaScribe and Veo, without whom the conference would not be possible in this form.
We hope to see you all in London soon! Don't forget to register as soon as possible if you're planning on joining us, so we can order enough food and drinks!
There's also a hackfest after the conference. If you're planning on joining us for the hackfest you must register separately for that, by 21 October 2025 at the latest.
Week highlights: new releases of GIMP and RapidRAW, new features in darktable and Ardour.
This is purely a bugfix release, don’t expect anything new. The release notes are here.
The team recently merged a patch by Kofa that adds AgX, a new tonemapper originally seen in Blender. This is not the first photography app to use AgX (Saulala is likely the first one), but definitely the most prominent one so far.
There have been several general tonemapper modules before AgX: base curve, followed by several variations of filmic (later renamed to filmic rgb), followed by sigmoid. I specifically do not mention other tonemappers here, as they were intended for use elsewhere in the processing pipeline.
Rather than emulating the film look, AgX aims for colorimetric accuracy and better chromatic consistency across the dynamic range. Kofa explained the mechanics of AgX in darktable early on in a thread on Pixls, I think you should read it if you are interested.
The module has controls for the input data, base and advanced curve parameters, and the look (slope offset, power, saturation, hue preservation).
My personal impression so far is that while AgX provides a lot of control, just like with other tonemappers, the defaults are not great.
On scenes with a wide dynamic range, details in highlights get flat, shadows/blacks get even darker, and hues change regardless of how much hue preservation you apply in AgX settings. Sigmoid and filmic rgb do a similar thing, but at least they don’t touch hues as much.
So, I guess, we’ll have to continue tweaking tonemapping settings quite a bit for the foreseeable future to get to a decent baseline.
Timon Käch released an update of RapidRAW with several quite useful improvements:
Unfortunately, as you can see, the recent fixes have not improved the situation with pink in overblown highlights.
Nevertheless, here are the usual downloads and release notes.
A year ago, Paul Ebbers picked up the SearchBar addon, originally created by Suzanne Soy, and started improving it. This is what you know from applications like Blender, GIMP, Olive and probably many others. Paul now proposes to include it in FreeCAD 1.2.
There’s also a pretty substantial patch by tarman3, adding numerous Array command improvements in CAM. It’s currently in draft and will likely be merged for v1.2 as well.
The release blocker needle is slowly moving towards zero and is currently at 27 remaining blockers. It may take a few more months to go all the way left.
Robin Gareus investigated the StaffPad’s audio stretcher now used by Audacity, found that it works better than Rubberband in some cases, and added it as an “Any” option in the Time Stretch tool.
Mixer channels now have an RTA (real-time analyzer) toggle:
Finally, Ardour now has support for the iCON V1-M controller, contributed by one of the Mixbus developers.
This is a recent find of a not-too-recent project. Ben Fox started working on a database for MIDI CC & NRPN of various hardware synths, samplers, etc., and 24 contributors joined over the years. If you have one of the supported devices and need to control it from the DAW, this may come in handy.
All the information lives in CSV files on GitHub and is available under the terms of the CC-BY-SA-4.0 license. You can contribute new descriptions to help make the information more discoverable for other users.
Silent Sunday artwork by Sylvia Ritter, made with Krita:
The Old Tibetan monastery by Maxim Petrov, made with Blender and Photoshop:
Tale’s Edge - Snowy Woodland Village by Andy Walsh, made with Blender, 3DCoat, and Photoshop:
Bose SoundTouch speakers were introduced in 2013, offering the ability to connect to online streaming services and play back audio on multiple speakers simultaneously using the accompanying mobile app. Now these features are about to be removed, including the mobile app, as Bose is set to discontinue support on February 18, 2026. From that point onwards, you can only use them via Bluetooth or physical connectors that may be present, like an audio jack or HDMI port. This includes fancy home theater system hardware like the above SoundTouch 520.
That is the official line, at least. We have seen the SoundTouch on Hackaday previously, when it was discovered how to gain root shell access to the Linux OS that powers the original SoundTouch system with Telnet access on port 17,000 to pass the listening service the remote_services on command before connecting with Telnet as usual, with root and no password. A quick glance at the comments to that post suggests that this is still a valid approach for at least certain SoundTouch devices.
The fallout from this announcement appears to be twofold: most of all that ‘smart’ features like WiFi-based streaming can be dropped at any time. But it also makes us realize that hardware hackers like us will never run out of new and suddenly obsolete hardware that need our rescue.
The Ubuntu Studio team is pleased to announce the release of Ubuntu Studio 25.10 code-named “Questing Quokka”. This marks Ubuntu Studio’s 37th release. This release is a Regular release and as such, it is supported for 9 months, until July 2026.
Since it’s just out, you may experience some issues, so you might want to wait a bit before upgrading. Please see the release notes for a more complete list of changes and known issues. Listed here are some of the major highlights.
You can download Ubuntu Studio 25.10 from our download page.
The Ubuntu Studio 25.10 disk image (ISO) exceeds 4 GB and cannot be downloaded to some file systems such as FAT32 and may not be readable when burned to a standard DVD. For this reason, we recommend downloading to a compatible file system. When creating a boot medium, we recommend creating a bootable USB stick with the ISO image or burning to a Dual-Layer DVD.
Minimum installation media requirements: Dual-Layer DVD or 8GB USB drive.
Images can be obtained from this link: https://cdimage.ubuntu.com/ubuntustudio/releases/25.10/release/
Full updated information, including Upgrade Instructions, are available in the Release Notes.
Upgrades from 25.04 should be enabled within a month after release, so we appreciate your patience. Upgrades from 24.04 LTS will be enabled after 25.04 reaches End-Of-Life in January 2026.
After a long hiatus, Internet DJ Console (IDJC) has returned. This package for creating and running Internet-based radio stations had been removed from Debian, but has returned, and therefore, returned to Ubuntu Studio!
Ubuntu Studio now includes JackTrip! JackTrip serves two purposes: low-latency networked JACK audio within your network, and low-latency Internet audio collaboration. Bands are even known to jam remotely using JackTrip’s services!
It supports any number of channels (as many as the computer/network can handle) of bidirectional, high quality, uncompressed audio signal streaming.
We came to the realization that we needed to support musicians a little better, so we added a few instrument and musical plugins to assist with that:
This release contains PipeWire 1.4.7.
PipeWire’s JACK compatibility is configured to use out-of-the-box and is zero-latency internally. System latency is configurable via Ubuntu Studio Audio Configuration and can now be configured on a per-user basis instead of globally.
Speaking of Audio Configuration, we have added a number of options for configuring the PipeWire JACK compatibility, as can be seen in the image below. Additionally, buffer size can now be configured from within any JACK application that supports it, such as Patchance, Carla, Ardour, and more!
This is, as of this writing, the latest release of Ardour, packed with the latest bugfixes.
To help support Ardour’s funding, you may obtain later versions directly from ardour.org. To do so, please one-time purchase or subscribe to Ardour from their website. If you wish to get later versions of Ardour from us, you will have to wait until the next release of Ubuntu Studio, due in April 2026.
Q: Does Ubuntu Studio contain snaps?
A: Yes. Mozilla’s distribution agreement with Canonical changed, and Ubuntu was forced to no longer distribute Firefox in a native .deb package. We have found that, after numerous improvements, Firefox now performs just as well as the native .deb package did.
Thunderbird also became a snap so that the maintainers can get security patches delivered faster.
Additionally, Freeshow is an Electron-based application. Electron-based applications cannot be packaged in the Ubuntu repositories in that they cannot be packaged in a traditional Debian source package. While such apps do have a build system to create a .deb binary package, it circumvents the source package build system in Launchpad, which is required when packaging for Ubuntu. However, Electron apps also have a facility for creating snaps, which can be uploaded and included. Therefore, for Freeshow to be included in Ubuntu Studio, it had to be packaged as a snap.
We have additional snaps that are Ubuntu-specific, such as the Firmware Updater and the Security Center. Contrary to popular myth, Ubuntu does not have any plans to switch all packages to snaps, nor do we.
Q: Will you make an ISO with {my favorite desktop environment}?
A: To do so would require creating an entirely new flavor of Ubuntu, which would require going through the Official Ubuntu Flavor application process. Since we’re completely volunteer-run, we don’t have the time or resources to do this. Instead, we recommend you download the official flavor for the desktop environment of your choice and use Ubuntu Studio Installer to get Ubuntu Studio – which does *not* convert that flavor to Ubuntu Studio but adds its benefits.
Q: What if I don’t want all these packages installed on my machine?
A: Simply use the Ubuntu Studio Installer to remove the features of Ubuntu Studio you don’t want or need! Additionally, we include a Minimal Install option that, when used with Ubuntu Studio Installer, will give you the Ubuntu Studio experience for whatever your desktop studio needs!
A wonderful way to contribute is to get involved with the project directly! We’re always looking for new volunteers to help with packaging, documentation, tutorials, user support, and MORE! Check out all the ways you can contribute!
Our project leader, Erich Eickmeyer, is now working on Ubuntu Studio at least part-time, and is hoping that the users of Ubuntu Studio can give enough to generate a monthly part-time income. We’re not there, but if every Ubuntu Studio user donated monthly, we’d be there! Your donations are appreciated! If other distributions can do it, surely we can! See the sidebar for ways to give!
The best way to contact the Ubuntu Studio team is via the Ubuntu Discourse.
Huge special thanks for this release go to:
I recently had a nice conversation with Amadeus from @linuxaudioplugindevelopment, talking about my involvement with Linux Audio, Ardour and free/libre software.
It turns out that I have short answers to long questions, and vice versa. :) You can find the interview with yours truly on the Linux Audio Developers Spotlight page on linuxaudio.dev.
I was supposed to host a hands-on workshop, planned for 5-6 persons at the Linux Audio Conference in Lyon in June 2025.
On the project rider I had “Boîte de macarons pistache”, not only did I not get that, but the night before I was told that the workshop space was not air-conditioned and +40degC (105 degF).
So I pivoted, spent some late night hours after the conference banquet (free drinks) and turned the workshop into a lecture to be presented in the main hall, which was air-conditioned, before the whole audience (it made be a bit nervous in the beginning). Here you go:
PS. Slides are available.
Hello everyone,
Change-log:
Description:
Project page:
Downloads:
Git repos:
License:
Enjoy!
Week highlights: new features in GIMP and Inkscape; new release of MuseScore Studio, first alpha release of Audacity 4.
Here is some of the ongoing work:
Additionally, Gabriele contributed a new Preferences option to disable the use of the TAB key to switch all dockable windows on and off. This is one of the maddening aspects of using GIMP for new users who press the key by accident and then struggle to figure out why all the docks have suddenly disappeared and how to bring them back.
Personally, I think the proposed patch is more of a workaround. All shortcuts should be configurable; singling one of them out and adding a dedicated switch in Preferences doesn’t seem like a consistent solution to me. Plus, bringing docks back should not be puzzling in the first place. On the flip side, I’m definitely biased here.
All of the above are unmerge patches at the moment.
Some fun things are happening in Inkscape:
The Blender Foundation has published all the videos from the Blender Conference 2025 on YouTube and Peertube. With over 80 videos in the playlist, there’s something for everyone: architectural visualization, production of animated TV series, simulating real-world camera lenses, recreating historical and cultural legacy, and so much more.
You know how much I love digging into arcane pull requests and showing exciting new features and quality-of-life improvements. So believe me when I tell you that there is nothing more exciting right now than seeing the number of v1.1 release blockers go down. If the trend continues, a release candidate in November would not be entirely unrealistic.
At the same time, the pile of post-1.1 work just keeps growing. 229 out of 256 submitted pull requests are now scheduled for inclusion in version 1.2. Sure, some of them are in Draft, but I can absolutely see the team pulling double code review shifts shortly after the v1.1 release again.
Among other “fun” things, the team recently had to discuss how they should deal with AI-generated patches.
The new version comes with many improvements and new features. Many of them are already covered in the release video:
Release highlights:
A bit silly to use OpenStrings (Rhapsody) when you have MuseSounds around, but just to show a VST3 plugin actually working:
See here for a more complete list of changes and download links.
Muse Group also released a technical preview of Audacity 4, the upcoming new release with the user interface completely reimagined and rebuilt with Qt. The important thing is not to expect this version to be production-ready yet. Or the project files to be backward-compatible.
Things like importing/exporting audio, cutting, and applying real-time effects already work. Here is the list of v3 features that are not there yet:
You should also probably expects the mixer to be available in v4. Automation is planned but won’t happen in the first v4 release though.
Notably, some of the missing features from the list above will likely not function exactly as they do in v3 today. My gut feeling is that envelopes and spectral editing are likely to undergo redesign. Martin specifically mentioned envelopes in the video he published several days ahead of the release:
The video focused on the various types of debt that the team inherited from the original team and how they addressed them. That list of debt includes the logo, and it’s a topic of its own.
Over the last 25 years, I witnessed dozens, if not hundreds, of logo proposals, because many people were not happy with the original one. I’ve seen symbolic logos, photorealistic logos, and just about everything in between.
Some contributors were adamant that only they have the right vision for the project’s branding. Others were very much self-aware (“Here’s yet another unsolicited logo redesign to add to the pile“). So it’s very tempting to smirk when you read things like “just deliver a logo people like” in the comments section at The Verge.
All in all, I feel it’s somewhat premature to comment on the new Audacity. There are aspects that I absolutely love. There are things I’m just not too sure about. Like the lack of grid lines above waveform visualization in tracks. Or some of the user interface being bloody enormous, like this built-in compressor plugin window:
So let’s wait for the final version to arrive. The current estimation is sometime in 2026.
Cyberpunk 2077 fan art by 長門ゆき, made with Unreal Engine, Blender, and Photoshop:
Echo City by UE班的小学生_Cgerjia, made with Substance 3D Designer/Painter, Unreal Engine, and Blender:
Skyshade: La Saga LightLark by Ferdinand Ladera (for Alex Aster’s recent bestseller), made with Blender and Photoshop:
LV2 plugins (and other data, like presets) are discovered by parsing Turtle files installed in various bundle directories.
If the host only needs to know which things are installed, then only manifest.ttl files need to be loaded.
That takes only a fraction of a second (60 ms on this machine, which has 897 plugins installed), but if the host needs more information (like the plugin's label or what ports it has), then the data files need to be loaded as well, which can take several seconds.
The parser (from serd) is very fast, so the overwhelming majority of this time is spent inserting data into a model.
I was recently doing some work on lilv related to discovery, and got sidetracked into investigating how much of this overhead could be eliminated. Quite a bit, as it turns out, but before explaining how, I'll give a brief summary of the relevant fundamentals so people who don't spend their days in the triple mines can understand what I'm talking about.
LV2 data is written in the Turtle syntax, which can have a lot of structure, but is ultimately just a shorthand for data that is simply a “flat” series of triples. For example, the abbreviated Turtle
<http://example.org/amp>
a lv2:Plugin ;
doap:name "Amplifier" .
represents the two triples
<http://example.org/amp> rdf:type lv2:Plugin .
<http://example.org/amp> doap:name "Amplifier" .
which describe a plugin with the name “Amplifier”.
Two implications of this format are important to understand here:
All data is a set of triples which can be stored in some lexicographical order to be quickly searchable (for example, a set ordered subject-first can be used to quickly find triples that start with a given subject).
All data can be streamed via a simple “flat” interface (for example a function with three parameters), and is trivial to inspect and/or filter on the fly (much like line-based text in POSIX pipelines).
The data may not be stored as a “literal” ordered set of triples (they're actually quads in memory for one thing), but this simplified way of thinking about it is good enough for this explanation.
Which order is best depends on the query.
For example (borrowing a bit of syntax from SPARQL where ?name represents a query variable), if the host asks something like “what's the name of this plugin” or
<http://example.org/amp> doap:name ?name .
then it needs to find triples that start with the given subject and predicate (<http://example.org/amp> and doap:name) to see what object (?name) they have.
So, a subject-predicate-object or “SPO” index will work well.
If, however, the host asks something like “which things are plugins” or
?plugin rdf:type lv2:Plugin .
then an SPO index doesn't help because there's no known subject to search for. Most queries are like this, with either a subject or object wildcard (querying relatively “fixed” predicates is rare), so lilv has always had both an SPO and OPS index to support them.
This is convenient, but twice the indexing means roughly twice the overhead. The SPO index is the natural order used in the syntax, and supports most code (which mainly looks up properties of known things), but the OPS index isn't used so much. Can it be removed entirely to speed things up? It is used for many important things, but conveniently, there's only a few fixed cases of those (like finding plugins as above). So, we can take advantage of the streaming nature of the data to record this information while it's being read, instead of inserting it into an index only to query it out later.
To do this in the implementation, I introduced the concept of a “skimmer”.
A skimmer inserts triples into a model as usual, but first "skims" them and records items of interest for later use.
For example, a skimmer checks whether a triple has rdf:type lv2:Plugin, and if so, records the subject in a result set that stores only plugin URIs.
Some cases are a bit trickier, and actually pulling this off cleanly took quite an overhaul, but details aside, it turns out that this approach can be used to eliminate the OPS index entirely without losing any functionality.
How much of an improvement does this make?
On this machine, using lv2ls -n as a crude benchmark, the time goes from 3.11 to 1.72 seconds, or about a 45% improvement.
The memory consumption goes down a bit as well, from (even more crudely) a max-RSS of about 138 to 112 MiB, or about a 19% improvement (everything here is an average of three runs).
The improvement will vary dramatically based on what's installed, for example in some earlier tests with a different configuration I saw drops from around 7 to 4 seconds, but in general, not bad!
Are there any downsides to this? Yes, primarily two:
As with any significant change, there is the possibility of regression. Discovery is a little more restricted than before, so although I've done my best to test things, there is a possibility of things not being discovered anymore. Usually the fix for this is adding information to the manifest that should have been there anyway.
Though the implementation itself doesn't make queries that require the OPS index, hosts themselves can since lilv provides generic query functions.
To support this, there's a new boolean option, LILV_OPTION_OBJECT_INDEX, which can be used to enable or disable the OPS index.
Since most hosts don't need it, I decided to disable this by default.
That will be a regression for hosts that do, however, who need to explicitly opt in to the old behaviour by enabling this option.
A warning is printed if a query will be slow because of the missing index, so it should at least be obvious if this happens.
These changes are now in the main branch in git, which will be released soon, probably as version 0.26.0.
Demonstration of the b4Modular synthesizer Series 7 by Malte Steiner. The system features 2 analog Oscillators / LFO, one digital oscillator with 6 different modes, oscillator bank with 6 square waves, triple clock module, 3 slew limiters, a lowpass filter, tone control filter, wave folder, one ring mod / wave folder thingy, 5 VCAs, crossfader, mixer, 2 pressure sensors, a trigger button, unity and gates mixer.
"My diy modular synthesizer in a suitcase which I developed between 2024 and 2025. The goal was to develop a cheap modular system mainly for live concerts which is repairable and can go into Checkin Luggage without much worries (I would never do that with my Eurorack). So far I used that system for several concerts of my projects Elektronengehirn and Notstandskomitee in Berlin and Helsinki, and local Jam sessions here in Aalborg. It is build in a Nanuk 923 case which can remove the lid, the rails are made of wood and wood screws, the front plates are 3D printed. Everything works fine and the concerts were great, but learnings so far:
- the frame is rigidly attached to the case so any shock impacts directly the system. So far one of my 3D printed brackets broke which didn't hinder a concert. I redesigned it to be more sturdy and it never happened since. But the rigid design is a bit questionable and I rethink the approach.
- the PCBs have been fixed to the frontplates with common metal screws and nuts. From the travel one nut unscrewed itself because of the vibration. I replaced it with nylon screws and nuts which have more grip. It remembers of a story from a Berlin company which created custom modular synths for Tangerine Dream back then. They tested the sturdiness against vibration by dragging those flight cases over a copplestone street at night until police stopped them asking what the hell they were doing.
- I hit a limit with my power supply design with a self made voltage splitter and an additional 7805 on the positive rail. It can't handle many microcontroller based modules before it collapses. In future systems I use another approach for the power supply which is much more stabile."
by herrsteiner (noreply@blogger.com) at September 22, 2025 09:02 AM
This post is to celebrate a few things despite the events that are clouding our feelings. 😠
Another thing to not celebrate is the slaughtering by Sourceforge of my developer web site, which they are calling "sunsetting", by October. I've already migrated it.
On the other, brighter hand, I'm celebrating this week La Mercè, which is the local festivity of Barcelona.
You may download it from GitHub (source code and APK), or you may get it from the IzzyOnDroid repository which is available in the F-Droid app, but also on Neo-Store, Droid-ify, and the unofficial IzzyOnDroid app.
If you already have the F-Droid app, you only need to add the IzzyOnDroid repository in Settings>Repositories and install it today, or you may prefer to use the official F-Droid repo.
I would like to add to the celebration a video live streaming concerto, but I am too lazy and odd playing for that. Better use this wonderful rendering of the Tchaikovsky Violin concerto by TwoSet Violin, with Brett Yang playing the soloist and Eddy Chen the rest of the orchestra. Enjoy!
by Pedro (noreply@blogger.com) at September 20, 2025 05:52 PM
The Ubuntu Studio team is pleased to announce the beta release of Ubuntu Studio 25.10, codenamed “Questing Quokka”.
While this beta is reasonably free of any showstopper installer bugs, you will find some bugs within. This image is, however, mostly representative of what you will find when Ubuntu Studio 25.10 is released on October 9, 2025.
We encourage everyone to try this image and report bugs to improve our final release. Pay specific attention to apps that might need to be forced to run inside Xwayland so we can patch their launchers.
The Ubuntu Studio 25.10 beta image (ISO) exceeds 4 GB and cannot be downloaded to some file systems such as FAT32 and may not be readable when burned to a DVD. For this reason, we recommend downloading to a compatible file system. When creating a boot medium, we recommend creating a bootable USB stick with the ISO image or burning to a Dual-Layer DVD.
Images can be obtained from this link: https://cdimage.ubuntu.com/ubuntustudio/releases/25.10/beta/
Full updated information, including Upgrade Instructions, are available in the Release Notes.
This release is more evolutionary rather than revolutionary. While we work hard to bring new features, this one was not one where we had anything major to report. Here are a few highlights:
There are many other improvements, too numerous to list here. We encourage you to look around the freely-downloadable ISO image.
Further known issues, mostly pertaining to the desktop environment, can be found at https://wiki.ubuntu.com/QuestingQuokka/ReleaseNotes/Kubuntu
Additionally, the main Ubuntu release notes contain more generic issues: https://discourse.ubuntu.com/t/questing-quokka-release-notes/
Please test using the test cases on https://iso.qa.ubuntu.com. All you need is a Launchpad account to get started.
Additionally, we need financial contributions. Our project lead, Erich Eickmeyer, is working long hours on this project and trying to generate a part-time income. Go here to see how you can contribute financially (options are also here in the sidebar).
Q: Does Ubuntu Studio contain snaps?
A: Yes. Mozilla’s distribution agreement with Canonical changed, and Ubuntu was forced to no longer distribute Firefox in a native .deb package. We have found that, after numerous improvements, Firefox now performs just as well as the native .deb package did.
Thunderbird is also a snap in order for the maintainers to get security patches delivered faster. This is done by the Thunderbird team in cooperation with Canonical.
Additionally, Freeshow is an Electron-based application. Electron-based applications cannot be packaged in the Ubuntu repositories in that they cannot be packaged in a traditional Debian source package. While such apps do have a build system to create a .deb binary package, it circumvents the source package build system in Launchpad, which is required when packaging for Ubuntu. However, Electron apps also have a facility for creating snaps, which can be uploaded and included. Therefore, for Freeshow to be included in Ubuntu Studio, it had to be packaged as a snap.
Also, to keep theming consistent, all included themes are snapped in addition to the included .deb versions so that snaps stay consistent with out themes.
We are working with Canonical to make sure that the quality of snaps goes up with each release, so we please ask that you give snaps a chance instead of writing them off completely.
Q: If I install this Beta release, will I have to reinstall when the final release comes out?
A: No. If you keep it updated, your installation will automatically become the final release.
Q: Will you make an ISO with {my favorite desktop environment}?
A: To do so would require creating an entirely new flavor of Ubuntu, which would require going through the Official Ubuntu Flavor application process. Since we’re completely volunteer-run, we don’t have the time or resources to do this. Instead, we recommend you download the official flavor for the desktop environment of your choice and use Ubuntu Studio Installer to get Ubuntu Studio – which does *not* convert that flavor to Ubuntu Studio but adds its benefits.
Q: What if I don’t want all these packages installed on my machine?
A: We now include a minimal install option. Install using the minimal install option, then use Ubuntu Studio Installer to install what you need for your very own content creation studio.
Hi all,
Change-log:
Description:
Website:
Project page:
Downloads:
Git repos:
Wiki:
License:
Enjoy && Have fun!
Hello all, this is the monthly report for all software things related to KXStudio, DISTRHO & falkTX projects.
Some applications in the KXStudio Website repositories' pages have been hidden and some plugins have been marked as "abandoned".
Everything is still available to install through "apt-get" though.
That is all for now, see you next month!
London is very well served for independent cinemas, often showing classics, obscura and independent films that mainstream cinemas don’t have.
But, it’s not trivial to find or keep track of the films you’re interested in. There’s no way to search for a film across all the cinemas, or even to see what’s on today, without painstakingly checking all the individual cinema sites. It’s very easy to miss a rare theatrical showing of a beloved film.
So, I made filmhose.uk.
FilmHose lets you browse each day’s listings for the next couple of months. You can choose between the full listings or the “distilled” listings, which have less noise from the big current releases that you can see “anywhere”. You can also select only the cinemas you’re interested in, if you don’t think you’ll ever make it to Romford or whatever (although the Lumiere Romford is cool, you should make the effort). You can also search by title if you want to know where and when a specific film will be showing.
A more commercially focused post would probably skip this section, but I’m not that so I’ll share some caveats:
At some point maybe I’ll just ask them if I can have their listings, like it’s the twentieth century or something. Or some of them have few enough that I could enter them manually. But for now I’m just doing the lazy thing and omitting them.
So far it seems to be working out pretty well. I’m able to get data for 27 cinemas, currently covering about 700 separate films, 2500 showtimes, with an average of 36 film options and 67 showtimes per day. Film lovers in London are pretty blessed, especially when you consider that’s not including the big chains.
The site loads very quickly and has very little extraneous nonsense, for me it’s easily the best way to see what’s on that’s interesting. I hope other people will find that too.
You can’t, it’s a free website with no login. Just go to filmhose.uk.
But if you really want to sign up for something you can follow on X / Twitter or Bluesky.
Hello all, it has been a while since the last project update/news.
Life has been very chaotic and I was not able to pay too much attention to "optional" projects, other things needed priority.
Now with work and housing situation sorted and also some holidays, it is the right time to give some general project update.
That said, I always have trouble writing these kind of updates, taking me quite some time to go through each individual thing that happened, giving it an explanation/reason, plans for future, etc.
So starting this month, KXStudio project updates will be more formal and generic so I can mostly copy & paste between each one, keeping the same format but just changing the content.
Some applications in the KXStudio repositories do not run on new systems and have also been abandoned by their official upstream authors, I will soon remove some of them.
That is all for now, see you next month!
A touch of music
Audio – Stefan Westerfeld's blog
Audio, Linux and the combination
Blog - Ardour
FreqRush - experiences with shared audiosoftware
GStreamer News
Home on Libre Arts
Hometracked
Internet Archive - Collection: osmpodcast
JACK Audio Connection Kit News
KXStudio News
Linux Archives - CDM Create Digital Music
Linux Audio Conference 2018
Linux Recording
LinuxMuso
MOD Audio website
Midichlorians in the blood
Musings on maintaining Ubuntu
News – Ubuntu Studio
Nothing Special
PipeManMusic
Robin Gareus
SFZ Format news
Testbit
Thorwil's
Using Open Source Software For Creative Purposes
aubio
blog4
digital audio hacks – Hackaday
drobilla.net - LAD
fundamental code
harryhaaren
joebutton.co.uk
linux-audio « WordPress.com Tag Feed
linux_audio – autostatic.com
m3ga blog
process();
rncbc.org - a.k.a. Rui Nuno Capela
Last updated:
October 26, 2025 03:02 PM
All times are UTC.
Powered by:
How merger works?
I cant figure it out how the merger works, It won't change anything. Is there more details how to use?
re. How merger works?
it just applies to active patchbay persistence:
so that, all nodes having the same name are treated as one (thus merged); most useful for setting persistent/pinned connection rules for media players that spawn a new node yet on every song, video, track or part, on play, pause, stop, replay or whatever...
actually useful for web browsers like "firefox", "chromium", etc.
byee
If I understand, if the…
If I understand, if the binary spawns line "app.1", "app.2" nodes, etc, they will connect to the same nodes I've connect "app" before?
re. If I understand, if the…
yes, exactly, as long "app" appears in the merger list.
Thank you, I think a get it.
Thank you, I think a get it.
Add new comment