Undoubtedly a very useful device and a great piece of work. Massive props.
Maybe a next phase could be a glide feature so that parameters do not jump from one state to the other as this may cause clicks and unexpected gain issues when used live. I have done enough Max4Live programming to appreciate that this is orders of magnitude more complex, but it would elevate the tool to an altogether different status. I have implemented this for one parameter in my unit2 device which is on maxforlive.com so I know it is in theory possible.
Just my 2p worth.....
Kapture - next phase?
-
Macrostructure
- Posts: 665
- Joined: Wed Dec 22, 2004 2:51 pm
Re: Kapture - next phase?
This doesn't strike me as necessarily orders of magnitude harder. It's either possible or not. My assumption without looking at it is that is involves the pattr system. If that's the case, then it enables interpolation right off the bat.
I've been meaning to check into this patch. Perhaps I'll look at it now.
EDIT: Whoa, now that's some nice use of js with the api. I would prefer a tutorial but...
I've been meaning to check into this patch. Perhaps I'll look at it now.
EDIT: Whoa, now that's some nice use of js with the api. I would prefer a tutorial but...
Re: Kapture - next phase?
One thing that I noticed was that the "filter" is not midi-mappable. However, this can fixed by control/command clicking on the subpatcher, selecting to edit the original, copying these guts and pasting them into the actual patch. Then, swapping the toggles with live.toggles would probably work. I think this would be a good thing to try out if I were to use this patch heavily. Seems that otherwise there are lots of cpu-based jumps and scene-change-based audio-level/continuity-spikes.
What I meant in the last post about wether or not it could be done was sort of what I expected, or what I feel I saw when I looked at it: changing all of these things dynamically at once seems to make a big impact on the performance of the set. I don't think it's so much a question of building the set much differently as much as it might be a natural limitation of the implementation of m4l with the pattr system, or perhaps just the pattr system.
What I meant in the last post about wether or not it could be done was sort of what I expected, or what I feel I saw when I looked at it: changing all of these things dynamically at once seems to make a big impact on the performance of the set. I don't think it's so much a question of building the set much differently as much as it might be a natural limitation of the implementation of m4l with the pattr system, or perhaps just the pattr system.
Re: Kapture - next phase?
Is it possible to use Kapture without an iOS device? I'd love to have this functionality via a button press on my APC, not sure if it's possible though.
tarekith
https://tarekith.com
https://tarekith.com
-
Macrostructure
- Posts: 665
- Joined: Wed Dec 22, 2004 2:51 pm
Re: Kapture - next phase?
sorry, but what is an iOS device and why is it relevant?
Re: Kapture - next phase?
iOS the operating system on iPhones and iPads, and this Max for Live software called Kapture also exists on that platform.
-
Macrostructure
- Posts: 665
- Joined: Wed Dec 22, 2004 2:51 pm
Re: Kapture - next phase?
Just downloaded the M4L demo so I can try out Kapture (and the other great M4L devices of course).
I'm surprised there's no ability to switch between presets via MIDI CC without going in and making the necessary tweaks. I would figure for live performance this would be the obvious logical thing to implement.
Anyhow, I did look under the hood to see if I could switch the menu with buttons so I can assign the buttons to MIDI but I'm doing this without reading the manual, needless to say, I have gotten nowhere even though I'm having fun geeking out a bit.
Since I only have 30 days to demo this, I was wondering if anyone here can tell me what I need to do so i can switch between parameters with MIDI?
I'm surprised there's no ability to switch between presets via MIDI CC without going in and making the necessary tweaks. I would figure for live performance this would be the obvious logical thing to implement.
Anyhow, I did look under the hood to see if I could switch the menu with buttons so I can assign the buttons to MIDI but I'm doing this without reading the manual, needless to say, I have gotten nowhere even though I'm having fun geeking out a bit.
Since I only have 30 days to demo this, I was wondering if anyone here can tell me what I need to do so i can switch between parameters with MIDI?
Re: Kapture - next phase?
Not being a dick: spend the first of your ten days doing the tutorial. Otherwise you will be off to an ad hoc start and you will never know if you were meant to get this thing. The plus side is, the tutorials are fun, straightforward and will expose you to universally useful and creative stuff. Don't bother tweaking without doing the tutorials. You will be wasting your time and anyone else's with questions. Don't hesitate to ask questions on this forum about max. We need to generate some more helpful discourse over hereStrut wrote:Since I only have 30 days to demo this, I was wondering if anyone here can tell me what I need to do so i can switch between parameters with MIDI?
Re: Kapture - next phase?
Found a nice work around for those interested:
http://forum.ableton.com/viewtopic.php?f=35&t=161474
It works for me putting Kapture on a MIDI track and naming the track Kapture (not Kapture Pad as someone in that thread stated). Then name each clip in accordance with the preset names on Kapture and oila. Just set each clip to MIDI and you're good to go.
http://forum.ableton.com/viewtopic.php?f=35&t=161474
It works for me putting Kapture on a MIDI track and naming the track Kapture (not Kapture Pad as someone in that thread stated). Then name each clip in accordance with the preset names on Kapture and oila. Just set each clip to MIDI and you're good to go.