Description

STFT allocates an output buffer, but sometimes you might want to have it compute directly into an existing buffer. For example, in griffin-lim, the method alternates stft/istft for each iterate, which is then discarded. It would be better if we could give it an out= variable, which it would use instead of allocating a new buffer; this way, we could cut down on redundant mem

As code on master is Python3 only depndency on six should be removed and affected code needs to be adapted to use Python3 constructs.

• Consolidate Python examples notebook merging more examples from https://github.com/MTG/essentia-tutorial.

Also consider:

• TensorFlow auto-tagging and classification examples
• Audio problems algorithms examples
• Monophonic pitch detection
• SuperFlux
• Visualize various onset detection functions
• Constant-Q
• Real time analysis of an audio stream

Would be great to add some simple examples to the repo. Feel free to close if this is not something you're interested in.

Having read the Faust documentation, it is unclear what is the best way to get host tempo (BPM, speed etc) into a plugin DSP.

I am referring to DSP code that is compiled with the faust2/plugin/ scripts.

Can this be made clearer in the documentation?

I would like to propose the below adjustments to the installation guide.

Building on Debian-based distros

git clone git://github.com/jgaeddert/liquid-dsp.git
cd liquid-dsp
./bootstrap.sh
./configure
make
sudo make install
cd ..
sudo apt-get install qt5-default libfftw3-dev cmake pkg-config
mkdir build
cd build
cmake ..
cd ..
make
sudo make install

Tks

Motivations from this issue from Sporth.

dmetro has a few shortcomings which should be specified in the documentation.

Mainly, the things I wish to bring up:

• sample accuracy vs sample precision (and how the latter is more important in this context)
• why dmetro adds one sample to the duration in the seconds to

• Features. Update page. Among other things, add audio backends and formats.
• Upgrading. Add new "Upgrading" section. Provide instruction for upgrading from 0.1 to 0.2 (URIs, options, API).
• Network protocols. Add "Formats" section with links to RFCs for URIs (base, file, network) and SDP. Add RTCP and RTSP to the "Protocols" section.
• Data flow. Update "sender pipeli

Pressing the right click button a windows keyboard when editing the name of a new node, creates a dark grey box that glitches out when moving nodes around over it and doesn't disappear.

Edit: Added pictures for clarity

![image](https://user-images.githubusercontent.com/29534646/46904

As of PR #115 we started seeing warnings for clippy's missing_safety_doc lint. Unsafe functions should document what preconditions have to be met in order to safely call those functions.

Remove all instances of -A clippy::missing-safety-doc in .travis.yml (or whatever pipeline we're using by then) when resolved.

Now that we have auto-generated doc with http://dplug.dpldocs.info/dplug.html the docs should be more welcoming.

Expected behavior

Readme or installer or website does not mention where amsynth is installed to when users run the automatic packaged installer. I cannot find it.

Actual behavior

Running the Mac .pkg installer works, the installer completes successfully. However, I can't find the amsynth binary. There is no binary amsynth in /Applications or in home directory or in /usr or