OS 2x - JOYS AND PAINS thread PT1

I think that the level bug should have it's own thread. This is a big problem in my opinion.

And it's NOT just a bug with Bluebox Pgms..

Akai need to become aware of this!

What do you say mods?

sumedho wrote:The level bug seems to occur with pgms made using Bluebox. My pgms that I made using the mpc itself work fine with the new version. Maybe if someone else can check this out as well.

i don't think it has to do with bluebox, i never uses it and I get the level differences.
i did not use the mixer for level either.

so it seems that the difference can happen at every place levels can be set (porgram level, mixer level, and velocity of recorded pads in the track).

as people stated, it *seems* that the sounds with lots of high frequencies (hihats, congas) became much louder than the rest.

i am not sure if it is a good thing or bad thing yet. maybe there was a level issue on the previous os, and the programmers fixed it...

When things will have settled down, it would be real nice to know akai opinion about that.
I they think it is an issue and plan to change it, i'll stay with os1.07 until a next release.
If they don't plan to change it, i'll spend the time to modify all my programms to fit v2.10.

Anyway, both case i am happy, just i don't want to re-level all my programms now, and then have to do this again at the next update.

----
btw maybe a sticky like "upgrade for dummies" is needed ? anyway Sparq and the other mods, thanks for all the hard work

Balls wrote:I think that the level bug should have it's own thread. This is a big problem in my opinion.

And it's NOT just a bug with Bluebox Pgms..

Akai need to become aware of this!

What do you say mods?

akai is aware of it, as Sparq stated earlier.

Balls, i perfectly understand why you seem a bit upset about the level difference, but...
please understand that the programmers did such a big work, and also were blatantly in a hurry to release, so it is unfortunate, but perfectly normal that there are small glitches.
mpc1k with os2 is like a new machine, and this is an early os, which will evolve in the future.

also i would not call this a bug, as it might be a bug fix (see my post above). the user can just tell its experience, only the programmer can tell
what is a bug and what is not. (and calling things "bugs" is the best way to piss off programmers and slow things down. i know, i am a programmer )

as i said, the workaround i will use is to revert to os1.07 and wait for akai opinion.

peace

i got the same problem as adl1. ive followed the instructions carefully and when the new os installs the screen is blank. i really wanna use this now but im gettin frustated,,,can ne1 help

oh and i id thought id mention that it is def installed on there cos when i triued insytalling again it said the current os is 2.10

thanx

Davaro wrote:i got the same problem as adl1. ive followed the instructions carefully and when the new os installs the screen is blank. i really wanna use this now but im gettin frustated,,,can ne1 help

Turning the MPC on while holding ERASE solved his problem.
Did you try that?

jus tried dat thanx a lot it has worked

A number of people seem to have this issue. For some reason installing 2.1 isn't always working and the FLASH needs to be initialized.
Perhaps Akai should put that power-up + ERASE button solution in their "How to update" instructions.

Just got home and check the thread to see the new OS. Man yall should be praising Sparq cuz he definitiely been proven right all along and the mad suckers bitiing, complaining, and cracking up should ........................................









































































go make a beat and learn a valuable lesson on growing up.


Peace I gotta go download the OS and the manual. he He

Balls wrote:I think that the level bug should have it's own thread. This is a big problem in my opinion.

And it's NOT just a bug with Bluebox Pgms..

Akai need to become aware of this!

What do you say mods?

yes. I had one but it was closed

hutchthemack wrote:dont know if this is me but you cant hold tap tempo and use your midi keyz at least it aint working for me it did in 1.07 but im still happy

any body else have this issue???????

yeah, me to.

And another thing i don't understand.. trackvelocity, it seems that turning it above 100 % (->200%) doesn't affect the actua volume of the track at all.. why did they make it possible to turn it up to 200% if it doesn't erally turn up the track??

Balls wrote:yeah, me to.

And another thing i don't understand.. trackvelocity, it seems that turning it above 100 % (->200%) doesn't affect the actua volume of the track at all.. why did they make it possible to turn it up to 200% if it doesn't erally turn up the track??

Because I would assume all your individual sequencer notes are at full velocity already (127), so doubling track velocity won't do anything - you can't get a higher velocity than 127.

On the other hand, if you have sequence notes at small velocity, say 30, then turning track velocity to double (200%) will indeed double the individual note velocities to 60, and hence increase the loudness of these notes.

It's the same on the XL, it's not a bug.

MPC 1000 w/ 2.01 = MPC 1000 on Steroids.

Good thing this is not against the law

man im lovin this ish man bugs or not btw what is a lfo im only 1/2 thru the manual