Marbles alternate firmware possibility?

How difficult would it be / and would it even be worthwhile to have an alternate mode for Marbles where instead of taking an incoming steady clock and dividing/multiplying it, it would step forward on each pulse? Sort of like how the Wogglebug behaves. I know a mode like that would render the jitter ineffective and obviously the rate knob would not control the divisions/multiplications anymore but there have been many times where I would prefer to send it my own irregular pulses to step it forward instead of feeding it a steady clock. Do any of you who know more about this stuff than i do think this could be a feasible and/or useful mode for Marbles?

Some features of Marbles require the module to know in advance, at a given point in time, when the next pulse is going to happen (for example everything happening on the left side of the STEPS knob, JITTER, and clock multiplication).

However, if you don’t use these features, the module can deal with irregular pulses, both on the t and X clock inputs.

Interesting, thanks for the info. I will give it a try.

Hello folks, my first post so hopefully a relavent place for this.

I’m interested in modifying the Marbles firmware to allow for longer loop lengths.

What might be the theoretical maximum number of steps be?

Thanks.

Thousands.

4 Likes

Thank you @pichenettes.
I best start digging:)

Just change these two occurrences of 16:

to, say, 64 or 128. You’re adding more capacity for storing and replaying values.

And this is where the course of the DEJA VU knob is sliced into small 4° arcs to which a loop length is assigned. https://github.com/pichenettes/eurorack/blob/master/marbles/marbles.cc#L195

For example the value 5 is repeated 4 times, so it covers 16° in total of the course of the knob. I had to come up with this table empirically, because the response of the pot is not perfectly linear!

9 Likes

That is wonderful, thanks again.
I had an inkling about those two areas, can’t wait to try it out.

Here is the code for my little modification of the Length control…

int loop_length[] = {
1,
2, 2, 2,
3, 3,
4, 4, 4, 4,
5, 5,
6, 6, 6,
7, 7,
8, 8, 8, 8, 8, 8, 8,
10, 10, 10,
12, 12, 12, 12,
14, 14, 14,
16, 16, 16, 16, 16, 16, 16,
24, 24, 24, 24, 24, 24,
32, 32, 32, 32, 32, 32, 32,
48, 48, 48, 48, 48, 48,
64, 64, 64, 64, 64, 64, 64,
96, 96, 96, 96, 96, 96,
128,
};

3 Likes

Hello insoul8, did you ever get to achieve this? Looking for the same thing but haven’t got a clue about programming.

For anyone who would like to try more steps.
Compiled from version 1.2
https://www.dropbox.com/s/uty5z028dyotq5a/marbles128v1p2.wav?dl=0

2 Likes

@Jthrw: Thanks alot for that!!!
I have always liked all kind of step sequencers and over the years my length of patterned thinking has far extended over that typical 16-step margin to 32 at least, but often longer. So yeah, having a longer step count in marbles is such a good thing: sure, when going completely on random, there’s no difference, but when locking it - hmm, you can stay on a steady repeating piece of music and build a track around that or may-be inject just a bit of randomness and it starts to live independently by itself.
Btw, I just installed the update this morning and just tested out, that everything works, but yes, once again, thank you.

Well, not that the Marbles is used here to the fullest, but just to celebrate it’s first proper use, I threw together a silly track, where Marbles drives the bass part. As the text of the vocoder is in estonian, I’ll approximate a translation here:
Why a modular guy has cables around his neck? Please answer if you know.
When he puts the cables around his neck, is there anything difficult/hard on his mind?

Modular guy has cables around his neck, so that they wouldn’t get lost.
He needs those cables very much for patching the synthesizer.

And here’s the masterpiece:

Yep, it sounds abit raw and the vocoder might be too loud over everything else, but it’s made just for fun.