Dear all,
here is QMidiArp 0.6.5. Another year has passed, and qmidiarp again only
slightly changes, improves, adapts itself. A few more factory patterns were
added to the Arpeggiator, a new "As Played" repeat mode has sneaked in, and
for making things easier the MIDI OMNI mode is now default when modules are
added.
QMidiArp also builds against Qt5 by default now (it's about time ;) ), no more
--enable-qt5 needed at configure stage.
Enjoy!
Frank
--------------
Here is the full changelog:
qmidiarp-0.6.5 (2017-12-17)
*Improvements*
o MIDI OMNI Mode receiving on all MIDI channels is now available and
even default for all modules.
o Arp: Some more 'factory' patterns added to the LV2 presets and to
the .qmidiarprc file. Latter requires deleting the original one in
the home directory and launching the standalone application.
o Arp: New pattern repeat mode "As Played" for following the played
note order instead of reorganizing them up, down or random.
o Arp: For deliberately clearing buffered incoming notes the modules
now all react to ALL_NOTES_OFF and ALL_SOUND_OFF MIDI messages.
o LV2: The DSP ("generic") parameter interface has gotten some
improvements for better usability (thanks Holger Wirtz for input on
this)
*Fixed Bugs*
o LV2: Latch mode was not working properly when using release function.
o LV2 Arp: when running with host transport sync, transport start
caused received notes to be cleared. This also cleared those notes
received before the transport was starting and led to missed notes
especially in qtractor. This should work better now. (Thanks to
Webmadman for reporting, and to Rui).
o Seq and LFO: the "Note Off" option had no effect (regression).
o Recent Files menu in main app displayed extra characters with Qt5.
*General changes*
o Building against Qt5 is now default. No more --enable-qt5 needed.
o LV2: Category set to MIDIPlugin instead of Instrument
o The DSP classes including the LV2 DSP modules no longer use
Qt libraries. However the LV2 and App GUIs do.
o New build configure options for more flexibility
--enable-alsa (default=yes) set no for building on systems without alsa
--enable-buildapp (default=yes) set no for building only LV2 modules
--enable-lv2-pluginuis (default=yes) set no for LV2 module dsps only
*Website*
http://qmidiarp.sourceforge.net/
*Download*
https://download.sf.net/qmidiarp/qmidiarp/0.6.5/qmidiarp-0.6.5.tar.bz2
*Description*
QMidiArp is a MIDI arpeggiator, phrase generator and controller LFO for ALSA
and JACK. It can run multiple synchronized arpeggiators, LFOs and step
sequencers. The modules are also available as LV2 plugins with Qt user
interface.
*SCM Repos*
https://git.code.sf.net/p/qmidiarp/codehttps://github.com/emuse/qmidiarp
Dear all,
here is QMidiArp 0.6.5. Another year has passed, and qmidiarp again only
slightly changes, improves, adapts itself. A few more factory patterns were
added to the Arpeggiator, a new "As Played" repeat mode has sneaked in, and
for making things easier the MIDI OMNI mode is now default when modules are
added.
QMidiArp also builds against Qt5 by default now (it's about time ;) ), no more
--enable-qt5 needed at configure stage.
Enjoy!
Frank
--------------
Here is the full changelog:
qmidiarp-0.6.5 (2017-12-17)
*Improvements*
o MIDI OMNI Mode receiving on all MIDI channels is now available and
even default for all modules.
o Arp: Some more 'factory' patterns added to the LV2 presets and to
the .qmidiarprc file. Latter requires deleting the original one in
the home directory and launching the standalone application.
o Arp: New pattern repeat mode "As Played" for following the played
note order instead of reorganizing them up, down or random.
o Arp: For deliberately clearing buffered incoming notes the modules
now all react to ALL_NOTES_OFF and ALL_SOUND_OFF MIDI messages.
o LV2: The DSP ("generic") parameter interface has gotten some
improvements for better usability (thanks Holger Wirtz for input on
this)
*Fixed Bugs*
o LV2: Latch mode was not working properly when using release function.
o LV2 Arp: when running with host transport sync, transport start
caused received notes to be cleared. This also cleared those notes
received before the transport was starting and led to missed notes
especially in qtractor. This should work better now. (Thanks to
Webmadman for reporting, and to Rui).
o Seq and LFO: the "Note Off" option had no effect (regression).
o Recent Files menu in main app displayed extra characters with Qt5.
*General changes*
o Building against Qt5 is now default. No more --enable-qt5 needed.
o LV2: Category set to MIDIPlugin instead of Instrument
o The DSP classes including the LV2 DSP modules no longer use
Qt libraries. However the LV2 and App GUIs do.
o New build configure options for more flexibility
--enable-alsa (default=yes) set no for building on systems without alsa
--enable-buildapp (default=yes) set no for building only LV2 modules
--enable-lv2-pluginuis (default=yes) set no for LV2 module dsps only
*Website*
http://qmidiarp.sourceforge.net/
*Download*
https://download.sf.net/qmidiarp/qmidiarp/0.6.5/qmidiarp-0.6.5.tar.bz2
*Description*
QMidiArp is a MIDI arpeggiator, phrase generator and controller LFO for ALSA
and JACK. It can run multiple synchronized arpeggiators, LFOs and step
sequencers. The modules are also available as LV2 plugins with Qt user
interface.
*SCM Repos*
https://git.code.sf.net/p/qmidiarp/codehttps://github.com/emuse/qmidiarp
Dear all,
here is QMidiArp 0.6.5. Another year has passed, and qmidiarp again only
slightly changes, improves, adapts itself. A few more factory patterns were
added to the Arpeggiator, a new "As Played" repeat mode has sneaked in, and
for making things easier the MIDI OMNI mode is now default when modules are
added.
QMidiArp also builds against Qt5 by default now (it's about time ;) ), no more
--enable-qt5 needed at configure stage.
Enjoy!
Frank
--------------
Here is the full changelog:
qmidiarp-0.6.5 (2017-12-17)
*Improvements*
o MIDI OMNI Mode receiving on all MIDI channels is now available and
even default for all modules.
o Arp: Some more 'factory' patterns added to the LV2 presets and to
the .qmidiarprc file. Latter requires deleting the original one in
the home directory and launching the standalone application.
o Arp: New pattern repeat mode "As Played" for following the played
note order instead of reorganizing them up, down or random.
o Arp: For deliberately clearing buffered incoming notes the modules
now all react to ALL_NOTES_OFF and ALL_SOUND_OFF MIDI messages.
o LV2: The DSP ("generic") parameter interface has gotten some
improvements for better usability (thanks Holger Wirtz for input on
this)
*Fixed Bugs*
o LV2: Latch mode was not working properly when using release function.
o LV2 Arp: when running with host transport sync, transport start
caused received notes to be cleared. This also cleared those notes
received before the transport was starting and led to missed notes
especially in qtractor. This should work better now. (Thanks to
Webmadman for reporting, and to Rui).
o Seq and LFO: the "Note Off" option had no effect (regression).
o Recent Files menu in main app displayed extra characters with Qt5.
*General changes*
o Building against Qt5 is now default. No more --enable-qt5 needed.
o LV2: Category set to MIDIPlugin instead of Instrument
o The DSP classes including the LV2 DSP modules no longer use
Qt libraries. However the LV2 and App GUIs do.
o New build configure options for more flexibility
--enable-alsa (default=yes) set no for building on systems without alsa
--enable-buildapp (default=yes) set no for building only LV2 modules
--enable-lv2-pluginuis (default=yes) set no for LV2 module dsps only
*Website*
http://qmidiarp.sourceforge.net/
*Download*
https://download.sf.net/qmidiarp/qmidiarp/0.6.5/qmidiarp-0.6.5.tar.bz2
*Description*
QMidiArp is a MIDI arpeggiator, phrase generator and controller LFO for ALSA
and JACK. It can run multiple synchronized arpeggiators, LFOs and step
sequencers. The modules are also available as LV2 plugins with Qt user
interface.
*SCM Repos*
https://git.code.sf.net/p/qmidiarp/codehttps://github.com/emuse/qmidiarp
Here's me, having to deal with a 48 channel live recording over the
course of six shows. Since my MADI gear is kinda heavy and the rental
company had a Dante system on offer, I dusted off the 2013 Macbook pro I
bought used, purchased a Dante virtual soundcard license from Audinate
and happily tracked the first three shows with Ardour.
On the train on an off-day, I started a rough mix-down so that the
client can begin the selection process. In the middle of exporting, my
Mac shuts down and boots into a PIN unlock screen, telling me it has
been locked via "Find-my-Mac".
For the record, this Macbook had been purchased from a reputable large
online dealer, and it had been factory-reset and completely installed
from scratch.
The first thing I find as I frantically research this issue (on my
proper laptop, that is controlled by me, not by some iFuckwits), is that
this iFeature even contains the option of a remote data wipe.
My excuses to my fellow passengers who got in the way of a stream of
expletives suddenly bursting forth from an otherwise unobtrusive
business traveller, as said traveller notices he doesn't have a
screwdriver to yank his data drive out of this ransomware machine, and
cannot even be sure it's off when it says it's off because of course the
battery cannot be removed without major surgery, either.
Was able to salvage the data at home using a real operating system on
real hardware, and today I'm going to find an authorized mac reseller
and give the guy at the guru bar a day he will remember and testify
about at the next Apple employee incentive day.
Long story short: don't.
--
Jörn Nettingsmeier
De Rijpgracht 8, 1055VR Amsterdam, Nederland
Tel. +49 177 7937487
Meister für Veranstaltungstechnik (Bühne/Studio), Tonmeister VDT
http://stackingdwarves.net
Hi all,
New images are ready for testing (amd64, i386) ;)
io GNU/Linux is a Live DVD/USB based on Debian Sid and focused on multimedia.
-> Kernel 4.14 and 4.14-rt1, Jack2+PulseAudio as default sound server (can
be easily changed to Jack2+AlsaLoop, Jack2+ZitaBridge, PulseAudio or Alsa)
-> Enlightenment (e22) as desktop environment and a big collection of
installed software... Full persistence for USB install (with encryption) and
more stuff...
For more infos: manual, packages list, screenshots, video etc... Visit:
-> http://io.gnu.linux.free.fr
-> https://sourceforge.net/projects/io-gnu-linux/
Feedbacks welcome, enjoy :)
MK
Hi all,
New images are ready for testing (amd64, i386) ;)
io GNU/Linux is a Live DVD/USB based on Debian Sid and focused on multimedia.
-> Kernel 4.14 and 4.14-rt1, Jack2+PulseAudio as default sound server (can
be easily changed to Jack2+AlsaLoop, Jack2+ZitaBridge, PulseAudio or Alsa)
-> Enlightenment (e22) as desktop environment and a big collection of
installed software... Full persistence for USB install (with encryption) and
more stuff...
For more infos: manual, packages list, screenshots, video etc... Visit:
-> http://io.gnu.linux.free.fr
-> https://sourceforge.net/projects/io-gnu-linux/
Feedbacks welcome, enjoy :)
MK
On Sun, Dec 10, 2017 at 7:43 PM, Gordonjcp <gordonjcp(a)gjcp.net> wrote:
<snip> Previous discussion about plugins using GUI library frameworks like
Gtk/QT, which are not designed for plugin usage. As a result, they export
symbols that may collide when loaded in a DAW and plugin, when DAW and
plugin are compiled against different version, ending up in a segfault that
is no single softwares fault, but one of usage of a library for a purpose
it is not appropriate for.
> So what would you write it in instead?
There are a range of toolkits / libraries available especially designed for
plugin usage.
In no particular order, the following come to mind. (Note, as OpenAV I'm
the author of Avtk(a), </disclaimer>)
Toolkits / frameworks:
https://github.com/x42/robtk/ (meters.lv2, scopes.lv2 and other x42
software)
http://distrho.sourceforge.net/ (particularly the "DGL" component IIRC)
https://github.com/mruby-zest (new Zyn Fusion UI toolkit)
https://github.com/wrl/rutabagahttps://juce.com/http://openavproductions.com/avtk/ (and its WIP 2.0 version
https://github.com/openAVproductions/openAV-avtka)
<apologies; I expect there to be others toolkits, the above are all I can
think of right now.. >
Many of the above are based on a fantastic abstraction library from the LV2
author, specifically abstracting away platform and implementation details,
without any static data. That means it was designed for a purpose - like
embedding and plugin GUIs: https://github.com/drobilla/pugl
I have previously used Gtk, FLTK/NTK, and other toolkits. None of them are
guaranteed to work correctly in DAW X that links to the same libraries.
They're just not designed for that use case - and that's fine. But we (as
developers) need to be careful to not consume a library in a way not
intended for it to be used..
As such, Avtk is developed on PUGL to ensure there is no static data, and
to fix lots of other potential issues that many toolkits have (forking new
threads, waiting for a response in a thread while displaying a modal
dialog, using static caches for data, etc...) For details on AVTK, there
was a presentation at LAC '15 video, slides + paper available[1].
OpenAV dog-fooded[2] writing the ArtyFX[3] plugins using the AVTK library
for the UIs. Based on the experience, I'm developing AVTKA (Avtk v2) in
plain C, with emphasis on ease of use and simplicity in getting lightweight
plugin interfaces built. This makes it easier to use the toolkit for LV2
plugin UIs, as well as a range of other uses. An example of other uses is
creating "virtual hardware" devices for the Ctlra library, inside existing
audio software without needing to care which UI toolkit: eg: Mixxx + Ctlra
virtual interface, built using PUGL + AVTKA. A demo video of exactly that
from the Sonoj event available here[4].
As you may notice, I'm a little passionate about doing the right
engineering in terms of solving the UI toolkit + plugin problem. As
hardware controllers are getting more fully-featured, they also have
screens available. In order to capitalize on thier potential, we need to
handle this use case too - so we can have user-interfaces on Desktop, DAW,
and Hardware controller that have similar look and feel.
Looking forward to what the next steps are in Linux Audio Community start
doing, with these root problems addressed, and various solutions
available...
Regards -Harry
[1] http://lac.linuxaudio.org/2015/video.php?id=14
[2] https://en.wikipedia.org/wiki/Eating_your_own_dog_food
[3] https://github.com/openAVproductions/openAV-artyfx
[4] https://youtu.be/qHt-AQHcBXg?t=1237
--
http://www.openavproductions.com