Alexandernaut released Arpeggionome Pro (Matrix Arpeggiator) v.1.3 with Ableton Link Support

SYNTH ANATOMY uses affiliation & partner programs (big red buttons) to finance a part of the activity. If you use these, you support the website. Thanks! 

After the release of the new version of Fugue Machine, Alexandernaut released today also a major update for the Arpeggionome Pro (Matrix Arpeggiator) app for iPad. One of the best news is the support of Ableton Link. Also this app is now ready for the upcoming AudioBus 3 app.




































What’s New in Version 1.3.0

New Features: 
  • Ableton Link Support: Ableton Link is a new technology that synchronizes beat, phase and tempo of Ableton Live and Link-enabled iOS apps over a wireless network. It’s awesome. Go to Settings>Ableton Link Settings for more info.
  • AudioBus3 Midi Support: Audiobus 3 brings MIDI support to Audiobus, and Arpeggionome Pro is good to go :]
  • 64 Lil Bits: Arpeggionome Pro now supports 64 bit architectures. Yee.
  • Dotted Notes: Arpeggionome Pro has a new setting called ‘Matrix Mode’, which adds dotted note values to the Performance Matrix. To try it out, go to Settings >Interaction Settings and set Matrix Mode to ‘Halves+Dotted+Triplets’. You’ll notice the matrix now has two columns of squares, triangles, and dots.
    • ■ Rows with squares play rates that are perfect halves of a measure — starting at 1/2 at the bottom row.
    • ● Rows with dots play rates that are the dotted values — i.e 1.5x the length of the square row above.
    • ▲ Rows with triangles play rates that are triplet values — i.e. 0.33x the length of 2 square rows below.
  • Alt Interaction Settings: In Settings>Interaction Settings, you’ll also find a new button at the bottom of the list called “ALT Interaction Settings”. This is an alternative interaction state that I recommend trying. It’s a bit more difficult to control, but I find the results quite interesting. Compared to the “Default Interaction Settings”, it uses the new Matrix Mode setting and disables Retrigger for all parameters.
  • Bug Fixes
  • Virtual Midi Clock Bug: In previous versions, when listening for MIDI Clock on the Arp MIDI In port, Arpeggionome Pro read the MIDI clock twice, and therefore went twice as fast as it should. Fixed now.
  • Notes about this update: Hey, it’s been a while! The last time I looked at the Arpeggionome Pro code base was over 2.5 years ago! Time is weird. In any case, I’m really glad to finally get this long overdue update of Arpeggionome Pro out. And I’m especially excited about adding Link and the new Matrix Mode setting. 
  • On Link: By supporting Link, Arpeggionome Pro has actually become more playable, and perhaps in a not-so-obvious way. I’ll explain… As you may know, Arpeggionome Pro is designed to play super fast arpeggios. Further, it’s designed to be held in your hands in portrait mode, so you can quickly perform changes with your thumbs. Also, under the hood, all changes you make are quantized — allowing you to anticipate time by touching a parameter early, so the change happens at exactly the right time.This is great, and works very well… However! It’s always been a challenge to start the sequencer from not playing to playing. You could press the play button and just let it run, but if you wanted to control starting and stopping in a more expressive way (which I very much prefer!), it gets a bit more complicated. That first touch would always happen the moment you touched, but every other touch would be quantized. Subtle difference for sure, but definitely weird. Ideally, what should happen is that all touches are quantized, even that first one. So that, when you stop and start playback, it starts quantized, just like the other touches. So, something exciting… This is exactly how it works now! And it’s all thanks to Ableton Link :]
  • On Matrix Mode: Basically, at some point after releasing Arpeggionome Pro, I realized how I missed an opportunity to have dotted note lengths on the Performance Matrix — it launched with just halves and triplets.  Yes, I could have just updated the app… but since I try to be super strict about not changing UI after an application has been released, I just accepted it and moved on (see Fugue Machine and Link to MIDI). However… now that I’m here and revisiting the project, I figured out a way rationalize adding it… by simply burying it in an optional setting. I think I’m ok with this :] 

Be the first to comment

Leave a Reply

Your email address will not be published.


*