I think that’s my thoughts as well, so happy with what’s already in its initial OS.
Not that you asked, but feel like chiming in with my thoughts— when Schwung first came out, I installed all of the modules, and then when more and more kept getting added, I realized that there were so many devices that didn’t even know what they were, and I removed most of the ones I knew I wouldn’t actively use. I’m really happy I have Schwung installed on the move, it works really well, but I basically only use it for chord mode, the JV-880 emulator (which is one of my favorite plugins I’ve used in the past year on every/any platform), the DX-7 emulator, and the access virus emulator. Really easy to overcomplicate things with Schwung if you aren’t deliberate about why you are using it, but having a JV-880 and a DX-7 (at least for presets) is invaluable to me.
Excited to spend more time with RNBO on Move, but as cool as hardware granulator is, I’d rather just write some music with the Move.
8 Likes
I wish I could get the JV-880 on my push 3
Thanks for the insight. Sounds like the approach I will take when my move arrives this week.
Just to be clear, can I sequence the (eg) JV internally, or externally, bounce to audio and then import that back into a move track as a normal sample ?
Any of the sound modules in Schwung can be sequenced “internally” by one of the four Move tracks by setting a particular output midi channel for the Move track and setting the input midi channel for the Schwung module to that same channel number.
There are ways to bounce it to audio, but I don’t know the best way to do that off the top of my head! The Schwung manual (at the github) will have the required info. It might involve using Ableton Link Audio to track the audio out to Live, and then saving the sample from there? Let me know what you find haha, I’ve been super busy so I haven’t spent quite as much time beyond jamming as I’d like.
1 Like
With all this discussion about using Schwung being in parallel to the standard Move OS. It got me thinking there must be quite a bit of headroom still left on Move, CPU wise. Which fills me with hope for a future update with some more master fx and a simpler Simpler.
3 Likes
Yeah, and I think you can even use RNBO modules in Schwung in the latest version (@charlesv correct me if I’m wrong) without the whole thing exploding. So there is indeed quite some power left it seems.
wow, I missed that RNBO takeover mode was added. wild!
Has anyone here connected their Move with a separate sampler device? I took the bait and bought an MPC Sample last week… looking forward to triggering the MPC Sample with the TR-style step sequencer on the Move… apparently it can also do some of the skipback recording that people love about the SP-404mk2, and that could be really cool to capture some Move noodlings…
1 Like
Schwung currently lets you run RNBO takeover concurrently with Move/Schwung tracks (and can control RNBO devices with the move sequencer). It doesn’t blow up but does add overhead!
And @rg01a schwung has skipback built in to Move too 
2 Likes
Yeah, each to their own - not for me from all I’ve seen, I think the balance of the stock OS is pretty great and don’t want to disturb it. For other synths or custom bits I’m much more comfortable with using RNBO full device takeover. The only thing that’s really tempted me is that I’ve seen reports of running Norns off the back of a Schwung install, but again would personally prefer a route that avoids that so happy to sit tight.
This one is RNBO but I think Schwung-adjacent - trying to hold tight on paying for devices right now as afaik they will all need to be updated whenever there’s a new release of the underlying RBNO alpha, but still pretty hard to resist.
Also gave this one a go, works pretty well: Async 4Track Looper for Move - RNBO Forum | Cycling '74
In terms of headroom, Ableton has said in previous AMAs that they stress test pretty comprehensively before introducing any new features, so while there may be headroom there’s a tradeoff in terms of possible loss stability / snappiness if you start to push things. The stock firmware has been pretty great for this, including betas, so again personally not inclined to rock the boat.
2 Likes
You’re not disturbing balance of Move OS by installing Schwung. It’s layer on top which you access by shortcut key combo. If you dont press combo it basically doesn’t exist. Move experience is 100% exactly the same as stock Move. You just get the option to press shortcut and have acces to dozen of additional synths and sequencing tools which you can resample back. But like you said, to each his own.
2 Likes
Yeah, that’s the thing - I don’t want a layer over the top of the stock OS. I would count that as interfering with its balance. Especially when I’m not inclined to use much if anything of what it offers - happy enough to trust Ableton’s judgment on how/whether any additional features fit with its overall design philosophy and their QC processes in terms of implementation. Not in any rush to see a bunch more features being added anyhow.
But if there is a way of installing Norns fully in parallel without touching the stock OS in any way I’d definitely want to take a look at that…
2 Likes
There’s not. It runs on top of Schwung so it’s not possible without installing that.
It’s not quite accurate of the other poster to say Schwung will definitely have zero impact if you don’t trigger it - it shouldn’t have any impact but it is definitely possible it could be buggy or whatever. Some element of it must always be running to intercept key presses etc.
The good news is you can follow DFU instructions to fully factory reset your device if you do try it and decide it isn’t for you!
I am the exact opposite of this. Not a knock on you benway, I very much believe to each their own. I just find it interesting.
Technically speaking, installing Norns alongside the stock OS is touching the stock OS, no? The OS is just a collection of processes running in Linux, and adding anything to run alongside it is modifying that collection. I think it’s probably worth noting that Schwung intentionally sits separate from the processes that make up the stock Move OS and only works alongside of those processes, rather than interfering with or modifying the processes that define the “stock” or unmodified Move OS. It was a wise choice by bobbyd (for move-anything) and charlesv (for taking that ball and running with it) and I bet it’s a contributing reason why Ableton is pretty laissez-faire about it (they also seem like curious and cool people…)
this is all to say that installing schwung and using norns as your only module is basically doing exactly what you describe as your only conceivable use case for modifying which processes are running on the Move. It runs entirely parallel to the Move OS.
also, sorry to the people who argued for splitting the schwung discussion into a different thread...
but I’d argue this is slightly more general/conceptual discussion around how we choose to use the Move.
going to pick up my MPC Sample later today and I already know I’m going to be wishing it was as open of a platform as the Ableton Move… we have it so good with Ableton. Open dialogue about feature requests and what the users want to see…
1 Like
Has anyone here tried Move with the latest Beta of Live 12 that allows individual track streaming of Move audio into Ableton channels? I have precious little hard drive space to install the Beta (my current first world problem) but I’m curious how seamlessly this works. I know there’s always Controller mode, but this seems like it would also be a great workflow.
1 Like
From further up thread:
1 Like
I’ve not been keeping up with the betas, resampling into an audio track still isn’t an option is it?
Also can someone ELI5 this whole RNBO thing?
I’ve never been a Max user, despite going into a PureData rabbit hole some years back.