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.
By Spoff77 Sat Oct 11, 2014 3:37 am
[quote="pituchez"]wtf is plugin delay compensation![/quote]


What I am referring to is that if you use some plug-ins, especially things like good third-party compressors, limiters, etc the sound or track you put the plug-in on will be delayed compared to how it hits right now. So if you put one of these effects on a snare your snare will be delayed compared to the rest of the sounds, and thus be out of time with the rest of your sounds. This is bad. While this can be corrected by shifting the sound or track with the plug-in earlier in the mix, it is time consuming and not realistic when some of the sounds start right at 1/1/000. Not having this feature makes using things like a lot of the UAD plug-ins difficult.

Luckily most plug-ins report the amount of ms delay they add to the OS, so a program can sync things back up automatically. They also make it so that if you record a new track or sound to a sequence that has delay compensation on it already it will shift what you recorded the right amount so that it is completely aligned with the sequence you were listening to while you recorded. In other words if what you were listening to from the MPC while you recorded was delayed by 40 milliseconds, it then puts what you recorded 40 milliseconds later. Then when things are bounced down to disk it starts things off at the beginning as it doesn't need to delay when doing a bounce.


Spoff
By Spoff77 Sat Oct 11, 2014 1:57 pm
I would also pay for some drum modeling like that in Machine 2.0. Although if something like this would tear them away from more basic MPC workflow things (i.e. if they didn't hire someone else to work on this) I would rather keep seeing workflow improvements.
User avatar
By BDRAKE Sat Oct 11, 2014 3:54 pm
Spoff77 wrote:I would also pay for some drum modeling like that in Machine 2.0. Although if something like this would tear them away from more basic MPC workflow things (i.e. if they didn't hire someone else to work on this) I would rather keep seeing workflow improvements.


I think drum modeling is an excellent Idea. :nod:
I would welcome that. I would'nt have to do it in another application. I mean it is drum related and I don't think that strays from what the Ren is meant to do.
By mcroepster Sat Oct 11, 2014 6:07 pm
SimonInAustralia wrote:
pituchez wrote:wtf is plugin delay compensation!

wtf is Google!

wtf is researching shit yourself!

:Sigh:


+1

peace :smoker:
By Nubian Mindz Mon Oct 13, 2014 12:45 pm
BDRAKE wrote:
Spoff77 wrote:I would also pay for some drum modeling like that in Machine 2.0. Although if something like this would tear them away from more basic MPC workflow things (i.e. if they didn't hire someone else to work on this) I would rather keep seeing workflow improvements.


I think drum modeling is an excellent Idea. :nod:
I would welcome that. I would'nt have to do it in another application. I mean it is drum related and I don't think that strays from what the Ren is meant to do.


Yes! :nod:
By dazastah Tue Oct 14, 2014 11:17 am
I'd prefer more features built into the sampler engine over a drum synth engine.. Like a pitch envelope, velocity effecting decay/sustain(soft hit shortens decay), Pretty much the drum synth features that are in a drum synth, but you can just use them on your existing drum samples.. Would be much more flexible, even on non drum samples...
By dutch Mon Nov 03, 2014 9:27 pm
1.Audio to midi
2.Drag and drop midi files
3.Midi batch import
4.Full external midi control
5.Rewire