Happy New Year all,
I was curious, if doubling the sample rate is a
practical way to reduce latency for live effects
processing. I would think it would reduce latency by half.
If one wanted to avoid the tradeoff of handling twice the
usual amount of audio data, I was curious if ALSA sample
rate conversion, or some other clever hack could be used to
get low latency advantage of the high sample rate, while
actually dealing with 48k streams through JACK.
best wishes,
Joel
--
Joel Roth
Hi,
It's been a while since I researched notation software. What are the
major players in the linux world? What is being actively maintained?
What is new and cutting edge?
Note: I use lilypond for printed scores but I'm looking for some
distinct functionality for in-score composing and orchestrating:
- individual jack midi routing at least at the staff level, better if
staff supported multiple voices and each could be routed separately.
- step input with both external keyboard as well as mouse
- customization for in-score articulations, e.g., staccato -> channel
change or slur/legato -> insert note ( for key switch software instruments)
- lilypond and/or midi export functionality.
I'd appreciate any advice. thanks,
David
Hello list,
I've come across a problem where the hardware latency numbers entered into
qjackctl setup window don't take effect. I wrote up the details here:
http://quinoa.blizinski.pl/~maciej/latency/calibration-problems.html
The workaround was to start jackd from command line and pass the -I and -O
options that way.
It is possible (but not certain) that the problem was caused by qjackctl. I
wrote a post on the qjackctl forum, but I'm not sure how much attention it
gets.
http://www.rncbc.org/drupal/node/749
Since my setup is fairly common components: Ubuntu 13.10 with ardour, jackd
and qjackctl installed from packages, it sounds like I shouldn't be the
only person to experience this problem.
Has anyone else come across that?
Maciej
QMidiArp 0.6.0 is out, since of course it cannot miss the huge TGV train of Q-Application updates just racing by for the new year!
This release includes LV2 plugins of the three QMidiArp modules. They are synchronizable to the transport info provided by different hosts in different ways, and they work well with the new Qtractor, thanks to Rui for updates regarding this.
I don't claim that I have fully understood LV2 host-GUI communication, but I found the recent sisco plugin by Robin Gareaus very instructive for this, thanks!
Happy new year!
Frank
---------------------------------------
http://qmidiarp.sourceforge.net
Direct download:
http://sourceforge.net/projects/qmidiarp/files/qmidiarp/0.6.0/qmidiarp-0.6.…
----------------------------------------
qmidiarp-0.6.0 (2014-01-01)
New Features
o LV2 Plugins are now available for Arp, LFO and Seq modules
- They have full functionality as known from the standalone
application except MIDI control, which can be provided by the host
- The LFO plugin also has a LV2 control output scaled from 0 to 1
- When the 'Sync to host' option is checked, the plugins support
transport LV2 atom data from hosts as well as host transport
information available from designated lv2 time ports (Qtractor,
thanks Rui!)
- Arp pattern presets are available in the LV2 module but cannot be
written to the .qmidiarprc file. This has to be done with the
standalone application
- On hosts with small atom port capacities that do not honor the
lv2 rsz:MinimumSize property, there will be issues with displaying
very large LFO waveforms
- Features of QMidiArp beyond the modules themselves (including
global storage) are not available
Fixed Bugs
o Trying to open an inexistent file from the recent files menu led to
crash (reported by Frank Neumann)