#154

Output of Marbles into a precision adder?

1 Like
#155

That seems like a good solution. Was hoping there might be a setting in Marbles that I was missing.

#156

i haven’t checked this precisely but have you played with Spread and Bias to any appreciable result?

1 Like
#157

I have. It’s just not very intuitive or applicable for matching another quantized unit in my skiff

1 Like
#158

I output through uO&C. It allows for both octave and percise root transposition. It’s very flexible and accurate.
I haven’t been able to accurately transpose root in Marbles by itself but look forward to learning when someone figures it out.

#160

You could also record two scales, with differen root notes, into two slots and then switch between them. Admittedly scale switching isn’t super quick though.

2 Likes
#161

which mode do you use on the uO_C for this?

2 Likes
#162

would assume quantermain

#163

Yep Quartmaine for sure. My go to patches are either Kira->Quartermaine->Marbles or Marbles->Stages patched as a shift register->Quartermaine or some combination there in. It’ll take me years to exaust the sequencing variety these few modules provide. The uO_C replaced Beast’s Chalboard and the Disting Precision Adder for me and I couldn’t be happier.

4 Likes
#164

A little off topic, but how are you patching Stages to do a shift register? :thinking:

1 Like
#165

Hmm, I thought the post about Stages as shift register was here, but I can’t find it in a search…

The answer is: far too many stackables. Set all 6 segments to S+H, mult all the gates together, and mult the output of each stage to the time/level input of the next stage.

I did it once. Never again :laughing:

4 Likes
#166

That’s what I was thinking, but wouldn’t pinging them all with the same gate make for timing issues? :thinking: I presume not since y’all have done it. :laughing:

#167

Hmm… Marbles does some self-patching detection. Maybe Stages does too, and if you patch one of its outputs to one of its inputs it applies appropriate gate delays? Or maybe it just coincidentally works the right way, or intentionally works that way through some other design choice. Anyway, it works :slight_smile:

1 Like
#168


Nothing fancy, just toying with marbles’s knobs.

Now that the code has been made public, i would really like to find someone able to make possible that little option that i talked about last year:
https://llllllll.co/t/mutable-instruments-marbles/12603/96?u=martinmestres
:kissing_smiling_eyes:
Émilie told me that it is something like a 20min work, so if someone has time to loose :heart:

1 Like
#169

It would be great if the two sides could be broken out into smaller, individual modules. I personally LOVE the features of the timing side, but don’t really care for the voltages aspect, so I can’t justify putting the full module in my case.

#170

Hi @grey, @baleen, @Starthief, @Calytrix

I liked what you were writing about Marbles in the general modular thread. I am hoping you could share more about what you were doing with seperate clocks to to the the t and x sides. Seems like it might be a key.

3 Likes
#171

To me, the point of clocking X separately is to synchronize all the X outputs. It can act something like a shift register that way, particularly when sampling external CVs.

But I also like letting t clock that side, and getting other rhythmic variations on the sampled input.

To be honest, I’m often lazy with Marbles and just let it do its thing with no modulation, though I do like clocking the t side from rhythmic patterns rather than a simple clock.

4 Likes
#172

Uncoupling the two sides feels like it gives me more flexibility. I like to clock the two sides separately so I can use the t side to control some rythym, while the X side is providing some sort of modulation elsewhere in my system.
But that’s just what’s working for me right now.

1 Like
#173

I haven’t ventured into independent clocking. My current challenge is getting the triggers to feel in sync with Grids. I’ve experimenting with catching triggers for a reset on Grids, but it’s actually pretty tricky to get the timing right which might just be me missing something. :thinking: I REALLY wish there was a reset input.

I was thinking I was going to use the triggers from Marbles for voices, but decided Grids actually made more sense for voices than Marbles, so I’ve been experimenting with that. Trying to use the triggers for drums in the “grids” mode of Marbles, and initial impressions are good. I get the nagging feeling I may just need a second Grids eventually, but I want to work with all of the triggers I’ve got for the moment. Nothing set in stone yet. Still feeling around for my ideal solution here. Everyone has different goals.

As for what I mentioned in the other thread:

The record mode is probably my favorite feature on the module. I have pop-ier aspirations than most lines folks, so I’m looking to use more traditional music structures. Since everything I do is improvised, is nice to be able to feed a melody in to Marbles and then have it improvise around that sequence on the fly. That was also how I was using it before I traded it away, but I need to give it another chance. I had trouble with the triggers before, so if I can make those work now, it’ll be a keeper.

Also the random value output is nice for Sloth like functionality, which feels like a nice bonus.

Happy to speak to things more specifically if you have any questions.

5 Likes
#174

I’ve had marbles since it came out and still have recorded any notes lol. I really need to get in on this action.

I ended up trading my grids but when I had a grids and marbles I got the best results by feeding them into a seq switch. Lots of interesting combinations to be had with this set up. Especially when locking the t mode. It doesn’t replace a hard reset but I’d give it a shot.
If you own one…I was using the ornament and crime (hemisphere) as a simple 2 channel switch.