User Details

Username: mganss
Website: None provided
Facebook: None provided
Twitter: None provided
Soundcloud: None provided
Account Status: enabled
Member since: Dec 20 2018
About mganss:
(report this profile)

Devices by mganss

Aicd Version 1.3.1
LFOi Version 1.2.1
DrumBrain Version 1.2.1
MidiMorph Version 1.0
Image to MIDI Converter Version 2.0

Total Downloads: 4,414


Comments by mganss

Comments

@daveybfire The clips need to be on the same track as the MidiMorph device. Select a clip first, then click the button on the MidiMorph device you want to assign it to (from, to, out). The button should then be active (yellow using the default theme in Ableton 10) and show the name of the clip. As soon as you have assigned all three buttons the out clip should be filled (assuming from and to have any notes in them :).

It's not necessary to always have an out clip assigned, though: The device will play the current pattern through its MIDI output (if the play button is on). Also, you can click Clip to create a new clip in the current track.

If it still doesn't work, please open an issue at GitHub. I don't get notifications of new messages here :(

@braduro It's a 5x5 two dimensional array of static patterns (hard coded). The axis resolution is 8 bits, i.e. there are 256 steps along each axis. For each coordinate, the closest pattern from the 5x5 array is determined along with 3 neighboring patterns. These are then linearly interpolated to compute a pattern for the chosen coordinate.

Each step of a pattern is an 8 bit-value that encodes the "height" of the terrain at the coordinate in the map. The density parameter works like a sea level setting, i.e. it defines a threshold where the terrain becomes visible/audible. The height of the terrain is additionally modified dynamically by a random value.

I couldn't find any indication of how the array of static patterns was chosen or generated. That would have been very interesting, because the Mutable Instruments product page mentions "a healthy dose of machine learning and graph algorithms, megabytes of drum loops, hours of intensive computations".

@mots VS Community Edition is now free. I don't have time to try this, but another idea would be to use emscripten to port the code to javascript and get rid of the external.

Great pragmatic device. Thanks for sharing.

I have modified it to make it MIDI mappable.

@Prebentious Can I share the modified version as a separate device?

@broah Thanks! Tbh I haven't actually done anything with it yet. I just thought it was a cool idea and became fascinated by the problem space (assignment problem, Hungarian algorithm etc). My initial intended use case was to automatically create subtle transitions from one drum pattern to another (or possibly bass lines).

I also would love to hear about actual uses of the device :)

The settings for random mode now flip out to the side in v1.2 (click the little dot next to Random to toggle settings).

@hatyn I can't repro. Which version of Live are you using? Can you provide steps to repro (preferably based on a fresh set)?

I've checked: AFAICT the "Parameter Visibility" cannot be set through attributes at runtime. You can easily edit the device to disable undo for patterns, though: Open Max, Uunfreeze device, select the "patternStep" object (the live.step sequencer object) and set "Pattern Visibility" to "Hidden", save the device.

@mafgar Thanks! I can't repro the issue, though. Playback starts in sync with the arrangement position (the bars-beats-units counter at the top next to the play button in Live) which doesn't have to be at the beginning of a bar.

@broah Thanks! I'll check if I can make it configurable. I want to keep a way to go back to a previous pattern, though.

@telkmx Did you use v1.1? If so, can you provide steps to repro?

Sorry, fixed in version 1.1. Max seems to do this automatically when the project setting "Keep project folder organized" is enabled.