ArpGun is a powerful chord and arpeggio generation tool for Renoise, built upon the foundation of the legendary ChordGun. It allows you to quickly insert complex chords into your patterns and instantly transform them into a variety of arpeggiated patterns across successive lines.
ArpGun is an evolution of ChordGun, originally developed by pandabot. While ChordGun focused on rapid chord entry on a single line, ArpGun extends this functionality to support rhythmic āspacingā and melodic movement, making it a complete tool for both harmony and rhythm.
Is it possible to integrate Renoise 6.2 API for Note playing too? I would prefer it over the old OSC Server method. It could be maked choosable about Tool preferences config.
I considered updating the whole plugin to be compatible with 3.5+ and then felt like I should keep it as backwards compatible as possible. Would it be better to just have it be as modern as possible?
I see it a few more differentiated! Backward compatibility is a good thing! But supporting new technology is it too. So if you ask me that from the standpoint as a Renoise user i would answer you: I want both possibilitys!
From developer sight this is something more complex!
My personal Meaning as dev isā¦ Let the user Choose!
Why?
Thats simple. The old code exist and is approved and stable. The work is done and time and effort was done for it! So you should not waste it. Use it!
New code must be developed with new work- and time effort in any case.
So the decision on the end is. How big are the costās of supporting both ways! As long the old API is working and only marked as ādepreacatedā you can/should support it too. It is marked as āEnd of live / intended for removalā you should not.
The cost in this case are fairly low. A checkbox in config dialog and the branching logic behind. If old code is good structured there should be no problem to integrate it. If the old code is āSpaghetti codeā then the costs are higher.
The basic principle for compatibility is this: as long as the APIs are available and functioning, and the costs of implementing and maintaining are lower than the development costs of the old code, compatibility should be retained.
UPDATE: I have implemented the requested features:
It now includes:
Renoise 3.4/API 6.2 Requirements: Explicitly states the need for Renoise 3.4+ so users know that OSC is no longer needed to play back/audition native notes.
Euclidean Rhythms Documentation: Adds the Euclidean features to the list of capabilities and clearly explains how to access them using the new āTiming Modeā contextual dropdown (Standard vs. Euclidean).
Write Modes Clarified: Updated the old terminology (āInsertā) to the correct term (āMergeā) to accurately reflect what the dropdown does compared to Overwrite.
Current Build Info: Updated the installation instructions to refer to the latest package file (ArpGun_v1.0.xrnx).
Thank you very much; this is a very useful tool for me.
Is there a way to disable the note preview using a keyboard shortcut or a mouse click? I couldnāt find one in Chordgun either. Right now, I stop the preview using the MIDI mapped āStopā button on my MIDI controller, but that also stops the entire song.
Click on a chord with the mouse while not in recording mode, the selected instrument plays it (preview, without inserting). But the chord doesnāt stop, it just continues playing. Would be nice if a second click on the chord or a right click would stop it.
