Timestretch Instability ?

Just found some time to start to hammer the 2500...

Ive had 6 or 7 crashes (mainly complete lockups, a couple of times screen garbled, but luckily still able to save) in the last 24 hours when using the timetretch in trim->edit mode.

not had a single lockup until ive started to use the TS.

anyone else seeing this ?

in fact it seems to be reproducible every time i try and use overwrite after the timestretch.

i'll try with some diff sounds later...

i had a crash too when i tried the timestrech function - haven´t done it since then cause i prepare the samples on the mac first...

using the time stretch on the 1k has not given me the same problems you have. it's the same feature (built and written the same as the 2.5k) i tried to overwrite after stretching and still was not able to reproduce the problem. i have to see what's up.

how long are u waiting after u timestretch or cancel because it can take a while depending on the size of the sample

If you need help trouble shooting this problem, you need to give more details.

1. The size/tempo of the sample
2. Time stretch settings
3. Memory size/brand

jahrome wrote:If you need help trouble shooting this problem, you need to give more details.

1. The size/tempo of the sample
2. Time stretch settings
3. Memory size/brand

thanks jahrome, i work in software, so know the procs when it comes to bug reporting - was just an initial post to see if it was a known problem - save myself the trouble of writing all the following

its reproducible nearly every time with this unit, and this particular sample. other samples seem to cause no problem (not entirely true as it has happened with other samples, but infrequently)

its not something im doing wrong. the timestretch itself works fine, and i can hit PLAY and audition it. Its when I try to select overwrite that the problem occurs.
I just did it again and it didnt freeze but the screen became garbled:



clicking EDIT on that screen gets this:



I can go back to MAIN and continue working no problem, but at this point ive been saving to a new folder and rebooting the machine, out of precaution. Far more irritating (and unfortunately more regular) is the complete lock up....

> Memory - standard 16mb
> Sample is approx 200,00 samples in length, stereo, sampled directly into the unit
> Time stretch settings have mainly been LF Orch C, but has happened with other settings too
> Original tempo set to 94, new tempo 83, but again, has happened with other settings.

just had a crash in song mode too, whilst deleting a sequence...

Man I hate to jump the gun but I was having a problem like this too. Which turned out to be a bum unit.

I was getting the same screen when I went to save.

Do you have a HD in the there? My HD wouldnt show up half the time as well and when I went to save to it bam, I would get that screen. Plus it eventually started doing that all the time. I got a new unit to replace the old one.

You may want to call akai or the place you bought it from.

Aprim

Thanks for the heads up.

I do have a HD in there, but have had no probloems whatsoever with it, or any of the disk operations.

Will keep monitoring it and if it propagates to areas other than where Ive seen it so far I'll get it replaced.

Im hoping a firmware upgrade could address some glitches like this..

Looks like a software bug to me, those screens remind me a bug in the 1k back on os 1.0.4
There was an issue with trimming mono samples and if you pushed it too far the screen would scramble like that.

subvertbeats,

When re-producing this problem, are you close to maxing out the MPC 2500s memory? How long is sample (in terms of time)?

Also, is this sample 16 bit and is it a sampled at 44.1 Khz?

hi jahrome.

> sampled directly into the mpc, 16bit 44.1
> sample around 1 second in length
> memory in use around 10mb of 16

thanks

subvertbeats wrote:
hi jahrome.

> sampled directly into the mpc, 16bit 44.1
> sample around 1 second in length
> memory in use around 10mb of 16

thanks

Confirmed

I can reproduce a similar 'bug' 90% of the time. When attemtping to time stretch samples 1 sec in lenghth and shorter can cause your MPC 2500 to crash. I didn't get the exact results you did, but doing this cause my MPC 2500 to shut down and reboot.

Also, if you attempt to edit samples when you are close to maxing out the MPC 2500s memory will cause the MPC to crash as well.

damn, well whilst its not ideal, its a better result than having a defective unit

Im sure the upgrade is just around the corner anyway.

thanks for putting the time in to investigate this, have a good xmas bro...

No problem. I just wish Akai steps up and give us an OS update to fix these issues. Its been 3 months since the release and in the past, there have usually been at least 1 OS update within the first couple of months of an MPC release.