grid edit (audio) forthcoming os 4.5X

the more i think about it, the more i realize how possible an offline destructive version of ableton live's REALTIME TIMESTRETCHING wave warper is possible with some particularly brilliant coding

it wouldn't require a new type of timestretching, just the ability to timestretch bits of a sample rather than the whole thing - all it would be is stretching different sections by different BPM conversion ratios...

it's not essential to me but it could really change the way i work - i'd start using the audio tracks a HELL of a lot more. i'm such a control freak, which is why i never have a sample with more than 1 transient/note in it, everything is chopped note per note no matter how small the chops get. however, this grid audio thing has the potential of changing that.

TBonus76 wrote:
Heh... why does hearing Jahrome say that make me feel so warm inside? Has the mighty JJ actually humbled the stongly-opinionated Jahrome? I never thought I'd see the day!!

btw... props go to Jah on the new less-confrontational attitude... you turned over a new leaf for sure man. I noticed you toned it down man... good job... a lot less drama lately. Nice job.

This was never about me vs JJ

I am an MPC-head. Of course I will challenge any programmer to improve the MPCs operating system..Akai/JJ/Roger Linn/Rohan....whoever. But I have still reserved some of my praises. We are still just 5 days removed from the last bug fixes (that were not there before). And with the additon of a new functions that will be added during the next OS release, there will most likely be more bug fixes to come. So we will see....

As far as being confrontational, I haven't changed at all. As long as catz don't talk out their azzes...I am cool


Regarding realtime timestretching, Akai/JJ can just add this function to the INPUT THRU like the realtime pitchshifting. While this isn't like Ableton, its a start. Akai/JJ should be able to easily add timestretching in these current MPCs (if the hardware/software can support this) or future MPCs. This technology has been around for some time now and practically all software DAWs has this function.

realtime timestretching wouldn't work on a live input. otherwise, if you were to put the speed all the way up, you'd be able to hear into the future. and that's a whole different ball game. i can imagine the newbie questions now: 'i found out with the time-machine function on my 1000 that my wife/girlfriend/partner is going to cheat on me, should i shoot them?'

Mr modnaR wrote:you'd be able to hear into the future.

Lol... I was thinking that too... no way to speed it up... and you'd need some kind of way to buffer it if you were going to slow it down.... pretty useless.

imagine being able to move warp points via qlinks or data wheel in grid edit...hit apply/create new sample...boom, your sample is timestretched and copied, so the original is still there if you want it.

Mr modnaR wrote:
realtime timestretching wouldn't work on a live input. otherwise, if you were to put the speed all the way up, you'd be able to hear into the future.

The incoming audio will be processed by the MPC and that audio would be routed to the MPC's audio outputs.

How would you be able to hear into the future?

What if you are speeding up the sample... He's saying that if you speed it up, how can the processed sample be playing faster then the original if you are doing it in realtime... the processed version would get ahead of the original.... it's impossible... thus the "hearing into the future" thing.

The original audio source is not being sped up and will remain at a certain tempo. The MPC receives and processes this audio and play it back according to the tempo you have set on the input through page. What you will be hearing from the audio outputs would be a latent audio signal. The faster you increase the tempo, the more latency will be involved.

that's a lot different than the existing realtime pitch shift...there'd be lots and lots of latency involved in playing a sample off a record that's about 120 bpm and "realtime" timestretching it to play at 180. what would be the point? wouldn't it be better to be actually in the sequencer/effects rather than another realtime X shift thing for input thru? also, if i remember realtime pitch shift turns off after five minutes because it's such a resource hog...a real gimmicky feature that dont find myself using for anything other than a parlor trick

Of course having it in the sequencer would be better. Expanding realtime pitch shift to include samples already in memory would be better as well. But I was just talking about programmers making baby steps.

Realtime time stretch initially turned off after 5 minutes. I haven't used it that much but believe the 5 minute limit has been removed. Realtime sample manipulation isn't gimmicky...Features like Ping-pong, and Splash Screens are more gimmicky than anything else.

oh cool, i wonder how he went about securing it beyond the 5 minute limit
no i thought you would have preferred applying "realtime" time stretch to input thru as opposed to in the sequencer...

pong and splash screens are def gimmicky, but i'd still have to say realtime pitch shift is as well. especially compared to recordable realtime sample manipulation like automatable levels, filter, resonance, etc. especially since we already have tune, although it does change the sample's tempo as you detune it.

unless the movement of the realtime pitch shift could be recorded into the sequence. as it exists now, applied only to input thru, it's cool n all but i dont see many uses for it other than making funny super pitched sounds. at least we know such stuff is possible though, which means that a possibility for the timestretch i described previously exists...

in terms of bogging down the resources though, i'd still have to say it should be a semi destructive (ie applied to a copy of the old sample) effect so it's not really "realtime," just an offline emulation of ableton's wave warper.

I would much rather have the realtime timestrteching done within a sequence, Also, if I had to choose, I would much rather have a form of realtime timestretching than realtime pitchshifting. However, both of these functions are useful for sampling producers. And because tuning samples changes the tempo, the added feature of pitch shifting in real time is a major improvement.

nice to see jj updating the direct audio in feature. this should be really cool. 8-12 bit sampling is unneccessary though.

jahrome wrote:faster you increase the tempo, the more latency will be involved.

Exactly, that's why it wouldn't really be "realtime".

rabulisten wrote:nice to see jj updating the direct audio in feature. this should be really cool. 8-12 bit sampling is unneccessary though.

Awwwwwhh!!!! come on! I know if you have a daw blah, blah, blah.... "you can change the bit rate on blah, blah, blah, and then sample it back."


The real point of this feature is for samplists who DONT WANT TO USE THEIR COMPUTERS. Or anything else for that matter.


Just the MPC 1000, some turntables, and some dirty a$$ scratched the F'K up records.



I guess that i love lo-fi a helluva lot!

But still all props go to jj for buffing up our MPC's.

The 8 to 12 bit resampling feature would be the last thing i personally would request... anything else after that would be icing!