Device Details

Device Overview

Name/Version: Multi-Looper Visuals and Window 1.0
Author: pyamada  
Description: Forked from https://maxforlive.com/library/device/5526/live-looper-visuals-large-screen-looper-state.

This allows 3 loopers to be visualised both in the device GUI and on a separate window.

Let me know if there's some packaging issue.
 

Device Details

Downloads: 234
Tags utility
Live Version Used: 11.0.5
Max Version Used: 8.1.5
Date Added: Aug 16 2021 01:04:35
Date Last Updated: Not updated yet
Average Rating -n/a-
Rate this device: (must be logged in to rate devices login)
Device Type: audio_device
URL (optional):
License (more info): Attribution

Device Files

Device File: Looper Control.amxd
 


Comments

Hey pyamada, thank you so much in advance! This is pretty much what I?ve been looking for since ages... and it works on return tracks!!!! BUT: all three loopers should be on the same track!??! Wouldn?t it make more sense to have the ability to show/hide looper 2&3? Like one floating window represents one looper... or being able to set each looper visualization from a seperate track! So if i see the status of three loopers but sitting on track 1,2&3 for example! cause in my case my 8 loopers sitting in return 1-8, and i really just need to see 2 or 3 formy band mates... I would even pay something for this feature!!! But Mostly important your device works!!! Cheers man!!!

Hey, realVZI, I think you could achieve that with the original device, just drop one on each track.

I've tried to document the whole patch on https://yamadapc.medium.com/looping-ableton-and-max-for-live-patching-5cd8d80cdb77, that might be able to help you modify it to suit other needs.

Hey! Great idea and great device! Do you have any idea why I might not be able to get it to recognise and display the track names correctly?
In my projects, the trackID is always displayed like yours, in the tutorial/blog post. "Super freeze pad", etc.

I'm guessing it's got something to do with 'get name' from the Live object, but I can't pin down exactly where it's going wrong.

Hm... I see :D then I might have bugs. Let me try to address this in a bit.

Login to comment on this device.

[ browse device library ]