CHAOS | July 15 2013 | 16.7 MB
AudioMulch is an interactive musician’s environment for PC and Mac. It is used for live electronic music performance, composition and sound design.
AudioMulch allows you to make music by patching together a range of sound producing and processing modules. Unlike some patcher-based programming environments, AudioMulch’s modules perform high-level musical functions, so you don’t have to create things from the ground up using individual oscillators and filters. AudioMulch is designed for live performance and improvisation – you can process live audio sources and control every knob and slider on the user interface using a MIDI controller.
Changelog
This is a stability update. It fixes several crashes and bugs in the LoopPlayer and LiveLooper contraptions, Audio Unit hosting and Network Synchronization. If you’re using AudioMulch 2.2.0 thru 2.2.3 we recommend that you upgrade to this version.
Fixed LoopPlayer bug where a muted LoopPlayer would sometimes start unmuted until the beginning of the next bar. This happened if a document was first played starting from anywhere other than the start of a bar (including when synced to MIDI or Network Sync).
Fixed extremely distorted audio when using over-unity floating point sound files in some contraptions (e.g. LoopPlayer).
Fixed LiveLooper crash when creating very short loops.
Fixed LiveLooper assertion failure crash “Assertion failed: (state_ == RECORDING)” if automation or MIDI control tried to clear a track while it was recording.
Fixed intermittent LiveLooper assertion failure crash “Assertion failed: (nextRecordTrack_ == 0)” when all tracks were empty.
Fixed AudioUnit hosting bug: sliders in the generic editor were not updating when parameters were changed using the custom editor or automation.
Fixed Network Chase Sync bug where tempo could sometimes become unstable (even after resetting sync by toggling enable audio off and on again).
Fixed rare crash in automation graphics rendering triggered by MIDI and/or Network Chase Sync bug(s) above.
Windows: fixed issue where no audio devices were listed if any ASIO device returned an error at startup. The MOTU “MOTU PCI Video ASIO” device was triggering this behavior when not connected and powered on.
[toggle title=”Home page”]https://tinyurl.com/697s3v[/toggle]
http://alfalink.to/4529f345e74a6a27ccf7
Please REPORT in Comment Broken Links
