thanks for the information and the work done!
I stay tuned ; )
Statistics: Posted by barabou — 03 Apr 2015, 11:59
]]>
Yes I have PXT General. It's a pretty cool script, but for me it does not work well for my imaginary "ultimate Usine" controller.
Why? Because it takes over the Push. It does provide the note grid, but then it is only the note grid. So any Usine native grid patches will not work (or at least I was unable to get them to).
So it always seemed to me that the best option was to have the same note grid but implemented as a patch in Usine. But I could not motivate myself to make it.
Luckily drakh has put in the hard work to make this part easy. I hope to have an update here about it soon.
I think I will also be porting the existing Push scripts into C++ and releasing them with documentation. Stay tuned here for more info!
(Oh, and if you are considering a Push, I can say that it is a really really nice piece of hardware).
Statistics: Posted by ceasless — 03 Apr 2015, 11:30
]]>
I am looking for a matrix controller and therefore very interested in your work on integration of push in usine.
Just saw this from nativeKontrol, it seems to be done to integrate push in any DAW :
PTX general
Did one of you try to used PTX-general in usine (or HH or HH2)?
Thanks a lot
Statistics: Posted by barabou — 03 Apr 2015, 10:55
]]>
Last night I wired up a "grid monitor" that translates midi notes to matrix indices. This should be a good first step for world domination, I think
Statistics: Posted by ceasless — 05 Feb 2015, 12:44
]]>
http://www.sensomusic.com/forums/viewtopic.php?pid=29194#p29194
I've just implemented it in my workspace (now using touchscreen only for vst presets combobox and a routing matrix),
and it works like a charm.
I didn't managed to translate it into hollyhock, so i send all the datas via localhost osc.
Statistics: Posted by Fléau — 03 Jul 2014, 09:22
]]>
Statistics: Posted by seamus — 03 Jul 2014, 04:00
]]>
Just curious what you guys are up to with Push/Usine, and whether you owuld be willing to share some of it?
I've gotten distracted by a new influx of hardware, but I will be back to working on this soon. But would love to get some inspiration from you both.
Statistics: Posted by ceasless — 02 Jul 2014, 12:40
]]>
Between this and the ability to understand the knobs that I added last week, you've got a whole lot of opportunity already. There is one feature still missing in this patch: the 8-segment LCD inputs aren't ready. After that we can easily build a template patch for making the knobs with arbitrary values (such as to your favorite VST synths, perhaps?).
Get it on github
CODE:
Changelog:Hot fresh text inputs straight to LCDThe liquid crystals on your Push's text display are yours to patch.Each line can take 68 characters. It probably won't work if you send itmore.NOTE: The 'LCD 8' segment inputs are not yet ready, these will becommatext and should make setting up some generic CC send patches easyas pie.
Statistics: Posted by ceasless — 06 Apr 2014, 23:23
]]>
For now we will call it 'Patch Pusher'. I'm hoping to get lots of people addicted to patching with this one, so it seems fitting.
The changes are:
CODE:
- Provides an 'off' version of the pad colors. This is for you fléau :)- CC values now transmitting from rotaries/encodersThe Push sends its encoder values in a relative format already ( 1+n isturned right, 128 - n is turned left, where n is a value that increaseswith the speed of the turn ). These values now show up on 'rotary rel'param outputs.All other new parameters are not yet functional.Oh, and speaking of outputs... I have a surprise on the way with regards to a certain I/O element of the Push. It's working I just need to add some input params to control it with
Statistics: Posted by ceasless — 02 Apr 2014, 22:03
]]>
I can understand this as a feast of patches for interfacing with the Push in Usine 5, and I can imagine doing a lot of things with these grids, but I don't yet know how to make anything happen in Usine 5. I did not realize what a big shift it is to Hollyhock before.
I noticed that the isomorphic keyboard is in a very different style than the Push version. Can you explain a bit more how it works? Did you decide from experience that this version works better for you?
Statistics: Posted by ceasless — 25 Mar 2014, 18:52
]]>
plus, i totally forget to said that exemple pages are on
addeffect,addtrack,note,session,select buttons. AND 'up arrow' for the isomorphic keyboard
you should understand it a lot more now
Statistics: Posted by Fléau — 23 Mar 2014, 20:25
]]>
Taking a look at the the 5.8 patch, I see a lot of impressive stuff happening. I'm going to have to digest it a little bit before I really understand what is going on. Quick question: is it supposed to be making any sound? There's a pad mode that looks like a sequencer of some sort, and knobs labelled as if they might control levels for instruments. It's a deep example either way, I just wanted to be clear that my setup is working correctly.
Also, it's slightly shocking how differently Usine and Hollyhock operate. I'll have to read up a bit on that.
By switching to a new version of Hollyhock and not copying the config, I was able to get the pads to stop flashing. I think some bad sysex got stuck in the device setup in the previous version. The color transition link looks great but I'm going to put the more aesthetic stuff on the backburner and focus on getting the pads array operational.
Statistics: Posted by ceasless — 23 Mar 2014, 19:01
]]>
http://cycling74.com/wiki/index.php?title=Push_Programming_Oct13_03
BEWARE with sysex, it can do wrong thing on the firmware!
Statistics: Posted by Fléau — 23 Mar 2014, 17:30
]]>
here is mine:
push for v5.8
i'm really sorry but i can't make it works under hollyhock ( error, crashes)
but it will certainly give you some ideas.
-8 pages of encoders selectable via: volume,pan,track,clip,device,browse,master, stop buttons
-quantize buttons are assignable to functions (page select or whatever)
-the rest of the right buttons are assignable to 32 matrix page
those matrix page have a setup popup page where you can select:
-colors
-toggle,button or group button
-up to 4 clock bar lighting
Statistics: Posted by Fléau — 23 Mar 2014, 17:27
]]>
It shouldn't be too hard to beat Ableton at integration. Their's is pretty bad, even with their own stuff (and quite worse with third parties). I'm demoing the 9 Suite, but it's not all that compelling versus what I can do in Intro with regards to the Push. Plus, I've already got plenty of synths and sounds. Stuff like PXT Live shows how many crazy ways we can interface through this device, and will keep me having fun making music until we've got a framework for creating instruments in Hollyhock with it.
For instance we should be able to automatically create pages and pages of parameters just through grabbing the params list off of a VST. With IML we can create a structure you can follow which will allow you to group params according to containers you yourself set up (yes this is kind of a pain, but you get organized knobs on your racks for free too
I'm also dreaming of 'Patch Happy', an 8x8 grid of pads. Hold an empty one down and scroll through your patches. Add one. Toggle it on and off with multiple presses (loop mode) or have them react as triggers. Hold it down and press the 'Note' button and then dive into whatever pad sequencer/interface has been setup within that patch.
Statistics: Posted by ceasless — 23 Mar 2014, 15:12
]]>
)Statistics: Posted by nay-seven — 23 Mar 2014, 14:53
]]>
Luckily I've managed to figure out a 'quick' way to code this, so that the actual dispatching to outputs requires far less code than typing out all these constants, creating the arrays, etc.
Some brief thoughts on where I plan to take the scripts. Please feel free to comment or propose new/different approaches.
# Push Core
This is the script I'm currently working on. It will be the extra-large version of bringing Push into your workspace, as it will contain things you won't need for every place you'd like to give and get feedback with Push in a patch. It will all go here first until it's fully functional and then I will break things out into different modules.
For instance this touch rotary functionality I just added would make a fine patch of its own. Maybe you only want those on a workspace level, maybe for turning on and off different modulation sources, or whatever. So you only have to have that code in one place, whereas maybe you will have dozens of pad related patches across your racks.
It's the 'or whatever' that I'd like these scripts to allow most.
## Next steps (in no particular order)
- create more commatext/array pairs to allow some combobox patches which allow you to choose which values you want to send to button parameters (for instance, 'blink fast')
- finish adding parameters for all the other buttons on the Push
- get the pad array working, as well as parameters to get changed values as x,y,note,and velocy as pads are pressed. it should also be possible to double buffer, so you can set a color to switch to rapidly
- implement 'transitions' so that you can trigger different wipes,explosions of color,nyan cat rainbows,etc to the pads that can be optionally triggered when you "return to" a specific pad interface mode (for telling different patches/racks apart, for instance)
- write text to the LCD, make it dead simple to choose how values are displayed and use all the special symbols
- scrolling text on the pads
Probably some other things I'm forgetting as well.
Then there's the stuff I want to build on top of these functionalities...
P.S. fleau, were you asking me to change the color values coming out of the script to have +2, or were you commenting on the overall patch?
Statistics: Posted by ceasless — 23 Mar 2014, 14:37
]]>
One thing I'm definitely inspired by is the clip launching functionality. The pads are divided into two halves, the bottom half select the clip playback length and the top half gives 32 trigger slices. These slices are based on the selected playback length, or can be set to manual quantization.
I think I've found a good first not-about-pad-color patch to build.
Statistics: Posted by ceasless — 15 Mar 2014, 14:17
]]>
Feel free to change it around, etc. I'm hoping to have a "scrolling text display" demo patch sometime soon.
Thanks for the updated Hollyhock workspace, and very much looking forward to the new fusion patch you mentioned!
No worries about the programming, it's great just to have someone else to work with in imagining a new control surface for Usine.
So your advice will definitively come in handy. I've been thinking about all sorts of approaches, will try to present them to you and seamus soon.
Hope you don't mind that we do the work in Hollyhock?
My native language is English and unfortunately I don't speak any others very well
Statistics: Posted by ceasless — 13 Mar 2014, 15:20
]]>
No blinking here, did you tried to restart the push?
I had blinking issues only with sysex when the string lines weren't multiplexed.
(seems you can makes matrix pads blink via sysex)
if i can make some suggestion about your color setup procedure,
-it would be better to choose the color then press the pads (in case you have a lot of pad to setup)
-increase the color mapping value by 2 (it makes an 'off pad' and that way, you'll just have do decrease by 2 when it'll be on)
-don't worry, keep monophonic, it's just a setup page
I repatched all the novation launchpad engine, and now fusioning it with the push patch,
it will give you some ideas.
I will post it asap.
I'm sorry i can't help with scripting, but i can give some procedure and variable ideas,
maybe some diagram.
What is your native language?
Statistics: Posted by Fléau — 13 Mar 2014, 10:48
]]>
Instructions: touch a pad. Then use the combobox to select a color. Now that pad will appear in that color.
A very simple beginning, but I wanted to get the grunt work done before starting on anything cool.
In the patch is a script which:
* provides a 'clear pads' button which sends the proper midi to turn off all the pads
* gives two parameters per the three color type as provided by fléau: one is the array of values to send and the other is a commatext you can use to make a select-mapping with those values
Note that the 'note pads' array params don't do anything yet.
Still a bunch of things to do, and design to think about.
Also, I've got an issue where the lights are blinking. The clear and color options work fine but the pads are always blinking. Any idea how to fix that?
BTW, fléau can you post a fixed version of your patch? I couldn't see what you meant when I looked through it.
Statistics: Posted by ceasless — 12 Mar 2014, 23:40
]]>
CODE:
case N of:CODE:
case N ofI've almost got pad clearing implemented. Hope to have more for you folks soon.
Statistics: Posted by ceasless — 12 Mar 2014, 20:48
]]>
I've gotten all the color, note, and cc constants all defined. That took a while, but it should make for some real fun.
So the definitions work great
But I've hit a bug while implementing the first function that uses them. Memory access violation -- in my experience this is caused by something stupid I'm not seeing right now.
Statistics: Posted by ceasless — 12 Mar 2014, 00:36
]]>
]]>
About the textfield: it's a wrong wiring,
look at the 'string to sysex' patch:
the text is wired to the second input.
great!
Statistics: Posted by Fléau — 11 Mar 2014, 20:33
]]>