#61

@jasper_ryder it changes the interval for the rows.

#62

did a quick M4L conversion of ‘control’. still some issues (like automation and autofocus not liking each other) but working fine over here. auto-loading layout and preset when opening a live set is for the next version.

download available at github.

3 Likes
#63

ive been using this patch alot. A couple things:

  • Say i have two faders on the last two columns on the right side of my monome, they are all the way up. Cool, now i hold the control page button (bottom right corner), begin recording for that page and release the control button. When the midi controls reappear, the far fader (as in the fader that also is in the same column as the control button) is now all the way down at the start of my automation. I wanted it up. The control button is simultaniously sending MIDI cc values and recording them into the automation. Ive stopped using that column for faders.

  • Now, in this same example as above the second to last fader i never touch in the automation. After I close the recording loop, i wanna fuck with the second to last fader slowly up and down and up and down. The problem is, everytime the automation loops back to the beginning, the fader i didnt record any automation for, jacks itself back to the highest position. I think this is the case for any toggle, XY, and fader. All are reset back to thuer original states.

can this not happen is my request?

#64

@raws true, the rightmost column should be avoided for faders due to the presence of the shift key (I’ll work that in for the next version). automation idd starts by recording the original state of the object (fader, toggle, …). I’ll look into individualizing them (might take some time cause I got my hands full with another project at the moment).

#65

Love this set of tools however, once creating an xy control I only seem to be able to get one axis to transmit a midi cc. How do get both to transmit control messages?

#66

@Holl1f3ld are you using the m4l device or the standalone? just checked both and all seems to be working fine. when mapping you should push a button in the same column/row as the lit LED … the cc number should change.

#67

@raws found some time to look at this automation issue. fixed it for the M4L device (standalone/maxpatch will follow soon) … download new version on github. let me know how it works.

edit: updated standalone and max patch

1 Like
#68

@ithkaa Got it working… Thank u sir!

#69

@ithkaa thank you for hitting the request so quickly! I can confirm that its working nice and smooth on my setup here.

Of course, part of being a dev is deraling with the never ending stream of ideas, requests, bugs right!? One more: I noticed that when i stop the live transport, the automation recording continues to play retriggering midi CCs while live is stopped. So arte the automations purly a snapshot of the literal amount of time between start and stop automation windows? The window is probably not snapped to grid or following live quantize globals? While not a big deal really at all, these features (snap, global, play from automation start on transport start) would hopefully lead up to something like @elquinto’s MIDI press data recording equiv in your app. Wouldnt that be awesome?!?!?!

Alot of folks on the form are achieving great results by way of “touch and let the grid go” (TT WW MP MP2), which rules because there are many use cases for me, but it seems that the devel focused just a tad bit more on that aspect (im still learning). But at heart im the monomer that @misuba describes in his MP2 tshirt idea, im the “Constant touching everything all the time” guy, with my core monome/mpc influences being @edison, @pauk, @Galapagoose, Justin Aswell, Jel, and Exile. So im really happy and thankful for such an involved project you’ve put together for the community. Its helped me move away from the nonvaribright 32bit liveOSC java Pages project, and is just dope.

Whoa… i meant to get on here and say “Yeah all systems go man, it works!”
Side note: Ive been using a few of your non monome m4l devices for some time (years ?) just realized your username from maxforlive.com is the same here. Specificly GlitchR and ArtefactR.

#70

@raws tx! idd no quantization etc in automation. maybe in a future version. I myself prefer not to have quantization … keeps me focussed :wink:

good to hear you’re liking those m4l devices. they are all born from necessity (just like ‘control’). i’m not a real developer in that sense, just happy to share

updated the m4l device (click any github link in this thread and redownload the package). let me know how it works.

#71

@ithkaa
Hey ithkaa, How are you? I hope well.

I am having an issue with notes-3 maybe you can help me with. It’s an issue with autofocus again. Here’s what is happening.

I am playing notes_3 set on toggle. I will push some pads and the notes are playing nice and are sustaining. I then jump to another track and am playing whatever. When I jump back to notes_3 all the sounds that where playing stop abruptly but the pads stay lit. Needless to say it does not sound good when this happens.

Any help is greatly appreciated.

#72

@jasper_ryder tx for pointing out that issue! fixed it in updated version

#73

@ithkaa,
Thanks! That issue is gone!
Autofocus it a strange thing. It acts a little differently for different patches. Something that is different between notes and grid128.amxd (50.6 KB) I’ve noticed is:

Example 1: using two monomes with ‘notes’ and any other patch. Each monome is set to it’s respective patch in autofocus. I can only get ‘notes’ to react when I click on the track that ‘notes’ is in.

Now this seems totally normal and the way autofocus is meant to work but,

Example 2: using the exact same setup but using ‘grid’ instead of ‘notes’ I can bounce around to other tracks and continue to be able to play the monome that is focused on ‘grid’ the whole time.

I do prefer ‘notes’ to ‘grid’ because of the pattern recording, the random function and the all the options with row interval It is a far more useful patch, but damn I like being able to bounce around and solo a ton.

#74

@jasper_ryder updated the device. let me know if it works for you.

#75

@ithkaa,
Just trying it now. Been away from the computer for a few. So far I’m having strange feedback with record function. I arm the record pad, then hit a sound pad, all of a sudden the sound pad shuts itself off almost instantly.

Haven’t checked the other thing yet. Preparing my set for the radio show now so I won’t get to it presently.

#76

@ithkaa,
Hey Ithkaa,

This version solved the issue of bouncing around tracks. Thanks.

If you want to recreate the strange behavior with the pattern button:

put notes in toggle mode, then try to record a pattern. Strange button behaviors.

#77

@jasper_ryder check the updated device on github

1 Like
#78

added as a featured app on http://monome.org/docs !

3 Likes
#79

@ithkaa,
Works great ithkaa! Thanks again. Would it be much trouble to add a 64 version? If so don’t bother. (I’ll look at the code and see if I can hack one too)

I’m grateful for all the updates you’ve gone through. Thanks

#80

@jasper_ryder tx! will look into 64 support
@tehn tx!!

2 Likes