McMillen QuNeo looks to be everything I want in a controller

[trevox]

@shadx312...would be really interested to see what you've done....

[regretfullySaid]

Trev I'm really interested in getting at least part of it out, and the last part I started and have been working on is a drum rack sequencer very close to push, with some differences. The thing is, it is MESSY, and still has quirks. I'm almost compelled to practically start that mode from scratch just so it's organized and legible. But, if you've got Max experience, want to take a look and help, I'll make a version of the device for just that mode and see if you can help.

I'll do a video example and strip the device down to the DR Sequence version for you too look at this week.
And this goes for anyone else with Max experience. I need help with it. When I have it I'll post a new thread in the M4L section.

Besides that maybe it'd be good to start with something more simple. I'm also kind hyped about the "menu system" I've been tinkering with

[ZALTA19900]

his thing is so sexy. i was dreaming of having a kind of "blank template" controller like the touch DAW stuff for ipad combined with haptic feedback. first the 12 step and now this. they must be reading my mind.

[fishmonkey]

there is a new Enhanced Note Mode thing in case anyone here missed it:

http://www.youtube.com/watch?v=1RtMez7W ... e=youtu.be

[trevox]

Trev I'm really interested in getting at least part of it out, and the last part I started and have been working on is a drum rack sequencer very close to push, with some differences. The thing is, it is MESSY, and still has quirks. I'm almost compelled to practically start that mode from scratch just so it's organized and legible. But, if you've got Max experience, want to take a look and help, I'll make a version of the device for just that mode and see if you can help.

I'll do a video example and strip the device down to the DR Sequence version for you too look at this week.
And this goes for anyone else with Max experience. I need help with it. When I have it I'll post a new thread in the M4L section.

Besides that maybe it'd be good to start with something more simple. I'm also kind hyped about the "menu system" I've been tinkering with

Believe me, when you go out of presentation mode with most of my patches, it's a complete mess, but a structured mess all the same!

If you send something on, you'll have to tell me exactly what you are trying to achieve. So basically list all the functional requirements you want rather than explaining what you have done - sometimes it's not always obvious what a patch is trying to achieve just by looking at it, so this additional information will help. Hopefully I can relate the two by looking at your patch and follwoing the data to see if there's a leaner, less messy way of doing the same thing.

Here's my almost complete controller interface. For the Quneo, you can see all 4 banks of each fader bank on screen (and name each fader) and flick between what you are controlling using the relevant bank buttons on the Quneo. The bank you are on is always highlighted with a red border (so this is on bank 1 for vertical faders and bank 1 for the 4 sets of horizontal). I also have VU meters feeding into it from Logic. For the pads, you can see the X, Y and Press values under the pad and the pads light up when depressed. The assignment of these is done in little subpatchers where you can morph 2 controller values - including scaling/inverting the values sent separately for the X, Y and Press values along with the note value. You can also choose whatever midi port and midi channel you want for each one, so you can control 3 totally separate hardware synths with one pad if you like while triggering a sampler.

The BCR2000 is pretty much the same - assign whatever controller to whatever you want independently using little subpatchers. And with the Launchpad, you can freely scroll between LP pages and everything updates - including the names of the row and columns! I'm not actually using Live at the moment, but have mimicked the clip functionality in Logic - it all works the same really.

The great thing is, everything gets saved in Max. So once you have assigned everything you want to control, you no longer need to look at the DAW which is quite liberating. Everything gets labelled (click on the label itself and a dialogue box opens) and saves with the patch, all program changes (for multiple hardware synths) are saved in the patch etc, so all you need to do is load you track in your DAW and choose you track from the dropdown menu. This will update all controllers and you ready to go with everything set as it should. Some will say you get this in Live, but there is an enormous amount of flexibility built into this that is configured very easily. I also find it refreshing to look at a screen that is representing the "instruments" I am using rather than blankly staring at my DAW going "what the fuck is this mapped to" while playing a live gig drunk - peace of mind I guess!

I don't know, one of my mates thinks it's overkill, but it's done now. And I am fully aware it is ugly as sin, but I have been concentrating on functionality for now!

[regretfullySaid]

Very cool. Thanks for sharing. I've had to take a break from working on the patch to work on other things, but I've decided to spend this Saturday night cleaning up what I have so far. Party!

Where I previously left off that got me in a bind was getting the right kind of LED behavior when using an encoder to scroll the drumrack box up and down. I decided to mimic some push behavior, so the lower left qudrant of the Quneo grid will mirror which cells in the DR box have something in it.

I've already had the encoders set up to act as "Directional" (even though they're set as Location in the preset), in that they bang out 1's clockwise and 0's counter clockwise (or really anything I want to send for counter/clockwise, depending on the mode). I didn't know how to get max to behave to Lin 2's Comp, so I set them as Location in the preset and converted back to directional in Max. This works out well for different modes though and I really want to keep the patch dependent on only 1 preset as much as possible, so that works out well.

And, I already have a good connection between the encoder, scrolling the DR-box and getting the cell info, so the main problem is getting the LEDS to reflect right in an efficient dynamic realtime way. I previously had it set up where each of the 28 (or 29) scroll positions had hard mapped LED information, but that is not the right way to do it. It did have the advantage of making it easy to show which Cells were C notes though (Cells that are C notes are Yellow, the rest are green)

Then, in another sub-mode of the drum-rack mode, I have the 16 pads act traditionally as drum pads, for easier playability, even though it's still in grid mode (basically all 4 buttons on a pad work together to send out 1 note, which makes it a lot better for rapid finger drumming than being in the real Quneo Drum preset mode) so I need to get that same kind of DR Box to LED info the same way, except a different kind of conversion since it's 4 leds per pad x 16 pads, not just 16 buttons on 4 pads.

If that makes sense to you and you know how to go about it, let me know, otherwise I'll I should get to doing a video of the Drum_Rack mode soon after working on it tonight.

[hoffman2k]

I got a tip for making nice LED blinks.
If you use fixed lengths, it'll always look off at different tempo's. Therefore, control the blinking with a synced metro and a note length like a 16th. You can use the translate object to get millisecond values, so it doesn't have to be metro.

I realize this adds nothing to solving the problems you may have. But I suppose you got a lot of blinking LED's going on...