hex pimping #3
Comments
|
I've been meaning to add some of this functionality to hex for a while. The first three lines will make it into the next version. What do you mean by color coding on pad functions? PlayMode: you mean as opposed to record mode, I guess? less divs/mults.....would changing from 128 max to 64 max make a difference? I don't want to do less than 64, but I can see where you're coming from. Obviously, 64/1 is pretty fast, but 63/32, for instance, isn't I wanted to make hex as capable of "freewheeling" as possible, but still have it locked in a grid somewhat. FWIW, this is the sort of thing you could edit in the Max patch fairly easily just by opening up the patch and editing the max value of each of those live.dials. a |
|
color coding for pads means different colors on the pads depending on the mode you are in. currently its white , green, green. nice would be blue, green, magenta… play mode in addition to add mode would be nice. so that one can do finger drumming without and with recording. divs/mults… my issue currently is that its hard to dial in a specific speed and come back to normal speed. probably x/0, x/2, x/4, x/8, x/16, x/32, x/64, x/128 would be good values. that would be 15 values total on the knob… cheers, |
|
hi james, quick stupid question: i tried using hex with a drumrack today and i don't get the encoders to map to selected pad/chain. encoders stick to the pad that was selected when the drumrack was selected for that instance of hex. how do i have to set up the drumrack to get parameters of selected pad? how is hex 2.0 going? cheers, georg osswald On Nov 14, 2013, at 1:31 AM, amounra [email protected] wrote:
|
|
Make sure that the blue hand is actually on the DrumRack, not the nested device, when you hit the select button. There's some sort of bug in Ableton9 that causes some DrumRacks to not be "blue-handable"….I have the same issue with some of my own custom-built racks, its very frustrating! I did make some changes to hex over the weekend, no new features but I fixed some bugs that were causing issues for me. I will be adding two of the features you were looking for (play mode, mode cycle toggles in settings) soon, hopefully this week ;) I had a chance to work on my AumPush script extensively this weekend, which means I might actually get to start making some music again: that's good news for everyone using my stuff, since I'm much more inclined to work on it when I can actually use it! a On Nov 18, 2013, at 7:25 AM, gheehgt [email protected] wrote:
|
|
Ok, changes are done for now. Added advance button toggles to the settings menu. Added play mode for pads. Changed pad colors for Add. I'll get back to it soon, I want to fix some bugs with PolyPlay and finish tightening up the other play modes, but for now that'll do it. |
|
hi james, i'm having problems getting the new hex to work. so just to confirm installation i do:
do i miss something on installation? i do get the new options in hex's prefs for pads and row functions, but whatever i select/deselect there it doesn't work when cycling through functions with encoderpushes. they just cycle through same way they allways did… regarding the functions of buttom row keys in the aumtrollg-script, i just wanted to change those 2 'tempo nudge' buttons to scene up/down/start. currently i use one encoder for that but i got more than 128 scenes and that makes things a little messy with an encoder. it would be easier with those butons that i'm not using anyhow. i need some python magic as well:). i will ask marian from ableton later about the drumrack-blue hand issue. maybe we can solve that. cheers from berlin, georg osswald On Nov 19, 2013, at 2:17 PM, amounra [email protected] wrote:
|
|
It sounds like the javascript file hasn't been updated. Make sure there's only 1 version of this file on your machine: Delete all of them, checkout the repo again. Restart Live and Max. Let me know if that works :) a On Nov 20, 2013, at 8:32 AM, gheehgt [email protected] wrote:
|
|
allright , so i forgot to replace files in max app at: Cycling '74/java/classes/ georg osswald On Nov 20, 2013, at 8:25 PM, amounra [email protected] wrote:
|
|
They didn't change, and they're not used for this one. Shouldn't matter. a On Nov 20, 2013, at 11:51 AM, gheehgt [email protected] wrote:
|
|
mmhh i don't get the new hex to work. i tried a couple of monomodular reinstalls. but no luck today. will try tomorrow again. thanx+cheers, georg osswald On Nov 20, 2013, at 9:08 PM, amounra [email protected] wrote:
|
|
Yeah, but you have a "stuck" file. It's Max's fault, it happens all the time to me. Very irritating. My guess is you've stored a local path for the js file it needs (probably when unfreezing a file in edit), and it's persisting in Max. I'll rename the file tonight and freeze it for you, hopefully that will solve the problem. a On Nov 20, 2013, at 2:32 PM, gheehgt [email protected] wrote:
|
hi james,
here my suggestions for hex enhancements:
The text was updated successfully, but these errors were encountered: