v4.92 out now

-------------------------------------------------
Bug fixes & Change: Ver4.92 09-Nov-2007
-------------------------------------------------
1. [SEQ EDIT]
Edit:COPY and Edit:MOVE
  
From seq track type=MIDI
To seq track type  =DRUM
It cannot copy and MOVE on this condition.

2. Input thru LEVEL was memorized.
Notes
The value is set to 0.
Please set your value.

3. [MAIN]
Audio track
If it plays from the middle of Bar when tune of Audio sample is not 00:00
The position of the sample to play is different.  

4. MUTE TRACK was changed as follows.    Mute/stop of one-shot sample=IMMEDIATE
 Behavior at the time of MUTE(ing) a long sample on this condition.
 

this explains 4.





i liked it the way it used to be. but it looks like there were some issues jj could not fix...

But why?

The muting was working jst fine, wasnt it?

I can't see why he would want to change it to that ^^^^

CommanderRobot wrote:this explains 4.





i liked it the way it used to be. but it looks like there were some issues jj could not fix...

if i am understanding this correctly, this is terrible.
hopefully you can change the setting, if not that kinda ruins using track mutes for me...

it looks like it's either one or the other--muted samples take polyphony OR muted samples, once muted, don't pick up again after the mute

i really wanted a fix for this mute issue, but it looks like they've jumped in at the deep end here.

mute of one shot samples WASNT working - for those above who asked what was wrong, it was causing my mpc to slow down to a crunching locked up mess each time i used a few oneshots going, and had immediate set to on....and ive been using it for ages, and it went wrong around os485,

there must have been something in how it used all voices in order to pick up any unmuted samples - cos it would use more voices muted, than it did when not muted.

in a way, this isnt really a fix, its a change - one that does ruin some trax i had done back around 484, where recorded mutes are popping breaks in n out over their duration......and in later os's the sequencer nearly breaks apart trying to play them (assigning a voice for all the tracks - only 6/track/voices actually needed - but the bug causing the voice monitor to shoot up to 32 and above) now with this new os aaaarghhhh! they dont come back in....

super irony - cos these trax were the ones that made me notice the bug in the first place...and report it, begging for a fix.....im sure they CAN work around it 'cos it doesnt have any of these problems back in os4.84 - i just dont understand it.

Antonym wrote:it looks like it's either one or the other--muted samples take polyphony OR muted samples, once muted, don't pick up again after the mute

so why in os 4.84 do they NOT take polyphony, AND come back in when unmuted? theyve lost some code i reckon, and cant put it back due to something else.......

go on Ant....ask 'em why, they'll tell u.

i think i know why it was a problem, when oneshots are mono (not poly) they should only ever use up one voice right? here the voice allocation doesnt use just one voice, somehow, jj has it using 2 !? (check it out in 'voice monitor')

so - if say u had a sample triggering once at the start of each loop....that was longer than the length of the sequence loop, (ie: sample=2bars,seq=1 bar) even when the oneshot sample is in mono voice mode, up to 2 voices would be allocated to it (and i think thats the buggy bit).....now, say u have the 'immediate' setting on, as it now allocates 2 voices for every one (in order to run the sample silently to get it back on instantly), then once every loop, up to four voices are being used at any retrigger moment. so say u have a few tracks, a few samples (oneshot/mono) triggering a few times - in each case where a sample retriggers again, its clogging up loads of extra voice operators. dont ask me why - thats just the way it seems to be from messing about in this area.

there needs to be a fix this random panning that i've noticed since i changed over to JJ. All these updates are great but it doesn't really help when you're trying to record and notes randomnly pan.

eye_pee wrote:there needs to be a fix this random panning that i've noticed since i changed over to JJ. All these updates are great but it doesn't really help when you're trying to record and notes randomnly pan.

i think this predates jj though, im sure it was a very early grievance for both 1k and 25k owners

if jj nailed it that would be some ill troubleshootin

i think this predates jj though, im sure it was a very early grievance for both 1k and 25k owners

if jj nailed it that would be some ill troubleshootin

nah, this problem isn't on Akai's OS. I would go back to it if it wasn't for the pad sensitivity upgrade

arebee wrote:i think i know why it was a problem, when oneshots are mono (not poly) they should only ever use up one voice right? here the voice allocation doesnt use just one voice, somehow, jj has it using 2 !? (check it out in 'voice monitor')

I think 2 voices are used for stereo samples.
I see the problem with the retriggering you describe though.

And, yeah, the panning stuff needs to be fixed, most def.

earwolf wrote:

eye_pee wrote:there needs to be a fix this random panning that i've noticed since i changed over to JJ. All these updates are great but it doesn't really help when you're trying to record and notes randomnly pan.

i think this predates jj though, im sure it was a very early grievance for both 1k and 25k owners

if jj nailed it that would be some ill troubleshootin

For real? Notes panning by themselves?

Yep. Very rare in my opinion, but happens.