GithubHelp home page GithubHelp logo

m4m7's Introduction

mod ===

monomodular b997+

How to make this work:

  1. You MUST be using the most current version of Live! (as of this writing, version 9.71). You should also install the latest version of Max (7.31).

  2. Download this repository, preferably with a github client as I’m making frequent changes and it will be easier to update for you if you find bugs that I can quickly fix. Put the “m4m7” or “m4m7-master” folder inside Max’s packages folder, which can either be in ~/Documents/Max/packages or /Applications/Max/packages (either path will work).

  3. Copy all the FOLDERS* from inside the m4m7/Python Scripts/ folder to Live’s MIDI Remote Scripts folder.

  4. If you are using a Livid controller, you'll also want to copy all the FOLDERS* from the m4m7/Livid Python Scripts/ folder to Live's MIDI Remote Scripts folder.

  5. If you've commissioned a script from me, it will be in the /Commission folder and I've probably given you further specific instructions.

Notes:

Any help in testing is really awesome for me, please send me log.txt and Max window shots so I can trace things though, and as much detail as possible about how you broke something ;)

I do plan on making an installer for this at some point, but its very time consuming so no promises about when that might happen.

If you are using the Livid v2 scripts, I recommend turning off autoupdate in Live's preferences. There is no guarantee when (or if) I will update these scripts again, and it gets messy when trying to backdate github commits to try and find a compatible version to the last working build. Currently, most functionality works for the v2 scripts (including the DrumSteppr/SynthSteppr mods), but I will not be developing those scripts further beyond commissioned work.

It’s a good idea to keep a separate copy of Live for the new scripts just so you don’t fubar your working installation (if you have one). On OSX, you can do this simply by making a new copy of your Live.app bundle and naming it something different (option + drag and drop). If that doesn't work for you, just back up your old Mod/Livid Python scripts, _Mono_Framework folder (for pre v2 scripts) or aumhaa folder (for any of the newest scripts) in MIDI Remote Scripts (or simply archive the entire MIDI Remote Scripts folder somewhere).

If there are features or fixes that you need for something, I'm happy to consider making them on a commissioned basis, drop me some mail and we can discuss. I generally stay very busy, but often times small changes can happen easily and quickly.

(* Make sure you copy ALL THE FOLDERS FROM INSIDE the "Python Scripts" and "Livid Python Scripts" folders, not the "Python Scripts" or "Livid Pythons Scripts" folders themselves!)

[email protected]

m4m7's People

Contributors

aumhaa avatar

Stargazers

 avatar Raphael Kuster avatar Steven Noreyko avatar Carter Magee avatar elixx avatar ark1ee avatar  avatar Stu Fisher avatar Patrick Lenk avatar Thomas Frössman avatar  avatar Andrii Skaliuk avatar ozwa12ld avatar  avatar Adam Muntner avatar Andrzej Kopeć avatar Robbie Jacobs avatar mpw avatar

Watchers

James Cloos avatar Daniel Holmes avatar Patrick Lenk avatar  avatar Adam Muntner avatar  avatar Bagheera Tomahawk avatar Stefano avatar  avatar  avatar

m4m7's Issues

CNTRL R & PUSH

Hi Aumhaa

Please advice,

When using CNTRLR & PUSH in ableton, when ever using the CNTRLR , the push activates to the same channel, is there away around this happening.

As an example, the first 4 channels, are assigned to receive midi from CNTRLR and the next 8 channels are assigned to the PUSH, everytime i touch the CNTRLR, push dislays the channel assigned to CNTRLR..

I hope you understand what i mean.

Ableton 10

Hello Aumhaa-

Hope you're well!How is support looking for Ableton 10? Will you be updating the Python scripts? As of now I don't believe they work for the new Beta.

Cheers.

trying to get cntrl_r to work on 9.7.7

2961 ms. RemoteScriptError: File "/Applications/Ableton Live 9 Standard.app/Contents/App-Resources/MIDI Remote Scripts/Livid_CNTRLR_v2/init.py", line 5, in

2962 ms. RemoteScriptError:
2962 ms. RemoteScriptError: from .Cntrlr import Cntrlr

2962 ms. RemoteScriptError: File "/Applications/Ableton Live 9 Standard.app/Contents/App-Resources/MIDI Remote Scripts/Livid_CNTRLR_v2/Cntrlr.py", line 22, in

9.6 Compatibility

Hey dude! so can't seem to get Live to pick up the midi remote scripts -- They all previously worked in 9.5.

Whilst in 9.5:
Couldn't get any of the mod m4l patchers / instruments to work with MonOhm; but did not check OhmModes.

*notes on some specifics: I have not installed any Livid scripts. I've also dropped all ties to 9.2.

As always, thank you.
-Robbie

Trying to use Base 2 on Live 11

I have absolutely no idea, why or how this isnt working. Ableton Live 11 does not recognize these scripts but i loved my base 2 so much. Any Idea how we get this to work?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.