By seatown350
Wed Apr 26, 2006 12:06 am
im jus wouderin , what new things you think there goin to add on the New Os ?
By distortedtekno
Wed Apr 26, 2006 2:07 am
Antonym wrote:bug fixes, nothing else. that's all i want/expect
definitely bug fixes...
but grid edit would be really cool to create intricate rhythms more efficiently.
By punchdrunk
Wed Apr 26, 2006 4:21 am
i would never expect another feature from akai ever again.
unless you call bug fixes another feature...
honestly that last update was crazy.
akai went above and beyond the call of duty on that one.
asking for anything more than bug fixes at this point is just
being greedy as hell...
unless you call bug fixes another feature...
honestly that last update was crazy.
akai went above and beyond the call of duty on that one.
asking for anything more than bug fixes at this point is just
being greedy as hell...
http://www.myspace.com/sixlsixlsix
yeah, i'm bored.
yeah, i'm bored.
By ONE
Wed Apr 26, 2006 4:25 am
only thing I want in the new OS is the abiliy to input how many bars the sample is in timestretch and detecting tempo
By distortedtekno
Wed Apr 26, 2006 4:30 am
punchdrunk wrote:i would never expect another feature from akai ever again.
unless you call bug fixes another feature...
honestly that last update was crazy.
akai went above and beyond the call of duty on that one.
asking for anything more than bug fixes at this point is just
being greedy as hell...
yo, i hear ya. i'm not counting on anything more than bugfixes. having grid edit is wishful thinking on my part. but i'm sure it can easily be implemented.
By naugie
Wed Apr 26, 2006 8:00 am
u know what i want? i want a good explanation behind the detect tempo funtion. i notice through mathimatical steps (yes i took manual steps to detect tempo) that the detect tempo isnt always accurate. if its a bug that i caught, ill like to give it a name. ill call it naugtemps, naug for naugie. temps for tempo. and if its not a bug then im a retard and would like to know why it generates wrong numbers on the manual
maybe im asking for an faq cause that be sick, maybe if the community put one together. an updated one
maybe im asking for an faq cause that be sick, maybe if the community put one together. an updated one
By Balls
Wed Apr 26, 2006 8:41 am
naugie wrote:u know what i want? i want a good explanation behind the detect tempo funtion. i notice through mathimatical steps (yes i took manual steps to detect tempo) that the detect tempo isnt always accurate. if its a bug that i caught, ill like to give it a name. ill call it naugtemps, naug for naugie. temps for tempo. and if its not a bug then im a retard and would like to know why it generates wrong numbers on the manual
maybe im asking for an faq cause that be sick, maybe if the community put one together. an updated one
The reason why it fails on detecting the right BPM is that probably that you're trying to find it on a non-percussive sample (ie. strings or something). Of course it couldn't work in anyway when you're not telling it how many bars the sample is... The detect tempo function only works with percussion loops in 1 , 2 , 4 , 8 , 16 , 32 (and so on) bars. That's common sense in my opinion. It's not a bug. And i don't really see the big issue. I don't find it hard trying and listening, until I get it right. It trains your ear plus giving you a better sense of how much difference there is between 1 and a 100 BPM.
By Balls
Wed Apr 26, 2006 8:42 am
rare wrote:long samples stop!! (i know...chop)
track mute recording
There's a trick to this one... Just hit STOP 3 times fast. Everything will stop then.
By soyo
Wed Apr 26, 2006 10:21 am
PLEASE FIX THE HDD BUGS!!!PLEASE FIX THE HDD BUGS!!!PLEASE FIX THE HDD BUGS!!!
thank you
thank you
By naugie
Wed Apr 26, 2006 2:39 pm
Balls wrote:naugie wrote:u know what i want? i want a good explanation behind the detect tempo funtion. i notice through mathimatical steps (yes i took manual steps to detect tempo) that the detect tempo isnt always accurate. if its a bug that i caught, ill like to give it a name. ill call it naugtemps, naug for naugie. temps for tempo. and if its not a bug then im a retard and would like to know why it generates wrong numbers on the manual
maybe im asking for an faq cause that be sick, maybe if the community put one together. an updated one
The reason why it fails on detecting the right BPM is that probably that you're trying to find it on a non-percussive sample (ie. strings or something). Of course it couldn't work in anyway when you're not telling it how many bars the sample is... The detect tempo function only works with percussion loops in 1 , 2 , 4 , 8 , 16 , 32 (and so on) bars. That's common sense in my opinion. It's not a bug. And i don't really see the big issue. I don't find it hard trying and listening, until I get it right. It trains your ear plus giving you a better sense of how much difference there is between 1 and a 100 BPM.
ohh snaps thanks mang i never thought of it like that but it makes compelte sense though. ya im still learning sampling theorems. im just groping the surface of sampling. ima make a post about this detect tempo on a later date i have question floating in my head i just dont know how to ask it yet. thanks though