Max for Live MIDI Tumbler
Budget: $750 – $1,500 USD
I’m commissioning a Max for Live device that can scan, cache and serve up 10 k–50 k MIDI files from both local drives and a NAS without choking Ableton Live 12. The device—internally called “MIDI Tumbler”—must:
• Build and refresh an index of every MIDI file inside a chosen root folder (recursive) and hold that index in a local cache for fast recall.
• Pick files with a weighted-random algorithm that respects subfolder or genre depth, remembers recent plays and avoids immediate repeats.
• Drop the chosen clip onto a user-selected track, auto-loop it to bar length, and rename the clip in a clear, human-readable way.
• Co-exist peacefully on the same track with ReMIDI 4 and Captain plugins; no parameter clashes, no MIDI routing surprises, and minimal CPU/RAM overhead.
• Work strictly with .mid data—no audio or project files needed.
Deliverables
1. A fully functional .amxd device.
2. A concise PDF covering installation, setup, common troubleshooting steps and an outline of the caching strategy.
3. Thirty days of post-delivery bug support.
Schedule & terms
• Demo build by Day 7, final build by Day 14.
• Work-for-hire with a mutual NDA (both docs ready on request).
Max for Live – MIDI Tumbler (Random MIDI Loader | $800 | 2 wks)
To keep things smooth, include with your proposal at least one prior Max patch that handles large-scale file operations, confirmation you’re fine with the NDA/WFH arrangement, reassurance on the two-week turnaround, and a brief sketch of how you’ll handle the cache.
• Build and refresh an index of every MIDI file inside a chosen root folder (recursive) and hold that index in a local cache for fast recall.
• Pick files with a weighted-random algorithm that respects subfolder or genre depth, remembers recent plays and avoids immediate repeats.
• Drop the chosen clip onto a user-selected track, auto-loop it to bar length, and rename the clip in a clear, human-readable way.
• Co-exist peacefully on the same track with ReMIDI 4 and Captain plugins; no parameter clashes, no MIDI routing surprises, and minimal CPU/RAM overhead.
• Work strictly with .mid data—no audio or project files needed.
Deliverables
1. A fully functional .amxd device.
2. A concise PDF covering installation, setup, common troubleshooting steps and an outline of the caching strategy.
3. Thirty days of post-delivery bug support.
Schedule & terms
• Demo build by Day 7, final build by Day 14.
• Work-for-hire with a mutual NDA (both docs ready on request).
Max for Live – MIDI Tumbler (Random MIDI Loader | $800 | 2 wks)
To keep things smooth, include with your proposal at least one prior Max patch that handles large-scale file operations, confirmation you’re fine with the NDA/WFH arrangement, reassurance on the two-week turnaround, and a brief sketch of how you’ll handle the cache.