#9

Now that I think about it some more, the complexity comes from how the different sub-applications don’t have a strict ‘beginning’ or ‘end’ of a pattern. Just think about how flin can play highly varying poly-rhythmic patterns.

The point is, it’s easy to start / stop the sequence with a MIDI message, but making all the sequences restart in exactly the same way each time would require restructuring how a lot of the functionality is currently working.

If you need a performance to happen the exact same way every time, my suggestion would be to record the audio output!

1 Like
#10

So let me get this straight, because I want to make sure I really understand. If I record the audio, I can then play it back and it will sound the same as it did the first time? What sort of equipment would I need for this?

Anyway.

I guess I wouldn’t really care where the non-linear sequences start or end, in my mind it’s the grid based sequences that should have priority. What I’m imagining is just how traditional sequencers interact with one another:

  • When you hit play on a the master external sequencer or drum machine, etc, it should start Sum. (Linear based pattern sequences will start on the first step in the pattern)

  • If you stop the external device it should stop Sum and return to the first step of the (linear based) patterns.

  • If you hit play while the sequence is playing it should pause the sequence and pick back up where it left off when Play is pressed again. Otherwise, if a Stop message is sent it should reset back to the first step in the linear patterns.

Flin should just do what it does and stop when it gets a Stop or Pause command. It should probably not differentiate between stop and pause. Does that make sense? There is no real beginning or end to what it is doing.

Corners and Gome should ignore these messages altogether.

These interactions plus external control over tempo would make sum an incredibly useful tool for use in conjunction with other hardware - especially in a live setting.

#11

i did a quick/dirty port of sum to m4l and when u stop the transport, it pauses sum, then u can pretty easily set the playhead position to 1 in step, trigger sequences to play on the 1 in gome, flin, etc. when u start the transport.

i don’t think i even modified any of the time/sync part of the patch, it just ended up this way.

2 Likes
#12

@Gilles_READYdot: That sounds like it would be perfect.

@Galapagoose: Would this be tricky to achieve in the standalone version?

#13

Oooo… Specific?! Now you’ve done it!

MidiOUT: I’d like to see each of the sequencers (i.e. everything but mlr) spit out MIDI on different channels so that I can send midi to Ableton or my synths.

Individual channel rewire support: It’d be very useful to be able to record the separate channels. I’ve often recorded little jams with sum that have never really been used because the mix hasn’t been quite right or an individual sound hasn’t quite worked.

2 Likes
#14

also thanks for looking into this for us!

#15

Hey folks - any adventurous souls want to check out the preliminary updated version here that’d be great. Has MIDI Clock input for clocking from external source and a simple “multi-channel” breakout function using Outs 3-8 for individual tracks (intended for Rewire).

The in-built mlr files will be broken when not built as a standalone, but it should load external samples just fine.

This is for Max 7. Tested on 10.9.

3 Likes
#16

Wow. Thank you very much. Totally floored.

Working just fine so far in Max 7, OS X 10.10.4…

#17

Wowzer - busy with two jobs for the next few days, but will try to take a look at the weekend.

Thank you!

#18

I love the app switch in _sum the most. is there a way to break out that patch?

#19

Been enjoying sync. Thank you.

Would it be possible to send a full stop message to sum?

When I press STOP on my external sequencer sum jumps back to step 1 in step but then just keeps going. I’d like to be able to just outright stop it dead in its tracks and let whatever last playing notes ring.

#20

This is exactly what I would like out of monome_sum. All I want really. Sequencers spit out midi on different channels and individual channel rewire support. Boom.

#21

Regarding multi channel outputs in sum, is there a way to assign individual outs on my 4-output sound card, or are they fixed, meaning I would need an 8-output sound card to route everything out individually? I know I can rewire with live and assign them however, but it would be convenient to do it right out of max. Thanks!

#22

If memory serves the mapping is hardwired, but Max has internal output routings.

  • Go to ‘Audio Settings’
  • Click ‘Open I/O Mappings’
  • Assign the ‘Output Mappings’

What you’ll want to do is assign the first 8 ‘outputs’ (Max’s virtual outputs) to your hardware outputs. You can send more than one Max channel to a given hardware out.

#23

Okay, found it. Options > Audio Status > Open I/O Mappings. Thanks!

#24

Hi,

I’ve been facing trouble lately with monome_sum. I use OS X (10.11) and have a 128 walnut grid since 2014. The monome works fine in all other patches/applications, it’s just that it doesn’t work like it used to when using monome_sum.

When I plug in the monome (and get the connection indication lights) and launch monome_sum, I get no lights in response to pressing anything. I sometimes get some sounds from flin but there are no lights on the monome itself. When I try switching from flin to another application, I get no sound at all.

I tried reinstalling monome_sum but got the same results. Again, the monome works fine in when using Terms in Ableton or any other MaxMSP (I use Max 7) patch.

Thanks.

#25

Are you using the stand-alone application version of sum included with the monome device installer, or the max patch version that requires max to be installed (even the runtime version)? The former version is available here: http://monome.org/docs/app/sum/

I have not been able to get this version to run, as it seems to max out cpu usage and crash. The latter max patch version works fine for me, though. It is available here: https://github.com/monome/monome_sum

Just click on download zip.

It would be great (especially for those of us who have held off on going eurorack) to update the links on the sum page to include this, as this thread is the only place I am aware of where it is available. Or perhaps the application version could be updated to include the more recently added features. It would be great for both to be available on the sum page. Thanks!

#26

Many thanks for this. For some reason, the standalone version doesn’t work at all while the version that requires Max 7 works okay but crashes after a few minutes of use. I’m trying to use it for a live performance but at this rate I’ll have to rethink my performance strategy.

#27

@hujairi - What is your audio buffer size and sample rate settings with the max 7 version of sum? It’s solid for me at 128/44.1 in 10.10. I was having many issues with 10.11 with max and max for live, so I downgraded back to 10.10. All better.

1 Like
#28

@Galapagoose - Okay, having a problem with mlr in the max 7 version of sum. I can’t seem to assign loops to slots. I know you said: “The in-built mlr files will be broken when not built as a standalone, but it should load external samples just fine.” But if I load an external sample to a preset, then another to another preset, only the second sample loads for all presets when I open the patch again after saving. What am I doing wrong?

Edit: The max console posts the following error whenever I click on a slot in mlr or click on a preset:

buffer~ - filename.aif: can’t open