OS 2x - JOYS AND PAINS thread PT1

wtf is happening? i got this message and my mpc froze when i was messing with the LFO's..

Is this happened to anyone else?

One more annoying thing i have noticed; the trim-page is weird slow when i'm editing some long samples...

laban wrote:
One more annoying thing i have noticed; the trim-page is weird slow when i'm editing some long samples...

Yeah, I noticed that too.... especialy when I'm messin with slices... it's kinda sluggish, but not so much that it messes me up. It's all good though, I'm LOVIN this o.s.

since installing 2.0 , ive been having a problem whereas when i try to sample my record button(f6) is not working, sometimes i have to go back to main window or just reboot mpc altogether, was wondering if anyone else was having this problem.

TBonus76 wrote:

laban wrote:
One more annoying thing i have noticed; the trim-page is weird slow when i'm editing some long samples...

Yeah, I noticed that too.... especialy when I'm messin with slices... it's kinda sluggish, but not so much that it messes me up. It's all good though, I'm LOVIN this o.s.

same problem here...
It would also have been nice, if akai added some "next/previous slice" shortcuts on f2/f3 in slice mode...

laban wrote:

wtf is happening? i got this message and my mpc froze when i was messing with the LFO's..

Is this happened to anyone else?

One more annoying thing i have noticed; the trim-page is weird slow when i'm editing some long samples...

m8 that 'cpu address error' was what was happening wiv my **** up mpc. how often does it do it? still dont know what causes, but might be overheating? i let u know when i get my mpc back from its servicing

littlerob wrote:m8 that 'cpu address error' was what was happening wiv my **** up mpc. how often does it do it? still dont know what causes, but might be overheating? i let u know when i get my mpc back from its servicing

Rob, that CPU screen could mean all type of things. In this case it's probably a real bug.
I've had these screens back in 2004 when i was still running 1.0.3, which wasn't stable yet.
Your situation was strange cause you had the CPU error a lot on 1.0.7 while most of us didn't have them at all.

Any news on your 'lost' MPC?

laban wrote:

wtf is happening? i got this message and my mpc froze when i was messing with the LFO's..

Is this happened to anyone else?

One more annoying thing i have noticed; the trim-page is weird slow when i'm editing some long samples...

what type ram do you have? This happens to me everytime i load this one kit after having a bunch of stuff loaded. when i load the kit first it never happens. i always just assumed it was a ram issue.

Mr modnaR wrote:i guess if there is already NTFS on the hard disk, the mpc won't even want to format it. can you confirm that Sparq?

if there is NTFS already on the disk you would have to remove that partition and reformat the drive before attempting to format it in the mpc.

what?? i love the timestrech

cowbell wrote:Rob, that CPU screen could mean all type of things. In this case it's probably a real bug.
I've had these screens back in 2004 when i was still running 1.0.3, which wasn't stable yet.
Your situation was strange cause you had the CPU error a lot on 1.0.7 while most of us didn't have them at all.

Any news on your 'lost' MPC?

ah my bad, just a standard mpc 'somethings **** but u gotta work out what it is urself' message. i wish it was just a small prob on my mpc, but honestly it was trashed, so hopefully whoever else is getting that error is not experiencing it as often as i did, and that the issue is hopefully resolvable. as or my mpc, is still being underinvestigation whether or not the delivery company hav lost the mpc when delivering it to the repairs/service place. hopefully its been nicked and ill claim insurance, otherwise its gonna be some hefty charges to look at it and repair, plus its gonna take about 2 months.

anyhow, was reading thru the new manual, can u now pitch a sample up/down without changing how long the sample plays for, i.e a sample that is 2 bars at 100bpm, which u pitch up or down and it stays at a 2 bar length still at 100bpm? if u can thats sick, generally like to timestretch stuff then repitch the same sample as i please, then chop it. shit cant wait to start playing on this os. also im a bit confused about the differences between slicing and patch phrased, now remember i havnt got an mpc to play on to hear the difference, and ive read the manual, but it confused me a bit. now i know how slicing works, but patch phrases i dont quite get. is patch phrasing something along the lines of a method that allows a sample to be separated in to regions so that when u alter the tempo the regions will also auto in tempo?

for people with the cpu error (or peeps who get any issues that other don't, such as slow down in the trim mode or footswith not working)
maybe you could reset your mpc.

hold "erase" button + power up

and don't forget it will reset the settings in the "midi/sync" and in the "other" menu pads.

just an idea... let us now if it changes anything or not.
peace

truvc wrote:for people with the cpu error (or peeps who get any issues that other don't, such as slow down in the trim mode or footswith not working)
maybe you could reset your mpc.

hold "erase" button + power up

and don't forget it will reset the settings in the "midi/sync" and in the "other" menu pads.

just an idea... let us now if it changes anything or not.
peace

just to add to this, when using the erase+power command, that sends the mpc1k back to it's original factory settings.

if u hold the pad when ur previewing a region in slice mode at the same time u switch regions wit da wheel, it makes it easier to hear how each region will work wit da region before it or after it

just somethin i fount out, dont knoe if its a trick or anythin

Hey guys

I installed os 2.10 and i encountered a problem, which I then solved
I'm sharing it here, just in case somebody has the same problem.

I have clicktracks (for the drummer) in every sequence at track64.
They output on 1+2. Everything is stored in the autoload-dir.

After installing 2.10 the V% in the main screen
is zero. No matter what you do, setting it, saving it - it keeps going
back to zero (is this the same as the level bug mentioned before?).
I tried the powerup-and-erase-thingie - didnt work.

Solution:
Set the V% to the correct level and save everything to the root of your CF card.
Next, connect the mpc to your pc and copy everything from the root back to the autoload-dir
(your old 'defective' data) - overwriting everything.

Switch off, switch on, daniel-san - and huray!

cya
H

well i have os 2.1 now for some days and did not notice any big problems even no hardware failure like i´ve seen it above.

what i noticed is that if your working with MPC Pad 187 v1.1 (mac) the new os does not load the programs completely...
and dat sucks for me.
Anyone noticed this one too?

anyway i especially enjoy the slicing function - no more recycle