Kaiju wrote:Thanks so much. I have looked low and high for most of those answers. I'm sure the Manual will bring me up to date fast. Googled everything, watched all the vids on YouTube. Still only found super basic stuff.
Happy to help. And you are right, it's really hard to find the information you need sometimes.
Yeah, the zoom is a problem at least in my computer for now. I guess I can get used to using it.
Are you talking about how cluttered and smashed all the elements are on the screen? If that is the case you can disable certain modules in order to give you more real estate to work. For example, you can turn off the inspector on the bottom left and the file/midi browser on the bottom right to give yourself a lot more screen real estate.
When I'm chopping samples and I go to other window and I come back to that window the sample is deselected. There are a lot of minor issues that I find are crucial for a fast work flow.
I don't 100% understand all the details involved in that exact situation but....
I'm 100% certain that you can make this work the way that you want it to.
There's some other stuff like knowing at which DB's my channel is hitting. I can do that by ear, but when I need surgical precision it's a problem. Stuff like that.
If you click on the inspector icon on the bottom left, it should bring up a program and output channel strip with levels. If you have a second monitor, you can even see levels for every pad, program, track, and send in your project by clicking mixer window on the bottom left.
I'm guessing the manual will have most of the answers, or I just will get used to how the Software works. In my book the MPC1000 it's flawless. Fast workflow, everything makes sense, it has buttons to change sequences so I can hit them 3 times and know I changed up 3 sequences, stuff like, 2 midi ins and out, 4 (?) outs, stuff like that.
To be fair, I'm sure there was a learning curve with the MPC1000 just as there will be with this software. I also
think that the software allows for much more functionality. Thus more possibilities and problems along with it.
Also the workflow example you mentioned is applicable to the Beats software as well. You can assign buttons on your midi controller to change your sequence.
I know AKAI it's not really about Hip Hop anymore and I have heard complaints about its users that they don't listen to their requests, specially since the Ren came out.
I don't have a dog in that fight, but I'll comment on something that I have observed. I don't think "users" know what they want. If Akai fulfilled every request that was made, they would spend half of their time adding features that are already in the software.
I just have noticed though reading a lot of user comments and posts, that I wouldn't want the internet at large determining what Akai should be fixing or working on. This doesn't mean however, that there aren't some people out there with really good suggestions, because I have seen that too.
There's some stuff that it's not working too well with my Akai MPD32 controller, a matter of calibration, so I'm hoping the Manual has some info on that. I have it mapped, so when I scroll thru the Sequences they scroll super fast, barely touching the fader and they scroll from first to last in one go. Maybe I can calibrate it with the MPD32 software, like limiting the 0-127 cc mesages to 0-64. IDK.
This is a barrier for a lot of people. There are a lot of ways to get your midi controller to interact with the software, so the developer can't just offer you a template that's going to work with your MPD32 even if it's the same manufacturer. Users can configure the software correctly, they way they want, but miss something important the hardware configuration and it doesn't work as expected, or vice versa. I see it causing a lot of troubleshooting issues online.
Do you have your faders mapped to the Q-links? I prefer not mapping controls to Q-links, but sometimes you have to. They work best when mapped to encoders, but sometimes you don't have that option. When mapping some controls to faders or knobs with limits you end up with crappy resolution. This is true for controls with a wide range of values. And example would be Sequence length in Bars, or Sequence Tempo. The 128 values that your fader or knob can send, aren't good for controlling a parameter with 1000 settings.
But I need a hands of the computer and off the mouse experience. All hands on the MPC it's what I like. I love the sound of the MPC1000 and those before it. Not really a fan of touch screens either, but I could give the MPC Live 2 a go.
I feel you on this point. I hate using the mouse too. So I don't.
I don't have an MPC Live. But i'll say that if you don't get along with the software and aren't keen on touch screens, getting the Live isn't going to be a huge improvement.
I think they would sell a lot more units if they just made a faster and improved MPC1000. Taking in account all the mods that are out there. Make em with super fast loading times, XL screen with better resolution, not for pretty pictures for the Drum Programs, that's distracting. Something closely resembling JJOS. Fat or cork pads, and all the modern ins and outs the new ones have. USB ans SD slots. Two midi ins and outs, six audio aux outs. A serious profesional unit. For my taste the new layout it's not working. It's like pushed to the side, feels weird. I have a long list of stuff that I don't like in the new MPC's lol. I don't mind at all the quirks and "personalities" that all music software's and hardware's have, but some are really difficult to ignore and work with, not talking specifically about the new AKAI's.
Well, that's just my take on it. I'm trying to be constructive, I spend all day and most of the night, most of the days with these machines, others, instruments and music software's non stop since long ago.
I think the takeaway is that someone has to put in the work. The best example I can think of is a project template. A user can create a project template that is setup to do exactly what they want, the way they want it done, with the hardware they have. They can end up writing dozens of songs using this template.
The bulk of the work might be spending 200 hours creating and refining that template. To some people that isn't what making music is about. It might turn them off completely. But for some people (and I think I'm one of those people) figuring out a way to get things to work they way you want, or get them to work in a unique way, is a large part of the music creation process.
But there are lot of people who would rather have a framework like this created for them, which is totally a valid perspective. It's just difficult to create such a framework that's going to appeal to everyone. So things get left "open" for more flexibility.
We can help each other out though and that's how you get a more improved unified experience. It's one of the reasons that older hardware is held is higher regard sometimes while being less capable.