Think of the light as telling you 'MUTE'...
Statistics: Posted by shawnb — 24 Apr 2015, 08:44
]]>
It would really be great if the MIDI Learn, inverse property would work for pads (using NOTE ON/OFF) as well as with sliders, for which this functionality already exists. That would be intuitive from a user perspective IMO. It would have also saved my countless hours beating a dead horse, but I'll own that one.
Coloring the pads is another issue. I'm not sure on the best approach for that (moduling vs. fastscript vs. c+), but it is not an immediate need. The notion of being able to do that however is extremely empowering and motivating. The ability to send state information (via different colors) to the Livid CNTRLR is one of the reasons I bought it. Full of potential.
Time for me to move on and be creative and not stuck in left brain repetition cycles.
Statistics: Posted by parityflux — 24 Apr 2015, 08:19
]]>
]]>
I appreciate your thoughts. I will work on this tonight (I'm GMT-7). I plan on working on it until it works.
-j
Statistics: Posted by parityflux — 23 Apr 2015, 20:00
]]>
Note OFF turns your light ON
What you want is
Note OFF translated to Note ON - so your light goes OFF
Note ON translated to Note OFF - so your light goes ON
If so, keep it very simple:
/ MIDI Filter (Note ON) => Create MIDI (msg fixed at Note OFF) =>
MIDI input bus output bus
MIDI Filter (Note OFF) => Create MIDI (msg fixed at Note ON) => /
For both MIDI filters, connect the 'Pass' outlet to the corresponding Create MIDI inlet.
Also connect Chan, Code 1 & Code 2 to their corresponding inlets.
Statistics: Posted by shawnb — 23 Apr 2015, 19:56
]]>
I prefer the bus method, but it seems to break the MIDI learn ability on the system-supplied send (see very first screen shot). Using just a bus (which I can see the activity on), the system-supplied mute on that send does not react, and will not learn.I agree, device specificity is important. The workaround is to use buses.
I generally use buses, but where MIDI Learn is needed, I route to both the bus and the "Midi to Usine" module.
Statistics: Posted by shawnb — 23 Apr 2015, 18:51
]]>
I had the busses working fairly well (I thought), but the busses won't serve up data to the MIDI learn ##$%^. I've read all about the MIDI being mixed together, knew it ever since I bought the program in '13, but now, now it's really got me down. I'm now days behind schedule and tomorrow I'll have to decide what to live with and what to forget about.
Reboot.
Statistics: Posted by parityflux — 23 Apr 2015, 07:55
]]>
I'm having a hard time following this evolving patch... The input MIDI stream didn't make sense to me, looks like you're using NOTEs. I think CCs would work with less hassle, if you could use them instead of NOTEs.
HOWEVER, if the signal coming out of the 'msg' outlet is truly 0 or 1, I would suggest using the logical NOT function ("not (A)", under Math | Logical), which would reverse the 0 & 1.
I may switch to CCs, I was just trying use what is default on the Livid controller. Notes seemed ideal for simple pad buttons with no velocity out, saving some CCs. HOWEVER, if the signal coming out of the 'msg' outlet is truly 0 or 1, I would suggest using the logical NOT function ("not (A)", under Math | Logical), which would reverse the 0 & 1.
I will look at the logical NOT too. Thanks.
I'm going to start over in a new workspace and try to build a test case, without all of the distractions.
Statistics: Posted by parityflux — 23 Apr 2015, 01:17
]]>
I agree, device specificity is important. The workaround is to use buses.
I prefer the bus method, but it seems to break the MIDI learn ability on the system-supplied send (see very first screen shot). Using just a bus (which I can see the activity on), the system-supplied mute on that send does not react, and will not learn.Statistics: Posted by parityflux — 23 Apr 2015, 01:14
]]>
HOWEVER, if the signal coming out of the 'msg' outlet is truly 0 or 1, I would suggest using the logical NOT function ("not (A)", under Math | Logical), which would reverse the 0 & 1.
Statistics: Posted by shawnb — 22 Apr 2015, 20:57
]]>
]]>
]]>
So, I'm at:
It's still not inverting. When the send's mute is on (red), the button lights up; I want to turn off the pad light when muted. Actually, wait, MIDI learn won't work on the button anymore, because my device gets sent right to a bus to keep it separate from my keyboard controller. Dang it. I might have to go back to splitting MIDI by channel. The MIDI inputs/outputs continually give me grief in this program. It's freakin' painful. I know there are solid reasons behind it, but it makes things rough.
Statistics: Posted by parityflux — 22 Apr 2015, 06:43
]]>
Thanks for the suggestion. It is closer. I had to removed the pipe that goes from the A=B Out to the Create. I used the out from the 0 to 1 instead to trigger the Create. It's not working in an inverse way though.
Unfortunately I have two MIDI devices going into this rack, and I was using MIDI busses to split them, but something isn't right with the MIDI busses. I can't connected to an existing one anymore. It's really weird. I'm on 2.0.067b right now. Maybe I'll update it to see if being able to create them by dragging out a pipe appears again.
It's funny, your post is actually helping me with me earlier issue regarding changing the button color via velocity:
http://www.sensomusic.com/forums/viewtopic.php?id=4819 Point #2
I have fantasies about programming a module to better handle the Livid CNTRLR.
Statistics: Posted by parityflux — 22 Apr 2015, 06:12
]]>
-------------------------------------------
[sub]etui samsung galaxy s6[/sub] [sub]coque samsung galaxy s6[/sub]
Statistics: Posted by lgbtten — 21 Apr 2015, 09:52
]]>
Waiting for this , I've try your question with a launchpad mini and here a solution:
you create your midi learn but don't use the motorized feature
you create this patch (with your pad as input and as output midi device in the rack)
of course you can filter the notes you want inverse before,
i've test with the LP and this way you can choose the color of your pad, here the velocity of 14 give me a red color
Statistics: Posted by nay-seven — 18 Apr 2015, 18:21
]]>
The second message (out) is from my MIDI device patch in which I change all NOTE ON velocities from 64 to 127.
Statistics: Posted by parityflux — 18 Apr 2015, 17:31
]]>
have you try to change manually to note Off in the setting panel of the object ?
i will check that inverse feature
Statistics: Posted by nay-seven — 13 Apr 2015, 13:19
]]>
]]>