#101

Has anyone managed to port this for 64 yet? Would love to see or hear the results!

2 Likes
#102

Could it be that the Github file is damaged? When I download it my macbook shows that the file is damaged/corrupted.

#103

@kza perhaps this might help:

will look into 64 support soon!

4 Likes
#104

hello
control is great!
I have it running in Ableton Live as a m4l.amxd on a midi track - all good.
I’m also trying to send Meadowphysics to Ableton - and therefore attempting to ‘auto focus’ my 128 between MP and Control.
Is this possible?
so far when I switch to back Control, MP looses the 128.
Any help / suggestions would be great.
thx B

#105

try using this M4L version of MP:

3 Likes
#106

Thanks ithkaa!!!

  • got it working now - so good!
    128 control, mp and arc all controlling Ableton with Alto plugin - FM mayhem :smile:

YOU SIR are a CHAMPION!

1 Like
#107

Just discovered this - magic!
Wondering if the M4L version get the pages / keyboard / automation upgrades the standalone app has?

1 Like
#108

@drxcm having multiple pages in one track is not possible due to M4L restrictions in regard to MIDI-out configuration (it’s impossible to set the channel from inside M4L). You could use multiple instances of the M4L device and use autofocus to switch between them (you would need an extra controller).

Automation works in the same way as it does in the standalone, there’s just 1 page (per track).

Look for ‘Notes’ in this package to play the keys on your grid:

#109

This is just insanely well designed and implemented. I am floored. Real talk. Amazing work sir. I hope to buy you some beers some day. I feel like I am going to be able to get this working with Bitwig in the way I imagined when I bought this controller, and you just saved me months of coding to make that happen. One love.

PS - Standalone version is not working on MAC OX 10.12.3 - says damaged and move to trash. Max version seems to be working fine, but thought you would want to know.

#110

@pesky_human tx! try this for the standalone:

#111

I juuuuuuust found this before checking back in this thread and that works. Yay terminal! Thank you. Sadly, it appears that bitwig does not support even the most rudimentary MIDI routing. Checking on this, but it is going to be really sad if not.

#112

Seriously though, I am looking at this grid and what can be done with Control and if it can’t be done with Bitwig, then I will use or make something else in Max, even if it takes like 6 months to get around the language. It’s that good. It’s even better than I imagined it could be.

1 Like
#113

I am wondering if there is a way to make a “Keyboard” in Control that is just a simple 4x4 grid for setting off drum racks. On the 128, I could tuck it into a corner on one page, and still have tons of room for other toggles / momentary switches, etc. just on the first page, with other pages dedicated to controlling certain effects, synth parameters, levels etc. To this point, if I could just create a grid of momentary switches and assign note value outputs to them in place of the control messages that would work too…
Thanks again for this!

#114

@pesky_human try this little patch:

cctonote_4x4bottomleft.maxpat (122.2 KB)

it converts ccs from the bottom left corner (4x4) to notes. set ctlin to Control’s MIDI output. Then use noteout to send the converted ccs to another IAC Driver (or ‘from Max 1’ f.i.). Don’t forget to activate this MIDI input in you DAW. fiddle a bit with the notenrs. to fine tune to your needs.

I’ll put the your idea on my todo list :wink:

#115

Thanks so much for the assist! I am so fresh to Max that I am not fully understanding how to implement this in context with the layout I have designed, despite your explanation, and I fully realize this is not the spot for an in depth tutorial. I will mess around with it and see if I can get it to work. I am guessing that it would essentially make the bottom left corner of the existing “keyboard” in Control behave in the desired fashion? I know exactly which notes to assign to it and can at least get that sorted. My existing “K” in Control doesn’t seem to want to same to the octave setting when I save and load the layout. It seems like it is reverting to 4ths for some reason, so that when I am triggering samples on the second row, they don’t continue chromatically from the end of the first row as desired, but start back on root +5 semitones. If there was a way to lock that, it would be helpful as well. If I could lock to MIDI out IAC Driver Bus, that would be sweet too. I am sure if I dug around the code I could figure out how to do that. I am working in the standalone so that I don’t have to have Max open all the time on top of Bitwig.

Aside from this one little thing, I have the 128 ROCKING with custom mapping in Bitwig. I have never had a controller that does everything I want and isn’t cluttered by a bunch of stuff I don’t need or use. Keep up the great work. Control is amazing, and I feel like I am just scratching the surface of what I can do with it.

…and yeah, I am sure that people are constantly coming at you and recommending features. This kind of thing is useful to me because I am using the Monome as more of a traditional controller for a DAW as opposed to as a sequencer using Max patches etc. - at least for the time being. I am sure I will go all the way down that rabbit hole at some point. It’s a tiny workaround for me. What you have done already is absolutely fantastic.

4 Likes
#116

Would love to hear details on what you’ve done here.
Bitwig user myself (moved recently from Ableton).

#117

Keep in mind that I am only using a small subset of Bitwig’s capabilities. I am making old school acid house tracks, so I am basically using drum racks and a couple of soft synths. That being said, combining the 128 with Control and a MIDI Fighter Twister, I don’t need any other control options. Super powerful and compact. I am still getting into it here as we speak, and am switching up my Monome clip launcher page, but once I have something sexy, I would be glad to share it.

2 Likes
#118

This is page 1 of my Bitwig / Monome / Control setup. This is for recording MIDI, which is mostly how I record.

This is a keyboard set to C2 root on ‘octave’ setting so that the notes of a 16 pad drum rack is played using the 12 notes of the lowest row and the first 4 notes of the second. It also works chromatically for MIDI instruments of more than 16 notes. In order to get this functionality, unless I am missing something in the setup, I open a saved layout and also a saved preset. You must set MIDI out in Control to the IAC Driver Bus 1 every time you open Control.

On the rightmost column are transport controls. From top down are -

stop
play
record
metronome toggle
overdub toggle
loop toggle

The lit bottom right button is for page selection, which you will know if you have been using Control.

4 Likes
#119

Page 2 - Horizontal clip launcher (I.e. not mixer view) in arrange. Each row is an instrument and columns are scenes.

Column 1 are solos per instrument on toggles.
Column 2 are mutes per instrument on momentary switches.

Columns 4-14 launch clips on the grid as displayed on the screen. Each row controls a different instrument 1-8.

Transport controls in the last column along with page selection as per page 1.

3 Likes
#120

Page 3, which is a controller for a soft synth, distortion, and delay made out of Control faders.

Column 1 filter cutoff
Column 2 resonance
Column 3 envelope mod
Column 4 decay
Column 5 accent
Column 6 high pass filter cutoff

Column 7 (toggle switch) for wave shape saw / square

Distortion:
Column 8 volume
Column 9 fatness
Column 10 color
Column 11 gain

Delay:
Column 12 mix
Column 13 feedback

5 Likes