JAH wrote:Is there something that a hardware MPC or another product (Maschine, Spark, etc) that can do in this regard that the MPC Ren/MPC Software can't?
It is nothing to do with any other MPC or other product, this isn't some competition that you have to make Akai win.
JAH wrote:There are some capabilities right under folks noses they haven't fully explored yet. I have You Tube Video(s) that show how to use the MPC Essentials plugin. If you master this plugin, it will solve the issue of needing more virtual outs and it will solve the issue of not having enough MIDI Outs.
The MPC Essentials plugin does not solve any issue of not having enough MIDI outs from the MPC Software plugin. It is another of your stupid workarounds that does not provide the same functionality as the missing features it is supposed to workaround.
Eyalc wrote:But all in all, Essentials doesn't "solve" the issue per se - because in the end the flagship software still doesn't handle these things, IMO, as it should. Although I agree that it's a plausible workaround. But I'm still not seeing the benefit of it like I said.
There is no benefit, it is one of his workaround smokescreens, trying to control discussion, trying to force others to accept his workarounds, so that other user feature requests do not affect the implementation of his own requests.
JAH wrote:While I submit as many feature requests as the next guy....
You submit your feature requests, and the next guys feature requests, and everyone else's requests, and they all seem to become your requests.
JAH wrote:you, me, we, etc will ultimately have to find a way to work within the way the MPC Software is designed. It will most likely never have all the features being discussed across these forums.
If there is never a way to record samples in sync in the standalone software, or more than a single MIDI port out of the plugin, then there really is no hope for the future of the product, and you have to wonder who the hell is making, and influencing, decisions there.
And no, everyone will have to find a way to work within the way MPC Software is developed, and we have to try and get our required features implemented before the development cycle finishes, so quit trying to shut down this sort of discussion with your pathetic workarounds.
JAH wrote:You can search You Tube for 'Jah Rome' and find videos that may or may not help you. But I can think of numerous work-arounds for many functions.
Your workarounds are just that, ways to work around broken/missing features, that really do not provide the required functionality.
JAH wrote:1. Treat your MPC Ren/Studio like a hardware MPC. The Ren/Studio on one computer and your DAW on another computer. Then use the exact same process hardware MPC owners use everyday to track their music.
Wow, the new MPC is so integrated into the computer, that you have to use 2 computers, and track from one to the other! Pathetic!
JAH wrote:2. Use MPC Software in standalone. Go as far as you can go with your project. Export as audio stems and complete your song in your DAW.
Great, have to lock in your composition as a single linear sequence and move it into a DAW when you want to record anything, can't continue working with chaining individual sequences, the way the MPC is designed to work! Pathetic!
JAH wrote:3. Compose with the MPC Essentials inside of your DAW. You have the option of using the MPC Essentials sequencer, your DAWs sequencer, or a combination of the two.
You can not take your MPC Software project, load it into multiple instances of the Essentials plugin, and keep working on the same project inside your DAW, with the same workflow as your project within MPC Software! Pathetic!