#61

You nailed it @dan_derks! Although I think it’s a bit misleading to say that the new parameter toggles between recording to buffer 1 and 2. It’s more like it toggles between 1+2 and 2. At least that’s what I found to be the case (which is what I wanted - a way to overdub into both buffers at once). Does that make sense? Thanks so much for implementing this! Here’s a little 2.12b ditty:

8 Likes
#62

wowowow, that sounds excellent! thank you for sharing. what was the sound source on this? it’s perfect.

hmm. this isn’t consistent with intent or my test results – would you be willing to try this workflow?:

  • start a fresh cranes session, default values.
  • record about 6 seconds of audio, which should write into buffer 1 and buffer 2 simultaneously.
  • turn on full overwrite for buffer 1 / voice 1 (o1 = 1). this should eventually erase the content in buffer 1.
  • once buffer 1 is clear, overdub (so, o1 = 0.0) and play something different.
  • you’ll have two distinct loops going on L + R channels. toggle overdub off.
  • switch the voice 2 buffer reference to 1.0 in params
  • you should hear voice 2 now playing exactly what voice 1 is playing.
  • on the main performance screen, use K1 to toggle focus to voice 2 and set o2 = 0.25. hit K2 to begin overdubbing.
  • as you play, voice 2 will write into buffer 1 – since voice 1 is also referencing buffer 1, the changes should take be constant between the two voices.
  • toggle overdub off (K2)
  • head back to params and switch the buffer reference back to 2.0
  • you should hear the original first take audio.

if those steps return the results described, this means (to me) that the parameter controls which buffer voice 2 is referencing, exclusive – buffer 1 or buffer 2.

if no, please let me know what variance you run into so I can further troubleshoot! :revolving_hearts:

(fwiw, voice + buffer are separate terms – in standard config, voice 1 writes to / plays from buffer 1 and voice 2 writes to / plays from buffer 2. by toggling the buffer reference param, voice 1 continues to write/play buffer 1 but voice 2 will write/play buffer 1 as well. )

4 Likes
#63

Thanks @dan_derks, I will give this a try in a bit and let you know the results. In my example recording, the high notes that come in were an overdub on voice 2, writing to buffer 1, but sound as if they are present on both buffers, thus the nice delay between the 2 when modifying the start time on one. Maybe we are on the same page, and I just don’t understand how it works. That is entirely possible!

And thanks for checking out the recording, glad you enjoyed it. The source was a sample on the OP-1 created by Valotihkuu, who makes amazing sample packs for the OP-1.

2 Likes
#64

ah! if this was when the parameter setting for voice 2 buffer reference was 1.0, then this is expected – voice 2 is writing into buffer 1, which voice 1 and voice 2 are both playing. so, you’ll hear the same sounds through both voices.

bonus: if you set voice 1 and voice 2’s rates different from each other in this mode, then overwriting with either voice will write the sound at their respective rates into that shared buffer – so that when the other voice passes that part of the buffer, it’ll play the sound faster or slower depending on the relationship between the voices’ rates.

I think we’re talking about the same phenomenon, but with different terminology – it’s taken me a bit of time to fully understand how it all shakes out. please lmk if there’s any misunderstanding/misrepresentation on my side!

and thank you so so so much for engaging in this process. looking forward to your future experiments.

2 Likes
#65

@dan_derks Works exactly as you’ve described. The issue was me not understanding the exact magic of cranes. Thanks again for this amazing tool and all of the work you’ve put into it!

3 Likes
#66

= the wild magic of softcut. @zebra, thank you again – it’s a fuckin’ treasure.

9 Likes
#67

This is just wonderful. Well done @dan_derks.

I don’t mean to sound needy but - you know it’s just crying out for a playable playhead and pattern recorders.

4 Likes
#68

this has me thinking maybe i do was a norns and a new grid. i just sold my 256.

2 Likes
#69

Having ridiculous amounts of fun with cranes :heart_eyes:

I had a thought while jamming on it last night… It would be cool if connecting an Arc could represent the 2 ‘reels’ rotating… which could then be interfered with, like touching the tape heads on a physical machine?

3 Likes
#70

Is there any sort of demo video on Cranes with the grid? I would love to check it out. I only found a demo of the original with seams out of date now. Thanks

#71

I’ll take a peek at these – the first is definitely easy to add, the second will require thought. I’m also trying to keep cranes a specialized tool – those two features feel so deeply engrained (and expertly executed) in mlr that I haven’t felt compelled to bring them to cranes. thanks for the push, though – definitely worth considering if it’ll extend expression!

would be v cool – I don’t have an arc atm, but it’d be a great project for someone to fork off cranes :slight_smile:

not yet (still shoring up a few features :sweat_smile:), but are there any q’s I can answer until then?

3 Likes
#72

that was my first thought

just chiming in

6 Likes
#73

btw this is very impressive and immersive

i love it

1 Like
#74

Thanks in 20 characters!

#75

@Molotov I’m trying to wrap my head around how this could be done

The gesture for KEY 3 is uniquely suited to mimic touching a moving strip of tape (or turntable platter)

While the arc is perfect for visualising the data we have to find a way to register change of direction to trigger this command since the encoder itself isn’t actually free spinning

Any thoughts yall?

1 Like
#76

@dan_derks - Experimented with Cranes 2.12 last night, and though I wasn’t as methodical in my testing as I probably should have been, what I heard with the new buffer setting did seem to be what I was originally expecting :raised_hands: The session was a blast, too:

Cocoquantus, Cranes, acoustic guitar.

8 Likes
#77

i am working on an arc script where the last touched knob gets selected on the UI. from my experience, you really don’t have to touch it much at all to get a delta. the easy hack would be to simply say any delta calls warble(). but probably more expressive would be some arc specific function that warbles faster on positive deltas and slower on negative deltas? this would definitely be fun. i still need to check out 2.1!

4 Likes
#78

20 characters of same feeling

#79

Oh man that sounds really coool

#80

on the arc nudge tip- maybe an LED indicator sits at 12 o’clock when the loop is running at a fixed speed. then you can swish the encoder to the right to speed it up, or to the left to slow it down, but when you let go it drifts back to 12 o’clock. i’m imagining the led physics behavior feeling like there is some nice resistance to the movement. would make for some fun gestures.

9 Likes