User Details
Username: | pea |
Website: | None provided |
Facebook: | None provided |
Twitter: | None provided |
Soundcloud: | www.soundcloud.com/peterdekkers |
Account Status: | enabled |
Member since: | Aug 04 2018 |
About pea: | Hello. |
(report this profile) |
Devices by pea
Tetra Master Controller - with Push support Version 1.02 |
Total Downloads: 173
Comments by pea
Comments
I've not experienced any freezes yet. But I've only spent maybe 6-7hrs with it. Great to hear that it works with the Mopho! |
Posted on June 06 2022 by pea (report comment) (Goto Comment) |
Oops. I accidentally uploaded a broken version (patch not frozen in MaxMSP). It's resolved now. Thank you. |
Posted on May 17 2022 by pea (report comment) (Goto Comment) |
I've uploaded a copy of this device that adds Push and Push 2 support. Enjoy! And thank you @atari5200 for the awesome work. :) https://maxforlive.com/library/device.php?id=8164 |
Posted on May 17 2022 by pea (report comment) (Goto Comment) |
> @adh82- how do you rearrange the mappings so they are more Push friendly? For anyone looking how to do this, you need to add a "live.banks" object to the Max patch. Within it you can set up the banks of parameters accessible via Push. Happy wiggling. |
Posted on May 17 2022 by pea (report comment) (Goto Comment) |
I had to rename the download from "ORGBX_065.zip.amxd" to "ORGBX_065.zip", then unzip. Unsure what to do next, though. :) Thank you for developing this, looks like it has good potential. |
Posted on March 25 2019 by pea (report comment) (Goto Comment) |
Still good though :) |
Posted on August 05 2018 by pea (report comment) (Goto Comment) |
Will answer my question: no. Can't seem to get the tuner "needle" and/or note to show on the Push (2) screen. |
Posted on August 05 2018 by pea (report comment) (Goto Comment) |
Apologies, does this integrate with the Push 2 display? |
Posted on August 04 2018 by pea (report comment) (Goto Comment) |
@n0ael Agree, this would be super duper cool and I would love this, too.
Sadly I think that the only way to do this is to parse the SysEx information that is sent from the synth when it changes patches. This SysEx is entirely different kind of data to the NRPN/CC data that this Max device sends to the synth.
Therefore... not straightforward I'm afraid.