atsushieno
commented
4 years ago The list below is to describe how people can try out JuceAAPAudioPluginHost needs on Pixel2 (likely on any Pixel devices), step by step:
- make sure to install aappluginssample (otherwise there is no AAP).
- launch JuceAAPAudioPluginHost.
- disable audio input. It causes glitchy noises even on desktop.
- those mda-lv2 plugins do not expect sample rate 48000. Switch to 44100.
- adjust buffer size to less than 1000 samples. It's too big.
... and DO NOT try to make those changes AFTER you connected audio plugins. It will crash for WTF reason.bridge implementation issue, fixed at f591e25.- hold (long tap) on blank area and place MDA ePiano or Piano. Connect MIDI I/O and two audio outlets to the bottom-leftmost two.
- the dragging experience is horrible because it does not expect your fingers are on the same screen. It only premises mouse. Touch UI and desktop UI do not blend.
- Finally, play notes with the keyboard.
JuceAAPAudioPluginHost is often? always? horrible with low quality behaviors. It crashes very often only by changing audio settings. The app should consult plugins so that which sampleRate is appropriate (currently it blindly applies the device default sample rate). Each AAP should provide which audio device profile it can support through some property.
But in the end, JuceAAPAudioPluginHost (which is almost unmodified JUCE AudioPluginHost) is too low quality as a showcase. It is most likely problem in JUCE itself, but we need something more appropriate anyways.