Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

6 participants
7336 discussions

[ANN] The QStuff* Early-Spring'23 Release batch #1

by Rui Nuno Capela

Howdy! And here goes the first batch of the 'QStuff*': QjackCtl [1], Qsynth [2], Qsampler [3], QXGEdit [4], QmidiCtl [5] and QmidiNet [6], are now released for this Early-Spring'23 season. Enjoy. ** QjackCtl - JACK Audio Connection Kit Qt GUI Interface [1] ** QjackCtl 0.9.10 (early-spring'23) is out! QjackCtl is an aged yet modern, not so 'simple' anymore, Qt [7] application to control the JACK [8] sound server, for the Linux Audio [12] infrastructure. Change-log: - Setup: revert to previous settings when dismissing the dialog. - Graph: Attempt to make port labels as short as possible. - Graph: introducing touch pinch-gesture for zooming. Website: https://qjackctl.sourceforge.io http://qjackctl.sourceforge.net Project page: https://sourceforge.net/projects/qjackctl Downloads: https://sourceforge.net/projects/qjackctl/files - source tarball: https://download.sf.net/qjackctl/qjackctl-0.9.10.tar.gz - source package: https://download.sf.net/qjackctl/qjackctl-0.9.10-54.1.rncbc.suse.src.rpm - binary packages: https://download.sf.net/qjackctl/qjackctl-0.9.10-54.1.rncbc.suse.x86_64.rpm - AppImage [20] package: https://download.sf.net/qjackctl/qjackctl-0.9.10-54.1.x86_64.AppImage Git repos: https://git.code.sf.net/p/qjackctl/code https://github.com/rncbc/qjackctl.git https://gitlab.com/rncbc/qjackctl.git https://codeberg.com/rncbc/qjackctl.git ** Qsynth - A FluidSynth Qt GUI Interface [2] ** Qsynth 0.9.10 (early-spring'23) is out! Qsynth is a FluidSynth [10] GUI front-end application written in C++ around the Qt framework [7] using Qt Designer. Change-log: - Bumping copyright headers to the brand new year. Website: https://qsynth.sourceforge.io http://qsynth.sourceforge.net Project page: https://sourceforge.net/projects/qsynth Downloads: https://sourceforge.net/projects/qsynth/files - source tarball: https://download.sf.net/qsynth/qsynth-0.9.10.tar.gz - source package: https://download.sf.net/qsynth/qsynth-0.9.10-54.1.rncbc.suse.src.rpm - binary packages: https://download.sf.net/qsynth/qsynth-0.9.10-54.1.rncbc.suse.x86_64.rpm - AppImage [20] package: https://download.sf.net/qsynth/qsynth-0.9.10-54.1.x86_64.AppImage - Flatpak [21] package (thanks to Pedro Lopez-Cabanillas): https://flathub.org/apps/details/org.rncbc.qsynth Git repos: https://git.code.sf.net/p/qsynth/code https://github.com/rncbc/qsynth.git https://gitlab.com/rncbc/qsynth.git https://codeberg.com/rncbc/qsynth.git ** Qsampler - A LinuxSampler Qt GUI Interface [3] ** Qsampler 0.9.9 (early-spring'23) is out! Qsampler is a LinuxSampler [11] GUI front-end application written in C++ around the Qt framework [7] using Qt Designer. Change-log: - Bumping copyright headers to the brand new year. Website: https://qsampler.sourceforge.io http://qsampler.sourceforge.net Project page: https://sourceforge.net/projects/qsampler Downloads: https://sourceforge.net/projects/qsampler/files - source tarballs: https://download.sf.net/qsampler/qsampler-0.9.9.tar.gz https://download.sf.net/qsampler/liblscp-0.9.9.tar.gz - source packages: https://download.sf.net/qsampler/qsampler-0.9.9-53.1.rncbc.suse.src.rpm https://download.sf.net/qsampler/liblscp-0.9.9-53.1.rncbc.suse.src.rpm - binary packages: https://download.sf.net/qsampler/qsampler-0.9.9-53.1.rncbc.suse.x86_64.rpm https://download.sf.net/qsampler/liblscp6-0.9.9-53.1.rncbc.suse.x86_64.rpm https://download.sf.net/qsampler/liblscp-devel-0.9.9-53.1.rncbc.suse.x86_64… - AppImage [20] package: https://download.sf.net/qsampler/qsampler-0.9.9-53.1.x86_64.AppImage Git repos: https://git.code.sf.net/p/qsampler/code https://github.com/rncbc/qsampler.git https://gitlab.com/rncbc/qsampler.git https://codeberg.com/rncbc/qsampler.git https://git.code.sf.net/p/qsampler/liblscp https://github.com/rncbc/liblscp.git https://gitlab.com/rncbc/liblscp.git https://codeberg.com/rncbc/liblscp.git ** QXGEdit - A Qt XG Editor [4] ** QXGEdit 0.9.9 (early-spring'23) is out! QXGEdit is a live XG instrument editor, specialized on editing MIDI System Exclusive files (.syx) for the Yamaha DB50XG [14] and thus probably a baseline for many other XG devices. Change-log: - Drum Setup is being made possible for any drum-kit, with some provided default values, not just for the default Standard Kit anymore. Website: https://qxgedit.sourceforge.io http://qxgedit.sourceforge.net Project page: https://sourceforge.net/projects/qxgedit Downloads: https://sourceforge.net/projects/qxgedit/files - source tarball: https://download.sf.net/qxgedit/qxgedit-0.9.9.tar.gz - source package: https://download.sf.net/qxgedit/qxgedit-0.9.9-53.1.rncbc.suse.src.rpm - binary packages: https://download.sf.net/qxgedit/qxgedit-0.9.9-53.1.rncbc.suse.x86_64.rpm - AppImage [20] package: https://download.sf.net/qxgedit/qxgedit-0.9.9-53.1.x86_64.AppImage Git repos: https://git.code.sf.net/p/qxgedit/code https://github.com/rncbc/qxgedit.git https://gitlab.com/rncbc/qxgedit.git https://codeberg.com/rncbc/qxgedit.git ** QmidiCtl - A MIDI Remote Controller via UDP/IP Multicast [5] ** QmidiCtl 0.9.9 (early-spring'23) is out! QmidiCtl [5] is a MIDI remote controller application that sends MIDI data over the network, using UDP/IP multicast. Inspired by multimidicast [15] and designed to be compatible with ipMIDI [15] for Windows. QmidiCtl [5] was long ago designed for the Maemo [17] enabled handheld devices, namely the late Nokia N900 [18] and promoted to the Maemo Package [18] repositories. Nevertheless, QmidiCtl [5] may still be found effective as a regular desktop application and recently as an Android application as well. Change-log: - Bumping copyright headers to the brand new year. Website: https://qmidictl.sourceforge.io http://qmidictl.sourceforge.net Project page: https://sourceforge.net/projects/qmidictl Downloads: https://sourceforge.net/projects/qmidictl/files - source tarball: https://download.sf.net/qmidictl/qmidictl-0.9.9.tar.gz - source package: https://download.sf.net/qmidictl/qmidictl-0.9.9-53.1.rncbc.suse.src.rpm - binary packages: https://download.sf.net/qmidictl/qmidictl-0.9.9-53.1.rncbc.suse.x86_64.rpm - AppImage [20] package: https://download.sf.net/qmidictl/qmidictl-0.9.9-53.1.x86_64.AppImage - Android packages: https://download.sf.net/qmidictl/qmidictl-0.9.9-53.1.arm64-v8a.apk https://download.sf.net/qmidictl/qmidictl-0.9.9-53.1.x86_64.apk https://play.google.com/store/apps/details?id=org.rncbc.qmidictl Git repos: https://git.code.sf.net/p/qmidictl/code https://github.com/rncbc/qmidictl.git https://gitlab.com/rncbc/qmidictl.git https://codeberg.com/rncbc/qmidictl.git ** QmidiNet - A MIDI Network Gateway via UDP/IP Multicast [6] ** QmidiNet 0.9.9 (early-spring'23) is out! QmidiNet is a MIDI network gateway application that sends and receives MIDI data (ALSA-MIDI [9] and JACK-MIDI [8]) over the network, using UDP/IP multicast. Inspired by multimidicast [15] and designed to be compatible with ipMIDI [16] for Windows. Change-log: - Bumping copyright headers to the brand new year. Website: https://qmidinet.sourceforge.io http://qmidinet.sourceforge.net Project page: https://sourceforge.net/projects/qmidinet Downloads: https://sourceforge.net/projects/qmidinet/files - source tarball: https://download.sf.net/qmidinet/qmidinet-0.9.9.tar.gz - source package: https://download.sf.net/qmidinet/qmidinet-0.9.9-53.1.rncbc.suse.src.rpm - binary packages: https://download.sf.net/qmidinet/qmidinet-0.9.9-53.1.rncbc.suse.x86_64.rpm - AppImage [20] package: https://download.sf.net/qmidinet/qmidinet-0.9.9-53.1.x86_64.AppImage Git repos: https://git.code.sf.net/p/qmidinet/code https://github.com/rncbc/qmidinet.git https://gitlab.com/rncbc/qmidinet.git https://codeberg.com/rncbc/qmidinet.git -- License: All of the Qstuff* are free, open-source Linux Audio [11] software, distributed under the terms of the GNU General Public License (GPL) version 2 or later [12]. References: [1] QjackCtl - A JACK Audio Connection Kit Qt GUI Interface https://qjackctl.sourceforge.io [2] Qsynth - A fluidsynth Qt GUI Interface https://qsynth.sourceforge.io [3] Qsampler - A LinuxSampler Qt GUI Interface https://qsampler.sourceforge.io [4] QXGEdit - A Qt XG Editor https://qxgedit.sourceforge.io [5] QmidiCtl - A MIDI Remote Controller via UDP/IP Multicast https://qmidictl.sourceforge.io [6] QmidiNet - A MIDI Network Gateway via UDP/IP Multicast https://qmidinet.sourceforge.io [7] Qt framework, C++ class library and tools for cross-platform application and UI development https://qt.io/ [8] JACK Audio Connection Kit https://jackaudio.org [9] ALSA, Advanced Linux Sound Architecture https://www.alsa-project.org/ [10] FluidSynth - A SoundFont Synthesizer A real-time software synthesizer based on SoundFont 2 specifications https://www.fluidsynth.org [11] LinuxSampler - The Linux Sampler Project A modular, streaming capable, realtime audio sampler https://www.linuxsampler.org [12] Linux Audio consortium of libre software for audio-related work https://linuxaudio.org [13] GPL - GNU General Public License https://www.gnu.org/copyleft/gpl.html [14] Yamaha DB50XG (https://web.archive.org/web/20150607065739/) http://www.soundonsound.com/sos/1996_articles/may96/yamahadb50xg.html [15] multimidicast - sends and receives MIDI from ALSA sequencers over network https://llg.cubic.org/tools/multimidicast [16] ipMIDI - MIDI over Ethernet ports - send MIDI over your LAN https://nerds.de [17] Maemo.org - Home of the Maemo community https://www.maemo.org [18] Maemo.org Wiki - Nokia N900 https://wiki.maemo.org/Nokia_N900 [19] Maemo.org - Downloads: QmidiCtl https://maemo.org/downloads/product/Maemo5/qmidictl [20] AppImage, Linux apps that run anywhere https://appimage.org/ [21] Flatpak, next-generation technology for building and distributing desktop applications on Linux https://flatpak.org/ See also: https://www.rncbc.org/drupal/node/2424 See you all next time! -- rncbc aka Rui Nuno Capela

21 hours, 52 minutes

Status of Pipewire

by Fons Adriaensen

Hello all, I've been contemplating trying out Pipewire as a replacement for Jack. What is holding me back is a what seems to be a serious lack of information. I'm not prepared to spend a lot of time and risk breaking a perfectly working system just to find out that it was a bad idea from the start. So I have a lot of questions which maybe some of you reading this can answer. Thanks in advance for all useful information. A first thing to consider is that I actually *like* the separation of the 'desktop' and 'pro audio' worlds that using Jack provides. I don't want the former to interfere (or just be able to do so) with the latter. Even so, it may be useful in some cases to route e.g. browser audio or a video conference to the Jack world. So the ideal solution for me would be the have Pipewire as a Jack client. So first question: Q1. Is that still possible ? If not, why not ? If the answer is no, then all of the following become relevant. Q2. Does Pipewire as a Jack replacement work, in a reliable way [1], in real-life conditions, with tens of clients, each maybe having up to a hundred ports ? Q3. What overhead (memory, CPU) is incurred for such large systems, compared to plain old Jack ? A key feature of Jack is that all clients share a common idea of what a 'period' is, including its timing. In particular the information provided by jack_get_cycle_times(), which is basically the state of the DLL and identical for all clients in any particular period. Now if Pipewire allows (non-Jack) clients with arbitrary periods (and even sample rates) Q4. Where is the DLL and what does it lock to when Pipewire is emulating Jack ? Q5. Do all Jack clients see the same (and correct) info regarding the state of the DLL in all cases ? The only way I can see this being OK would be that the Jack emulation is not just a collection of Pipewire clients which happen to have compatible parameters, but actually a dedicated subsystem that operates almost independently of what the rest of Pipewire is up to. Which in turn means that having Pipewire as a Jack client would be the simpler (and hence preferred) solution. [1] which means I won't fall flat on my face in front of a customer or a concert audience because of some software hickup. Ciao, -- FA

3 days, 22 hours

Happy birthday, LAC! 20 years, and..going? Strong?

by Frank Neumann

Hi all, not posting to any of LA* mailing lists often in the last years, but today I thought I should make an exception to point out that it's now exactly 20 years ago that the first Linux Audio Conference or "LAC" for short (then still called "Linux Audio Developer's Meeting") took place at the ZKM in Karlsruhe, Germany. https://lists.linuxaudio.org/hyperkitty/list/linux-audio-dev@lists.linuxaud… Wow, 20 years come and gone so quickly! It's great to see a couple of "early adopters" are still around today here, and many new names have entered the scene in the meantime and left/leave a lasting footprint in it. As a quick "trip down memory lane", here's a short list of things that happened back then: - Takashi Iwai dove into the innards of an ALSA driver - Fernando Lopez-Lezcano introduced the PlanetCCRMA distribution, based on Fedora - Steve Harris explained the concept of a Bode frequency shifter as a LADSPA plugin - Paul Davis held the keynote, AND spoke about JACK, AND shared his experience of writing a DAW that is at the forefront of free, open-source and cross-platform DAWs today. - Dave Philipps looked at the historic development of Linux audio, from OSS to ALSA and beyond - Jörn Nettingsmeier managed to get the audio part of the presentations both recorded AND live-streamed at a time when "streaming" was still a term unknown to most of us. - The term "Linux Sound Night" already existed, but was..perhaps not as musical yet as you might have expected :-). - And, we also learned that schedules are not easy to keep - I believe after the first day we ran some >2 hours late, and people begin to STARVE. - Posing in front of the ZKM "Kubus": https://linuxaudio.de/LAC2003_Posse.jpg For some more memories, see also http://lac.linuxaudio.org/2003/zkm/ Of course, on the downside it has to be noted that Corona has impacted us too - after an almost perfect track record of conferences or mini-conferences every year, 2021 and 2022 didn't see any event happening. There is a certain risk now that it won't recover, but that's in our hands to change (sidenote: I have talked to my contacts at ZKM here in Karlsruhe in January, but they are unable to finance and/or organize an event of this size at the moment - certainly somewhat influenced by current economics, but I am hearing ZKM has actually reduced their headcount quite a bit, and after the recent passing of its artistic-scientific chairman, Peter Weibel, it will have to be seen how his successor, Alistair Hudson, will steer it into the future). Whatever LAC's future will be, free and open-source audio software is certainly flourishing, and will continue to do so. It just would be soo nice to enjoy the results together with real, tangible people :-\. If anyone sees an option for hosting a future LAC, lac-team(a)lists.linuxaudio.org is willing to listen to proposals you might have (or just discuss it right here). Well, the heck - there is no steering committee or anything in place, so I guess the first one brave enough to say "I think we can do it" will get the job :-). I am forever grateful to all the folks who have enriched and continue to enrich our open-source audio life by writing or presenting software, creating documentation and tutorials, hosting (AND attending) conferences like the LAC, and whatever else helps to keep the penguin dancing! Greetings, Frank

1 week, 3 days

[semi-OT} c++20 concepts and syntax

by Jeanette C.

Hey hey, figuring out the syntax for c++20 concepts I run into challenges. With a two parameter template concept like swappable_with or convertible_to is it always necessary to use a requires statement like this: template<typename T> requires std::convertible_to<T,int> void f(T t) ... ... With single parameter concepts like integral a syntax like this will work: template<std::integral T> void f(T t)... Also with single parameter concepts a statement like this should work: std::integral auto my_variable; Will that work with a two parameter concept like the above convertible_to? I haven't seen/found a syntax which does it. Any help is appreciated, definitely including a good read that WILL demonstrate or demystify these things. Best wishes, Jeanette -- * Website: http://juliencoder.de - for summer is a state of sound * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g * Audiobombs: https://www.audiobombs.com/users/jeanette_c * GitHub: https://github.com/jeanette-c Don't care about money It doesn't give me half the thrill <3 (Britney Spears)

2 weeks, 1 day

[LAA] Programming LV2 Music Production Plugins Tutorial Series II

by Sven Jaehnichen

Hi, a story to continue. I'll release a second block of video tutorials about LV2 plugin programming from the scratch. For everybody who wants to make his/her own plugins. This time about graphical user interfaces. I'll show you: * the LV2 way to go, with turtle and C/C++, * toolkits and the pitfalls, * some of the toolkits we can use, and * finally how to make UIs for the plugins we made before. Every Friday, for the next some 10 weeks. Starting with this announcement video: https://youtu.be/7mCLDBBXajU See you on Friday Sven

2 weeks, 3 days

SoundTracker 1.0.4-pre1 released

by Yury Alyaev

Hi all, I just have released SoundTracker v1.0.4-pre1. I've decided to make a feature-freeze at this point, this means that 1.0.4 will have no new features comparing to this pre-release, only fixes and small improvements if something will be found inconvenient. So I ask everyone who has interest in SoundTracker to test this release. Here are main features of the 1.0.4-pre1 release comparing to 1.0.3: * General: - Full-screen mode - Volume of all samples of an instrument / all samples in the module can be set to a value, not only gained. Also all samples panning can be adjusted. These functions can also modify the explicitly given values of volume / panning of notes in patterns - Improved compatibility with FastTracker, also MOD files are played more correctly - Unused patterns are listed in the Pattern Sequence Editor - Sampling rate can be specified while saving a sample as WAV - New module optimizer with many control parameters * Track Editor: - Moving notes up / down is implemented * Sample Editor: - External programs can be used for samples processing. The interaction between such a program is described using XML spec, no ST recompiling required - The whole sample is drawn after recording - Exponential / reverse exponential volume fade transients * Instrument Editor: - Envelope inversion and shifting is implemented SoundTracker download page: https://sourceforge.net/projects/soundtracker/files/ Regards, Yury.

3 weeks, 2 days

Timed MIDI event handling

by Jeanette C.

Hey hey, I want to record MIDI into a sequencer application, using RtMidi. My understanding is: inside that application's tracks events are directly stamped with delta times, measured in ticks, since the last event in that track. Internally the sequencer runs a clock at a high rate (480PPQ or higher). It's probably best to "quantise" events to that internal clock while they are recorded. So the track object, with its connected MIDI input device, must be linked to the clock, which will wake up, whenever it is time for a tick. Linked meaning there must be some way to exchange relevant info (one of them owning a reference, callback, shared data, ...) If that basic, and simplified, principle is sound. Which solutions have been proven feasible to achieve that? For example: make every active track a thread and have a global mutex? Each track registers a callback function with the clock to store events. ...? RtMidi's input object (RtMidiIn) offers to register a callback function, that will be called with a received MIDI message, when input is available. Such messages could be stored in a container and be delivered when it's tick time. -- So again, a track might own a reference to the Clock thread object and query the current tick count since the last record start command and use that information to calculate the correct delta. Not sure though, whether that might raise issues with execution times. Using an atomic variable as a tick counter will avoid having to use mutex locks, at least. Is there any practical advice? Something based on experience? A good read? Best wishes and thanks, Jeanette -- * Website: http://juliencoder.de - for summer is a state of sound * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g * Audiobombs: https://www.audiobombs.com/users/jeanette_c * GitHub: https://github.com/jeanette-c But now I'm stronger than yesterday <3 (Britney Spears)

3 weeks, 4 days

Calculating logarithmic curve for controller automation

by Jeanette C.

Hey hey, how is a logarithmic curve usually programmed in a DAW or sequencer? Do you scale the values of (log1) to log(2) to the desired range and stretch it over time? Do you ajudst steepness by either using more less of the log function or changing both values like log(20) to log(21)? I'm sure there are many ways to do it, but I'd assume that there are a few "classic" ways to approach this with anything from controller "automation" to envelope curve settings to ... I'd appreciate any hints or simple examples from software practise. Best wishes and thanks, Jeanette -- * Website: http://juliencoder.de - for summer is a state of sound * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g * Audiobombs: https://www.audiobombs.com/users/jeanette_c * GitHub: https://github.com/jeanette-c Baby, take the time to realize I'm not the kind to sacrifice <3 (Britney Spears)

4 weeks

Tempo change functions.

by Fons Adriaensen

Hello all, What exactly is meant by a linear or exponential tempo change ? Is the tempo a lin/exp function of time, or of score position ? A bit of algebra leads to this: Let t = time (seconds) p = score position (beats) v = tempo (beats / second) [1] We have v = dp / dt # by definition If v is a linear function of t, then v (p) = square root of a linear fuction of p If v is a exponential function of t, then v (p) = a linear function of p if v is a linear function of p then v (t) = an exponential function of t If v is an exponential function of p, then v (t) = inverse of a linear function of t So there is plenty of room for confusion... [1] Using SI units :-) Ciao, -- FA

4 weeks

Admissable clock inaccuracy for MIDI

by Jeanette C.

Hey hey, I'm experimenting with c++ trying to program something nice for MIDI. I'm now experimenting with clocks, using both the standard c++ chrono library and the boost chrono library. My example program sets a desired delta between ticks of 250ms. I see that there is a difference, since Boost chrono can also use pthread thread parameters foor realtime scheduling and priorities. With the standard chrono and thread library my ticks are usually out by anything between 150.000 to 290.000 nanoseconds. Using boost a tick is out anything between 110.000 to 124.000 nanoseconds. Yes, much better. But, assuming that I correct the drift, does it make a difference for MIDI instruments? I know one of my MIDI instruments with a clock sync'able delay can be rather touchy with MIDI clocks, but are there good estimated guidelines experience values how precise ticks should be? Best wishes and thanks for any help, Jeanette -- * Website: http://juliencoder.de - for summer is a state of sound * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g * Audiobombs: https://www.audiobombs.com/users/jeanette_c * GitHub: https://github.com/jeanette-c Top down, on the strip Lookin' in the mirror I'm checkin' out my lipstick <3 (Britney Spears)

4 weeks, 1 day

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-dev