I too have learned important information from this thread that is not in the manual.
At a minimum you really need to read the manual, the technical FAQ, etc. to really get a good overview of Move’s capabilities and limitations.
Ableton has not made it easy to figure out what this thing can and can not do.
I am very excited by this. Bought it within minutes of watching the Sonic Lab video. I am not a “beat maker” and don’t do hip hop. this is my Push on the go. I’d really wanted a Standalone Push, but it is too heavy already (I have a P3C), which I really like, but it is not portable, due to weight, size, and needing to be tethered to the computer. I travel quite a bit, and it was going to be something like this or an OP-1, which is really expensive and an entirely new OS to learn. So, for my “noodling” on the couch, plane, or cabin, this looks pretty perfect. If I do end up coming up with the beginnings of a song, so easy to put it into live and work with it and expand it on my Push/Live.
Can anyone comment on pad sensitivity yet? How hard do you have to hit these to register, on the scale of Model:Samples to Launchpad Pro?
Immense, that first jungle beat is absolutely legit, nicely done fella 
2 questions for those who already have it:
Actually - yes, you can: Presets on Move – Ableton but you’ll have to rebuild them using the templates. You can upload the samples w/o presets, though using the Move Manager (or whatever it’s called).
Supposedly not
Great! Evidently it’s an experimental feature, which would explain why it’s not in the manual yet.
I mean maybe theoretically but the workflow for it was just bad. Maybe I didn’t give it a proper fair shot before selling it but I’ll take the 8 macros per patch (+ track effects) any day over the labyrinthian Roland UI.
I have a Push 3 Controller, which I plan to use in Studio. I’d hoped Push would be a mobile solution, but it’s too big, heavy, and I didn’t want to spend another $1,100 to get it standalone (I don’t do live sets). So, to me, Move is an actual mobile sketch pad that I can integrate with Push/Live in the studio.
Splitting hairs here but it’s a slightly different workflow. Lazy chop in other samplers I’ve used implies that source material has already been recorded in, then is lazy chopped across different pads. With Move you’re doing the lazy chop during the record in process.
got a link for that?
Re: the CPU 
Would be great if someone with Move already could run an experiment, i.e. create a full loaded Set on Move and then export it to audio using the Move Manager. Assuming the export is run on the move itself (and that’s a big if, but would make sense), they could time how long it takes to export the Set and divide it by time it takes to play the Set start to finish on Move. This could indicate how much free CPU resources are there 
Sorry to beat the dead horse 
As a bald guy, I’d like to point out that it seems you can have the original drum loop in one pad - or definitely on a different track - have it playing and multi-pad record (aka “lazy chop”, aka “resample”) into remaining pads.
But I’m not 100% sure.
Very different that exporting about 4 tracks using Ableton’s own engines.
took me a second to get why you mentioned you were bald. Well played sir
I ordered a Move even though I’m fully dedicated to Push 3. There are three-and-a-half selling points for me:
1 - Sampling Workflow. On the Push, you record a clip into an audio track then convert it to Simpler. It’s fine, but it’s a multi-step process that still doesn’t feel intuitive. The Move has a dedicated button on the front panel that lets you sample with basically no friction. I also like that the Move has a built-in microphone like the OP-Z.
2 - Size. The Push 3 is definitely portable, but I’ve flown with it in my carry-on six times now and it’s not ideal. Worse, it got flagged for secondary security review on four of those flights. We have a three-year-old so anything I can do to make travelling easier while still being able to pursue my hobbies once we’re at our destination is going to make everyone happy.
3 - Family Time. The Push 3 is perfectly fine on my lap but it’s big enough that I need to be very deliberate about how I sit, and I can’t just set it down anywhere and walk away. That’s far from ideal when my daughter suddenly gets bored of colouring and wants to jump on me or whatever. The Move’s form factor should make it a lot easier to use when we’re all together but doing our own thing in the living room, and I think I’ve said this four times in the thread already, but the Push‘s screen is juuuuuust prominent enough that I feel guilty using it after telling my daughter she’s had enough screen time.
.5 — Workflow Familiarity. I got a Push 1 in late 2013 after almost ten years of recording into a Tascam 788, and I didn’t really have any preconceived notions about what a DAW or groovebox workflow should be so I adopted the Push as my standard method. Since then, I’ve had a hard time getting into anything else. I clicked with the OP-Z and developed a really good muscle memory for it, but I sold it a couple years ago because the durability just wasn’t up to snuff. This is only a half point because the Move has some frankly-puzzling changes from the Live paradigm (horizontal scenes?!), but I’ve tried and given up on the Digitakt, Polyend Tracker, Circuit Tracks and Rhythm, and Octatrack mki, and I’ve avoided the MPC and SP-404 because I can finally accept that i prefer Ableton despite some shortcomings.
Hope this helps!
So can this be used to control Note on iOS, or not? I only see them mention controlling Live with it in the product description…?
