Linux-audio-dev

linux-audio-dev@lists.linuxaudio.org

3 participants
7520 discussions

[ANN] Qtractor 0.6.4 - The Baryon Throne beta release!

by Rui Nuno Capela

Aw, snap! Wait, there's no big deal (nor chromium's) cosmic (mis)alignment being announced here now. Rest calm. Sorry to delude some of you :) But, there's one (notable) leap on this tiny side and part of the universe... (or is it a multiverse? move along...) What I really want to tell is all about this happening and none else's freaking business: Qtractor 0.6.4 (baryon throne beta) is released! Release highlights: * Punch-in/out over loop-recording/take modes (NEW) * Latch/momentary MIDI Controllers toggle mode (NEW) * JACK client/port pretty-name (metadata) support (NEW) * Custom style and color themes (NEW) * Mixer strip multi-row layout (NEW) * Muted audio tracks monitoring on playback (FIX) * Clip fade-in/out resize on time-stretch (FIX) As for the clueless (as if there's any): Qtractor is an audio/MIDI multi-track sequencer application written in C++ with the Qt4 framework. Target platform is Linux, where the Jack Audio Connection Kit (JACK) for audio and the Advanced Linux Sound Architecture (ALSA) for MIDI are the main infrastructures to evolve as a fairly-featured Linux desktop audio workstation GUI, specially dedicated to the personal home-studio. Well, although this being yet another milestone--if one may call it that way--it also makes it official (yes, deeply engraved in stone) and definitive as a migration to Git can be, as for source-code control and management (it's a dirty job I know, but someone has to do it, right?). Nevermind. It's done. Meanwhile, please, don't ever hesitate to ask whether any of the above does affect you some way or another. Or maybe anything else, yay? Indeed, the puzzled you feel, the better :) Website: http://qtractor.sourceforge.net Project page: http://sourceforge.net/projects/qtractor Downloads: http://sourceforge.net/projects/qtractor/files - source tarball: http://download.sourceforge.net/qtractor/qtractor-0.6.4.tar.gz - source package (openSUSE 13.2): http://download.sourceforge.net/qtractor/qtractor-0.6.4-14.rncbc.suse132.sr… - binary packages (openSUSE 13.2): http://download.sourceforge.net/qtractor/qtractor-0.6.4-14.rncbc.suse132.i5… http://download.sourceforge.net/qtractor/qtractor-0.6.4-14.rncbc.suse132.x8… - quick start guide & user manual (see also: the wiki): http://download.sourceforge.net/qtractor/qtractor-0.5.x-user-manual.pdf - wiki (help wanted!): http://sourceforge.net/p/qtractor/wiki/ Weblog (upstream support): http://www.rncbc.org License: Qtractor is free, open-source software, distributed under the terms of the GNU General Public License (GPL) version 2 or later. Change-log: - Fixed some old loop-recording clip drawing glitches. - Current assigned track/channel instrument definition names for MIDI controllers, note keys, RPN and NRPN, are now in effect on the MIDI clip editor drop-down lists, whether available. - Clip/Take/Range... input dialog values are now properly sanitized as long to prevent invalid take/folding ranges. - Audio capture/export file type default now set to "wav". - Extending punch-in/out over loop-recording/takes modes. - Make audio tracks monitoring always flow while playback is rolling, independently of their mute/solo state. - Fixed undo/redo conversion of audio clip offsets under (automatic) time-stretching eg. due on tempo changes. (ticket by Holger Marzen, thanks). - Latch/momentary MIDI Controllers toggle mode introduced (a request by AutoStatic aka. Jeremy Jongepier, thanks). - JACK client/port pretty-name (metadata) support is being seamlessly introduced. (EXPERIMENTAL) - Audio frame/MIDI time drift correction is now an option on View/Options.../MIDI/Playback/Enable MIDI queue time drift correction. - Transport auto-backward feature now honoring last position playback was started. - Introducing brand new application user preferences on View/Options.../Display/Options/Custom style and color themes (eg. "KXStudio", by Filipe Coelho aka. falkTX). - Mixer widget gets automatic multi-row strip layout. - Clip fade-in/out now follows time-stretch resizing, via shift/ctrl+click and drag one of its edges. - Fixed a typo causing FTBFS when VST plug-in support is explicitly disabled (./configure --disable-vst). See also: http://www.rncbc.org/drupal/node/834 Enjoy && have plenty of fun. -- rncbc aka. Rui Nuno Capela

11 years, 1 month

[LAU] [LAA] Guitarix 0.32.0 released

by hermann meyer

The Guitarix developers proudly present Guitarix release 0.32.0 For the uninitiated, Guitarix is a tube amplifier simulation for jack (Linux), with an additional mono and a stereo effect rack. Guitarix includes a large list of plugins[*] and support LADSPA / LV2 plugs as well. The guitarix engine is designed for LIVE usage, and feature ultra fast, glitch and click free, preset switching, full Midi and/or remote controllable (Web UI not included in the distributed tar ball). Here is the " Ultimate Guide to Getting Started With Guitarix <http://libremusicproduction.com/articles/ultimate-guide-getting-started-gui…>" This release fix the bug #16 "empty effect menu with clear-skin option", add new tuning scales (19- and 31-TET) to guitarix and Gxtuner.lv2, add Midi Clock and Jack Transport support to guitarix and move a couple of controllers from unit:ms|hz to unit:bpm, so that they could easy synced with the Midi Beat Clock. and introduce a new LV2 plug: * GxMultiBandReverb Please refer to our project page for more information: http://guitarix.sourceforge.net/ Download Site: http://sourceforge.net/projects/guitarix/ Forum: http://guitarix.sourceforge.net/forum/ Please consider visiting our forum or leaving a message on guitarix-developer(a)lists.sourceforge.net <mailto:guitarix-developer@lists.sourceforge.net> regards hermann

11 years, 1 month

How can a LV2 plugin know on what host's MIDI Channel it's on?

by Phil CM

Is there a way to retrieve this info (and others, ideally) from the host, thus removing the need for a "midi channel" control port? Also, is there a way to tie the "volume" controller of the host (in Qtractor's case, the volume fader of the mixer strip) to one "volume" control port of the plugin, thus removing the need for the "control mode" control port ? Yes because you see, here in my Qtractor (latest SVN - but it has always been that way) I can either edit the plugin (about 50% of my plugins behave that way) controls but then the mixer's volume is inoperant, or control the volume w/ said mixer but NOT the plugins controls. How can I have my cake and eat it? Ta-ta --Phil

11 years, 1 month

DTS-HD bits out HDMI port

by Kip Warner

Hey list, I'd like to be able to stream DTS-HD Master Audio bits out the HDMI port in their compressed form - not decompressed to LPCM. I'll let the receiver handle the decoding. From what I can gather, this may be possible with the ALSA API, provided the HDMI port is >= 1.3 and the audio card supports high bit-rate (HBR). Is my thinking way off? Is there a more suitable API or approach for this? If it requires specific hardware, I am less concerned about that as I am the feasibility of the end goal. Regards, -- Kip Warner -- Senior Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com

11 years, 1 month

Midi Beat Clock to BPM

by hermann meyer

Hi I try to fetch the bpm from the Midi Clock, and stumble over "jitter". So I start to collect data for a larger amount of time, but it wouldn't help. Here is what I do: else if ((in_event.buffer[0] ) == 0xf8) { // midi beat clock clock_gettime(CLOCK_MONOTONIC, &ts1); time0 = (ts1.tv_sec*1000000000.0)+(ts1.tv_nsec); static int collect = 0; static int bpm = 0; bpm += ((1000000000 / (time0-time1) / 24) * 60); // nanosec to bpm collect+=1; if (collect >=30) { set_bpm_val(bpm/collect); collect = 0; bpm = 0; } timed = time0-time1; // printf("Midi clock event %X time0 %f time1 %f timed %f ts1.tv_nsec %lu\n",in_event.buffer[0], time0, time1, timed, ts1.tv_nsec); time1 = time0; } else if ((in_event.buffer[0] ) == 0xfa) { // midi clock start printf("Midi clock start\n"); //set_ctr_val(MIDICLOCK, 1); } else if ((in_event.buffer[0] ) == 0xfb) { // midi beat clock continue //set_ctr_val(MIDICLOCK, 1); printf("Midi clock continue\n"); }else if ((in_event.buffer[0] ) == 0xfc) { // midi beat clock stop //set_ctr_val(MIDICLOCK, 0); printf("Midi clock stop\n"); } else { printf("CC number %x\n", in_event.buffer[0] ); } tim0 and time1 are set as double. I experience jitter around 1 or 2 beats around the "original bpm set in the master. When master is set to 360 I receive 374. How do you usually fetch the bpm from Midi Clock, any pointer will be welcome. regards hermann

11 years, 1 month

Invitation - Control Chain interface and communication protocol

by Gianfranco Ceccolini

Hi LADs This is an invitation for all those who are interested in the Control Chain system, the MOD approach to external hardware controllers. The Control Chain interface was conceived with the LV2 control ports properties in mind. It tries to dis-abstract the LV2 Control structure in tangible (and material) form. The first purpose of the Control Chain was to connect the MOD and its external peripherals. The MIDI system is very generalistic and we didn’t want to design a “MIDI Clone”. As the LV2 standard enables the developers to add important metadata to describe the Control Ports, the MOD platform makes use of all this info to offer a good user experience to the musicians. A good example is the footswitch. The Control Chain footswitch has built in its firmware different behaviours depending on port properties. It alternates the state of toggles controls, it can trigger an event, it can run the items of an enumeration list and it can also measure time and offer TapTempo for time based units. All this is accomplished with the same physical actuation - the pressing of the button - but according to the control that has been addressed to it. The GUI decides which actuator it offers the user for each of the Controls. The physical interface of the Control Chain devices is an RS-485 full-duplex serial line running at 1Mbit/sec. Currently up to eight devices can be daisy chained and by use of the RJ-45 cable we also power the devices ( 1 pair for input,1 for output and 1 for power supply). After some development we came to the conclusion that such a protocol could be extended for virtual devices in the GUI as well and this would make the development of plugins interfaces much easier. The reason for sharing this with the Linux Audio community is to involve as much people as possible in electing the needed features for the plugins. At this current state, the Control Chain supports only Input ControlPorts. People have been asking about the Tuner and other plugins that have Control Outputs. So we’re opening up the discussion to set the requirements and possibilities that shall be implemented. The discussion is to happen on our mailing list: http://portalmod.com/cgi-bin/mailman/listinfo/developers <http://portalmod.com/cgi-bin/mailman/listinfo/developers> and at the #portalmod IRC channel @ freenode. Hope to see you all there Kind regards Gianfranco The MOD Team

11 years, 1 month

LADSPA::run_adding() anyone?

by Tim Goetze

Good morning lads, among the people still using LADSPA, either directly or wrapped into more fashionable plugin APIs, is anyone actually dependent on run_adding()? (Asking, of course, because I intend to drop support for it.) Thank you, Tim

11 years, 1 month

Update advanced gtk+ sequencer

by Joël Krähemann

Hi, I'd like to update wiki entry http://wiki.linuxaudio.org/apps/all/ags but can't log in anymore. regards Joël

11 years, 1 month

Announce: MFP 0.05

by Bill Gribble

MFP -- Music For Programmers Release 0.05, "Mighty Fine Patching" I'm pleased to announce a new version of MFP, containing many new features, fixes and improvements. This is still a very early release that is missing a lot of expected functionality, but it's a significant step forward from 0.04 in every way and I thought it might be of interest to the wider community. A summary of changes is below. Please see the GitHub issue tracker for complete details: http://github.com/bgribble/mfp This version is still source-code-only, but the new build system should make it a bit easier for those who would like to try it. Significant changes since release v0.04 ---------------------------------------- * MFP patches can be saved as LV2 plugins that can be live-edited while loaded in a host (see doc/README.lv2) * New build system using 'waf' for one-line build and install (see doc/README.build) * Support for user patches with dynamic creation of inlets/outlets and other objects at instantiation time (with examples) using the "@clonescope" method * Lazy evaluation of expressions using a leading "," syntactic sugar is available in message boxes (i.e. the message "datetime.now()" is a constant, but ",datetime.now()" is evaluated each time the message is emitted) * More sample patches, including a basic tutorial covering app interaction, "hello, world", and patterns for things like iteration, conditionals, etc * Improvements to stability and error handling * Many other bugfixes and improvements. The complete list of 60+ tickets closed since the 0.04 release is in the 0.05 milestone: http://github.com/bgribble/mfp/issues?q=milestone%3A%22mfp+0.05%22+is%3Aclo… About MFP ---------------------------------------- MFP is an environment for visually composing computer programs, with an emphasis on music and real-time audio synthesis and analysis. It's very much inspired by Miller Puckette's Pure Data (pd) and Max/MSP, with a bit of LabView and TouchOSC for good measure. It is targeted at musicians, recording engineers, and software developers who like the "patching" dataflow metaphor for coding up audio synthesis, processing, and analysis. MFP is a completely new code base, written in Python and C, with a Clutter UI. It has been under development by a solo developer (me!), as a spare-time project for several years. Compared to Pure Data, its nearest relative, MFP is superficially pretty similar but differs in a few key ways: * MFP uses Python data natively. Any literal data entered in the UI is parsed by the Python evaluator, and any Python value is a legitimate "message" on the dataflow network * MFP provides fairly raw access to Python constructs if desired. For example, the built-in Python console allows live coding of Python functions as patch elements at runtime. * Name resolution and namespacing are addressed more robustly, with explicit support for lexical scoping * The UI is largely keyboard-driven, with a modal input system that feels a bit like vim. The graphical presentation is a single-window style with layers rather than multiple windows. * There is fairly deep integration of Open Sound Control (OSC), with every patch element having an OSC address and the ability to learn any other desired address. * MFP has just a fraction of the builtin and addon functionality provided by PD. It's not up to being a replacement except in very limited cases! The code and issue tracker are hosted on GitHub: https://github.com/bgribble/mfp You can find the LAC-2013 paper and accompanying screenshots, some sample patches, and a few other bits of documentation in the doc directory of the GitHub repo. The README files at the top level of the source tree contain dependency, build, and getting-started information. Thanks, Bill Gribble <grib(a)billgribble.com>

11 years, 1 month

Jack not starting MOD-Duos Audio Interface Driver

by Rafael Guayer

Hi, I developed an aSoC driver for MOD-Duos Sound Card and i can aplay and arecord, but when calling jackd (jackd -dalsa -r48000 -p256 -P hw:0 -C hw:0 &) i get an alsa format error. I get this message: -- Rafael Guayer www.portalmod.com <http://www.portalmod.com.br>

11 years, 2 months

Jump to page:

2025

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