OS 2.1 Pains - Please read first post.

they haven't lost "sound qualitY"

the issue is that some of the pads are quieter since the velocity curve of 0-100 is different.

just turn up what needs to be turned up. it takes like 3 seconds.

truvc wrote:

yepz wrote:The "Dectect Tempo" suck ass. As the reference manual states on page 67

"Note : Depending on the sample, the DECTECT TEMPO may not be able to detect the the correct tempo" ?

Maybe its just me but i like my functions to work everytime all the time

it is more or less the same on every hardware / software whic has a detect tempo function.

I dont know what hardare or software you are talking about.....but my Xl never lied when it came to "dectecting" a bpm.

This shits me, Akai puts out a new OS and let us do the hard yards in finding all the bugs . Do you know how much Akai saves in doing this ?. In return for saving them time and $$$$, they release to us crappy beta OS systems.

Akai has become the homeless man of the musical equipment !

I noticed when i try to save on my memory card the MP doesnt see the root folder its just blank and it sees only folders i give names to. Any one else have this problem? Also i was messin with the automation and when i had my levels down the sound was still playin!

it's not that i like bugs, but...

personally I would rather be a 'beta tester' with the new OS then sit around with the old one waiting for them to work out more bugs.

As long as they are still dilligently checking the bug reports and doing more testing.

Perhaps the only way for them to handle this a little better would be to realize that the os still has a few major bugs and give it a version designation like 2.01beta. But that would cause people to complain more, I'm sure...

I'm really happy with this new update!

BUT, I have some pains I'd like to share :

Is it me, or does the Q-Link sliders not work when slicing? I would like that.

And with 1.07 I used to loop my beat in the beginning (live, you know?), using a combination of "STOP" and "PLAY", but in 2.10 I can't press "PLAY" while holding the "STOP"-button. It's make it a bit harder to loop...

And I'm still waiting for someone to come up with an easier way of assigning samples to programs/pads when having 200+ samples loaded into the MPC. Hates scrolling all the way to the end!

BESIDES that I'm totally thrilled with 2.10!

When I slice stereo samples and decide to have them chopped into individual samples, the new samples are mono!?! This also happened when I made a patched phrase from a stereo sample... has this happened to anyone else? Am I doing something wrong? Because that kinda kills those features for me...

Kayelel wrote:And I'm still waiting for someone to come up with an easier way of assigning samples to programs/pads when having 200+ samples loaded into the MPC. Hates scrolling all the way to the end!

I was thinking about that the other day when OS2 reared its head: why haven't they added a popup WINDOW button feature that brings up an abbreviated sample-name list like the Mute Track page, where you can jump to different samples and flip through entire 16-sample pages' worth with a click of the wheel? Should be fairly easy to implement and in my opinion fairly intuitive to navigate. Three step process: WINDOW, wheel, pad and it's there to demo or load! An alternative would be a simple 4 or 5 line (dunno how many the MPC screen can fit) scrollable list of everything, but that'd seriously take damn near as long to navigate as the existing system!

Anybody else got a better way of solving this predicament of loading samples so slowly? I'm talking proposals to Akai, here. It's been a problem with MPCs since the beginning, but now that we've got ever-larger space to store **** in it's starting to seriously cramp my style on the regular.

Oh yeah, one funny thing in the manual. (there are others of course haha) I assume it's because they copied it over from the 2500 manual or something. I can't remember the page, but it references 8 individual outs for the MPC, and last I checked, my 1k didn't sprout new ports when I installed OS2!

(I do love the PLAY function from the load screen now! Among many other new features...)

-tank.

astralpirate wrote:When I slice stereo samples and decide to have them chopped into individual samples, the new samples are mono!?! This also happened when I made a patched phrase from a stereo sample... has this happened to anyone else? Am I doing something wrong? Because that kinda kills those features for me...

This does indeed happen when using the auto-slice, regardless of whether you turn it to a PP or a new program/individual samples. I'm not sure why other than L and R channels might not match up and could show artifacts, but that should be a user decision in my opinion, deal with these glitch sounds and keep it stereo or drop it to mono.

Email Akai?

yepz wrote:

truvc wrote:

yepz wrote:The "Dectect Tempo" suck ass. As the reference manual states on page 67

"Note : Depending on the sample, the DECTECT TEMPO may not be able to detect the the correct tempo" ?

Maybe its just me but i like my functions to work everytime all the time

it is more or less the same on every hardware / software whic has a detect tempo function.

I dont know what hardare or software you are talking about.....but my Xl never lied when it came to "dectecting" a bpm.

if you take a badly trimed violin part. it is very likely that even your xl will not detect the tempo. thats what akai meant by "depending on the sample".

yepz wrote:This **** me, Akai puts out a new OS and let us do the hard yards in finding all the bugs . Do you know how much Akai saves in doing this ?. In return for saving them time and $$$$, they release to us crappy beta OS systems.

Akai has become the homeless man of the musical equipment !

so you would rather have 1.07 than the current os ? fine, nobody is forcing you. just go back to os 1.07 (as i did).
thats incredible, people would have killed their mum to get hold of a beta of this os, and now, people complain that akai released it to quick.

Kayelel wrote:I'm really happy with this new update!

And with 1.07 I used to loop my beat in the beginning (live, you know?), using a combination of "STOP" and "PLAY", but in 2.10 I can't press "PLAY" while holding the "STOP"-button. It's make it a bit harder to loop...

YO! me tooo!!! it driving me nutz!!!

Kayelel wrote:And I'm still waiting for someone to come up with an easier way of assigning samples to programs/pads when having 200+ samples loaded into the MPC. Hates scrolling all the way to the end!

BESIDES that I'm totally thrilled with 2.10!

Bluebox, put 4 sounds to one pad each then select the velocity of where u want the sound to trigger. this way you can have 256 sounds in one program.

N17TUG wrote:Bluebox, put 4 sounds to one pad each then select the velocity of where u want the sound to trigger. this way you can have 256 sounds in one program.

i think he means when using the mpc and finding wavs on the hard drive, but yeah bluebox is the way to go!

Is it me, or does the Q-Link sliders not work when slicing? I would like that.

most definitely

but all is well

Antonym wrote:

Is it me, or does the Q-Link sliders not work when slicing? I would like that.

most definitely

but all is well

when trimming, the sliders work but with slicing and adjusting the slice points, the sliders do not work.

Hi all, I'm seeing a problem with 2.10 that I haven't read here. Apologies if this has been raised already.

I'm finding that 2.10 won't output MIDI Program Change messages, whether they are selected in the main track parameter page or written into the step sequencer as an event. In other words, if I set up the MPC to output a Program Change message to a piece of external exquipment, that message is not received by the external equipment.

I reverted back to 1.07 and it will, as before, successfully output program changes which are inserted as events in the step sequencer.

It doesn't seem symptomatic of a hardware defect to me but I can't believe that such a big issue wouldn't have already been reported by someone else or logged as a known issue by Akai.

I'd be very thankful if someone could try to change the program on an external device using their MPC with OS2.10 and confirm whether it works or not.

Yeah, this has been asked, yeah you can transmit program changes, and the answer is here : http://mpc-forums.com/viewtopic.php?t=43199