Push developer kit: M4L devices for Push!

Come here to discuss Push with other users.
For tech support, please head to http://www.ableton.com/help
greaterthanzero
Posts: 103
Joined: Tue Apr 09, 2013 5:48 pm

Re: Push developer kit: M4L devices for Push!

Post by greaterthanzero » Fri May 31, 2013 1:23 am

To clarify:

You're not running a monome emulator on the Push hardware. Nor is Push communicating with any monome protocol, at all. What you are doing is replacing the monome communications in a monome app with an equivalent connection to the Push hardware.

(Did you download polygome? Note how it doesn't require you to nest all any monome software to run. Way you're building won't either.)

But, yeah. This isn't a beginner-friendly task. If you don't know how monome apps are put together, you're going to have a real hard time replacing the guts of one without breaking everything.

greaterthanzero
Posts: 103
Joined: Tue Apr 09, 2013 5:48 pm

Re: Push developer kit: M4L devices for Push!

Post by greaterthanzero » Fri May 31, 2013 7:57 am

flocked,

This has probably been brought to your attention already, but I just noticed that [p push_scene_buttons] doesn't respond to the "all" command anymore. ("set" still works, no problem.)

zigzag
Posts: 155
Joined: Wed Mar 19, 2008 6:29 pm

Re: Push developer kit: M4L devices for Push!

Post by zigzag » Sat Jun 01, 2013 2:29 pm

greaterthanzero wrote:To clarify:

You're not running a monome emulator on the Push hardware. Nor is Push communicating with any monome protocol, at all. What you are doing is replacing the monome communications in a monome app with an equivalent connection to the Push hardware.

(Did you download polygome? Note how it doesn't require you to nest all any monome software to run. Way you're building won't either.)

But, yeah. This isn't a beginner-friendly task. If you don't know how monome apps are put together, you're going to have a real hard time replacing the guts of one without breaking everything.
I can't say how much you have helped me in understanding what the tasks are in converting monome apps to push-controlled ones. If I get further and manage to convert some apps, I will be posting my results here.
Again, many thanks for all your time/effort

Because789
Posts: 440
Joined: Thu Apr 28, 2011 1:26 pm

Re: Push developer kit: M4L devices for Push!

Post by Because789 » Thu Jun 20, 2013 5:37 pm

From the Max 6.1.3 change log (http://cycling74.s3.amazonaws.com/suppo ... 6_1_3.html):

"•closebang: works as expected in M4L devices and Max"

Just tested it with the patch below and the Push button matrix is still not released when you delet the device *sighs*

Did anyone find a workaround in the meantime?

Code: Select all

----------begin_max5_patcher----------
2211.3oc2bs0iiZCF84rR8+.JpOlF4qbou08s9PU66qphHAOYXWBDAjYmNq5
+85K.AHPvSBv3zc0DRrA7wG+cyeX7O9oOsX41jWYYKs9UquXsXwO3krPVlnj
EkErX4A+W2E4mIOwkwrumr8qKWUTWN60bY46hRxXa8i2WU0SIw4w9GXxp+sz
P+HqOmDETUe7oCgwQrb48EVVZXf774swu.qN0jS47SL+eNxTfcorgr96x5O5
mu64v38aRY6xUmBAAWiwXDEsxBaiWCwHWHdkkMXMXkEzcM37kyQhpEZBEQGH
K7MYaB4Wlr3+8m9j3H+vJs4rcIGNvhyujzRYQL+L1HRY1muWo62JJWze6mlv
T7Za9+P1bZh3rFXC.TuUVDugnoy20TVFu24mGlD2.W0qnVSBo1h6Muw7bcv.
Z2M1zS96S82NhLO5cx7HnWmLOFLYLOk1h36psFMhe6o7bNtzlActG08FrYM0
cjrGJ9bP08aiMsIUib0aqYi0n2Cq0P6edXsBs+wl15yszaQqSYWymT2LMpKM
bGb+b8xU7+ttDJ2JGrfqI.u0tHOHP3bhNj9NZzUMmA1BA.2CagccpbeaprUT
3Kr07ZDf9l7izIuguRXOCHggQUZyHtocHB.gN2UHOkkm4+BKXiputwOOOMja
mRE53hyz1hkaNxRyByxYw6T2CUEEr9Mw9GXYY96YcDwoeTjkvI9lcbTmlDYE
FX8yvwbn.cyCE1zJkcL.WYqCJFE3GrmyvOuNCVDC5zQh3akDIbhqJD95jXQX
KyJI1mQfSwG828MKf3+iWzjH7U7qGJhlswA8MKXipnQG3PlEvyrn3dVdkX3m
kwAs4O741ZdcLEGcFCyqPr8ZpCxgR3emRLGwwiBR72C9ym9qSYOOlxit2toP
PEs43HXJGu61ejrcXoW3+4ovH1KBWPMCFcwR+iGqU9h5WjfY+Zh7dYu5bYgw
pxfmKKk8RX4s.etX+TdeNm2gOkpX3WsIKKpULnVhgZV1jw.CAR5f3JUDoPZM
BgK.rOJY22XA0mwGm7OxhCiaGz845CXO4eJJeSChCst6S3IekW5tqs6H+Vvm
2bXPRr.HMuVQ4kMoHNeYWrYeRdJw9G65xy3cmSYa8SEb71HVcMXt.dRRTy5N
O1xUU7iCO3myxCUPlG7YUsgGNlJsQVuwXw97ayyY63lZhZd2TU8RWUEvG+2w
9dXP9yMmeunJ9EDdrb.Y4Y5JHbOKKuUg496yZUTibw0P9rtwflUbUiBsR0DW
8hYEdNQH5XXneapsMPXCabMCDwee1Jbk5ETOoAB5kgsdkv8627Z8.PWTYlc7
Y32hr3lexYoV0s8NxzLXDoYaYrnNOdz7dtv7QK2ogho1iHECUl1cern3H9L3
d5TbLK59nXXeT7.FKDsu1TLQJ+Ro5PwPighUlik84IQJ1c7DhIpIJP8drDhy
s1ZMQxunALQndLX5vvPNsHxCumjowDwOLKJt0L1Z8HTJ51ShHLhLfLrtxuHr
7f8EyRynsPzQ1EGW9kzTJdWRjZBOegGXqmKAC4ysEr1E5YCbEeCPAd7u.aSf
29.CwQeCKWcfodcCjpxViGWlxxyix0GlmugbNc87DY1BLUC3qz0iRo8tBWJP
cF4wFiJIeZ27osFXIFhrJRT0lrSoh4QmMMiYDu60HXIkSTYoh5XdAJcUeLfI
JLevcSrdRhEoLlgQRe2OLtW1kbJlOW06ibo8PtvAbcWj55x+ZjB6gjigJ+3P
sjiIFCee5svoQPFR0KXzxiuGxtP1VOaFlic5LVj0DY1f3NVg9SkA6i.xbCfw
OVStpHahASDI6LFydkVLaJRwhd5AjfG2XL5ktGkjJVZxPIPCgOboKHzZ6zDC
GzVKugMWtVCQypkQkm2ioX8oo54P.cFQY4BaG1TyijGJsLRJdtre.u2PowtR
5VsR.EOaciKSMWmuSxSrNcbhjn8FoIpTPuEdBebXW4rsEoFYSFahrZftaIXD
wtFGWrzZdrx03Dl3IzGdhmJrvnVJjdFXdmjrX+TKnOpcjDbQx.IPzxO0Vts7
0qPtXFFcVQ0p2PHWK0JCz1Dp9cav70sGTWM+4vL0pQYhdBsD8llaWqAwAjzb
n8rFvFIUvZK2nnv3dWRMR.JNgdFOxRNktqr6V7DUsZA1.VVdXb0pv5KmW.As
OymCCBZsfmTqMnLwhMJn4ycXPon2M1EqNG8.Oz7vNPWraadfuKYgdjZLPvSz
E7HCD7ZKx2k.1GM30VlWjocKjQAdwirRSwFyi4IZalmnuL+gvfiIbejE9hrk
YU.gImWyGM9ATtfcsHEIRC01G4rxEPsjB8tUtvQ1IQDYD4H4yPqwOf.EYATo
FP7qOHxvQaACWySpVa2PFH101PtXZllF3AuqnFg2hJTQNGPD4yPBUpQU+WDO
UReT1Wj+5CRKReGalWTzHacsGRzevbVAudpQDyi40NRThAJ1fzVrwwLAORKE
VCD7OxtNPZapDYfx7Z61y7L1.8dfkZf5Glp4M4Kn1NXoFJ30KzFp4Ad56JgC
FF30O5.uQE7E6WM0dIe0dix39eMb03M88c8Jo1MRtFB5sk2Gkr0Op3czt5p6
5se892dP56EgW75+DNlu.7dCrQKo0VwPs2EdHDtl.ITJrZwC++3c0FB3l2+.
puuI4.VioDhG5QeWs4pre8mD+HH5RfCrSLM7dWkCoZL.5cd+iiZRagHc9VYL
t6kMDxMKEWmAscVS.PWpbAiLZaHPpqu4C8rfRa6RsjXuvUZynG6cld3lm1kt
P6v8Ymi0ZCLpN.StmiMy.SJSnAzZkFy4AZvFwS2Kz.MOMCBZX37CMgmdcXMx
7Ofh8zRVC67A.MW8fl2G.zbzCZe.Znhs4qZoWqWngMWng9.fFVeuAyswCj9d
PmanA0SMfN+Cns8aeMGUyKztHVGCBZyQHQEAU1Z6SSho1aaZs2xz5X6Rq2sJ
MYCx+3+Pa8cga
-----------end_max5_patcher-----------
Live 9.5 (64bit), Max 7.0.6, Windows 10, Push 2, Korg electribe2, Bass Station II, Launch Control XL, Faderfox DJ3

M4L

greaterthanzero
Posts: 103
Joined: Tue Apr 09, 2013 5:48 pm

Re: Push developer kit: M4L devices for Push!

Post by greaterthanzero » Thu Jun 20, 2013 11:59 pm

Only being in the habit of disabling Push-centric devices before we delete them.

(Again, it is not necessary to select "off" from the drop-down menu. Toggling the device itself is sufficient)

ZALTA19900
Posts: 26
Joined: Sat Jun 22, 2013 5:29 pm

Re: Push developer kit: M4L devices for Push!

Post by ZALTA19900 » Mon Jun 24, 2013 1:28 pm

very good work

irrelevance
Posts: 463
Joined: Tue May 20, 2008 7:31 pm

Re: Push developer kit: M4L devices for Push!

Post by irrelevance » Mon Jun 24, 2013 1:58 pm

You're right. This glitch happens occasionally when using external VSTs / Live effects with high CPU usage or when switching devices. For this glitch it's the latter. I'm still working out a couple bugs, hence the reason I haven't released this out into the wild yet. It seems to be related to efficient data flow through the max patch which is harder than one would think. Dealing with the javascript adds a level of complexity. I did, however, want to get a video out to demonstrate what's possible with max for live, this developer kit, and Push. Florian Zand has done a great job putting this kit together. Without it, development would be taking much longer.[/quote]

Hey Blenny just reread my post and wanted to apologise as it seemed I was nit picking for the sake of it when I'm sure you were already aware of the issues and was simply sharing your efforts here in the thread.

Also wanted to thank everyone who has worked on and posted the Matthew Davidson device port for polygomé...very inspiring tool! Having great fun :)

Because789
Posts: 440
Joined: Thu Apr 28, 2011 1:26 pm

Re: Push developer kit: M4L devices for Push!

Post by Because789 » Thu Jul 11, 2013 5:58 pm

Here's a method to send a 0 when you press the User button and a 1 when you switch back to Push mode (= press the User button a second time):

Code: Select all

----------begin_max5_patcher----------
839.3oc4X10aaBCEF9ZpT+OXg1kYQXCl.6hIs9eXWMMgLfapqH.x1jk1p8ee
9CHoMEZnMIrLsKJQ9Cvu9gy43W5SWekiaZ0FpvE7EvO.NNOo5wwzmtGmtNbb
WQ1jUPDlI5VR+UU58tyZGSR2HM8Wypo.Hxa6HrbS+pI+Y31NKaVU0HKnRyCC
10ssO4C0TqXbcA+rarZhL6NV4xDNMSZG1OXNdFH.5M2aF.C0WgQy81cO2VUJ
ErGMOMyr1s7rxtUG87YWRVYls623LRgqYjee8U5eU+L6nwSVUSojxAvd4CDM
.gBFjPrRo6LEnZ+S2bDLyeQjlVg9ePlgmRlInECwqghnPCxqTR4RCrFCkBB0
7w2+egHquB5OmC58ty5FaPDzhGjtwkBdVQEBxR5q4ym5ODxK9rTTBEEaXioz
jlSWzrolWUS4xG.qIEMz93DBgNwbBh0nAgVLGFfwdQy.Khujf0P4YEr0z4Uo
BJeMk2KpfAu6pRishDJzDPs3LTQBbSUQ9VgKHqo4IpsiR.IDojyRajVOBN6H
liahJtQvDRZYlcksCzB7SJ3kfTPQ+.GelNFXA1x434wdvHL9HJ1AOD4+v7R8
hQVU1GXhhd24rFt7lLI.Yh.M9GPdcW2cKubWexiBdr.HJXYz9cDDEeFR8r6X
XnwfIF0ep2sj1DfK3x7YjhBvRpLISsZ7pBv2UUwRtYv3mX+SbM+VR5EZRhBV
b5q2ej4RGnnutZXufJ37.JqySb7+gU6MDWQl65k2CUv2+sSyOXpdnwQa.9n9
fxyWo9gMvo.EnMqNQzv0UiDf9s7FGdhCVsPy5mChhmnjZ6iWEmT9p+0EFMpG
XOVJpZ3Yc6ose.I3YJMmJjrRhjoJH97ogd4ztikmSMyX6dImIHoETCl8F9E7
3kl9CSFiz7ldos+ZNjzfStzLduGgz1GtSfzzVS.vCoLiW1IGZ3wIsfWNsISZ
G78o4qSmZps+Z9VTahC0hFixzt6lXgoO5YDBa5SA1mECHro+UY7nRM2+E9Ei
vhm9RFwi5Dfn3+BGaNpBFG2glsthH00q0V0sOYqlTVIuuhqaGNy1lUZaaM94
xoqYc2h0HsKgqL6IUN8Z3V+XaBCzFwLKn5xe.zItGiA
-----------end_max5_patcher-----------
I applied it to the Track/Device selected object in Parameter Masher 1.2. I had to introduce a delay of 120ms to make it working (30, 50, 100 were not enough in my tests).
Live 9.5 (64bit), Max 7.0.6, Windows 10, Push 2, Korg electribe2, Bass Station II, Launch Control XL, Faderfox DJ3

M4L

jonkers303
Posts: 17
Joined: Thu Jan 17, 2013 1:36 pm

Re: Push developer kit: M4L devices for Push!

Post by jonkers303 » Thu Jul 18, 2013 3:21 pm

Is it just me or is the Polygome device broken in the 6.0.5 update?

The push is just in note mode and the m4l does not seem to accept midi input.

The push LCD shows the polygome things thou.

/j

greaterthanzero
Posts: 103
Joined: Tue Apr 09, 2013 5:48 pm

Re: Push developer kit: M4L devices for Push!

Post by greaterthanzero » Thu Jul 18, 2013 7:24 pm

jonkers303 wrote:Is it just me or is the Polygome device broken in the 6.0.5 update?

The push is just in note mode and the m4l does not seem to accept midi input.

The push LCD shows the polygome things thou.

/j
It's not just you, nor is it just polygome.

This is the second Live update in a row that broke flocked's API, requiring a fix on his end followed by a replacement of every app that uses it.

This shouldn't be happening with such regularity. That's alarming.

queglay
Posts: 522
Joined: Wed May 03, 2006 7:15 am

Re: Push developer kit: M4L devices for Push!

Post by queglay » Fri Jul 19, 2013 1:25 am

i've been getting random pauses in live sessions since i started using live 9 and the push dev kit. support had this to say -
In your log.txt file, I was seeing a lot of errors like this:

57261 ms. RemoteScriptError: File "MIDI Remote Scripts/_MxDCore/MxDCore.py", line 142, in _get_lom_object_by_lom_id

57261 ms. RemoteScriptError: KeyError
57261 ms. RemoteScriptError: :
57261 ms. RemoteScriptError: -36
57261 ms. RemoteScriptError:

MxDCore is the pipeline between the Control Surface (Python script) and Max.

The value -36 is an ID. The minus signifies that its a Python object you are addressing, e.g. a button.

The errors above come from Live not recognizing these IDs. It could be that you are using the same IDs each time. Basically the Push team told me that once the script refreshes, these IDs will be lost.

Although I am not a Max expert, I think that when using live.path, you should use the "follow object" rather than "follow path" outlet.

By using follow object, this ID will always stick to the object, no matter what changes.

I hope this helps! If you have any questions please get back to me.
not sure if what is said is true. why have a follow path outlet if it shouldnt be used? are you guys experiencing this too?
Load VST Presets from Push's Browser!
http://www.audiomodder.com

Because789
Posts: 440
Joined: Thu Apr 28, 2011 1:26 pm

Re: Push developer kit: M4L devices for Push!

Post by Because789 » Fri Jul 19, 2013 8:13 am

Since Parameter Masher still works, i guess it has to do with the Matrix_Modes ID. Does it work again if you apply 2. of this post:

viewtopic.php?p=1516088#p1516088

? Alternatively you could try the track/device selected object out of Parameter Masher, there I did apply the change + a User button observation (link in signature).
Live 9.5 (64bit), Max 7.0.6, Windows 10, Push 2, Korg electribe2, Bass Station II, Launch Control XL, Faderfox DJ3

M4L

jonkers303
Posts: 17
Joined: Thu Jan 17, 2013 1:36 pm

Re: Push developer kit: M4L devices for Push!

Post by jonkers303 » Fri Jul 19, 2013 6:42 pm

Hey thanks Because789, now it works again!

I copy pasted your box named Push Control from Parametermasher and reconnected the wire in Polygome.

This was the first time i actually opened a Max patch and looked under the hood :)

Now i will go google how to get the new object visible in the UI!

/J

greaterthanzero
Posts: 103
Joined: Tue Apr 09, 2013 5:48 pm

Re: Push developer kit: M4L devices for Push!

Post by greaterthanzero » Fri Jul 19, 2013 8:18 pm

Way to go, community!

I figured we were just dead in the water until Florian noticed we were talking about him again. =)

Shokol8
Posts: 155
Joined: Tue Sep 07, 2010 1:07 am

Re: Push developer kit: M4L devices for Push!

Post by Shokol8 » Wed Aug 07, 2013 9:38 pm

That look wicked!
Shokol8
Paris, Bristol
MBP i5 2.3Gh 8GB 500SSD, 1TB HDD
Sierra Suite 9.7 Edirol FA101
CME VX5, Irig Keys Pro
APC40/Push 1
Ipad Air, Alesis I/O dock, NI S4 & F1
http://soundcloud.com/dr_goldsylver-fastfinger

Post Reply