I created a preset where each pad in the rack has its Audio To set to FX and loaded it into Move, but it seems the settings are ignored and revert to the usual Send configuration.
Thanks!
Can you abort the slicing process? It doesn‘t seem that way. If you accidently navigate there you would be forced to commit to them, right?
Yeah, seems like something that should be corrected - trying to back out of slicing commits the slices. But then hitting undo snaps back to where the drum rack was so not a big deal. Although it also leads to another point, slicing into an empty drum rack and copy/pasting out the pads seems to me like the best way of doing this at the moment.
For fans of shaky phone clips - slightly awkward to do because there are a couple of shift actions, but you’ll get the gist. But imho there’s no reason not to install the beta and try it out.
3 Likes
In beta 1.5 - I think there’s an issue with step length workflow that was introduced recently, where we could hold two steps to set the length of the note, instead of holding the step and turning the wheel dozens of time:
a) sometimes it stops working at all - I can’t replicate it reliably, but it required to switch between Sets to have it working again and happened twice
b) I think before 1.5 beta I could see the length of the note with the steps being lighter and now it’s only the beginning of the step that lights up - I’m not sure about this one, though; if it wasn’t a feature before, I think it should be 
Can anyone chime in on these?
Also, I find the choice of parameters available for Auto Filter quite wanting. Would be great if they added the 2nd page 
can anyone who’s on beta 1.5 check how the timing/latency is when playing multiple channels via MIDI?
for instance if you sequence it via any elektron box, does the audio line up with the audio output from the elektron box or is it late? i’m kind of expecting this to have a certain amount of latency but don’t wanna buy and return it just to figure that out
I haven’t had any luck getting Move to recognize two devices connected via a USB hub — I’m pretty sure it can only act as a USB host for one device at a time. However, the USB to 5-pin MIDI cable that rg01a linked above will work. I have a Roland UM-One (same basic idea) and was able to connect a Launchkey mk3 to Move’s MIDI input and a Volca Keys to its MIDI output.
I had MIDI In set to Auto, so the Launchkey sent notes to the currently-active track and the Volca received anything Move sent on Channel 1. Coupled with a MIDI splitter, you could easily control multiple devices.
I couldn’t find that info anywhere, but the pads have very low latency IMO (for me - imperceptible) so I’d imagine it should be similar.
Although frankly I’m surprised anyone would consider it as a sound module. Its sound design capabilities are average at best.
1 Like
I can see the point of sequencing it with an Elektron box though, less pattern changes and such to worry about during performance
frankly I prefer the presets on the Move to something like the MC-101
8 Likes
honto!!!
What‘s up with lazy chop? Works since day one for me.
Thanks @benway for the video!
Looks like you are able to change both start and end point? There was a frame showing the end point I think. Can you confirm pls?
Also can you audio preview the slices when choosing which division you want?
Thanks
1 Like
Yep, but endpoint is for the entire sample. So if you want to e.g. use it just for editing a loop, you can set the endpoint, select two slices, and edit the start point of the second slice to the start you want, commit and then copy/paste out the slice. Or just use the start points of a slice and the next one to set start and end, depending. You can preview slices by hitting the corresponding pad at any point of the process, standard kind of approach.
Works well for what it is, but there are significant limitations right now. Once the slices are committed, the end point turns into a percentage and can’t be adjusted further on the waveform. Personally I don’t really get why fine-tuned endpoints are a big deal for loops, but obviously for a lot of people they are, so still not great there. And when you commit the chops it overwrites the drum rack you’re working in. So you need to keep an empty track to do this kind of chopping / editing in, i.e. a quarter of the available tracks, and then copy/paste to other drum racks. The good news for me at least is that by the time I’ve filled a drum rack or two I’m pretty much done so can repurpose the track for melodic parts.
But it’s a beta, and still a massive deal - has completely changed how I use the box. I think the slicing mechanics are pretty much there, give or take lazy chop, but imho they’ve got to eventually get to a place where it can be done on a per pad basis, with the slices assigned to a 16 slices mode to complement 16 pitches. Also an editor mode per pad that just does the sample start and end points and/or having the length parameter to display the waveform rather than a percentage. Can’t really justify having to give up a track in a four track box just for basic editing and slicing in the long term. But still, very happy with what I’m seeing here.
It’s definitely fast and easy to use, especially if you’re used to slicing in Simpler using the Push. I definitely agree that using a whole track as a working scratchpad for slicing is not right for the Move.
Also, copying between tracks is kind of a pain. I’ll probably stick to using Koala to slice things for now, then resample back to the Move’s pads.
Thanks @benway and @Mistercharlie for your answers I’m not sure whether I’m reassured or not but I will give the beta a go and report back 
1 Like
How do you do?
No reason not to try it out in my view. My take fwiw - it’s not what I’d see as a viable end point, but it’s also a massive improvement right now that immediately opened up a whole new way of working with the box. Subject to a couple of relatively minor tweaks if they could make these slicing mechanics available on a per-pad basis I’m not sure there’s much more I’d want from this device.
One other thing I didn’t mention, it doesn’t have a preview that plays a short bit of the sample up to the end point like a lot of other samplers do if that’s an issue, but seeing as you can just use the next slice’s start point instead I don’t think it really is personally.
I actually find copy/paste better than expected, but you do need to keep track of what’s where in the rack. I had assumed that Koala would be the interim slicing solution when it got audio over usb, but that hasn’t really worked out for me. I think having used it with the 404 where it’s basically seamless integration probably set an unrealistic bar, but also the low level jank of how sampling works on Move. Must give it another go, though.
1 Like
I‘m fine, thanks!