Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

3 participants
7448 discussions

The mysterious revival of www.nekosynth.co.uk

by Gordonjcp

Hi folks, Some of you may recall that about ten years ago I wrote some LADSPA and DSSI plugins and hosted them on a Trac install on www.nekosynth.co.uk until I moved away from doing music with computers, and gradually the site became abandoned and the domain lapsed. Someone pointed out that the site is back up on https://www.nekosynth.co.uk with a load of content downloaded from archive.org and indeed there it is - loads of it although the audio examples are missing. This is seriously weird. Like, really, really weird. It wasn't one of you lot, was it? I'd love to try and get in touch with whoever put considerable effort into setting it up. If anyone knows anything I'd appreciate the information. -- Gordonjcp

3 years, 10 months

Fluida.lv2 - Fluidsynth a LV2 plugin

by Hermann Meyer

Hi This is the initial release of Fluida.lv2 Fluida is a wrapper around Fluidsynth https://github.com/FluidSynth/fluidsynth allowing to load and control Fluidsynth as LV2 plugin within your DAW. Fluida is knowing to run well with lv2vst https://github.com/x42/lv2vst wrapped as VST2 for the case your DAW didn't support the LV2 standard. project page is here: https://github.com/brummer10/Fluida.lv2 initial release is here: https://github.com/brummer10/Fluida.lv2/releases/tag/v0.5 regards hermann

3 years, 10 months

DrumGizmo 0.9.19 released

by Bent Bisballe Nyeng

DrumGizmo 0.9.19 Released! DrumGizmo is an open source, multichannel, multilayered, cross-platform drum plugin and stand-alone application. It enables you to compose drums in midi and mix them with a multichannel approach. It is comparable to that of mixing a real drumkit that has been recorded with a multimic setup. This release is a feature release with some rather interesting new features in it. Highlights: * Default midimaps now read from drumkit file so no explicit loading of midimap are needed for kits that provide these. * Add OSX retina display UI scaling. * Sample selection default values improved * UI rendering speed improvements * New powermap feature, to make it easier to get a good natural feeling when playing a midi-drumkit. * Improved dgvalidater tool to include a lot more validation checks. * Add gettext support to plugin UI with French translation. * Per instrument voice limit feature to enable playing very fast with low latency without the engine dropping out. * Resampling quality (and thereby cpu usage) can now be controlled. And a lot of bugfixes. As usual read the detailed description of all the new shiny features, see the detailed changelog: [1]. And now, without further ado, go grab 0.9.19!!! [2] [1]: https://drumgizmo.org/wiki/doku.php?id=changelog:drumgizmo-0.9.19 [2]: https://drumgizmo.org/wiki/doku.php?id=getting_drumgizmo

3 years, 10 months

Alpha release of zita-avc1

by Fons Adriaensen

Zita-avc1 0.1.0 ---------------- 'Analog' style vocoder, inspired by the famous EMS vocoders from the 1970's. Standalone app, using Jack for audio and MIDI I/O. Zita-avc1 uses two sets of 24, 6th order bandpass filters to analyse the voice input and to impose the same spectral envelope on another signal. The filters span a frequency range from approx. 70 Hz to 14 kHz. Filter spacing is 1/4 octave over most of this range. Voiced / Unvoiced detection is based on the power ratio of the high vs low frequency bands. A sawtooth oscillator and a noise source are provided, but normally you should use external signals, at least for the voiced excitation. Bright strings-like signals seem to work well, but anything with a dense 'pinkish' spectrum should do. The voice input should be a clean, full-bandwidth voice signal, speaking or singing. This is very much an alpha version, released to invite comments and suggestions. Future developments may include: - Pitch tracking. - Filter band matrix. - Store and recall formants with MIDI control. - ... See the README for a quick guide. Available at the usual place: <http://kokkinizita.linuxaudio.org/linuxaudio/downloads/zita-avc1-0.1.0.tar.…> Ciao, -- FA

3 years, 10 months

[LAU] [LAA] Mamba - Virtual Midi keyboard for Jack Audio Connection Kit release 1.8

by Hermann Meyer

Hi Mamba release v1.8 is out Mamba is a Virtual MIDI keyboard with some extended, unique features. Virtual MIDI Keyboard Mamba comes with some predefined key-maps, qwertz, qwerty, azerty(fr) and azerty(be), but you could define your own with the included Key-map Editor as well. Beside the computer keyboard and mouse, Mamba supports jack-interconnect-ALSA MIDI I/O. Every channel use it's own Color to display the played Notes per channel. Jack and ALSA connections could be managed within the connection menu. 16 Channel Live MIDI Looper: To record a loop, press "Play" and then to start recording press "Record". To stop recording press record again. Playback will start immediately. The first recorded channel will become the Master channel. This one set the time frame for all later recorded loops. For the Master Channel the recording time will be stretched/clipped to match the next full beat time point. To record a new loop, switch to a other channel, select your instrument and press "Record" again to start recording. The later recorded loops will be synced to the master loop. When the recording time extend the absolute Master loop time record will be switched off. Absolute time is not bound to the loop point, so you could record loops crossing it. You could as well stop recording by press "Record" again before the time expires. Each Channel could be cleared and re-recorded separate at any time. even when you press "Record" on a already recorded channel, it will be cleared before recording starts. You could record the connected input device or play the Keyboard itself. MIDI File player You could select a MIDI file with the File Selector, or just drag'n drop it in from your Filemanager. It will be loaded in the play buffer of the first channel, regardless how much channels it use. You could use then channel 2 - 16 to record your own playing into it. To play along with it you could use any channel. A loaded file will become the Master channel for the looper. To save your work just go to Menu -> "File" -> "Save MIDI file as", select the path and enter a file name. If you don't give the usual file extension Mamba will add the extension .midi befor save it. Fluidsynth When you load a Sound-font via the Menu -> "Fluidsynth" -> "Load Sound-font", or just drag'n drop it in from your Filemanager Mamba will start the Fluidsynth engine and do the needed connections so that you could just play along. Menu -> "Fluidsynth" -> "Settings" will pop-up a new Window were you could select the Instrument for the channel and do settings for Fluisynth Reverb and Chorus. All your Settings will be saved on exit, so on next start you could just play along. Mamba is released under the BSD Zero Clause License license The GUI is build on libxputty - A damn tiny abstraction Layer to create X11 window/widgets with cairo surfaces https://github.com/brummer10/libxputty To build Mamba from source, the following dependencies must be meat. * libfluidsynth-dev * libc6-dev * libsmf-dev * libcairo2-dev * libx11-dev * liblo-dev * libsigc++-2.0-dev * libjack-(jackd2)-dev * libasound2-dev So, here is the project page: https://github.com/brummer10/Mamba and here you'll find the last release: https://github.com/brummer10/Mamba/releases/tag/v1.8 regards hermann

3 years, 10 months

Linux audio Conference next Wednesday

by Thibaud Keller

Dear All, This year's Linux Audio Conference will start next Wednesday at 4:30 pm CET. For this 18th edition, the conference will take place remotely in this Big Blue Button room: https://visio.octopuce.fr/b/thi-wau-dt7-nxk Please find the program and the complete Artwork Playlist here: https://lac2020.sciencesconf.org/program https://tube.aquilenet.fr/videos/watch/playlist/3dc308f2-c8a6-4d28-b19b-4b1… The rest of the playlist will be updated with all recorded presentations during the event: https://tube.aquilenet.fr/video-channels/lac2020/video-playlists If you were hoping to do some sight-seeing when visiting us in Bordeaux, the following links will take you on a remote tour - which hopefully will give you some ideas for vacations after international travel resumes ! We are looking forward to seeing all of you and to all the verry promising presentations ! 'til Wednesday The LAC 2020 team *Vidéos* The city 1/ *https://www.youtube.com/watch?v=x3uJj0zVzm0* <https://www.youtube.com/watch?v=x3uJj0zVzm0> 2/ *https://www.youtube.com/watch?v=0bSDhaDzrqY* <https://www.youtube.com/watch?v=0bSDhaDzrqY> 3/ *https://www.youtube.com/watch?v=BiNl1IoshyA* <https://www.youtube.com/watch?v=BiNl1IoshyA> 4/ *https://www.youtube.com/watch?v=hcgj8uYwvSE* <https://www.youtube.com/watch?v=hcgj8uYwvSE> Musée d’Aquitaine : *https://www.youtube.com/watch?v=OcUJZXBV6w0* <https://www.youtube.com/watch?v=OcUJZXBV6w0> Museum d’histoire naturelle : *https://www.youtube.com/watch?v=v930TfV8eUA* <https://www.youtube.com/watch?v=v930TfV8eUA> Grand théâtre 1/ *https://www.youtube.com/watch?v=WzDR5F1lSTU* <https://www.youtube.com/watch?v=WzDR5F1lSTU> 2/ *https://www.youtube.com/watch?v=JFpS0JxWsp8* <https://www.youtube.com/watch?v=JFpS0JxWsp8> *360° Images* Palais Gallien *http://www.aquitaineonline.com/vision360/Palais-Gallien-Bordeaux.html* <http://www.aquitaineonline.com/vision360/Palais-Gallien-Bordeaux.html> Colonne des Girondins *http://www.aquitaineonline.com/vision360/Patrimoine-Bordeaux-Colonne-des-Girondins.html* <http://www.aquitaineonline.com/vision360/Patrimoine-Bordeaux-Colonne-des-Gi…> Pont Chaban – Port de la Lune *http://www.aquitaineonline.com/vision360/Pont-Jacques-Chaban-Delmas-Bordeaux-Port-de-la-Lune.html* <http://www.aquitaineonline.com/vision360/Pont-Jacques-Chaban-Delmas-Bordeau…> Place de la Bourse – Miroir d’eau 1/ *https://www.360images.fr/360/bordeaux/bourse.html?ml=1&iframe=1* <https://www.360images.fr/360/bordeaux/bourse.html?ml=1&iframe=1> 2/ *https://www.360images.fr/360/bordeaux/miroir_night.html?ml=1&iframe=1* <https://www.360images.fr/360/bordeaux/miroir_night.html?ml=1&iframe=1>

3 years, 10 months

some updated RT programming wisdom

by Jörn Nettingsmeier

It may be old news for seasoned programmers, but I found this to be a trove of information that goes a bit beyond of the traditional wisdom of "what's safe in a jack process() thread", so I thought I'd share it here (courtesy of LWN's free subscriber link feature, please check out LWN!) https://lwn.net/SubscriberLink/837019/e323ab1009054668/ https://ogness.net/ese2020/ese2020_johnogness_rtchecklist.pdf All best, Jörn -- Jörn Nettingsmeier Tuinbouwstraat 180, 1097 ZB Amsterdam, Nederland Tel. +49 177 7937487 Meister für Veranstaltungstechnik (Bühne/Studio), Tonmeister VDT http://stackingdwarves.net

3 years, 10 months

G++ trouble

by Fons Adriaensen

Hello all, I'm having a strange problem with G++... In one source file 'fb3data.cc', I define arrays like this: const float svcoeff44 [216] = { 1.631996e-03, 6.335480e-02, ... ... }; There are five of these. In 'fbdata3.h' I have extern const float svcoeff44 [216]; extern const float svcoeff48 [216]; extern const float svcoeff88 [216]; ... Finally in 'filtbank3.cc' there is const float *c; switch (fsam) { case 44100: c = cvcoeff44; break; case 48000: c = cvcoeff48; break; ... } Everything compiles without errors or warnings, but the linking step fails: /usr/bin/ld: filtbank3.o: warning: relocation against `svcoeff88' in read-only section `.text' /usr/bin/ld: filtbank3.o: in function `VocFiltbank::init(int)': filtbank3.cc:(.text+0x159): undefined reference to `svcoeff192' /usr/bin/ld: filtbank3.cc:(.text+0x1d3): undefined reference to `svcoeff48' /usr/bin/ld: filtbank3.cc:(.text+0x1e3): undefined reference to `svcoeff96' /usr/bin/ld: filtbank3.cc:(.text+0x1f3): undefined reference to `svcoeff44' /usr/bin/ld: filtbank3.cc:(.text+0x1ff): undefined reference to `svcoeff88' /usr/bin/ld: warning: creating DT_TEXTREL in a PIE collect2: error: ld returned 1 exit status When I put the arrays in 'filtbank3.cc' instead, everything works. Any hints ?? Ciao, -- FA

3 years, 10 months

Re: [LAD] G++ trouble

by Kjetil Matheussen

Alexandre DENIS: > On Mon, 16 Nov 2020 09:43:42 +0100 > Fons Adriaensen <fons(a)linuxaudio.org> wrote: > > > Hello all, > > > > I'm having a strange problem with G++... > > > > In one source file 'fb3data.cc', I define arrays like this: > > > > const float svcoeff44 [216] = > > { > > 1.631996e-03, 6.335480e-02, ... > > ... > > }; > > > > (...) > > /usr/bin/ld: filtbank3.o: warning: relocation against `svcoeff88' > in > > read-only section `.text' > > Hi, > > I've already seen this strange behavior with gcc 9.x : symbols with > a const definition are by default not publicly visible. It works > if you explicitly add an "extern" in the definition: > > extern const float svcoeff44 [216] = (...) > > I am not sure whether it is a bug in gcc or a strict application of the > standard. Yeah, I just read this: https://gcc.gnu.org/gcc-10/porting_to.html " C language issues Default to -fno-common A common mistake in C is omitting extern when declaring a global variable in a header file. If the header is included by several files it results in multiple definitions of the same variable. In previous GCC versions this error is ignored. GCC 10 defaults to -fno-common, which means a linker error will now be reported. To fix this, use extern in header files when declaring global variables, and ensure each global is defined in exactly one C file. If tentative definitions of particular variables need to be placed in a common block, __attribute__((__common__)) can be used to force that behavior even in code compiled without -fcommon. As a workaround, legacy C code where all tentative definitions should be placed into a common block can be compiled with -fcommon. int x; // tentative definition - avoid in header files extern int y; // correct declaration in a header file " Guess that could explain it.

3 years, 10 months

Re: [LAD] G++ trouble

by Kjetil Matheussen

On Mon, Nov 16, 2020 at 12:59 PM Roman Sommer <roman.sommer(a)fau.de> wrote: > > Kjetil Matheussen <k.s.matheussen(a)gmail.com> writes: > > > > Yeah, I just read this: https://gcc.gnu.org/gcc-10/porting_to.html > > > > " > > > > C language issues > > > > Default to -fno-common > > > > A common mistake in C is omitting extern when declaring a global > > variable in a header file. If the header is included by several files > > it results in multiple definitions of the same variable. In previous > > GCC versions this error is ignored. GCC 10 defaults to -fno-common, > > which means a linker error will now be reported. To fix this, use > > extern in header files when declaring global variables, and ensure > > each global is defined in exactly one C file. If tentative definitions > > of particular variables need to be placed in a common block, > > __attribute__((__common__)) can be used to force that behavior even in > > code compiled without -fcommon. As a workaround, legacy C code where > > all tentative definitions should be placed into a common block can be > > compiled with -fcommon. > > > > int x; // tentative definition - avoid in header files > > > > extern int y; // correct declaration in a header file > > " > > > > > > Guess that could explain it. > > Hm? Why would that explain this behaviour? > It seems to me Fons already (correctly) uses "extern" in his header Guess you're right. I didn't read the posts very thoroughly. That's also why I wrote "could' and not "would".

3 years, 10 months

Jump to page:

2024

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