Enhancement Summary

It would be helpful to include BPM tags for the built-in samples, particularly those in the "beats" folder. For example, "909beat01.ogg" has no BPM tag.

Justification

All of these beats sound great on their own, but its hard to know how to use them in a project without knowing the BPM of the sample. This goes for all of the loops within the "beats" folder.

Wondering if you could provide a basic example on how to use this in a express app?

Starting from v0.15.4, Giada supports a primitive form of mono/stereo plug-ins. Full support is welcome, where the user can customize the channels layout through the channel matrix (see Reaper for example).

Useful JUCE classes:

https://docs.juce.com/master/classAudioProcessorGraph.html
https://docs.juce.com/master/classAudioProcessorPlayer.html

Readings:

https://forum.juce.com/t/audio

You already mention the licensing in the README, however, having a LICENSE or COPYING file in the repository would make it easier to spot what license is used.

Additionally, the individual code files are currently having a header which smells like "All Rights Reserved". Ideally they'd receive a file header which would restate the license (GPL header and a note that commercial licenses are avail

I tried running the documentation generator and the following error occurred:

PHP Warning:  preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /home/joe/git/xrnx/Xtra/HtmlGen/api_to_html.php on line 152

And it spit out .html pages with no documentation.

I have PHPv7 on my machine. I've never touched PHP code before, so I looked at their docs and

See tooltip API https://material.angular.io/components/tooltip/examples

It'd be cool if when playing and selecting audio at the same time, when it paginates, if it did a little animation of the end of the selection that you're dragging from where it was, spatially, to where you're dragging,
so that there's not a jarring recontextualization of spacial... [whateverything](https://www.reddit.com/r/LibraryofBabel/comments/7p2zyf/always_coin_unique_new_terms_thats_my_mott

Currently all operations done on the synthesizer properties aren't stored in state history, therefor they cannot be undone/redone.

Link these actions to the state module.

Question is: do we maintain a separate history for the instrument editor or do we think it is logical that upon closing the window, clicking undo/redo restores the slightest of changes made to all the sliders in the now clo

// Clear flags
void CGenCF1::ClearFlags(int step1, int step2) {
if (!skip_flags || flags_need2) {
fill(flags.begin(), flags.end(), 0);
fill(fpenalty.begin(), fpenalty.end(), 0);
}
flags[0] = 1;
for (int i = step1; i < step2; ++i) {
anflagsc[cpv][i] = 0;
}
}

• structure and format
• compression - gzip w/ brotli or zopfli?
• buffers
  • markdown
  • ChucK code See #7
  • Faust diagrams See #11
• pattern data
  • notes
  • envelopes
  • per-note
  • per-channel
  • per-pattern
  • per-document

For patches with note-based keyswitches, the bank list should somehow show the note numbers to allow for manual triggering without needing to open the patch.

Currently, gfx_text is used, but it is very inflexible. gfx_glyph is lower level but should satisfy flexibility needs.

Bitmap fonts / pixel perfect TTF is not supported in gfx_glyph as well as gfx_text. We can live without.

Repository

https://github.com/to-the-sun/amanuensis

Details

The Amanuensis saves a file called Amanuensis.json which stores all of the general settings for the program, including audio driver, folders, the tolerance and memory span, compressor settings, gain levels, as well as all of the last used sounds for each track. This information is stored and recalled through a single preset (