Bug reports & end-user support for Akai's MPC Software 'controllers' including the new MPC Studio 2, the MPC Touch, MPC Renaissance & original MPC Studio and MPC StudioB lack.
User avatar
By Rokgod Mon Sep 24, 2012 12:04 am
ceasi wrote:You people are fckn unbeliveable. Stick to maschine, or your 4k. Like I said, some don't deserve the Ren, because no matter what it can do, all you hear about is what it can't do. I've never known anyone to record all of their sounds on 1 track, people who use DAW's to make beats don't even put all of their drum sounds/samples on 1 track. Thats just stupid.


I think the Ren can tell when a maschine user touches it lol, causing it to crash lmao. I wouldn't be surprised. Seems like 75 percent of these people with all the problems are former Maschine users with little mpc experience, or little production experience for that matter if they trying to fit all this different data/sounds on 1 single track and plan to bounce out sounds as if they are separate tracks :lol:

ok, look guys, kick on track 1, snares on track 2, hats on track 3, samples on tracks 4, 5, 6, 7, and plugins/vsts on tracks 8, 9, 19, 11, and 12, thats leaves you with what? 100 something more tracks to play with lol
By mcroepster Mon Sep 24, 2012 12:04 am
Ill-Green wrote:I make tracks on one track. But thats because I'm a ninja and know what the **** I'm doing. Feels good owning an MV right now.


:hmmm: :lol: :lol: :lol:

MV is def cool.:nod:

peace :smoker:
User avatar
By ceasi Mon Sep 24, 2012 12:12 am
InspectahEX wrote:
ceasi wrote:You people are fckn unbeliveable. Stick to maschine, or your 4k. Like I said, some don't deserve the Ren, because no matter what it can do, all you hear about is what it can't do. I've never known anyone to record all of their sounds on 1 track, people who use DAW's to make beats don't even put all of their drum sounds/samples on 1 track. Thats just stupid.


I think the Ren can tell when a maschine user touches it lol, causing it to crash lmao. I wouldn't be surprised. Seems like 75 percent of these people with all the problems are former Maschine users with little mpc experience, or little production experience for that matter if they trying to fit all this different data/sounds on 1 single track and plan to bounce out sounds as if they are separate tracks :lol:

ok, look guys, kick on track 1, snares on track 2, hats on track 3, samples on tracks 4, 5, 6, 7, and plugins/vsts on tracks 8, 9, 19, 11, and 12, thats leaves you with what? 100 something more tracks to play with lol


:nod:
User avatar
By Dee-J Mon Sep 24, 2012 12:18 am
InspectahEX wrote:
ceasi wrote:You people are fckn unbeliveable. Stick to maschine, or your 4k. Like I said, some don't deserve the Ren, because no matter what it can do, all you hear about is what it can't do. I've never known anyone to record all of their sounds on 1 track, people who use DAW's to make beats don't even put all of their drum sounds/samples on 1 track. Thats just stupid.


I think the Ren can tell when a maschine user touches it lol, causing it to crash lmao. I wouldn't be surprised. Seems like 75 percent of these people with all the problems are former Maschine users with little mpc experience, or little production experience for that matter if they trying to fit all this different data/sounds on 1 single track and plan to bounce out sounds as if they are separate tracks :lol:

ok, look guys, kick on track 1, snares on track 2, hats on track 3, samples on tracks 4, 5, 6, 7, and plugins/vsts on tracks 8, 9, 19, 11, and 12, thats leaves you with what? 100 something more tracks to play with lol



That's still not good enough.....People will still complain :lol:
By bobbybland Mon Sep 24, 2012 1:00 am
Just curious how do you guys track when using something like toontrack in a daw, does it even occur that you can actually use just one midi track and then use the split midi events feature, or do you create 16 midi tracks?

Inexperience lol have you owned the 4k? Or did you even know that it had the feature? :mrgreen:

Funny how some can talk, but not even understand there are actually faster ways to do things. :roll:

Maschine users? How about daw users,that have brains and decide it's faster to work in one vs an ancient outdated technology :fku:

Don't hate on the request to make the mpc work better,then it's current design
By TT_Lab Mon Sep 24, 2012 1:35 am
Hey bobbybland did you even think that some of us would prefer what do you call an outpdated workflow? Actually I sold my maschine for buying the ren cos the mpc tracking workflow seems more intuitive for me...I do beats faster with my mpc1k workflow than with my maschine....just throwing my 2 cents here.
Cheers
User avatar
By JAH Mon Sep 24, 2012 1:46 am
bobbybland wrote:Inexperience lol have you owned the 4k? Or did you even know that it had the feature? :mrgreen:

Are you sure?

The MPC 4000 has a feature to separate a track into 16 tracks by MIDI channel. But if I have a drum kit loaded and recorded all the sounds on 1 track, this function is not splitting my sounds into their own track....unless I am missing something.
User avatar
By Lampdog Mon Sep 24, 2012 2:32 am
JAH wrote:unless I am missing something.

Nope, ur not missing anything. Placing all sounds on one track is unconventional, you know that already.

Seems as though bobby is used to an unconventional way of working and nothing is wrong with that at all.

There are no rules.

To say something sucks because it doesn't conform to an unconventional way of working is not the business, not realizing that your workflow maybe or is unconventional, possible ego fail.

People say "old workflow" well how old is midi? Really old and the spec hasn't changed in decades, so that "old" point holds no water. Some things don't change, much or at all, while many others do. (how many people make banger better than you and they still use mpc 60's, you'll never know because the network is down.

Adapt, or adapt and salt to taste..
User avatar
By ceasi Mon Sep 24, 2012 3:15 am
TT_Lab wrote:Hey bobbybland did you even think that some of us would prefer what you call an out dated workflow? The mpc tracking workflow seems more intuitive for me...


Bobbybland your work flow is not used by many, and I agree its unconventional to the MPC way of doing things, some don't mind recording there kick, snare and even their high hat together, then copying and deleting, it doesn't hinder the WORK FLOW at all. Besides I'm not into making 15 min beats, all the good ones take time, this work flow argument is being confused with work speed. To me work flow is the way something works, the process you go thru to get from A to B. Like copying sequences, editing them, then putting them in the form of a song, as opposed to patterns and scenes and groups, I prefer Programs over groups any day. Im just SMH at this guy.
By bobbybland Mon Sep 24, 2012 3:32 am
You make a valid point, but to me it's still slow.Too slow, but hopefully akai can see others will want a faster option. Just because a few heads don't get it, doesn't mean that others won't.. fwiw it's software, it can be written into the code n I don't see why it's not.
User avatar
By Blue Haze Mon Sep 24, 2012 3:52 am
bobbybland wrote:
JAH wrote:
bobbybland wrote:Well Currently if I have a program, and I use 16 sounds in it, I sequence 16 sounds in a sequence, I then go to mixdown the tracks separately, I change the outputs to different outs, , there's a problem ,I can't get anything other then a single wave file for the entire sequence and .pgm, so this is a major problem, which will probably make me RETURN the MPC. As this is a complete workflow killer.

I'd say this constitute's a major flaw in the current OS. To not compare the ren software to Maschine is pretty far fetched and it's gonna happen daily, for the rest of the lives of the products.Just saying, when a features good, perhaps the opposing team should run with it,if it works better.


Dan, is wrong if he thinks this isn't a major flaw.

That doesn't sound right...

1. Load a program with 16 sounds
2. Assign these program to 16 tracks
3. Record 1 sound per track
4. Go to Export and check the 'Render Separate Tracks'

You don't get 16 tracks of audio?


We're off to a bad start here, I'll explain..
MPC REN
1. Load program with 16 sounds - YES
2. Assign the program to 16 tracks <--- Are you kidding me? Why would I wanna do that? Other then the fact, that it's the only current way that Akai see's this fit...

Let me refresh my workflow with Maschine...

1. Load a program with 16 sounds..
2. Mixdown every sound from one track!!! <<<--- Notice no need to create 16 tracks!!! Does that make the workflow easier? Yeah it does, and this is apparently where Akai doesn't get the term workflow.. :roll:

And #3.on the akai mpc ren workflow, Seriously?? Like I'm really gonna wanna track drums like this, record a kick track 1, record a snare track 2..Cymbal on track 3..

Not sure who in the world even tracks like this, but I bring up a kit, and record one .pgm all on one track.. Kick snare, Hats etc.. I never in my life would load up 16 different tracks for a realtime drum performance, not to mention chops and stabs..

That's just ridiculous



This is a big misunderstanding on maschine and mpc. Maschine's pattern is what MPC calls a sequence. All of maschines sounds are assigned to a track in the pattern. On the MPC the user can assign the sample aka midi note to a single track or multiple tracks free choice; whereas the Maschine this is automatically set up as multiple tracks. So in essence when you export the tracks in Maschine it is the same as the Ren a sound is assigned to a track. There are no single tracks with multiple sounds in maschine except instruments. Group in Maschine is equal to program in mpc when it comes to drums. Thus we drag out patterns aka sequences on the maschine with each sound be it a drum kick, snare, hi hat or bass riff assigned to a track in that pattern the same as Ren does export or logic bouncing midi to audio for export!


And another thing is that it is important to define export files and assigning outputs cuz some are getting it twisted.

Both maschine, mpcs, logic you named it allows for sound, pad, zone whatever you call it to be assigned to an individual output. Each output has to be assigned to a aux track in a daw for the audio to be mixed in the daw. But aux tracks don't record the audio until you bounce down the whole thing in logic pro. And aux tracks don't record or output midi data either. Aux tracks are essentially returns in a mixer,they are not multitracks in a records so it is asking for the impossible.


Second exports tracks is just that a bounced midi region that was assigned to a track changed into audio stems. All daws have the same function you can make a midi region on a track, separate the notes to tracks, like 8 or 10 fot drum programming, then select all to bounce the tracks to audio and export will take the audio stems outside your project, sequence, or whatever you call it saved to your desktop or external drive. So you can load it up in another daw or multitracker that has audio tracks. Line them up and mix.

Now if you want to send the tracks off to another studio this is good or a joint project this is idea to export tracks. But if you are working another and using maschine or Ren as a plugins it is simple and easy to just assign the sound aka pad to an output and that output to an aux track.

As for as midi simply save the pattern aka sequence drag or import to the daw and on logic pro hit separate note to track. But if mpc grooves better than logic why bring the midi region into logic in the first place?
Last edited by Blue Haze on Mon Sep 24, 2012 4:54 am, edited 1 time in total.
User avatar
By JAH Mon Sep 24, 2012 4:16 am
Exporting is what you would do when taking MPC material to import into another environment aka DAW. Exporting has absolutely nothing do to with the workflow and speed of creating music inside of an MPC. And this is what surprises me. We are talking about leaving the MPC environment. This is something, I believe, most people would do once. Typical MPCs users don't start creating tracks and then pause to export just to continue working on tracks inside of an MPC. I don't even believe Maschine users work this way.

Maschine users drag-n-drop and export audio to take this material to an environment where they can actually mix as Maschine does not have anything remotely close to an actual mixer. The Ren doesn't have this limitation. It can create complex mixes with automation onboard. And that is how I see the Ren....a self-contained MPC DAW. And at the end of this process, if I need to import it into a DAW and separate tracks are needed for my drums, it takes very little time to do that.

Continued discussion on this is pointless. Unless Dan sees this thread and comments he will ensure that Rendering Audio at the Program level is added, your chances to see this in 1.1 are slim.

...Also....like all the other feature requests written in this forum...its already been submitted to Akai....

Peace

J