I think my refrain for the next while is "sequencing is hard". I used to have a BeatStep Pro and much prefer Kria (and even Teletype, which I usually do not use for melody sequencing). That said, I did get a Keystep (partly to have a small controller with keys to use with my laptop) because it’s just easier for me to stumble onto things with a keyboard.

I really like Kria’s approach to phasing and building up melodies out of smaller pieces with the metasequencer, and I really appreciate the visual aspect of the interface. Having spent some time deliberately thinking about how to break musical ideas into “chunks,” I think I’m starting to get the hang of it.

Haven’t really looked at the Hermod at all. Seems powerful?

3 Likes

Yeah, I feel that haha, I feel like the direction I take will certainly influence how I actually create music(thus stressing me out particularly with such a large purchase but that’s beside the point). Do you feel like this is the case?

As an example, I purposefully don’t have a keyboard to use with my modular to try and break from more traditional composition that I would do with keys. I feel like the “chunking” you’re talking about might be an example of how the actual system is pushing your workflow and composition in seemingly a positive and progressive way?

And everything I see about Hermod seems super useful as well as convenient I’m just not sure it’s for me at this point.

What are you feeding into the uScale?

Feeding (attenuated!) envelopes into Scales (which I think functions similarly?) has been my most recent sequencing experiment. For me it’s been Zadar envelopes triggered / reset by gate sequences from Teletype, but you could probably accomplish similar with Pam’s & Wogglebug into uScale?

(A decidedly non-Monome answer I acknowledge. Just responding more to what you have in the rack already.)

2 Likes

At this point, I’ve been feeding attenuated random stepped voltage from Wogglebug into uscale then to a variety of places. Which is my current primary source of v/oct since selling the sq1 and bsp.

positive and a learning experience for sure, but full of a lot more of the "learning things is harrrrrddd" frustration than I expected to encounter. I think this is just a fact of learning how to sequencer and not the fault of any particular device.

2 Likes

Hello,

I’m curious about the deep and esoteric world of monome/mannequins/od

Im interested in buying a TT, JF & W/. I’d like use the TT to lead the ER-301, JF & W/

Mind you I have no experience with any coding or the TT language but I’m interested in learning a few simple scripts and taking it slow.

I’m wondering is a backpack from the TT with designated i2c cables to each of those modules the proper way to go?

Do I need a txb in order to connect my 16n Faderbank to any of the modules mentioned above?

Is there a diy solution for a txb?

Thanks!

Gotchyea, I think my questioning is more rooted in the fact that I know the processes are fairly different and am hesitant to make the “wrong” for me choice. Thanks for the insight!

1 Like

i’m wondering about a diy txb as well. i have a busted half of my @MengQiMusic DPLPG that i was wondering if could be modded to have 3 seperate i2c connections (1 to er301, 1 to teletype, etc)…

anyone out there know how this could be done? just a regular audio jack that accepts TRS? also, does the DPLPG’s inputs only accept mono?

thanks/

Quick question for the Monome vets and “super users” out there: How do you keep track of everything thats going on with grids when you use it live? I’ve been reading through the material, and between Kria and Meadowphysics, the different pages, settings, presets, looping points, etc, I find myself getting lost as to what page,button, row does what for what implementation. Is there a handy dandy cheat sheet for a dumb dumb like me? I have seen pics of peoples grids with little stickers/letters taped onto their grids, which I suspect is aimed at addressing this issue. Thanks in advance for all the input.

N

1 Like

I’m definitely not a super user, but I do find that with practice at a specific app, the worries start to fade away into muscle memory. This, of course, takes a while, so in the mean time I sit at my synth with my laptop open to the manual, trying to figure out what does what. :joy:

(This definitely applies to Teletype, Ansible’s Arc apps, W/ and even Just Friends to an extent :sweat_smile:)

3 Likes

Don’t call yourself dumb. Each grid application is a different instrument that can require hours of practice to become comfortable with, some are more complicated than others. Kria in particular with meta-sequencing can get pretty complex. I would practice and focus on 1 app at a time. I think Meadowphysics would be easier to get along with at first. Keep the documentation handy and work through it.

With Teletype, I prefer to not save scenes as I’m learning and then rebuild them from scratch to see how much I remember, while keeping the command pdf handy.

2 Likes

Thanks for the tips…I’m totally new to this world. Got Norns, got hooked, sold off a bunch of my eurorack stuff and in short order got Grids, teletype, with arc and ansible on the way :exploding_head: totally overwhelming. I guess I just need to jump in and start somewhere.

N

3 Likes

That’s quite a lot to take on. I’ve downsized my rig quite substantially due to the functional complexity of monome + mannequins and how much they can do together.

yea, I’m kinda a spazz :slight_smile:
already gotten so much out of Norns without Grid or Arc (and gained so much knowledge from the awesome humans on this forum)

1 Like

Hello,

I am very interested in Monome but I have some quick questions.

  1. How exactly does ANSIBLE and TELETYPE talk? Does either send back CV info back to the computer itself? I would love to use CV and triger events in a visualizer like Mark Eats.

  2. Is there a connection with Monome and Mannequins? I see so many folks combining these.

Thanks.

1 Like

(this thread seems excellently suited for this discussion, so I moved your post here)

Teletype and Ansible mainly communicate together via a wired protocol called I2C. Neither is capable of sending CV to a computer on their own (there are murmurs that Crow might do such a thing?), but any DC-coupled audio interface together with additional processing power on the computer side would help with that.

Trent Gil, one of the people behind Mannequins, used to work for Monome, and is still friendly. Monome and Mannequins are collaborating on the aforementioned unreleased Crow module. Certainly the “ethos” of Monome and Mannequins are compatible.

4 Likes

Ok very stupid question, but would Ansible do the same thing as Teletype? For example could I just use super collider and send similar Gate and CV to Ansible vs using the language in Teletype?

Also can anybody explain the monome grids to me? There are so many versions, any disadvantages just using the old ones?

Not really, no. Ansible is open source, so theoretically many things are possible if you’re willing to rewrite the firmware, but as-is the only way for Ansible to interface with a device that is not a Grid or an Arc is by receiving MIDI and responding in one of a few prescribed ways to it. Teletype, by comparison, is able to communicate with a different range of devices and is open-ended without rewriting firmware by design.

As for the grids, they are a device that communicate via an OSC-over-serial protocol. They send messages corresponding to button-presses, and light LEDs in response to messages received. Thus they’re far “dumber” than they might look from a distance, but it’s this lack of purpose that allows their use in a wide variety of contexts. Most community development of applications that use the Grid assume—to greater or lesser extent—that Grids have 128 buttons and 16-step variable brightness. Older grids may or may not. This means using an older grid may sometimes come with UI compromises if you intend to use community applications. Of course, if you write your own code, your grid is your grid.

7 Likes