os 4.28

Bug fixes: New OS Ver4.28 04-Jan-2007
--------------------------------------
[GRID]
　　It will crash, if a sequence is changed.

Change:
The audio track changed into eight tracks.
Old:61-64 4tracks
New:57-64 8tracks

グリッドの画面でシーケンスを変更するとハングする
メイン画面で音が出なくなる

変更
オーディオトラックを４トラックから８トラックに変更しました。(57-64)

updates..inbetween updates... damn.

Rise of EPC wrote:updates..inbetween updates... damn.

hahahahh

Too fast for us...

Great isn't it! That was the bug I reported. They sent me an email stating that they would do an update with a fix for this before 4.30 & here it is.!

They are hustling on that end. This also makes me wonder, where are they going with this thing? How much more can they do? What does the machine have left in it before it starts to spit up (Breaks Down) on us. So far, everything that they have done has been very useful. If you are a midi guru, they have you covered now. The sample junkies are well taken care of with the newer OS.

I mean really, what is left? Yes they can make some functions a bit more easier to do & what have you. But I'm talking about new stuff. Any ideas??? Just a thought.

Well the timestretch algorithm is flawed but they even made a work-around for that.

I'm talking about the creature comfort type of stuff. I mean some really new & functional features.

Well the timestretch algorithm is flawed but they even made a work-around for that.

could you explain both the flaw and the work around? i don't follow.

From my experience, the 1k does not read the bpm correctly. Even in a 4 bar sample. Ie, flaw. The JJ OS work-around lets you put in the correct bpm. Go to Trim>Edit>Timestretch>F2-Tempo & there you will see the difference between JJ & Akai. Akai did not have a tempo detect manual option for tempo detect in the time stretch area like this.

Anyways, if you put your time sig in (Which I think is an error. It shows, in the manual mode 1/4, 1/8, 1/16, which are not time sigs but note values, you can get a decent timestretch. It works pretty good the manual way.

Either way, this is the work-around I'm refering to.

oh i got you now.

How about the click at the end of the sample in timestretch, wonder when that will get fixed...