its a fairly simple arpeggiator called 'arpeggio' for the moment.
guess we'll see where this goes.

pre-release binaries for Windows XP and later [VC2013rt]: 64+32 bit.
There are just the dlls in the 7z archive (no readme er nuttin).

See the releases page.

---

PITCH CONTROL knob (-128 to 127) pitch-key up or down the scale; Notes fall out if not within [0-127] range.
Like the GATE knob/feature, this is one of the last things added could use some work on predicting/preventing note-on/off-overlap quirks.

UI KEYBOARD — a little buggy when it comes to turning off the last note depressed since I had spent the least amount of time working a few changes into Tale's MIDI-Keyboard IControl. (mouse-wheel) middle-click to stick a key down, right-click-drag to wipe clean specific depressed notes.
The bug is where/in when you right-click, the last key stuck down gets un-stuck—will get to it.

• left mouse-down/drag/up sends midi note-on/off messages to quantized, arpeggiated and triggered.
• right mouse-down/drag to clear depressed notes
• middle-click on a keys to make it stick down

"K-AMP" on/off switch/button toggles enabling a amplitude knob which forces midi messages to the particular amp or otherwise relies on what you press in your midi keyboard (or in the tiny UI keys---the lower the louder)

GATE — knob percentage from 1 to 200, generally for shrinking down the length of a generated note.
CAUTION: Generated NOTE_ON/NOTE_OFF combination will interfere when the same key gets repeated. This is an acceptable quirk as long as you're aware. Like the KEY_PITCH knob/feature, this is one of the last things added could use some work on predicting note-on/off-overlaps.

TIMING: BEATS (1-16) VS DIVS (1-64) knobs for controlling as well as...
FIRST top row of fraction looking buttons are [1/n] divisions; Second row: [3/n] divisions and [4/n] divisions in the last. will probably be re-written/designed

SYNC button [on/off] should sync the timing to the DAW transport/clock if the transport is running.
It can generate MIDI with the DAW in idle mode so play/stop DAW-transport to potentially re-sync if sync is on.

PANIC button (triangle near midi-kb) releases all depressed keys/notes

RAMPING 4 ramp modes at the moment: up, down, up-down and down-up. more to come of this area.

---

This is generally for playing on your piano. There isn't any latency/compensation (like "MIDI Strum" for example) which in a nut-shell translates to that when in a DAW's piano-roll mode, the first trigger (multiple notes all hit at exactly the same 0-delta timing) might sequence out of order... So start-up notes would have to be ordered like you would when playing on a piano to ensure the notes are in sequence. If this changes, this note will too ;)

---

If you're not sure how to use a MIDI effect in live, it has to be VSTi. (See this img)
Most DAW explain how they support MIDI effects if they do.
Ardour, Cubase, and REAPER among a few other DAW I'm aware of properly support MIDI VST effects (not compiled as instrument) chains properly.

ARPEGGIATOR IS

Secrets of the Arpeggiator — by Jim Atkin of O'Reilly Digital-Media (20060629).
Wikipedia — Arpeggio

Firstly, most DAW include some form of an arpeggiator.

The following table is what has it my radar. There are more.

name	type	vendor uri
Blue Arp	free	graywolf2004.net
Catanya	commercial	see me, search youtube.
Kirnu	commercial*	kirnuarp.com
Nora, NoraCM	commercial*	squaredheads.com
MIDI Strum	Lv2	x42-plugins.com

• *Kirnu demo doesn't allow you to store presets but works fine otherwise (I'm told)
• *NoraCM is distributed with Computer Music magazine (including digital editions).

CLOCK/TIMING

// timing calculation
// - Bb (class member) is our calculated beat
// - Lb (class member) is the length of a beat division.
inline int32 calculate()
{
  Bb = ((60.0 * mSampleRate / mBpm));
  Lb = double(mBeat) * (1. / double(mDiv)); 
  if (Lb <= 0.) Lb = 0.00001; // prevent zero division

  double actualLength = Bb * Lb;
  mNoteDurationOn = int32(floor(actualLength));
  mNoteDurationOff = int32(floor((actualLength * mGateDiv))); // *bad

  return mNoteDurationOn;
}

WINDOWS DEV

• github.com/olilarkin/wdl-ol (you know)
• github.com/tfwio/twix is a small include (extensions) library containing a few abstractions (IControls) and patches over IPLUG.
• compiles in Visual Studio 2013 Express and 2015 Community
• compiles in Codeblocks configured to msys2+GCC+boost

Visual Studio 2013+2015

• wdl-ol/iplug
  • common includes and few cpp dependencies are in there (such as a patch)
  • wihtout the notes on the readme there this would be fairly difficult to compile.
• compilation options
  1. using VisualStudio 2013 Express load the SLN (Arpeggio.sln)
  2. using VisualStudio 2015 Community load the SLN (Arpeggio-vc2015_c-r3.sln)

CodeBlocks notes

using BOOST filesystem lib and msys64-mingw32/GCC-6.3 at the moment

I named the compiler configuarion GCC msys64/mingw64 so when creating your 64-bit compiler configuration for using the codeblocks projects, using that will prevent a few more project-config steps.
eventually there'll' be slate-template project… and these notes will move to the twix project-space…

• x86 include search directories (example)
  • C:\msys64\mingw32\include
  • C:\msys64\mingw32\i686-w64-mingw32\include
  • C:\msys64\mingw32\include\c++\6.3.0
• x86 linker search directories (example)
  • C:\msys64\mingw32\lib
  • C:\msys64\mingw32\i686-w64-mingw32\lib
• x64 include search directories (example)
  • C:\msys64\mingw64\include
  • C:\msys64\mingw64\x86_64-w64-mingw32\include
  • C:\msys64\mingw64\include\c++\6.3.0
• x64 linker search directories (example)
  • C:\msys64\mingw64\lib
  • C:\msys64\mingw64\x86_64-w64-mingw32\lib
• targeting x64 abd x86 we want to apply the same config setting to IGraphicsWin.cpp.
  $compiler $options $includes -c $file -o $object -fpermissive
• targeting x64
  • in stead of using compiler flag -fpermissive globally, we're applying this only to the cpp files that need it.
    • WDL/IPlug/IPlugGraphicsWin.cpp and whatever CPP has int main and VstPluginMain (in this case: arpeggio.cpp) have these settings however targeting x64, we need to apply the -fpermissive flag if you re-define a differently named GCC compiler in your CodeBlocks preferences (hence the project files).
      Right-Click the file and select the compiler targeting x64 (combobox), check the checkbox and type into the textbox:
      $compiler $options $includes -c $file -o $object -fpermissive.

Feel free to 'comment' any issues or questions on the comment sections of the github-commit pages.

NON-WINDOWS (noop)

Theoretically it be possible yet even easy but we need a few hacks into IGraphics to get the global timer (if its similarly implemented in windows) to trigger a call to void IGraphics::OnTimer and possibly implement some mouse-cursor native API for a particular text-control that'll end up being used in here. Otherwise you can simply disable the OnTimer updates all-together and move what is (currently) only text-updates to the audio-thread. I would prefer this to be an animation example not running off of the audio-thread in due time—even if I do have to buy an old duo-book-pro.

TODO

• few more ramp modes
• MIDI channel specific notes
• preset, bank?
• sub-intervals, div level 2 (another layer of divisions with pitch or other controller ramping methods applied)
• MODULATION MATRIX editor making for more PARAMs
  • mod wheel
  • pitch wheel
  • LFO/CC-trigger
• UI
  • param triggers for key-offset (pitch knob)
    • maybe note 'collision prevention' if it works out
  • skinning possibilities / *.ini er whatever
• presets and/or midi import/export
• There may or may not be prevention/detection for this in the future.
• what else?

license

© tfw 2016-2017
disclaims any to all liability

• cockos/wdl
• JNetLib
• LibPNG
• GifLib
• JPEGLib
• zlib
• taletn/wdl, github
• olilarkin/wdl-ol

all rights reserved