Hello community. First, have to note, that i'm not sure, what fluidsynth
backend is best today, as first time i got it, was several years ago when i
tried ubuntustudio (even simpler - just installed pro-media software to Ubuntu
7.04) and when ubuntu 10.04 released and even 12.04, i still suppose using of
qsynth, since i don't now others with such full amount of settings.
Now proposals.
1 - optional feature (i.e. with switch to disable it) to publish fluidsynth
engines as dbus or other kind of services, exactly like what jack already has.
If such option is enabled by default, then even when engine is loaded via
linked library, as done in MuseScore, it still may be controlled by external
gui like QSynth. Also, another example of such way is linuxsampler way
(limited, because qsampler only allowes to change backend addess in settings,
but hope it is to be fixed).
2 - only about gui at all, not only qsynth: i read one time somewhere, that
fluidsynth supports microtonality (scale tuning), but only few months ago could
try it in action, controlling manually standalone fluidsynth, started in
terminal. It would be great to add in qsynth panel like in zyn/yoshimi for
scale tuning. Also interested, is there some gui, where scale tuning is
implemented (hard even to hope when even most featureful gui doesn't have it).
Audiality 2 is now hosted on GitHub!
------------------------------------
Figured it's about time to make an announcement,
now that it's been on there for a few weeks... ;-)
Overview:
Audiality 2 is a realtime audio and music engine,
primarily intended for video games. While it
supports traditional sample playback as well as
additive, subtractive and granular synthesis, the
distinctive feature is subsample accurate realtime
scripting.
Some of the changes since 1.9.0:
* Subvoice spawn and event timing fixed - now truly
subsample accurate! (For granular synthesis etc.)
* Added generic stream API for wave uploading,
audio streaming etc.
* 'filter12' no longer blows up at high cutoffs.
* 'filter12' supports 2 channels/dual channel mode.
* More accurate pitch control in 'wtosc'.
* More logical unit autowiring: Now wires outputs
to any inputs down the chain by default; not just
the next unit.
* 'run' statement removed.
* Comma as a statement delimiter now deprecated.
Next few upcoming changes:
* Command line player.
* Boolean and comparison operators.
* Normalize, crossfade and reverse mix processing
for wave uploads.
* Render-to-wave, for creating complex waves.
* Buffered taps/inserts, for easy implementation of
GUI oscilloscopes and the like without realtime
callbacks.
Official site:
http://audiality.org/
GitHub:
https://github.com/olofson/audiality2
Related; Kobo II site:
http://kobo2.net/
--
//David Olofson - Consultant, Developer, Artist, Open Source Advocate
.--- Games, examples, libraries, scripting, sound, music, graphics ---.
| http://consulting.olofson.nethttp://olofsonarcade.com |
'---------------------------------------------------------------------'
I want to detect INFs and NANs in my DSP graph to avoid having
them spread and cause various trouble.
Here is the straight forward way:
int i;
for (i=0;i<num_samples;i++)
if (!isfinite(samples[i])) break
if(i!=num_samples)
error();
But is this as efficient as we get it?
I'm wondering if comparing samples using for instance SIMD
instructions, for instance, could make it around 4 times faster,
Something like this:
for(i=0;i<num_samples;i++)
if(samples[i]!=samples[i]))
break;
where the samples[i]!=samples[i] test would succeed
if it was a nan or inf, since INFs and NANs don't behave normally.
I don't think this particular example works though (?),
but perhaps something similar could?
Anyone doing something like this?
As falling leaves drift by the window, and without any further ado:
Qtractor 0.5.11 (lima oscar) is now released!
Soon we'll hear a new winter's song. This code-naming series, which
started on a sunny summer day two years ago as TYOQA, is now converging
to an end. It will be no surprise for some that today's release precedes
the very last one on that series. So let's get those autumn leaves
falling and grab them while they're crispy red and gold ;)
Release highlights:
* Extended automation curve editing (NEW)
* Extended clip selection (NEW)
* LV2 UI resize feature support (NEW)
* Aux-sends to audio buses (FIX)
* MIDI editor overlapped event velocity/value (FIX)
* Accidental export muting and/or freezing (FIX)
Website:
http://qtractor.sourceforge.net
Project page:
http://sourceforge.net/projects/qtractor
Downloads:
http://sourceforge.net/projects/qtractor/files
- source tarball:
http://downloads.sourceforge.net/qtractor/qtractor-0.5.11.tar.gz
- source package (openSUSE 12.3):
http://downloads.sourceforge.net/qtractor/qtractor-0.5.11-8.rncbc.suse123.s…
- binary packages (openSUSE 12.3):
http://downloads.sourceforge.net/qtractor/qtractor-0.5.11-8.rncbc.suse123.i…http://downloads.sourceforge.net/qtractor/qtractor-0.5.11-8.rncbc.suse123.x…
- quick start guide & user manual (outdated):
http://downloads.sourceforge.net/qtractor/qtractor-0.5.x-user-manual.pdf
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:
- Adding a track now inserts it after the current one, if any; one can
also drag and move a track below the last one in the track list (main
view left pane).
- Extended Edit/Select Mode/Automation: multi-selection mode, cut, copy,
paste and delete of current track's automation curve nodes, now reached
implementation ready status.
- Another old silent bug bites the dust: changing track names were
dropping any track gain/volume and panning automation curves when saving
the session.
- A primeval processing bug has been sorted out: aux-sends to audio
output buses that just appear to be after the input bus where they're
inserted were being left muted and silent (on a ticket follow-up by
Holger Marzen, thanks).
- Fixed a sure crash bug exposed when processing of aux-send plugins
when inserted too early on audio input buses chain (after a ticket
report by Holger Marzen, thanks).
- Allow the build system to include an user specified CFLAGS (patch by
Cristian Morales Vega, thanks).
- Shift/Ctrl keyboard modifiers now set to extend current clip selection
while in main track view's Edit/Select Mode/Range, Rectangle modes.
- Main Edit/Select Mode/Automation icon retouched to look a bit more
obvious and intuitive, hopefully ;)
- Allow to change the velocities/values of the current selected events
which have the exact same onset times and hide beyhond each other on the
MIDI clip editor's pane below the main view piano-roll (ie. the one that
represents MIDI event values as a bar chart).
- Fixed some problematic playback/export muting and annoying cleanup
freezing, due on audio tracks with too many clips eg. more than hundred
clip splits (hopefully fixes an issue reported by Louigi Verona, thanks).
- LV2 UI resize feature support/control added.
- Fixed dedicated MIDI control and MIDI metronome port connection
restore conflict (thanks to jhammen catch & patch:).
- New user preference option added: reverse middle-button role to
Shift/Ctrl keyboard state, in special regard to edit-head/tail vs.
play-head positioning while on the main track and MIDI clip editor (aka.
piano-roll) views.
See also:
http://www.rncbc.org/drupal/node/710
Enjoy && have (a plenty of) fun.
--
rncbc aka Rui Nuno Capela
The current state of
https://github.com/nickbailey/jackmix
represents JackMix 0.5.1. It could probably do with a bit more testing, but
couldn't everything? :/
New in this version: rename inputs and outputs post hoc. Order of the inputs
and outputs on the GUI is preserved across save/load operations.
Nick/.
$cat NEWS
VERSION 0.5.1
-------------
Added File->Rename Inputs... and File->Rename Outputs... which
changes the labels on the GUI, the channel's position and Jack
connection name while preserving volume levels etc.
There is a video describing the use and motivation behind
developing JackMix on Vimeo. See
https://vimeo.com/75655401
...
On 28 September 2013 22:01, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
> If the problem is the same as with the original LP, then
> the ALSA driver can't do anything about it, unless it would
> contain LP-specific code.
>
But isn't the problem a general running-status problem if multiple programs
are receiving from the same device? Is it a problem with the way the ALSA
sequencer works (this seems to ring a bell somehow) as you said in the
older thread that using Jack-MIDI would solve it?