5.04 is out!!!

Yes Akai's extended period of NO updates to a buggy OS is FAR superior.

Far superior? I would leave the deifinition to each user. For me, I haven't encounter the buggy Akai OS you are talking about (if you are talking about OS 1.22).

But please feel free to revist this topic again. What bugs are you talking about?

The JJ OS adds more features, but is not more stable..at least not yet. Don't be suprised to get another OS update this week fixing more bugs.....

jahrome wrote:

Yes Akai's extended period of NO updates to a buggy OS is FAR superior.

Far superior? I would leave the deifinition to each user. For me, I haven't encounter the buggy Akai OS you are talking about (if you are talking about OS 1.22).

But please feel free to revist this topic again. What bugs are you talking about?

The JJ OS adds more features, but is not more stable..at least not yet. Don't be suprised to get another OS update this week fixing more bugs.....

Chop Shop creating mono slices is definitely a major bug and a showstopper for my workflow. Glad JJ managed to fix that issue!

S.

Chop Shop creating mono slices is definitely a major bug and a showstopper for my workflow. Glad JJ managed to fix that issue!

If you read the manual (something I don't do ), you would know that it wasn't a bug but a choice Akai made at the time the MPC was released....l

jahrome wrote:

Chop Shop creating mono slices is definitely a major bug and a showstopper for my workflow. Glad JJ managed to fix that issue!

If you read the manual (something I don't do ), you would know that it wasn't a bug but a choice Akai made at the time the MPC was released....l

I read the manual but fail to see the point for this behaviour. And even if this might have been due to time limitations before releasing the 25oo, Akai should have been able to fix it by now.

I mean seriously, chop shop ilooked great on paper but if you can only produce mono slices or if you have to manually extract slice for slice it's a bug to me.

S.

Can i ask who is this JJ guy?

I mean, could it be that JJ is from Akai/Numark. This could be a ploy for making side cash on Akai's behalf. This way they don't have to do the updates for free, and purposely p*ss users off for the slow offical OS releases.

Correct me if you feel i'm wrong or totally chattin sh*t. Just pointing put another side, thats all.

Sonny Chiba wrote:I mean seriously, chop shop ilooked great on paper but if you can only produce mono slices or if you have to manually extract slice for slice it's a bug to me.

you gotta be the kidding me! i can't believe how lazy some of you people are.

i've been using mpc's for 6 years, and before that i had a crappy yamaha sampler. i've never let the machine chop anything for me, i use my ears. 90% of people on this board are lookin for easy ways out of everything. they download samples from the internet and wonder how to get them on their mpc, then they want the mpc to create their programs automatically, chop all of their sounds... what's next, you going to hit a button and it will automatically sequence up your beat? no wait, a button would be too hard, maybe they should just add a sensor that you can wave your hand over and everything will be taken care of.

mono chop shop was not a bug, it was a choice, and it probably had something to do with the fact that the left and right channels of a stereo sample can have completely different dynamics which could cause the algorithm that calculates the chops to come up with some weird results. either way, they didn't think it was necessary to add but maybe they will now that they see everyone needs everything done for them.

"you gotta be the kidding me! i can't believe how lazy some of you people are. "

HAHAHAHAHAHAHAAAAAA
You tell em Mike! I've been saying the same thing for years! Folks wanna sound like Dilla/Premo/Pete Rock right out the box. Anything that may require just a little work needs a dedicated button or an operating system upgrade! haha

Mike Feedback wrote:

Sonny Chiba wrote:I mean seriously, chop shop ilooked great on paper but if you can only produce mono slices or if you have to manually extract slice for slice it's a bug to me.

you gotta be the kidding me! i can't believe how lazy some of you people are.

i've been using mpc's for 6 years, and before that i had a crappy yamaha sampler. i've never let the machine chop anything for me, i use my ears. 90% of people on this board are lookin for easy ways out of everything. they download samples from the internet and wonder how to get them on their mpc, then they want the mpc to create their programs automatically, chop all of their sounds... what's next, you going to hit a button and it will automatically sequence up your beat? no wait, a button would be too hard, maybe they should just add a sensor that you can wave your hand over and everything will be taken care of.

mono chop shop was not a bug, it was a choice, and it probably had something to do with the fact that the left and right channels of a stereo sample can have completely different dynamics which could cause the algorithm that calculates the chops to come up with some weird results. either way, they didn't think it was necessary to add but maybe they will now that they see everyone needs everything done for them.

I am not using chop shop to automatically create slices (which doesn't work anyway if you use material with little or no transients), but to me it's much easier to manually create them on the fly. Since I'm using a lot of slices (I like to divide a phrase into up to 60 chops), it's cool if the machine is doing what it can do best and leaves me time for the creative process. In my opinion there's nothing artistic about pressing "Edit", "Extract" and then entering a new name for each file x-amount of times in a row.

S

mono chop shop was not a bug, it was a choice, and it probably had something to do with the fact that the left and right channels of a stereo sample can have completely different dynamics which could cause the algorithm that calculates the chops to come up with some weird results. either way, they didn't think it was necessary to add but maybe they will now that they see everyone needs everything done for them.

i got to say that's pretty weak logic there mikey, taking into account the 1000.

especially because there was no autochop on the 1000 and it still chopped in mono.

not a "bug" probably just lazy ass coding.
and this comes from me who once said that stereo sampling wouldn't be that big a deal because "how much could you really be missing when you could just chop both sides" etc etc but i would never go back to mono chops unless the sample is mono to begin with.

plus whoever was bugging out there a second ago (i forget) about blah blah blah use your ears blah blah needs to realise that the autochop function gets used maybe 1 every 10 chops. anyone using autochop for every chop they make is going to be taking a LOT more time than if they just did it with their eyes, ears and fingers. it's no recycle, but it's useful when say there are 4 obvious transients that it can detect. even then it's probably faster just to divide 2 by 2 by 2 and so on.

90% of people on this board are lookin for easy ways out of everything.

a lot of people look for the easy way out, a lot of people look for shortcuts, and a lot of people look for more effective, quick and accurate ways to do the legwork that once was required. does this make the latter lazy, or industrious?

does using dreamweaver to code a webpage instead of raw html lazy? how about if you have been using html for years and suddenly get dreamweaver?

hmmm.

I use the chop-shop to get rough hitpoints to then move to the exact points I want by zooming fully in and also using divide and combine. Without chop-shop I'd still end up with exactly the same chops, but it would take longer to do.

I'm sure 99% of us do the same(?), so we're still ending up with the chops we'd have if chop-shop didn't exist. Therefore, it's not about lazyness. The point is that it's quicker

So finally, I complete exams and have more time to actually create with my MPC instead of just talking about it. So I load up the latest JJ OS...what is it 4.04 now. So I sample a piano loop so I can play over top of a drum loop that I already have sequenced. I go into the Trim screen where I can still play the sequence at the same time adjust the start/end points of the sample. However, when I hit the pads to play the sample (while still in the TRIM Menu), it throws off the timing of the drum track. The drum tracks pauses...slow downs/speed up. Of course I can just workaround it and don't do that anymore

JJ...great job with the OS. I found a bug within 5 ninutes of using this OS.

Antonym wrote:i got to say that's pretty weak logic there mikey, taking into account the 1000.

especially because there was no autochop on the 1000 and it still chopped in mono.

not a "bug" probably just lazy ass coding.

don't forget akai is a business. you might think the coder was lazy, but there's other factors that could have come into play. (p.s. even if being lazy was the reason, my comment that it was a choice rather than a bug is still correct. laziness is a choice, right?)

perhaps there was a deadline and the coder didn't have time to look into making chop shop stereo. or maybe the coder gave his boss an estimated amount of hours it would take to make it stereo, and then another estimated amount of hours it would take to make it mono and they decided they would go for mono.

i'm a programmer, and i've definitely had people ask me to take care of something but when i tell them how long it would take, they compromise for something a little less complex but can be done in less time.

and it's funny you bring up dreamweaver because i actually use that at work. i do everything in coder view rather than design view though. wouldn't be able to do the things i have to do in design view.

and it's funny you bring up dreamweaver because i actually use that at work. i do everything in coder view rather than design view though. wouldn't be able to do the things i have to do in design view.

HAHAH!
same here actually
td height/width n sht

they compromise for something a little less complex but can be done in less time.

agreed. we've all seen that.

jahrome wrote: However, when I hit the pads to play the sample (while still in the TRIM Menu), it throws off the timing of the drum track. The drum tracks pauses...slow downs/speed up.

Yeah I've noticed this. Although it's been happeneing for as long as I can remember. I thought the Akai OS was the same too, although I wouldn't swear to it.

Submit the bug to JJ dude. He's like Bob The Builder, he can fix it.

Rozzer wrote:

jahrome wrote: However, when I hit the pads to play the sample (while still in the TRIM Menu), it throws off the timing of the drum track. The drum tracks pauses...slow downs/speed up.

Yeah I've noticed this. Although it's been happeneing for as long as I can remember. I thought the Akai OS was the same too, although I wouldn't swear to it.

Submit the bug to JJ dude. He's like Bob The Builder, he can fix it.

the akai OS does that as well. also does it when you're adjusting start and end points in the trim menu. i don't recall if the 2000xl even allowed you to go into the trim menu while a sequence was playing. didn't it stop the sequence when you would go into trim mode? anyone?

on a side note i installed the JJ OS about a 2 hours ago and have been messing around with it.