I’ve hit a major software bug using it in controller mode. It can only move in odd numbers. Like I can only get track 1,3,5,7,9 or the same with sequences. Happens with the big knob and the q links. Don’t know what causes it but it’s happened more than once doing very little. Like almost fresh out of a new project
Same here.
I much prefer standalone. Faster and fun.
If I’m gonna use it as a controller, my PC is way more powerful than any Flattened iPhone.
Getting a standalone device and using it as a controller defeats the purpose.
You can make crazy good music on any setup, at the end of the day.
Your mixing up the conversations…
Easy to do, I know.
I don’t think anyone said about using their phone as a controller, that was meant instead of using an iPad as a sound source.
Computer as a controller to minimise cables was separate… and valid.
I like the flexibility of being able to do both.
I’m in the middle of midi mapping 2 controllers to a project template… and I’ve found just using the MPC software with the controllers attached is really straight forward, and I don’t have the physical MPC attached at all.
My new MBP has an SD card slot again (woohoo!!!), so it’s super simple to go between the laptop and the MPC.
Preliminary work is on the laptop so I can do the live performance work just with the MPC.
Yeah, sticking with 2.10 here for the time being
Yep!
Seeing a lot of posts about other device workflows without MPCs in a MPC thread.
Easy to mixup for sure😂
Some noodling with the Tube Synth and Flavor
Lost in all the whining about paid Instruments is the fact that Air Flavor is amazing and very usable
There are some serious sample chopping glitches that have been popping up on me since updating to 2.11. Like one of them is where it will just put a chop in some random place when I start chopping. And a lot of other glitches off and on like chops disappearing or moving around, the play marker in all sorts of random locations, it’s saying samples are assigned to programs they are not, etc. So this means purge is also getting rid of samples that are in use and keeping unused ones and other bizarre stuff. A real mess. Rolled back to 2.10 and everything is fine, so it is definitely the update.
Edit: Looks like I’m not the only one having some of these issues: https://youtu.be/SCuTUM3Acl4?t=143
I haven’t updated yet, let that thing bake a bit
One of the new features was that the play head can be modulated/automated so this (bug) may be a result of those changes?
That’s a pretty cool feature though.
It will be once it is fully baked ;-P. I use the MPC because it is the best at chopping so these issues are a real bummer for me atm.
it’ll get there, even on the previous os it was still the best chopper
Does anyone have experience with the Pioneer Toraiz SP-16?
I’m interested in how it compares to the MPC. It looks like it sits directly in between the Roland TR sequence approach and the MPC.
I’m not interested in swapping my MPC for a Toraiz, but it looks like it could replace some of my Roland gear.
Does anyone else have issues with Note On having no effect on the new update? Or am I missing a something?
When hitting a pad, it plays like a one shot…
that’s it!
I noticed this issue when using MPC software as a plugin in Bitwig, I’m working on Kit Creation/conversion software and so thought it was my code at first, in standalone software it works normally. I haven’t updated my hardware yet.
Okey. That’s strange… I’m in standalone on the latest firmware. I don’t use controller mode, and never ran in to this before.
Working fine in 2.11.2 for me - started from a blank project, set the track to kit, loaded a sample to pad 1 and changed to Note On. Works as expected - plays for as long as the pad is pressed. Definitely not a case of the release value being high on your envelope page?