This PR adds a path builder for NotReaper, similar to the path builder found in Reaper!
Clicking on the "Path Builder" button (or using the hotkey T) will open the beautiful UI:
Upon converting a note (or clicking on a valid pathbuilder note) the ui changes:
Pathbuilder notes act similar to sustain notes, with buttons above them to change the length of time the path takes to complete. The initial angle can be changed by holding down on a note, then moving outside the note to select the angle:
The options in the pathbuilding window are similar to the ones found in Reaper. One very important difference is that these values represent the final position at the end of the curve, not per step. I.E A value of 180° means the path will be semicircular in total, not incrementing by 180° per note placed)
As you change these values, you will see a line representing the path through all notes that will be generated by the path builder. Pressing "Generate Path", or exiting the path builder will place the notes.
Converting to a pathbuilder note is handled in undo/redo, although changing beat length or any pathbuilder values are not undo/redo-able.
The notes generated by pathbuilder notes are not intractable in any way, however the pathbuilder notes themselves are fully compatible as notes themselves, with the ability to move along the grid and timeline, and flip hand type as well as horizontally/vertically.
Some technical details
When saving out .cues files, all the pathbuilder notes are stripped and only the generated notes remain. The data is still saved, just under a new tag NRCueData. A sample looks like this:
When loading an .audica file with this data, NR will re-create the pathbuilder notes, and delete any notes in the original cues that match the generated notes of the pathbuilder. This does mean that if there are any changes to the pathbuilder algorithm, we will have to have some backwards compatibility path to load older NR saves without duplicate notes.
This PR adds a path builder for NotReaper, similar to the path builder found in Reaper!
Clicking on the "Path Builder" button (or using the hotkey T) will open the beautiful UI:![veryprettypathbuilder](https://user-images.githubusercontent.com/830434/68536825-ffd79c80-030d-11ea-874b-33bd47a073d4.png)
Upon converting a note (or clicking on a valid pathbuilder note) the ui changes:![fullpathbuilder](https://user-images.githubusercontent.com/830434/68536840-37464900-030e-11ea-9e6f-87342341e3aa.png)
Pathbuilder notes act similar to sustain notes, with buttons above them to change the length of time the path takes to complete. The initial angle can be changed by holding down on a note, then moving outside the note to select the angle:![initialangle](https://user-images.githubusercontent.com/830434/68536872-b50a5480-030e-11ea-810f-7fca57fb473e.gif)
The options in the pathbuilding window are similar to the ones found in Reaper. One very important difference is that these values represent the final position at the end of the curve, not per step. I.E A value of 180° means the path will be semicircular in total, not incrementing by 180° per note placed)
As you change these values, you will see a line representing the path through all notes that will be generated by the path builder. Pressing "Generate Path", or exiting the path builder will place the notes.
Converting to a pathbuilder note is handled in undo/redo, although changing beat length or any pathbuilder values are not undo/redo-able.
The notes generated by pathbuilder notes are not intractable in any way, however the pathbuilder notes themselves are fully compatible as notes themselves, with the ability to move along the grid and timeline, and flip hand type as well as horizontally/vertically.
Some technical details
When saving out .cues files, all the pathbuilder notes are stripped and only the generated notes remain. The data is still saved, just under a new tag
NRCueData
. A sample looks like this:When loading an .audica file with this data, NR will re-create the pathbuilder notes, and delete any notes in the original cues that match the generated notes of the pathbuilder. This does mean that if there are any changes to the pathbuilder algorithm, we will have to have some backwards compatibility path to load older NR saves without duplicate notes.