OS2 - Using outputs as Sends - pretty please JJ

Actually it can be used in combination with an external mixer, which is what I'd do, but it can also reduce the need for one.

definitely let jj know about this. it's a good request and shouldn't be too hard to implement. he might not be able to get to it right away but i'm sure he could get to it eventually.

Awesome Idea!

if your snare pad doesn't use velocity layers you could try duplicating the snare sample to a different layer on the same pad and simply route that layer to an aux out.

In other words:

Pad ---> Fat Snare

Layer 01 - Fat Snare ---> MPC Out 1-2 (Dry sound)
Layer 02 - Fat Snare ---> MPC Out 3-4 ---> Reverb unit (Processed sound)

The volume of the second layer becomes an "FX send", so you can control the amount of reverb applied to the sound.

only 10 outs..... snare can be mono !

lcvl wrote:if your snare pad doesn't use velocity layers you could try duplicating the snare sample to a different layer on the same pad and simply route that layer to an aux out.

In other words:

Pad ---> Fat Snare

Layer 01 - Fat Snare ---> MPC Out 1-2 (Dry sound)
Layer 02 - Fat Snare ---> MPC Out 3-4 ---> Reverb unit (Processed sound)

The volume of the second layer becomes an "FX send", so you can control the amount of reverb applied to the sound.

Ok, 2 things:

1. Is routing layers to separate outs a new thing in OS2? You can't do it in OS1.

2. I could use Simult Pad in a similar way, but it's not very elegant. If I change my snare sound I have to remember to change it somewhere else.

2. I could use Simult Pad in a similar way, but it's not very elegant. If I change my snare sound I have to remember to change it somewhere else.

you'd have to change it 'else even if it was just on a different layer
but here's the easiest way to use simult w/out forgetting where your layers are: if your snare is on A14, put your simulted layer on B14. that way it's the same pad, just hit a different pad bank. this is acceptably elegant IMO

great idea!!

Nym wrote:you'd have to change it 'else even if it was just on a different layer but here's the easiest way to use simult w/out forgetting where your layers are: if your snare is on A14, put your simulted layer on B14. that way it's the same pad, just hit a different pad bank. this is acceptably elegant IMO

Up to a point. It's ok as a workaround if you just want the occasional pad sending to an external device But if you want a whole program then it's just not practical to use Simult. My suggestion would work in all instances, and it doesn't compromise the current layout or functions in any way.

your solution was different layer-different routing, right?

what i've been dreaming about recently is a function for "simult program"
where essentially you chain 2 programs together, same midi notes go to both and trigger the same pads, same qlink data etc

a mini combinator from reason

Nym wrote:your solution was different layer-different routing, right?

No, that was someone else. Re-read the first post.

For production purposes the fx are definitely a little ropey, but for live use i think they're ok . Up until Qlink>in thru was removed it was pretty cool to hook my turntables to the mpc for filtering too. (please bring this back with the ability to record it onto a track!)

Rozzers idea is a good way to improve the flow for external fx and one which i support to the hilt.
I do think it'd be cool to have a little more flexibilty for the internal ones too. e.g. wet/dry mix on the reverbs and independent fx sends and filter for input thru left and right.
Out of all the MPC's the 1000 is the live MPC because of its portability.The MIDI in stuff thats on its way will improve this somewhat further. I might be in the minority but id like him to tweak these workflow aspects of the internal fx and in thru features a little.

Rozzers right though, his suggestion seems both simple and very useful.

My suggestion would work in all instances, and it doesn't compromise the current layout or functions in any way.

...by the way just got my new pads ten minutes ago!

http://www.mpc-forums.com/viewtopic.php ... hlight=emu

your solution was different layer-different routing, right?

what i've been dreaming about recently is a function for "simult program"
where essentially you chain 2 programs together, same midi notes go to both and trigger the same pads, same qlink data etc

a mini combinator from reason

You didn't dream it! you nicked it from me and i nicked it from emu.haha just kidding .
Now we just need to get JJ to steal this idea too cause it'd be awesome.

Im thinking that inst program velocity ranges could be easily implemented with this feature too: Imagine each program has a global velocity response range e.g. prog 1:64-127 and prog 2: 0-63.Link em together and hey presto you have keygroups and velocity ranges.
off course linking programs with totally different sample,filters,adsr woul'd be amazing for designing sounds.

(sorry that im taking this off topic..but this'd be immense)