amounra
Forum Replies Created
-
AuthorPosts
-
amounra
ParticipantThey are both cross platform. m4m7 is for Max7 and Live9, m4m8 is for Max 8 and Live10.
amounra
ParticipantHey Vito, welcome to the forum
The scripts work fine on Live 10, so you shouldn’t have any problems…and of course if you do, I want to know about them
I’m glad to point you in the right direction for information about how to get everything set up and working. Congrats on your new CNTRLR
a
amounra
ParticipantSorry for getting back so late, I’ve been out of town for a while!
I haven’t needed to do a reset in a long time, so I was surprised when the online editor didn’t work for me right away. A bit of research and found out that the Livid Online Editor doesn’t appear to be supported by any current browsers due to its use of NPAPI. Every browser has phased this out due to security concerns presumably.
To get the online editor to work, I’d recommend trying to use it on an older browser, anything prior to Safari 12 I think will work?
The online editor is here:
https://lividinstruments.com/editor_2017/
and instructions are here:
http://wiki.lividinstruments.com/wiki/Online_Editor
You may have to download the Jazz plugin to get things working, here’s a link:
https://jazz-soft.net/download/Jazz-Plugin/
None of that works on a modern browser, though, so your best bet might be to first try to use the maxmsp based editor applications, found here:
http://lividinstruments.com/support_downloads.php
I have one computer that will run it, and another that won’t….let me know if you can’t get it to work and I can see if our problems are the same, and figure out how to fix it.
To do a factory reset, you should just have to get the controller connected, then do a “reset to defaults” and “save to controller”, the buttons should be at the top I think.
amounra
ParticipantThanks for sending the log! I do see some errors showing up in the log.txt, but nothing that should be fatal. Additionally, I don’t see the same errors in the logs on my machines when using the script so I highly suspect that you still have the incorrect versions of the scripts installed in your local Ableton bundle. This is almost always the cause when I see these types of problems.
I’ve also double checked the current build of drumsteppr, and it’s working fine.
What I might suggest is starting from scratch:
1. Install a new copy of Ableton Live 10.1.6. (you don’t need to delete your old one, but you should rename it and put it inside a folder somewhere inside your applications folder. It’s fine to have multiple copies of Live on a Mac, I do it all the time to test different scripting setups
)
2. Download m4m8 from the repository: https://github.com/aumhaa/m4m8.
3. Install the scripts per the instructions. Make sure to install ALL of the scripts from both Python_Scripts and Livid_Python_Scripts folders.
4. Do a factory reset on the OhmRGB, just to make sure that everything is in the state the script expects.
5. Work for a while with it this way, and see if you can get the controller to freeze up. If you can, send me another log.txt. If not, we’ll move on to getting the stepprs working for you ; )
In response to your other questions:
>when the Script for Ohm RGB is loaded, does it still send notes ?
Generally, the script is not going to allow the passthrough of notes to Ableton unless you are in “modMode” (the Gary button is toggled) and a modDevice (i.e. steppr) is NOT currently the selected device in Live.When modMode is on and no modDevice is selected, the grid buttons send note messages to Live. The six buttons next to Gary work as a channel offset to the grid buttons. This way, you can use them to UserMap up to 64×6 different functions in Live.
Regarding the Digitakt, I’ll have to do some thinking…I may not totally understand your situation. Let me know if you can give me some more info, but it sounds like something coming from the Ohm is being mirrored through Ableton to it. It would be helpful if you could post a screenshot of your MIDI Settings in Live
a
amounra
ParticipantHey there Louis,
You’re in the right place. I wrote the scripts and m4l devices for Livid long ago, and still try to support them when possible. The Livid forums haven’t been functioning correctly for some time. I’ll do whatever I can to help you from here.
I may need you to send me a copy of your log.txt file from Ableton’s preferences. It sounds like maybe you’re hitting an error that I haven’t seen on my end. Likely an easy fix, but I’ll need to know what the error is.
The log.txt file is in your preferences folder, ~/Library/Preferences/Ableton/Live 10.1.6/log.txt.
If you can zip that up and email it to me, I can have a look and see if I can find a problem with the script. It’s best if you do this immediately after you experience the freezing situation.
As far as the steppr’s go, they are working on my machine. I would recommend two things: first, make sure you’re linked to the most current build of MaxMSP in your Ableton settings. Second, make sure the you don’t have multiple copies of the aumhaa or steppr files one your computer. Most of the time, it’s this second problem that prevents it from working correctly. We can revisit that, though, once we get the script problem figured out
a
-
AuthorPosts