|
|
Post by Stray on Feb 18, 2014 21:15:53 GMT -5
As of PXT-Live v1.1.0, hooks have been added that allow M4L devices to access/record/control aspects of Clip Play - Poly Sub-Mode. This M4L device provides examples of how this new integration works. Please post any questions/comments/requests about this integration in this thread. |
|
|
|
Post by beatkidd on May 23, 2014 20:08:29 GMT -5
Mr. Stray - I'm having a tough time implementing this one. I haven't spent a great deal with Max, beyond some Monome experimentation. Without holding my hand, is there any way you could point me in the right direction? My end goal is to have a Loop Recorder which feeds from the inputs created in the Mono/Poly Clip Play Submodes.
If this is built already in Max, I would gladly pay.
|
|
|
|
Post by Stray on May 24, 2014 6:16:03 GMT -5
First of all, just to be clear, this integration is currently only accessible for the Poly Sub-Mode.
At any rate, have you taken a look at the documentation in the M4L device linked above? This covers and demonstrates how the integration works. If you find something about this unclear, please feel free to ask for clarification.
As far as implementing functionality in M4L that utilizes this integration, I can really only be of limited help as I don't do much work in M4L. Generally speaking, the problem you're trying to solve is somewhat large, so I'd suggest breaking it into smaller chunks so that it's more manageable. For example, on the macro level, you'll need to be able to record and playback. I'd suggest figuring out one of those (each will consist of a bunch of smaller problems that need to be solved) at a time. In either case, I would think you'd want to start with something like polysync~. There's an example of that in the Randomizer sub-patch within the M4L device linked above.
|
|
|
|
Post by beatkidd on May 24, 2014 20:00:09 GMT -5
Stray -
Got it - thanks for the tip. I'm making some headway and running through a Max for Live refresher course. I will post an update as soon as I get this running.
Edit: I also now realize how ridiculous my original inquiry here sounded. I wasn't fully grasping that this was just a proof of concept.
|
|
dbk
New Member
Posts: 3 
|
Post by dbk on Aug 14, 2014 18:36:25 GMT -5
beatkidd, check out the [mtr] object in Max For Live, it´s a pretty good recorder. it doesn´t support looping but with proper bang methods it could work.
|
|
|
|
Post by crampe on Aug 17, 2014 11:03:05 GMT -5
Hi Stray
Is it still possible to grab/release (and thus repurpose buttons/encoders actions) through M4L when Push is in PXT mode, just like in the default Push mode ?
(I don't own PXT but I'm almost about to do it, I just need some little details like this one).
Cheers
|
|
|
|
Post by Stray on Aug 17, 2014 19:11:33 GMT -5
Welcome to the forum. No, that isn't possible. You can, of course, still use Push's default mode as you normally would while using PXT-Live/PXT-Live Plus.
|
|
|
|
Post by crampe on Aug 17, 2014 20:40:12 GMT -5
Ok Stray, thanks for your answer.
Maybe I should make a new post for this unrelated question, but... In the PXT videos the device mode looks like it doesn't give direct access to the various devices of a track from the 2nd row of buttons like in Push's default mode (it also looks like that their names don't appear). It seems that you can only navigate between them with the in and out buttons, am I right ? (I've search in the manual but didn't find any relevant information about this)
|
|
|
|
Post by Stray on Aug 18, 2014 6:07:49 GMT -5
Yes, that's correct though the name of the Device and the current Bank are momentarily shown in the display upon moving between Devices and Banks. It might be hard to see that in the video. Also, unlike Push's default Device Mode, PXT-Live's Device Mode can be locked to a Device directly from the controller. In this way, each Device Mode can control a different device.
|
|
