Looks like it yep. I assumed you’d get pad 1 = the first chop, and pad 2 = 2nd chop and you wouldn’t be able to move the points around. It’s hard to tell excactly what’s going on (whether it’s copying the file internally or just referencing one file). I’m guessing it’s copies of the file to allow individual pitching. Either way, start point plus plus attack should deal with clicks and pops really nicely.
When doing lazy chop, each pad shares the same sample.
That’s the absolute beauty of it IMO… I generally know if I’ve got something I want to develop from a 2-8bar loop or two.
If the vibe is there, job done for Move, I might pad it out some more there; but, I’m already visualising how I can take those seed ideas and develop them fast in Live.
The speed of that workflow is unparalleled.
MPC and Maschine can do something similar in a few more steps, but they’re nowhere near as slick.
And, on the ‘4-track’ thing, ‘Extract Chain’ from your Drum Tracks and you see what’s there really.
Obviously we’re all still in the honeymoon phase with Move, but it’s feeling like the device I’ve wanted for years.
That’s great, I’ve had the kids all weekend so my times been proper limited, but man this box just gets better and better…
This is exactly what I just did to prepare a recorded jam converted to slices to throw back into move.
haven’t done the last step yet, as I need to use the ‘experimental’ feature to get it into move, but I tested it in Live with Push and it works well. You have to make sure the ‘kit’ is mono only and set the ADS envelopes to suit. Unfortunately you have to do all the steps one at a time, as I cannot find a way of batch cropping etc in live yet.
Also, it’s annoying you cannot set a pad slice to loop more than 500ms. Ideally I would want to loop one whole slice until I play another one
I’m still waiting for my Ableton Move and started thinking how would I pack my samples into Move drum racks.
So while thinking on that, I made an open-source and free tool for slicing long samples directly into presetbundle files which can be transferred to Move or Note.
Feel free to create issues and feature requests https://github.com/alexfedosov/move-tool
PS: the tool does not have GUI (and likely won’t in any foreseeable future), so you will have to use Terminal app
Sounds great
When I’m trying to overdub a clip, track 2 here, it creates multiple clips and fills the track lane. Anyone know what’s going on here?
If you have a USB class compliant synth then I assume you could use that as a bridge between other gear with DIN MIDI. Something small/cheap like the Roland S-1 could work.
Spot on. I ended up getting this one in the end which is a perfect fit. https://amzn.eu/d/1azAAMd
I just found out that you can “parameter lock” per page in loop mode !
What do you mean?
I think you can finish songs on device. You just have to manually perform them.
Fun as always, but this is maybe the first time in my life that I’ve felt like I could teach Ricky a thing or two!
For anyone watching this video and wondering:
- ~10:45 regarding sample playback: Shift + Click the jogwheel on a Drum Sampler track to access a second page of parameters where you can select Gate mode. Edit: Ricky figured this out on stream at around 24:30.
- ~ 12:00 regarding captured clips: Hit Loop Select, hold the step key for the bar where you want to shift notes, and tap the arrow keys to nudge by 10%, Shift + tap the arrow keys to nudge all notes by 1%, or hold the arrow keys to nudge by a full step. Double tap a step key to loop a single bar.
- ~ 20:00 regarding audio interface: Confusing IMO. Currently, Standalone mode supports audio output over USB-C, so you can record directly into your DAW without needing a separate interface, but you can’t record audio input over USB-C or monitor your DAW through the Move’s headphone outs even though it shows up as an output source in your DAW. Move Standalone only receives audio from the mic or the audio input. Controller Mode allows you to monitor your Live session through the Move’s headphone jack and use the audio input to record, so it’s a full 2i2o interface. Note that it’s locked to 44.1kHz, which is fine except that Note exports at 48kHz, and the iOS Camera app defaults to 48kHz, so there are some edge use cases where you can run into sync issues – for instance, I had an issue importing 44.1kHz audio files into iMovie a few years back.
- ~22:00 regarding threshold recording: Ricky figured this out, but it’s worth restating: There’s no threshold recording, but it does automatically set the start point. Koala does the same thing and it’s actually preferable in a lot of cases – check out BlankFor.ms for some inspiration on how to use empty space at the start of your samples!
I’m drinking coffee and watching the recording so I’ll keep this updated if more things come up. I was really happy to see that Ricky bought a Move; he’s got such a strong Elektron and MPC background so I’m excited to see how he twists the Move’s workflow.
Also, there are no two ways around it – it’s really not ideal for integrating into a hardware setup right now. Ableton confirmed on Discord that the hardware is capable of much more MIDI, but there is no timeline or public roadmap for the improvements.
Let’s say you have 2 bars with a bassline and a few steps: instead of parameter locking a specific step to open the filter, you can open the filter for an entire bar in loop mode.
That was actually the fun part for me. Watching him playing around while discovering stuff. Makes me less a noob
Maybe it’s right under my nose, but is there a way to adjust the level of a specific pad within the drum rack track ?
Also, when you resample in a drum rack track to get around the 4 tracks limitation, what is your workflow in a set ? You use one drum rack track for drums and resampling in the pads, and the other tracks for sounds to be resampled ?
It’s not in front of me but can’t you hold the pad and turn the volume knob?
Ah yes it was right under my nose
Section 15.7 in the manual: “To adjust the sample gain, press and hold a pad, then turn the Volume encoder.”
Oh that’s pretty cool. Thanks for explaining